How should a distributed team decide where each shared document belongs?
Quick answer
Choose one primary home for each document based on its purpose and who maintains it. Group related materials in a clearly named project or team space, then link to the primary document from other places instead of making separate editable copies. Agree on a few placement rules, name an owner, and make the rules visible so teammates can decide consistently without asking each time.
The question, the details, the next step.
Our team is distributed, and people save shared documents in different places. How can we decide where each one belongs without creating a complicated filing system?
Start with a small rule: every shared document has one primary home, chosen by its purpose and the team responsible for keeping it current. The home might be a project space, a team space, or a shared reference area. Pick from the places your team already uses rather than designing a perfect system from scratch.
For each document, ask: “Who needs this, and who will maintain it?” A project plan may belong with the project team; a reusable onboarding guide may belong with shared team references. Keep the rule short enough that someone can apply it while saving a file.
How should we handle a document that is useful to more than one team or project?
Keep one primary document where its owner can maintain it, and put links to it in the other places where people look for it. Add a short note beside each link explaining what the document is and which team or work it supports. That makes it discoverable without implying that every linked location contains a separate version to edit.
For example, imagine a hypothetical launch checklist maintained by a project team and used by support. Its primary home could be the project space. The support space can link to that checklist with a note such as: “Launch checklist — maintained by the project team; use this link for the current version.” This example assumes your document system supports links and that the project team owns the checklist.
We already have several copies of important documents. How can we clean that up without losing useful context?
First, identify which copy the responsible owner intends to maintain. Compare the copies with that owner and decide whether any unique material needs to be transferred before the team switches to a single primary document. If the team cannot determine which one is current, mark the choice as unresolved and ask the relevant owner; do not guess based on a filename or location alone.
Once a primary document is agreed, replace other editable copies with links where practical. If a copy must remain for a specific reason, label it clearly—for example, “reference copy; see [link to primary document] for the maintained version.” A label is not a substitute for agreeing which document is primary.
What rules should we write down so new teammates can place documents consistently?
Write a short placement guide that covers the decisions people actually face: what each shared space is for, how to choose a home, how to link a document used in multiple places, and who to ask when ownership is unclear. Include a few examples from your team’s work, but treat them as examples rather than exceptions that add another layer of rules.
You could start with this copyable template and fill in the bracketed parts:
“Put [document type or purpose] in [primary space] because [reason]. The owner is [team or role]. If another team needs it, add a link in [secondary space] with a note that identifies the primary version. If the owner or home is unclear, ask [team or role] before creating another maintained copy.”
Review the guide when your team changes its shared spaces or finds a recurring placement question. The goal is a consistent decision, not a complete inventory of every possible document.
A practical checklist
Choose a primary home for each shared document based on its purpose and responsible owner.
Agree on what each team, project, or reference space is for.
Link to the primary document from other useful locations instead of creating competing editable copies.
Label any necessary reference copy so readers know which document is maintained.
Record who to ask when ownership or placement is unclear.
A few more useful answers
Should a document’s home be based on its creator or its main audience?
Use purpose and ongoing ownership as the deciding factors. The creator may not be the person or team responsible for keeping the document current.
What if two teams both need to edit the same document?
Agree on one primary document and make the editing responsibility clear. If shared ownership is appropriate, name the teams responsible and decide how they will coordinate changes.
Is a folder structure enough to stop people from making duplicates?
Not by itself. Clear ownership, a visible placement rule, and links to the primary document help people recognize where to go and whether a copy is meant to be maintained.