Content audit: a framework for knowledge estates
A content audit is a review of every important document in your intranet, shared drives and sites to decide what to keep, update, merge or retire. A useful framework has three parts: an inventory of what exists, a small set of criteria to score each document, and a clear decision rule for what happens next. Without the third part, an audit ends as a spreadsheet nobody acts on.
This framework is written for knowledge estates: the policies, procedures, guides and reference material spread across an intranet, Google Drive and SharePoint. It works with a spreadsheet and a few weeks of effort, and it scales with the right tools.
Content inventory and content audit: the difference
A content inventory is a list of what you have: file names, locations, owners, dates, how often each is opened. A content audit is a judgement about each item: is it accurate, is it needed, is it the official version? You need the inventory to run the audit, but the value comes from the judgements and the decisions that follow.
Part 1: Scope and inventory
Choose the scope. Name the places in scope: the intranet, specific shared drives, specific SharePoint sites. Be explicit about what's left out for now. A focused scope that finishes beats a complete scope that stalls.
Capture the inventory. For each document, record:
- Title and location
- Type (policy, procedure, guide, template, reference)
- Owner, and whether they still work here
- Last modified date
- How many people can open it, and roughly how often it's opened
Sort by reach. Order the inventory by how many people can open each document and how often they do. That order decides where you start.
Part 2: Five criteria to score each document
Score each document from 1 to 3 on five criteria. Keep the scale small, so different reviewers score the same way.
| Criterion | Question | 1 | 3 |
|---|---|---|---|
| Accuracy | Does it describe how things work today? | Clearly out of date | Checked and current |
| Consistency | Does it agree with related documents? | Contradicts another document | No conflicts found |
| Authority | Is it the official version? | A copy or draft | The approved version |
| Ownership | Is there a reachable owner? | Owner has left or unknown | Named, active owner |
| Need | Does anyone still use it? | Nobody opens it | Used regularly |
Agree what each score means before the audit starts. "Out of date" is a judgement call, and reviewers make it differently without shared examples.
Consistency is the criterion most audits skip, because it means comparing documents instead of reading them one at a time. It's also the one that matters most for AI assistants, which can't tell which of two contradicting documents is right. For a method, see Conflicting procedures: how to find documents that disagree.
Part 3: Decide what happens to each document
Use the scores to make one of four decisions:
| Decision | When | What it means |
|---|---|---|
| Keep | High on all five | No change; set a review date |
| Update | Needed and official, but inaccurate or unowned | Owner fixes it by a set date |
| Merge | Two or more documents cover the same ground | Combine into one, link the rest to it, retire the copies |
| Retire | Low need, or a copy of something better | Archive if it must be kept, otherwise move to trash |
Every decision gets a named person and a date. "Update the expenses guide" without an owner is a wish, not a decision.
Where to start
Start where a wrong document does the most harm:
- High-reach documents opened by many people every week.
- High-risk topics: HR policy, legal templates, security, health and safety, pricing.
- Areas after change: teams that have reorganised, merged or changed tools recently.
Involve the people who use the content. Give each team a filtered list of its own documents with suggested decisions, and let them make the final call. They know what's still used, and their sign-off makes the decisions stick.
What the audit should produce
- A ranked list of decisions, each with an owner and a date.
- A short record of the criteria and examples you used, so the next audit scores the same way.
- A few numbers to track: open issues, documents without owners, conflicts found and resolved.
When to audit again
Content drifts as soon as the audit ends. Plan a light review every quarter for high-reach content, a full audit once a year, and an extra review after triggers such as a merger, a platform migration, a major policy change or a new AI assistant rollout.
Why audits matter more with AI
An AI assistant reading your intranet and drives retrieves whatever matches a question best, whether it's the official version or an old copy. A content audit that settles which document is official, and retires the rest, is what stops the assistant repeating outdated guidance. Our AI readiness checklist covers the AI-specific checks.
Where Anchoris fits
Anchoris runs the checks behind the accuracy, consistency and ownership criteria on documents in Google Drive and SharePoint. It finds contradictions between documents, outdated and expired content, people named as owners or contacts who have left, unfinished placeholders, broken links and duplicates. It ranks each issue by how many people can open the document, suggests who should fix it, and fixes it at the source with approved workflows (move, rename or move to trash), with every run logged. You get a quality score from 0 to 10 for your documents, and first results within an hour.
You choose which drives Anchoris can reach, and nothing changes without your approval. It works alongside the assistant you already use: fix the source once, and every assistant that reads it answers correctly.
See what a content audit of your drives would find.
Book a demoFrequently asked questions
What is a content audit?
A content audit is a review of the documents in your intranet, drives and sites that scores each one against agreed criteria and decides whether to keep, update, merge or retire it.
What is the difference between a content inventory and a content audit?
An inventory lists what you have, with details such as location, owner and date. An audit judges each item's accuracy, consistency, authority, ownership and need, and decides what to do with it.
What criteria should a content audit use?
A small set works best: accuracy, consistency with related documents, whether it's the official version, whether it has a reachable owner, and whether anyone still uses it.
How often should we run a content audit?
A light review of high-reach content each quarter, a full audit once a year, and extra reviews after mergers, migrations, major policy changes or a new AI assistant rollout.
Should we delete or archive old content?
Archive content you must keep for legal or business reasons, with narrower access. Move clearly redundant or trivial content to trash. Check retention requirements before removing anything in bulk.
How to clean up Google Drive before Gemini
Read nextMore from the blog
How to find duplicate files in Google Drive
Google Drive has no one-click duplicate finder. Four manual methods, where they break down, and what it takes to stop copies coming back.
The anatomy of a documentation audit: what to look for
Most audits end as a 400-row spreadsheet. The four things a useful audit looks for, and how to keep its findings from decaying.
AI readiness checklist: 8 signs your company's knowledge is ready for an AI assistant
AI doesn't create bad information, it scales it. Eight checks that show whether your documents are ready for an assistant.