Organising scanned documents for a small team

A small team produces a steady trickle of paper: receipts, delivery notes, signed contracts, letters from the tax office. Scanning them is the easy part. Finding the right one six months later, and knowing it is the final version, is where it falls apart. Here is a simple system that works without special software.

1. One naming pattern, used by everyone

Agree on a pattern and write it down. A good one sorts by date automatically and says what the file is without opening it:

YYYY-MM-DD Type Party Detail.pdf

• 2026-11-04 Receipt Office-Supplies Printer-toner.pdf
• 2026-10-28 Contract Landlord Lease-renewal SIGNED.pdf
• 2026-11-01 Invoice Client-A INV-2026-014.pdf

Year first means files sort in time order in any folder. Avoid “final”, “final2”, and “new”: they stop meaning anything after a week. Use SIGNED only for the version that was actually signed and sent.

2. Few folders, by what you look for

Deep folder trees hide files. Most small teams need three to six top-level folders, organised by how people search:

• Finance: receipts and invoices, with a subfolder per year.
• Contracts: one subfolder per counterpart.
• HR: restricted to the people who need it.
• Letters: official correspondence.

If you hesitate about where a file goes, the folders are too fine-grained. Rely on the file name instead.

3. Scan once, at the right quality

• Scan on the day the paper arrives. A pile of unscanned receipts is how things get lost.
• One document per PDF. Combine its pages in order; do not mix unrelated documents in one file.
• Use a clean document style for text and colour only when it matters, such as stamps or highlights. Files stay small and readable.
• Keep originals that have legal or tax value for as long as your local rules require. A scan may not replace them.

See scanning tips for light and angle, and use PDF Studio to put pages in order.

4. Versions: never overwrite the signed one

The most expensive mistake is editing a signed agreement and saving over it. Treat signed and sent files as read-only. If something changes, create a new file with a new date. Tools with version history make this automatic: every save is kept with who changed what and when, and you can go back.

5. Who may do what

Not everyone needs to edit everything. Four roles cover most teams:

Give the smallest role that lets someone do their job. Review the member list when people leave the team.

6. Approvals in one place

“Did the manager approve this?” should not require searching chat history. Ask for approval on the file itself, with a comment or a signature request, so the answer stays attached to the document.