A freelance writer delivers a company’s website copy, sends the final bill, and receives a refusal to pay. The client says the writing appears automated and requests additional pages that were never discussed. The writer insists the project is finished.
In this hypothetical dispute, neither an angry email nor a polished invoice explains the whole disagreement. Start by organizing the agreement, the delivered work, and the objections. A clear record gives both sides something concrete to review before the matter escalates.
Establish What the Agreement Actually Required
Gather the signed contract, accepted proposal, relevant emails, and any approved changes. Identify the parties, deliverables, deadlines, revision allowance, and payment conditions.
California Courts’ guidance explains that a breach of contract case requires proving the relevant legal elements and documenting resulting harm. It identifies contracts, communications, receipts, and other records as potential evidence.
For the writer, compare the promised pages with the delivered files. Separate requested corrections from additional work, without assuming every objection is unreasonable.
Check whether payment depended on delivery, approval, or another specified event. Note any requirement to give notice or allow a problem to be corrected. Ask an attorney about unclear provisions rather than interpreting them solely in your favor.
Match the Invoice to the Work
An invoice generator with logo options can produce a consistent billing document, but presentation should follow a careful reconciliation of the charges.
Use descriptions that connect each amount to the accepted scope. Include the invoice number, relevant dates, agreed currency, previous payments, and remaining balance.
Suppose the agreed project fee was $1,200 and the client paid a $300 deposit. The starting balance is $900, before any documented adjustments. Show that calculation rather than presenting an unexplained total.
Keep disputed extras separate from the original fee. If the client requested another page, locate the communication approving its price before including it.
Save the issued invoice and explain subsequent corrections. Avoid silently replacing earlier versions with documents that suggest different terms were always agreed.
Examine AI Allegations Without Treating Scores as Verdicts
An AI content detector may provide a signal about a draft’s possible origin, but it should not settle whether the writer fulfilled the agreement.
The 2024 RAID study found that evaluated detection systems struggled with unfamiliar generative models and variations in how text was generated. Those results concern the tested systems, not every current service.
Ask the client to identify the disputed passages and the contractual requirement they believe was breached. Preserve research notes, drafts, and revision history, including records that do not support your preferred account.
Keep authorship, accuracy, and compliance as separate questions. A factually accurate text might still violate an agreed restriction on assistance; an automated classification does not independently establish that violation. Obtain legal advice where the agreement is disputed.
Preserve the Complete Digital Record
Keep original documents, attachments, delivery messages, and relevant conversations together. Export accessible records before accounts close or routine deletion removes them, and preserve dates and sender information.
Federal Rule of Civil Procedure 37(e) addresses electronic information lost through inadequate preservation when it should have been kept for anticipated or ongoing litigation and cannot be restored or replaced. Remedies depend on additional conditions, including prejudice or intent.
That federal rule is not a universal instruction for every state dispute. Ask counsel what preservation duties apply and whether automatic deletion settings need adjustment.
Do not delete embarrassing messages or rewrite earlier notes. Create a separate chronology with references to the underlying material. Label later recollections accurately and retain backups that you can open and inspect.
Request a Specific Resolution
Prepare a factual payment request identifying the project, outstanding amount, relevant agreement, and supporting documents. Ask the client to explain any remaining objection and propose a realistic response deadline. After telephone discussions, send a neutral written recap and invite prompt corrections to anything you misunderstood.
California Courts instructs prospective small claims plaintiffs to request payment before filing and explain how much is owed and why. Check the requirements applicable where your dispute would be heard.
Keep the communication focused on resolution, not public embarrassment. Avoid making unsupported threats about criminal charges or guaranteed legal costs.
If both sides agree on revisions or installments, document precisely what each will do and when. California’s court guidance recommends recording settlement terms in writing. Ask a lawyer before accepting language releasing claims you still intend to pursue.
Choose the Next Step With Local Advice
Before filing, check the correct defendant, appropriate court, filing deadline, and any contractual mediation or arbitration provisions. California Courts’ preparation guidance specifically flags dispute resolution clauses and deadlines.
Consider the cost of escalation alongside the amount disputed. Winning is not necessarily the final step: California Courts warns that a successful claimant may still need to pursue collection.
Bring an organized file to a consultation, including weaknesses and unresolved questions. General information cannot replace advice about your contract and jurisdiction.
The strongest preparation is not the most forceful accusation. It is an accurate explanation of what was promised, what happened, and what resolution you are seeking.
