Free demand letter: connect the requested amount to your evidence
A useful demand letter allows the recipient to identify the transaction, understand the amount requested and answer a specific question. It should not depend on legal threats copied from another dispute. The structure below is a free starting point for an ordinary payment disagreement; state law, the contract and the type of claim can require a different notice or process.
Published · Practical guide prepared with AI assistance and checked against the official sources below. General information, not individual legal advice.
Build the calculation before writing
List the original amount, payments received, agreed credits and the balance you are asking for. Keep disputed charges in a separate row. If you claim interest, penalties or legal costs, identify the basis and check whether they can be claimed in your situation. An invoice total is evidence of what was billed, not by itself a decision that every charge is enforceable.
Fictional example: a customer agreed to pay $600, paid $200 and later received a documented $50 credit. The requested principal would be $350 if those are the only adjustments. Attach the agreement, payment record and credit confirmation. Do not demand $400 while silently omitting the credit.
Identify the parties and the event
Use the contracting party’s correct name and a reliable contact address. A shop sign, employee name and registered company name may differ. State the agreement or event, its date and the obligation you say remains unfulfilled. Keep a disputed fact visibly disputed: “My record shows no transfer after 12 June” is more precise than accusing someone of dishonesty without evidence.
Label the supporting copies A, B and C and refer to each label once where useful. Keep originals. Remove unrelated personal information from working copies while preserving the date, name and amount needed to understand the claim. A concise evidence index is easier to follow than a large unexplained attachment bundle.
A plain-language starting structure
“Dear [recipient], I am writing about [agreement or transaction] dated [date]. Under the arrangement recorded in [attachment], I understand that [obligation]. My records show [what happened]. I request payment of [amount], calculated as [original amount minus payments and credits]. Please review the attached records and explain any disagreement with that calculation.”
“Please respond by [requested date] using [contact method]. If you believe the amount is incorrect, identify the entry you dispute and provide the relevant record. I would like to resolve this issue and retain a written record of our correspondence.” Replace every placeholder and remove statements that are not true. The requested response date is not automatically a statutory deadline.
Check the route before relying on the letter
The California Courts small claims checklist describes a demand for money, a brief account of the events and supporting copies. Its guidance also distinguishes claims involving government agencies. That is a California example, not a nationwide notice rule. Check your state’s court guidance and any subject-specific procedure before sending the draft or filing a case.
A demand letter does not file a lawsuit, answer an existing lawsuit or guarantee that a limitation period stops running. If a court deadline is approaching, deal with that deadline separately. Avoid promising a particular court outcome, adding criminal accusations or claiming that a recipient’s silence automatically proves the debt.
Keep the sent version and reconcile the response
Save the final signed or otherwise identified version, the attachments actually sent and the delivery record. Record the date and address used. If a payment arrives, update the balance before taking a further step. If the recipient provides a different calculation, compare it line by line and preserve both versions. The aim is a traceable request whose facts can be checked, whether the next step is a correction, discussion or a properly assessed claim.
Official sources checked on 24 September 2026
Describe your situation and view available document preparation · More legal guides
Build the demand from a transaction file, not from threatening language
A strong demand package starts with a compact transaction record. Create a one-page sheet identifying the parties, the agreement or transaction, the date performance was due, the amount originally expected, payments or credits already received, and the exact balance you are asking the recipient to address. Link each figure to a contract, invoice, receipt, statement, delivery record, or other source. If a number is disputed or estimated, label it that way. This prevents the letter from presenting an uncertain calculation as an established debt.
Separate the factual record from the legal route. Some claims have contractual notice provisions, statutory pre-suit requirements, special consumer procedures, or filing deadlines that a generic template cannot determine. Before sending a demand, check the governing agreement and the official court or agency material that applies to the type of dispute and jurisdiction. A useful working file should therefore contain a “requirements to verify” section rather than silently importing a deadline or legal threat from a sample letter written for another state.
Make the amount reproducible
Use a line-by-line calculation instead of one unexplained total. Identify principal or purchase price, any agreed adjustments, refunds, credits, payments, and each additional amount you believe should be included. If you claim interest, fees, consequential loss, or another category beyond the core amount, keep it on a separate line and record the source for claiming it. Do not add a charge merely because a template contains it. The recipient should be able to reproduce the arithmetic from the documents you identify.
For non-money disputes, replace the amount table with an obligation table. Record what was promised, what occurred, the document or communication that shows the difference, and the specific correction requested. A demand to repair work, return property, provide records, or stop a defined practice can be clearer when the requested action is stated as precisely as a dollar figure would be.
Choose attachments deliberately
A demand letter should not become a complete litigation archive. Attach or identify the smallest set of records needed to understand the request while preserving the full source file privately. Give each attachment a stable label and refer to that label in the letter. If a screenshot is necessary, retain the surrounding context, date, sender, or account information needed to understand where it came from. Redact unrelated sensitive information in the sharing copy without altering the underlying evidence.
Keep proof of the version actually sent. Save the final PDF or document, the attachment set, the address or electronic destination, and delivery evidence. If the recipient answers, preserve that response as a new document rather than editing the original demand. A later dispute often turns on what was requested and what response was given, so version control matters as much as polished wording.
Use a response matrix before escalating
When a response arrives, compare it with the demand item by item. Mark each point as accepted, disputed, partially answered, or unanswered and add the document supporting the recipient’s position where one is supplied. This makes it easier to decide whether the disagreement is about facts, calculation, contract interpretation, procedure, or simply missing records. If litigation or an administrative filing is being considered, use the relevant official forms and deadlines rather than assuming that the demand letter itself preserves a claim.
Before sending, perform a final neutral-language check. Remove claims of fraud, criminal conduct, bad faith, or guaranteed liability unless they are necessary, supported, and appropriate to the actual dispute. State the requested response date only after checking whether the contract or applicable procedure sets a required period. The goal is a document that makes the dispute easier to evaluate and resolve, not one that tries to create leverage through unsupported consequences.