Freelancer–client WhatsApp records: track scope, approval and payment

Start with the agreement, not the chat summary

Identify the parties, work, deliverables, price, payment schedule, revision allowance, intellectual-property terms, cancellation rules and governing law in the signed agreement or accepted proposal. Then use WhatsApp to show later communications against that baseline.

Do not label every positive reply as acceptance. ‘Looks good’ may refer to a draft, visual direction or one part of a delivery. Preserve the preceding question, attachment name and later qualification so a reader can see what the response addressed.

Build a scope-change table

For each requested change, record the date, requester, original requirement, new request, estimated price or timing impact, response and final status. Link to the exact proposal version or task record. If no price was agreed, state that rather than inventing one from hours worked later.

A useful timeline distinguishes a client idea, a request for a quote, authorization to proceed and approval of completed work. Those steps may occur in separate messages and may have different legal effects depending on local contract law.

• Original requirement
• Requested change
• Quoted impact
• Authorization status
• Delivered version
• Acceptance, rejection or unresolved status

Create an invoice and payment trail

Keep the invoice itself, its number, issue and due dates, delivery method and any receipt confirmation. Add the relevant promise, dispute or proposed payment date from the chat, then add bank records showing what was actually paid. A message about paying next week is not the payment record.

For UK business-to-business transactions, GOV.UK publishes rules on when commercial payment becomes late and possible interest or recovery costs. Those rules are jurisdiction- and transaction-specific; check eligibility and current official guidance rather than applying them globally or automatically.

Preserve deliverables and approvals separately

Store final files and important drafts in stable, dated locations. A WhatsApp export may preserve a filename or media placeholder without the attachment. Record hashes or version identifiers when appropriate, but do not imply MyChatWrap performs forensic verification.

If delivery occurred through email, cloud storage, a freelance platform or source-control system, retain that system’s record. The strongest chronology often combines chat context with independent delivery and invoice evidence.

Use a readable copy carefully

Generate a working transcript with dates and senders, then add a separate issue index. Keep the untouched export. If a dispute requires disclosure, mediation or court filing, follow the recipient’s rules for relevance, privacy, redaction and adverse material.

MyChatWrap does not authenticate authorship, determine contractual meaning, calculate interest, prove performance or produce a certified report.

Official starting sources

The sources below are UK examples, not universal rules. Localize the legal substance only after researching the official authority for the governing jurisdiction and contract.

• GOV.UK: Business records if you’re self-employed — sales, income, expenses and proof
• GOV.UK: Late commercial payments — when a payment becomes late
• Justice UK: Disclosure of documents
• The signed contract and dispute clause for the specific engagement
• Research reviewed: 4 October 2026