If it is not written, it did not happen, for scope and payment.
8 min readWhat to document
| Type | Examples |
|---|---|
| Agreements | SOW, contract, signed PDF |
| Recaps | Post-call emails, Slack summaries |
| Approvals | "Looks good, ship it" with date |
| Changes | Change orders, scope additions |
| Invoices and payments | Sent invoices, paid confirmations |
| Deliverables | Final files with version and date |
Simple folder structure
Clients/
ClientName/
01_Agreement/
02_Recaps/
03_Deliverables/
04_Invoices/
05_Changes/
Name files with dates: 2024-08-01_kickoff-recap.pdf. Future you will thank present you.
Daily habits (5 to 10 minutes)
- After every client call, send a recap email the same day.
- Save approvals in the client folder, not buried in chat.
- Log scope changes when they happen, not at invoice time.
- Weekly backup of active client folders to cloud storage.
Common mistakes
- Documentation only when fighting. Too late.
- Scattered across WhatsApp, email, and Notion with no index.
- No naming convention. Files called "final_v2_REAL.pdf".
- Deleting chat history that held approvals.
Final thoughts
Documentation is how professionals replace memory with proof. Build the system before you need it in a dispute.
How Salag helps
- Payment Method Risk Check. Match payment records to your documentation folders.
- Project Scope Calculator. Generate scope docs worth saving from day one.
- Scam Pattern Detector. Keep records that help if a client relationship goes wrong.
Move safer. Not faster.
In short
A freelance documentation system is where you store agreements, recaps, approvals, invoices, and change decisions so you can find them in minutes. If it is not written, it did not happen when scope or payment disputes show up. You do not need enterprise software. You need one folder structure and a habit.
Common questions
A freelance documentation system is where you store agreements, recaps, approvals, invoices, and change decisions so you can find them in minutes. If it is not written, it did not happen when scope or payment disputes show up. You do not need enterprise software. You need one folder structure and a habit.
Write down what you agreed on and what changed. Do not start new work on vague terms.
Use plain English, confirm in writing, and set clear hours. Clients hire you for reliability, not cheap labor.
Put the basics in your agreement or a recap email before billable work starts. Bigger projects need fuller terms.
Stay warm but firm. Offer options inside a clear process, like a change order or a short written recap.
VERIFY means: capture facts, compare to your agreement, name tradeoffs, confirm in writing, and save the decision for next time.
Escalate when the same problem repeats: unpaid extras, late approvals plus new asks, or refusal to confirm in writing.
Yes. A clear email with tasks, dates, price, and limits beats a verbal yes every time.
Salag gives you tools and templates so you can set boundaries before small problems grow.
Use written recaps, scope trackers, and Salag tools like agreement builders and scope detectors.
Most recaps take five minutes after a call. That small step saves hours of arguing later.
Yes. Retainers need weekly change logs. Projects need milestone gates. Always compare new asks to written terms.
Pause billable work on unclear items. Send a narrow summary of what you will do. Save their reply either way.