The dispute file: your documentation story
Rung 10 of 10 · Power-ups + stakes
1 · Learn the move · Power-ups + stakes
When a job goes sideways, you don't need more paper — you need the paper you have arranged into a story a stranger can follow. Tell the AI the stakes: what's in dispute, how many dollars, and that every claim must trace to a dated document. Make it think step by step through the timeline and flag every gap as [NEEDS] instead of papering over it. The gaps it finds now are the holes the other side finds later. The AI organizes the evidence; a construction attorney runs the fight.
You are a claims-prep analyst. Stakes: a client is disputing [$amount] of my invoices. Think step by step: build a dated timeline from my logs, photos, COs, and emails, tie each disputed dollar to its documents, and flag every gap as [NEEDS: ...]. Invent nothing. End with the 3 weakest points in my file. This organizes facts for my construction attorney — it is not legal advice. [documents]
2 · Your turn. You write the prompt
The Hendricks job ended ugly: the client is refusing the final $18,400 invoice, claiming the rot repair was never approved and the schedule slipped from your side. You have four months of daily logs, 61 photos, six change orders, and the email thread. Write a prompt that assembles it into a documentation story.
Remember: the AI sees only your prompt, not this page. If the situation isn't in your prompt, it doesn't exist.
Optional. These shape the output when you run your prompt below, not your score.