How to Write a Demand Letter to a Contractor
This guide addresses the specific U.S. task “how to write a demand letter to a contractor”. It is organized as a contractor demand workflow, not as a generic legal-writing checklist. The objective is to separate the original scope from approved changes, connect payment to milestones and acceptance, document defects or incomplete work, reconcile invoices and credits, and make a demand that matches the actual construction or services record. Rules, deadlines, forms, and remedies vary by state, court, locality, contract, and facts, so the relevant official source must be checked before action.
1. Original scope
At the Original scope stage, the work should advance the specific contractor demand objective rather than repeat general advice. For “how to write a demand letter to a contractor”, use this stage to test the factual and procedural assumptions that matter to the requested result. The core mission is to separate the original scope from approved changes, connect payment to milestones and acceptance, document defects or incomplete work, reconcile invoices and credits, and make a demand that matches the actual construction or services record. Record what is confirmed, what remains uncertain, and which jurisdiction-specific source resolves each uncertainty.
The decision questions for Original scope include what work was originally promised, which changes were authorized and by whom, what milestone triggered payment, what work remains incomplete or defective, how credits and retainage affect the balance, what notice procedure the contract requires, and what state-specific remedies may exist. Answer them in the context of the actual parties, forum, transaction, service history, and requested outcome. If the answer depends on state or local law, identify that dependency explicitly instead of presenting a nationwide rule. If the record points in two directions, preserve the conflict and explain what additional document or official source is needed.
2. Change orders
Build this part of the file from the signed proposal or contract, scope and specifications, drawings where relevant, change orders, written approvals, milestone schedule, site or project communications, photographs, inspection notes, punch lists, invoices, payment records, and notices concerning delay or defective work. Organize the material chronologically and connect each material statement to a source record. Where a number is important, reconcile the arithmetic and preserve the underlying ledger, invoice, receipt, contract term, docket entry, photograph, or correspondence. Do not convert a missing document into an assumed fact merely to make the draft read more smoothly.
The principal controls at this stage respond to these risks: treating informal discussion as an approved change order, double-counting disputed work, ignoring contractual notice clauses, confusing delay with defective performance, demanding payment for an unachieved milestone, or threatening lien or statutory remedies without checking local prerequisites and deadlines. Use neutral language, distinguish contractual requirements from statutory requirements, and distinguish a practical response date from a legally prescribed deadline. Before sending or filing anything, verify the current rule, form, fee, service method, address, and any precondition that can affect enforceability or admissibility.
3. Milestone status
The decision questions for Milestone status include what work was originally promised, which changes were authorized and by whom, what milestone triggered payment, what work remains incomplete or defective, how credits and retainage affect the balance, what notice procedure the contract requires, and what state-specific remedies may exist. Answer them in the context of the actual parties, forum, transaction, service history, and requested outcome. If the answer depends on state or local law, identify that dependency explicitly instead of presenting a nationwide rule. If the record points in two directions, preserve the conflict and explain what additional document or official source is needed.
The deliverable from Milestone status should contribute to a project-specific demand with a scope map, approved-variation log, milestone evidence, defect or completion record, reconciled payment ledger, contract-based notice language, requested cure or payment, and documented delivery. A reviewer should be able to trace the conclusion back to the evidence and the governing source without guessing. For this topic, the relevant authority starts with the signed construction or services agreement, incorporated scope documents, change-order and notice clauses, applicable state payment or construction statutes, licensing rules where relevant, and current court or agency guidance for the jurisdiction. Keep a note of the source URL, effective or access date, and the particular proposition checked so later review can detect a change in law or procedure.
4. Completion evidence
The principal controls at this stage respond to these risks: treating informal discussion as an approved change order, double-counting disputed work, ignoring contractual notice clauses, confusing delay with defective performance, demanding payment for an unachieved milestone, or threatening lien or statutory remedies without checking local prerequisites and deadlines. Use neutral language, distinguish contractual requirements from statutory requirements, and distinguish a practical response date from a legally prescribed deadline. Before sending or filing anything, verify the current rule, form, fee, service method, address, and any precondition that can affect enforceability or admissibility.
At the Completion evidence stage, the work should advance the specific contractor demand objective rather than repeat general advice. For “how to write a demand letter to a contractor”, use this stage to test the factual and procedural assumptions that matter to the requested result. The core mission is to separate the original scope from approved changes, connect payment to milestones and acceptance, document defects or incomplete work, reconcile invoices and credits, and make a demand that matches the actual construction or services record. Record what is confirmed, what remains uncertain, and which jurisdiction-specific source resolves each uncertainty.
5. Defect record
The deliverable from Defect record should contribute to a project-specific demand with a scope map, approved-variation log, milestone evidence, defect or completion record, reconciled payment ledger, contract-based notice language, requested cure or payment, and documented delivery. A reviewer should be able to trace the conclusion back to the evidence and the governing source without guessing. For this topic, the relevant authority starts with the signed construction or services agreement, incorporated scope documents, change-order and notice clauses, applicable state payment or construction statutes, licensing rules where relevant, and current court or agency guidance for the jurisdiction. Keep a note of the source URL, effective or access date, and the particular proposition checked so later review can detect a change in law or procedure.
Build this part of the file from the signed proposal or contract, scope and specifications, drawings where relevant, change orders, written approvals, milestone schedule, site or project communications, photographs, inspection notes, punch lists, invoices, payment records, and notices concerning delay or defective work. Organize the material chronologically and connect each material statement to a source record. Where a number is important, reconcile the arithmetic and preserve the underlying ledger, invoice, receipt, contract term, docket entry, photograph, or correspondence. Do not convert a missing document into an assumed fact merely to make the draft read more smoothly.
6. Invoice ledger
At the Invoice ledger stage, the work should advance the specific contractor demand objective rather than repeat general advice. For “how to write a demand letter to a contractor”, use this stage to test the factual and procedural assumptions that matter to the requested result. The core mission is to separate the original scope from approved changes, connect payment to milestones and acceptance, document defects or incomplete work, reconcile invoices and credits, and make a demand that matches the actual construction or services record. Record what is confirmed, what remains uncertain, and which jurisdiction-specific source resolves each uncertainty.
The decision questions for Invoice ledger include what work was originally promised, which changes were authorized and by whom, what milestone triggered payment, what work remains incomplete or defective, how credits and retainage affect the balance, what notice procedure the contract requires, and what state-specific remedies may exist. Answer them in the context of the actual parties, forum, transaction, service history, and requested outcome. If the answer depends on state or local law, identify that dependency explicitly instead of presenting a nationwide rule. If the record points in two directions, preserve the conflict and explain what additional document or official source is needed.
7. Contract notices
Build this part of the file from the signed proposal or contract, scope and specifications, drawings where relevant, change orders, written approvals, milestone schedule, site or project communications, photographs, inspection notes, punch lists, invoices, payment records, and notices concerning delay or defective work. Organize the material chronologically and connect each material statement to a source record. Where a number is important, reconcile the arithmetic and preserve the underlying ledger, invoice, receipt, contract term, docket entry, photograph, or correspondence. Do not convert a missing document into an assumed fact merely to make the draft read more smoothly.
The principal controls at this stage respond to these risks: treating informal discussion as an approved change order, double-counting disputed work, ignoring contractual notice clauses, confusing delay with defective performance, demanding payment for an unachieved milestone, or threatening lien or statutory remedies without checking local prerequisites and deadlines. Use neutral language, distinguish contractual requirements from statutory requirements, and distinguish a practical response date from a legally prescribed deadline. Before sending or filing anything, verify the current rule, form, fee, service method, address, and any precondition that can affect enforceability or admissibility.
8. Requested cure
The decision questions for Requested cure include what work was originally promised, which changes were authorized and by whom, what milestone triggered payment, what work remains incomplete or defective, how credits and retainage affect the balance, what notice procedure the contract requires, and what state-specific remedies may exist. Answer them in the context of the actual parties, forum, transaction, service history, and requested outcome. If the answer depends on state or local law, identify that dependency explicitly instead of presenting a nationwide rule. If the record points in two directions, preserve the conflict and explain what additional document or official source is needed.
The deliverable from Requested cure should contribute to a project-specific demand with a scope map, approved-variation log, milestone evidence, defect or completion record, reconciled payment ledger, contract-based notice language, requested cure or payment, and documented delivery. A reviewer should be able to trace the conclusion back to the evidence and the governing source without guessing. For this topic, the relevant authority starts with the signed construction or services agreement, incorporated scope documents, change-order and notice clauses, applicable state payment or construction statutes, licensing rules where relevant, and current court or agency guidance for the jurisdiction. Keep a note of the source URL, effective or access date, and the particular proposition checked so later review can detect a change in law or procedure.
9. State-specific remedies
The principal controls at this stage respond to these risks: treating informal discussion as an approved change order, double-counting disputed work, ignoring contractual notice clauses, confusing delay with defective performance, demanding payment for an unachieved milestone, or threatening lien or statutory remedies without checking local prerequisites and deadlines. Use neutral language, distinguish contractual requirements from statutory requirements, and distinguish a practical response date from a legally prescribed deadline. Before sending or filing anything, verify the current rule, form, fee, service method, address, and any precondition that can affect enforceability or admissibility.
At the State-specific remedies stage, the work should advance the specific contractor demand objective rather than repeat general advice. For “how to write a demand letter to a contractor”, use this stage to test the factual and procedural assumptions that matter to the requested result. The core mission is to separate the original scope from approved changes, connect payment to milestones and acceptance, document defects or incomplete work, reconcile invoices and credits, and make a demand that matches the actual construction or services record. Record what is confirmed, what remains uncertain, and which jurisdiction-specific source resolves each uncertainty.
10. Delivery and reservation
The deliverable from Delivery and reservation should contribute to a project-specific demand with a scope map, approved-variation log, milestone evidence, defect or completion record, reconciled payment ledger, contract-based notice language, requested cure or payment, and documented delivery. A reviewer should be able to trace the conclusion back to the evidence and the governing source without guessing. For this topic, the relevant authority starts with the signed construction or services agreement, incorporated scope documents, change-order and notice clauses, applicable state payment or construction statutes, licensing rules where relevant, and current court or agency guidance for the jurisdiction. Keep a note of the source URL, effective or access date, and the particular proposition checked so later review can detect a change in law or procedure.
Build this part of the file from the signed proposal or contract, scope and specifications, drawings where relevant, change orders, written approvals, milestone schedule, site or project communications, photographs, inspection notes, punch lists, invoices, payment records, and notices concerning delay or defective work. Organize the material chronologically and connect each material statement to a source record. Where a number is important, reconcile the arithmetic and preserve the underlying ledger, invoice, receipt, contract term, docket entry, photograph, or correspondence. Do not convert a missing document into an assumed fact merely to make the draft read more smoothly.
Final quality check before use
- confirm the correct state, court, agency, or contractual forum.
- confirm every deadline from the served paper, governing rule, or current official instruction.
- reconcile names, addresses, account numbers, dates, amounts, credits, and calculations.
- remove allegations that are not supported by the available record.
- separate requested action from threatened or optional escalation.
- index the exhibits and explain why each one matters.
- preserve proof of filing, delivery, or service.
- check whether confidential or sensitive information should be redacted.
- retain the final version and the source material used to prepare it.
- seek jurisdiction-specific legal advice when the consequence or deadline is material and uncertain.
This guide is general legal information for the United States and does not replace advice about a particular matter. For “How to Write a Demand Letter to a Contractor”, verify current state and local requirements, court rules, contractual notice clauses, and the facts shown by the actual records before relying on any filing, demand, response, or deadline.