Organize your business documents as a team

Choose an activity your team knows well: preparing a proposal, delivering a project or welcoming a new person. Rebuild how it unfolds with the people involved. Ask which files they open, what they look for in them and at what point they need to get a confirmation. You end up with an inventory tied to the work, which is more useful than a list of folders with no explanation.

For each document, write down its name, its current location, its purpose, its owner and its status. Add one simple question: can we use it today without asking which version to pick? If the answer is no, note the person who can decide. Avoid declaring a file up to date just because its modification date is recent. A layout fix can come after a substantive decision that was never incorporated.

In a fictional example, a small team is preparing a website redesign proposal for Atelier Nord, a client invented for this guide. It has a proposal template, the client’s information, a list of pages and comments exchanged by email. The template is the starting point; the approved proposal becomes part of the client file. The comments explain the requested changes, but they do not automatically amount to an approval. These documents serve different purposes and deserve separate statuses.

Start with the active documents of this activity. Spot the archives and the files whose use is unknown, without deleting them during the inventory. A file that looks old may still support a decision or an obligation specific to your business. For invoices and supporting documents, for example, Revenu Québec asks you to keep records related to the GST and QST (new tab) (in French) for six years after the end of the last year to which they relate. If keeping a file raises an accounting, contractual or legal question, have the right person deal with it before you decide what happens to it.

Your first deliverable can fit in a simple table: document, use, owner, reference version, access and next action. Here is that table filled in for the fictional proposal for Atelier Nord:

The last row shows the rule to follow: when information is missing, add the row and name the question instead of guessing the answer. This list will then help you prepare the daily organization of your business, with a clear distinction between what already exists and what still needs to be set up.

File documents according to the way people look for them. For a small team that works by mandate, grouping by client and by project can work. For a recurring activity, one space per function may be clearer. Choose the logic that lets you explain where to look without knowing each colleague’s personal history. A different filing system for each person makes that explanation difficult.

Prepare a short naming convention. A name can combine the project, the type of document and a detail that identifies the useful version. For the fictional proposal for Atelier Nord, “AtelierNord_Redesign-proposal_v3” shows the client, the purpose of the file and its version, but its status (to be validated, sent, accepted) must also be clear in your tracking. Avoid strings of “final”, “final2” and “reallyfinal”. They don’t say who approved the content or whether that approval covers the version being viewed.

Decide where the reference sits for each active document. Documents you receive can stay in an intake space while they are being filed. Documents in preparation stay identified as such. Approved versions carry their status and the date of the decision. This organization can take the form of folders, fields or a tracking list; it doesn’t require copying the same file several times.

When a copy has to be sent outside the business, note what was sent and to whom. Keep a distinction between the copy sent and the working document, which will keep changing. If the recipient sends back corrections, indicate who must incorporate them and which version must be reviewed. An attachment you receive should not silently replace a whole team’s reference.

Try your structure with someone who didn’t help create it. Ask them to find a specific document, then to explain why they think they have the right version. If they have to open every file or ask its author, adjust the names or the statuses. For a website project, the guide to preparing a website redesign then details the content and approvals to gather.

A clear filing system doesn’t say who can view or edit its content. For each space, distinguish the people who work on the documents, those who approve them and those who only need to read them. Also specify what outside collaborators need. A supplier may need a project’s images without needing your business’s other files. If a space contains personal information, this sorting is not optional: the Commission d’accès à l’information (new tab) (in French) points out that only authorized people, for whom this information is necessary to perform their duties, may have access to it. The complete guide to Law 25 also covers retention and destruction rules.

Prepare invitations based on these needs. Check the recipient’s identity and the rights granted in the tool you chose. Ask someone with the intended role to test the access, using a document with no sensitive information if needed. A test run from your own administrator account doesn’t prove that the recipient will see the same thing. In the same way, having a link should never be your only definition of an authorization. The Canadian Centre for Cyber Security (new tab) recommends that small organizations use individual rather than shared accounts, with the minimum permissions each person needs for their tasks.

Also describe how approval works. Who can approve a proposal, a page or a procedure? Where should that decision appear? What happens if the person asks for a change? An instruction like “to be validated” stays incomplete as long as no one knows who answers and which version must be reviewed. Attach comments to the document they concern so they keep their context.

Plan for replacing someone who is away and for the end of a collaboration. Note who takes over the active documents, who removes access and where the actions taken will be recorded. The same Centre advises managing the life cycle of accounts, so that access stays active only as long as it is needed. The point is to prepare how your team works; the features available and the actual permissions must be checked in your account. The page on plans and their availability helps you separate the offer presented from the items that need confirmation.

Finally, keep passwords and access codes out of shared procedure documents. Describe how to request access from one’s manager rather than copying a secret into a how-to guide. For a demonstration, choose clearly labelled fictional documents. You can test the filing system and the approvals without turning a trial into an unintended release of real information.

Run a complete trial with a limited activity. One person prepares the document, another reviews it, then the person responsible records their decision. Next, ask someone to find the approved document and the next action. This walk-through lets you check the links between filing, access and responsibility. It also shows where the team keeps working in parallel without knowing which copy to follow.

Write down the difficulties you observe along with their context: an ambiguous name, missing access, an approval received somewhere else, a document that can’t be found. Turn each one into a specific fix. “Improve the filing system” gives little direction. “Add the project name to active proposals” or “name the person responsible for correction requests” lets you check whether the action was done.

Then write a short operating sheet. It shows where to put a new document, how to name it, how to request approval and where to find the approved reference. Add the name of the person responsible for this sheet. A procedure with no one in charge of updating it risks describing an organization that no longer exists after a few team changes.

Gradually extend the method to other activities, keeping what works. Some documents need a different organization; document that exception instead of forcing every use into the same model. When a new need appears, start by describing the expected work, then check whether your environment can handle it with the planned access.

Your preparation file is ready when a colleague can understand the structure, find a reference and know who to ask a question. It can still contain open points, as long as they are named and assigned. You then have a concrete basis for discussing your work environment, rather than a general request to “centralize everything”.

Let’s talk about how your documents and your team are organized.