Documents

How to organize client documents without creating another filing problem

A simple folder structure, naming convention and review routine for keeping client documents easy to find across a small service business.

A document system works when someone can find the right file and understand whether it is current. More folders do not necessarily make that easier. For a small service business, begin with a predictable home for each customer and a short convention for project files.

The following structure is a starting point. Apply it to a sample project first, then adjust any labels your team finds confusing.

Give each customer a stable home

Create one customer folder or document index with an identifier that survives a change of contact person. An organization name is usually clearer than the name of the employee who first emailed you. If customers have similar names, add your internal customer reference.

Within that home, group material by its purpose.

  • 01 Relationship — working contacts and links to engagement records.
  • 02 Projects — one folder for each engagement or delivery.
  • 03 Reference — reusable brand material, instructions, or specifications.
  • 04 Archive — completed work that your retention process says to keep.

Store sensitive records in the location and access scope appropriate for them. A convenient customer index does not mean every teammate should see every file.

Separate working material from approved deliverables

Inside a project, start with Inputs, Working, Review, and Delivery. These names describe what the team should do with the contents. Avoid a shared folder where several files are all named “final.”

If your storage provider maintains version history, use that history for revisions to the same working document. When a deliverable becomes an approved release, give the release a clear name and record which version was approved. Keep the original approval or signing evidence in its original system while you establish any migration process.

Use a filename people can read

A practical convention is customer, project, document, version, and date when the date helps distinguish releases. For example, “Northstar — Website refresh — Content outline — v02 — 2026-11-08” gives a teammate more context than “outline-new-edited.”

Choose the date format YYYY-MM-DD so filenames sort consistently. Agree on what a version number represents. If every small edit increments the visible release number, the labels soon lose their meaning.

Do not rename large historical collections all at once just to make them look consistent. A clear index of existing material can help immediately while preserving references people already use.

Make the index smaller than the file collection

The customer or project record should point to the documents people need most often. It does not have to duplicate the storage system's entire directory.

  • The current brief and scope reference.
  • The active working document or review package.
  • The approved deliverable.
  • The relevant approval or agreement reference.
  • A short note explaining who owns the document and when it was last reviewed.

For an external file link, check access from the intended recipient's account. A URL opening successfully for the owner does not establish that a teammate or customer can open it.

Review access at handoff and completion

At project completion, confirm which documents remain shared, who maintains them, and which links should appear in the handoff. Follow the retention requirements that apply to your business and records. Keep deletion and access changes deliberate rather than treating an archive folder as permission to erase history.

A brief monthly review can identify broken links, unclear “final” versions, and files whose owner has left the project. Fix the active documents first. Historical cleanup can follow the business's retention process.

Put the structure into everyday work

In the Execuown preview, a document record organizes an external HTTPS link and can connect it to a customer or project. The file stays with its existing storage provider, where that provider's sharing settings continue to control access. Add a clear name and a short context note so the link is useful when someone returns to it later.

Use the client onboarding checklist to collect inputs, then the project handoff checklist to confirm the final package.

ABOUT THE JOURNAL

Execuown publishes practical workflow guides for independent businesses and small service teams. Our focus is clear records, thoughtful handoffs, and less administrative friction.