Vehicle Property Damage Claim Checklist

Maintained by Property Damage King, this public checklist helps vehicle owners and law-firm operators organize common property-damage claim documents after a crash or covered vehicle loss.

This project is intentionally generic and public-safe. It is not legal advice, does not create an attorney-client relationship, and does not include private client data, claim numbers, VINs, internal workflows, credentials, or jurisdiction-specific promises.

What is included

The checklist groups common items into four categories:

1. Incident and vehicle evidence
2. Insurance and claim communications
3. Repair, total-loss, and diminished-value proof
4. Out-of-pocket losses

Each item includes:

• id
• label
• description
• priority: high, medium, or low

Quick start

Run the sample packet summary with Node 18+:

node summary.mjs examples/sample-property-damage-packet.json

Expected output shape:

Vehicle Property Damage Claim Checklist Summary: Sample Vehicle Property Damage Packet
5/15 complete (33%)

High-priority missing items:
- Insurance declarations pages (Insurance and claim communications)
- Insurance letters, emails, and texts (Insurance and claim communications)
- Total-loss valuation report (Repair, total-loss, and diminished-value proof)

Use the checklist manually

The JSON checklist lives at:

checklists/vehicle-property-damage-claim-checklist.json

A vehicle owner or operator can use it without code:

1. Review each category.
2. Mark items already collected.
3. Focus first on missing high priority items.
4. Keep original documents and photos backed up securely.
5. Share documents only through secure channels approved by the law firm or claim professional.
6. Ask an attorney or qualified professional before signing releases, accepting a valuation, or giving recorded statements.

Safety notes

• Do not upload private records, VINs, claim numbers, license plates, photos, insurer letters, or client details to a public repository.
• Do not paste private insurance communications into GitHub issues.
• This checklist is an organization aid only. It is not legal advice and should be adapted to the facts, jurisdiction, insurance policy, and attorney guidance for each matter.

License

MIT