Find what you need when you need it.
Your organization already knows a lot. It lives in drives, threads, inboxes, and someone's head. Treat it like infrastructure: built on purpose, shared by everyone, maintained on a schedule. This guide covers what goes in, how it's named, who owns it, and how it stays current.
Common starting points:
I don't know where we stand
Take the eight-question check. Get a stage and a starting point.
I need to know who uses what
See every content type by team, and why each team needs it.
I'm ready to clean house
Log what exists, score it, and decide keep, fix, or retire.
I need leadership to say yes
Borrow the pitch: the problem, the payoff, and the ask.
Where does your knowledge stand?
Answer honestly. Nobody's grading you. Your answers stay in this browser.
Who uses what, and why
Content components are the building blocks: the pieces that get reused inside proposals, onboarding, reports, and pitches. Pick a team to see what it pulls from the library. Pick a component to see who depends on it.
The whole picture
Components shared by the most teams are your first migration priority. Break those and everyone feels it.
A place for everything
Six top-level categories. Every item gets one home, a set of metadata, a predictable name, and an access level. Tags do the cross-referencing so folders don't have to.
Metadata every item carries
Name files so people can read them
Format: [Type]_[Client or Dept]_[Descriptor]_V[Version]_[YYYY-MM-DD]
Spaces and special characters get stripped. Dates sort correctly because year comes first.
Access levels
Open to everyone inside, and safe to share outside. Marketing collateral, published case studies, company overview.
Limited to specific teams. Financial reports, active proposals, project-specific documents.
Named people only. HR records, legal matters, anything with personal or client-identifying information.
Status tags
Add quality flags alongside status: Needs plain language review, Needs alt text, Needs color contrast check, Accessibility compliant. They turn cleanup into a filterable to-do list.
Find out what you actually have
You can't organize what you haven't counted. Work through the five steps, then use the worksheet to score each item and get a recommended action.
Audit worksheet
Items save in this browser only. Copy the CSV to move them into your shared sheet.
Scoring rules
| Value | What it means | Action |
|---|---|---|
| High | Used often, accurate, reusable | Keep and migrate |
| Medium | Useful but outdated or duplicated, and fixable | Update, then migrate |
| Low | Redundant, unused, or irrelevant | Archive or delete |
Anything untouched for 18 months drops one level unless someone vouches for it. Duplicates always need a merge before they move.
Build components that travel
Structured once, reused everywhere. Each template lists what the piece must contain and the metadata that makes it findable. Copy any outline straight into your doc or library tool.
Twelve weeks, five phases
Organize before you shop for a platform. Most of the value comes from structure and ownership, and both carry over to whatever tool you land on. Check off tasks as you go.
Short on time? Run the 9-week version: fold Phase 3 into Phase 2 and populate only the components shared by four or more teams.
Keep it true
Libraries rot quietly. Governance is the routine that stops it: named owners, set review dates, and a clear path from draft to archive.
Who does what
- Executive sponsor
- Protects the time, approves scope, breaks ties.
- Library lead
- Owns the taxonomy, runs the audit, trains teams, reports on use.
- Content owners
- One per department. Curate, update, and retire their team's content.
- Contributors
- Anyone who creates content. Uses templates, tags correctly, flags what's stale.
- IT partner
- Sets permissions and connects the library to other systems.
Review cadence
Rolling it out
Engage early. Check in with every department so the structure reflects how they actually work.
Train hands-on. Show people how to search, reuse, and contribute. Record a short walkthrough.
Update in the open. Short async summaries: progress, blockers, what's next.
Name a help desk. One point of contact for questions, plus a feedback form that someone reads.
Measure what matters
Fewer “can't find it” requests. Track the drop.
Usage by item. Monthly report on most- and least-accessed content.
Freshness. Share of published items inside their review window.
Satisfaction. Target 8 out of 10 in a quick pulse survey.
Library tool setup checklist
Works for most knowledge and response-library tools. Check off as you configure.
Get to yes
Leaders fund what they can see. Show the cost of the current mess, the return on fixing it, and a small, specific ask.
The problem
The payoff
For leadership
Faster proposal cycles. Less rework. Consistent, compliant messaging. A foundation that scales with growth and feeds automation later.
For growth and business development
Proof points, bios, and past performance ready to drop into proposals. Win themes backed by evidence. Faster response to opportunities.
For every team
One place to look. Clear owners. Templates that adapt to the audience without breaking the source.
For new hires
A clear path to what they need. Ramp-up one to two weeks faster.
Targets
The ask
One dedicated lead at half time for twelve weeks. No new platform required to start. Approval to add the library to operations priorities.
A frame leaders already trust
IT teams run on shared standards for how services get designed, maintained, and retired. Treat knowledge the same way. Standard practices, a defined lifecycle, clear governance, and reusable components that serve many teams at once. Same discipline, different asset.