Choose tools that help you organise business information, a practical, low-risk approach

Why organise now (and what to expect)

Most small businesses lose time because people can’t find the right file, the right version, or the contact they need. Organisation isn’t only a folder layout, it’s a mix of structure, labels (metadata), findability and simple rules for what to keep. This reduces wasted time, supports data retention obligations and makes any future automation or migration less painful.

Sourced fact: Microsoft’s guidance for SharePoint frames information architecture as navigation, metadata, search and personalised delivery to help people find what they need and to reduce information overload. (See sources.) 1

A practical organising principle: “Work-first, not tool-first”

Pick one recurring business activity (for example: new client onboarding, monthly invoicing, or supplier quotes) and design the information pattern around the steps that activity needs. That means: what documents, who owns them, how long they must be kept, and which people need access.

Concrete step: map that activity on a single A4 sheet, list inputs (what you receive), outputs (what you produce), and three places those items should live (shared drive / client folder / archive).

Sourced fact: official UK records guidance emphasises identifying information that has continuing value and capturing digital records in an environment that supports retention and access. That is why a clear filing location and retention rule are practical governance controls. (See sources.) 2

Choose tools by fit, not feature count

Match tools to the way people actually work: use a simple shared files area for active collaboration, a read-only archive for completed projects and a searchable hub for repeatable templates and policies. Avoid adopting a solution because it has every feature, aim for the smallest configuration that enforces your basic rules (naming, versions, retention).

Concrete steps: (1) pick primary storage for working files (e.g., a team SharePoint site or a company shared drive), (2) decide where final versions live (archive library or archive folder), and (3) set a naming rule everyone follows (see the quick task below).

Sourced fact: Microsoft’s modern SharePoint documentation highlights metadata architecture, search experiences and navigation as the core elements that make content discoverable and manageable across an organisation. (See sources.) 1

Four short governance rules to apply today

1) One truth for each file: decide which location is the canonical copy and move duplicates to archive. 2) Use human-friendly labels: short consistent file names and a small set of agreed metadata fields (client, project, date). 3) Ownership and lifecycle: assign an owner for each folder or project who is responsible for cleanup and retention decisions. 4) Regular tidy-up: schedule a 30, 60 minute monthly review for stale files.

Sourced fact: the UK government records policies recommend declaring which information has continuing value, capturing digital records into managed systems and avoiding formats or practices that harm long-term integrity. Simple lifecycle rules make compliance and retrieval much easier. (See sources.) 2

A small task to try this week

Task (20, 40 minutes): pick one active client or project and do the following: (A) create a single shared folder named with the agreed pattern (e.g. ClientName_Project_YYYYMM), (B) move the current canonical documents into that folder, (C) add a short text file called README.txt describing who owns the folder and where to find old versions, and (D) flag any files older than 18 months for review. This creates a repeatable pattern you can copy across projects.

Why it helps: a short, visible standard reduces ad-hoc naming and scattered copies, and gives you a place to apply retention or archiving decisions later. 1 2

Next steps and what to avoid

If the simple task works, expand the pattern to two or three more projects and capture feedback from colleagues; then document your minimal naming and retention rules. Avoid heavy, one‑off migrations as a first move, you’ll get better results by iterating small patterns and learning where people actually search.

If you need better search, metadata or retention automation later, consider a staged plan that uses a supported platform with governance features; Microsoft’s SharePoint guidance shows how navigation, metadata and hub structures are designed to scale when you’re ready. (See sources.) 1

Sources

Checked 2026-10-09., Introduction to SharePoint information architecture, SharePoint in Microsoft 365 | Microsoft Learn, MHCLG: records and information management policy, GOV.UK, Information architecture principles in SharePoint, SharePoint in Microsoft 365 | Microsoft Learn