Keep a connected record for each job
Use a project code or client-plus-date naming pattern so related records can be found together. Avoid putting sensitive personal data in filenames.
- The inquiry or brief and the approved quote or agreement.
- Scope changes, approvals, key delivery notes, and acceptance.
- Invoices, credit notes, receipts, and payment-provider references.
- Expense evidence and supplier invoices related to the work.
- Important client communication about price, scope, dates, or payment.
Use predictable names and folders
For example, organize by year and client, then use names such as `2026-11-04-client-quote-Q104.pdf` or `2026-11-client-invoice-INV104.pdf`. Choose one pattern you can follow consistently. Keep originals and clearly label revised or corrected copies rather than silently replacing documents that matter to the audit trail.
Protect access and backups
Restrict access to people who need it, use strong unique passwords and multi-factor authentication where available, and back up important records. Be cautious with links containing customer data; limit sharing permissions and remove access when it is no longer needed.
Know what to retain
Retention periods and required records vary by jurisdiction, tax status, industry, and contract. Do not assume a general online checklist is the law for your business. Confirm the applicable schedule with an accountant, regulator, or qualified adviser, then set a calendar reminder to review old records safely.
Review monthly
Once a month, reconcile bank and payment-provider activity against invoices, identify overdue balances, check that receipts have been issued where needed, and confirm key files are backed up. A short recurring review is more reliable than an annual search through an inbox.
Worked example
A practical folder and filename system
Create one private folder per client, then one subfolder per project. Keep the approved quote, scope changes, delivery evidence, invoices, receipts, and expense records together. Use a stable name such as `2026-11-04-project-Q104-approved.pdf`; add a version or ‘corrected’ label rather than overwriting a sent document. Store a separate index of invoice status and payment dates, and back up the folder to a protected location.
Use before you send or file
Quick checklist
- Can you find the accepted scope and later changes for each job?
- Can every invoice be matched to work and every payment to an invoice?
- Are files named consistently without unnecessary personal data in filenames?
- Are access permissions, backups, and account security appropriate?
- Have you confirmed local retention and deletion requirements?
Common mistakes to avoid
- Keeping the only copy in email or on one device.
- Overwriting a sent document so there is no clear audit trail.
- Keeping sensitive customer information indefinitely without a purpose or policy.
Related guides
- Quote vs estimate vs invoice: what to send and when →
Understand the practical difference between a quote, estimate, and invoice, what each should contain, and how to move a client from approval to payment.
- Freelance invoice checklist: what to include before sending →
A practical invoice checklist for freelancers: identify both parties, describe work, show totals and due dates, and make payment instructions clear.
- How to write a project estimate clients can actually use →
Build a clear project estimate with scope, assumptions, itemized costs, uncertainty, validity, and a written approval step.
This guide is general educational information, not legal, tax, accounting, or financial advice. Rules vary by location and business circumstances. Check current local requirements or consult a qualified professional.