Demand Letter Skeleton Builder
Provide the incident facts, damages, liability theory, and recipient. Get back a structural outline an attorney can use as a starting point.
Outline only. Does not draft demand letter prose, compute settlement values, or make legal arguments. The final letter must be drafted and sent by a licensed attorney.
Demand outlines work from facts, damages, and theories — not party identities. Use [CLIENT], [CARRIER], [OPPOSING PARTY] and find-and-replace later.
Output will appear here once the tool runs.
Questions people ask first
What does this tool give me?
A structural outline of a demand letter — facts, damages, liability theory, demand, deadline, signature block — with the right sections in the right order and the kinds of language an attorney expects to see in each. It is a starting skeleton, not a finished letter.
Will it write the actual demand language for me?
It drafts placeholder language for each section so you can see what belongs where, but you'll rewrite most of it. The point is to remove the “staring at a blank page” problem — not to produce a letter you sign and send.
What inputs do I need?
The incident facts (what happened, when, where), the damages (medical bills, lost wages, property damage — concrete numbers if you have them), the liability theory (negligence, breach of contract, statutory), and the recipient (insurer, opposing counsel, defendant directly).
Should I paste actual case facts in?
Use the Redactor first. Replace client names and identifying details with placeholders before pasting. The skeleton-building logic runs on the structural facts (the “what happened”), not on identities — placeholders preserve the structure.
Will this work for my practice area?
It's calibrated for personal injury, breach of contract, and employment demands. For specialised practice areas (construction defect, professional malpractice, securities, etc.) the skeleton will be roughly right but you'll need to adapt the standard sections.