You know you saved it somewhere. There is a proposal in your downloads, a client folder in OneDrive, another version attached to an email, and a document called Final-Final-Revised that no longer feels final.

A useful filing system starts with a few decisions: where each kind of work belongs, who needs access, and how someone will recognize the right file. Here is a practical starting point for a small service business using Microsoft 365.

Start here: OneDrive or SharePoint?

Use OneDrive for work you manage individually. Use SharePoint for files your team needs to own and work on together. OneDrive can share files too; the difference is the role each location plays in your business. Microsoft explains this distinction in its small-business file storage guidance. This article refers to OneDrive for work or school and SharePoint in Microsoft 365.

Type of work	A useful starting home
Your working notes or an early draft you are developing alone	Your work OneDrive
A procedure the team needs to follow	A team SharePoint library
A project plan several people maintain	A team or project SharePoint library
Reusable proposal and onboarding templates	A shared template library
Payroll, personnel, or confidential financial records	A separately restricted location with access planned for the appropriate people
Documents a client needs to review	A deliberately configured client-sharing space

Ask: if someone else had to continue this work tomorrow, would they know where to find the current file and have the right access? If the answer is no, clarify its home and ownership before adding more folders.

Choose the right level of structure

A SharePoint site is a workspace. A document library is a collection of files within it. Folders organize files inside a library. You can use these levels differently as your business grows.

Start by grouping work that has the same audience and access needs. Keep confidential records and external client collaboration separate from everyday internal work. The example below is a suggested layout, not a set of permissions or a Microsoft-required template.

A simple structure for a small service business

Internal Operations — team site, internal access
  Operations — library
    SOPs and Checklists
    Tools and Trackers
  Templates — library
    Proposals
    Client Onboarding
    Project Delivery
  Client Work — library for internal project work
    Client Name
      Project Name
        01 Planning
        02 Working Files
        03 Approved Deliverables
        04 Closeout

Restricted Administration — separate site, limited access
  Finance
  Personnel

Client Collaboration — separate site for each client as needed
  Documents for Review
  Approved Deliverables

Use the parts you need. A solo business may begin with fewer locations. A team with distinct roles or several client collaborators may need more separation. Create an archive area when it becomes useful, with a clear rule for what moves there and who maintains it.

In this example, Client Work is internal. Creating folders for different clients does not automatically keep their contents private from other people who already have access to the site or library. Microsoft describes separate customer team sites as one approach to organizing client collaboration.

Give each file one agreed home

Decide where the working document lives and where approved deliverables belong. If a proposal is being developed in Client Work, that is the working source. When approved, place the issued deliverable in Approved Deliverables and make its status clear.

For example, a project might have an editable proposal in Working Files and an approved PDF in Approved Deliverables. That is an intentional pair with different purposes. Five editable copies called “latest” are harder to manage.

• Store reusable blank documents in Templates. Create a project copy before filling one in.
• Keep internal notes separate from documents intended for client review.
• Share a link to the agreed file when appropriate, rather than circulating more working copies.
• Assign a person to keep each library or project area organized.

Use file names that explain the contents

Choose a short naming rule your team can follow. For documents where the date matters, try:

YYYY-MM-DD_Client-or-Topic_Document-Type_Status

2026-10-21_Maple-Studio_Proposal_Draft.docx
2026-10-28_Maple-Studio_Proposal_Approved.pdf
Client-Onboarding_Checklist_Template.docx

Define what the date means: creation date, issue date, or reporting period. Pick a small set of status words, such as Draft, Review, and Approved. Agree on who can mark a document Approved. Dates and labels should communicate a decision, not make the name longer for its own sake.

Plan access before sharing

Give people the access they need for their role. Use established site or group membership for regular team access, and decide who can share externally. Microsoft explains SharePoint permissions and sharing links, including the difference between links for specific people and links anyone can use.

• Use view access when someone only needs to read; use edit access when they need to change the document.
• For confidential material that must stay internal, use a site with external sharing turned off.
• For client collaboration, confirm the intended guest’s access and check that unrelated client or internal material is unavailable.
• Review access when a project closes or someone changes roles. A folder name such as “Private” does not enforce privacy.

Available sharing options depend on your organization and site settings. If you are unsure how access is configured, have the person responsible for Microsoft 365 review it before sharing client or personnel information.

Try the structure on one active project

Choose a project you understand well and test the layout with a small set of files before reorganizing the whole business.

• List the documents you use most often.
• Give each one an agreed home and an owner.
• Create only the folders the project needs.
• Apply the naming rule to a few representative documents.
• Have another authorized person find the current proposal, checklist, and deliverable without coaching.
• Adjust what confused them, then write a one-page filing guide.

Before a wider move, plan how you will handle existing links, permissions, and the old locations. Keep a clear transition plan so people know which location to use.

When a folder cleanup needs a bigger plan

You may need a more tailored workspace if people repeatedly ask for access, the same records live in several places, client and internal work are mixed together, or every new project requires rebuilding the same folders and documents.

At that point, look at the workflow around the files: how a client enters the business, who creates each document, what approval means, and what happens when the work is finished. The filing structure should support those steps.

Give your files a home that supports the work

Start with one project, one naming rule, and one clear place for the current work. A useful system should make the next action easier to see.

Need help organizing your business workspace? Explore APS’s Structure services for support with SOPs, workflows, SharePoint, Microsoft 365, and practical business systems. Or start with a discovery session to talk through what your business needs.

From Jennifer Teope, founder of A Powerful Sorceress, LLC, based in Erie, Pennsylvania. Where logic meets magic.

Microsoft references

• Set up file storage and sharing in Microsoft 365
• Sharing and permissions in the SharePoint modern experience

Microsoft guidance checked October 21, 2026. The example structure and naming convention are suggestions from APS and should be adapted to your business.