Mapping Your QMS: Where Does Your Documentation Actually Live?

If I asked you right now, “Where is your validation master plan?” could you answer in under 10 seconds?

What about your critical process SOPs? Your completed batch records from two years ago?

If you hesitated, you’re not alone. One of the most common findings during FDA inspections is the inability to quickly locate documentation. Not because it doesn’t exist—but because no one can find it.

During a recent FDA inspection at a biologics manufacturer, an inspector requested a validation protocol. What should have taken 2 minutes took 45 minutes and involved three people searching network drives, SharePoint sites, and filing cabinets.

The protocol existed and was compliant. But the organization couldn’t demonstrate control over their documentation system. The result? An observation citing inadequate document control.

Common Documentation Mapping Failures

The “Shared Drive Graveyard”: A network drive with 847 folders, 15 naming conventions, and files from 2003 mixed with current SOPs. No one knows what’s current or where anything lives.

The “It’s Somewhere in SharePoint” Problem: Half your documents migrated to the new system, a quarter remain in the old one, and the rest are scattered. Everyone searches three places before finding anything.

The “Only Karen Knows” Risk: One person has a mental map of your entire documentation system. When she’s out, everything grinds to a halt.

The “Hybrid Chaos”: Some records are in filing cabinets, some are scanned PDFs, some exist in both places. During inspections, you’re pulling from multiple locations hoping you grabbed the right version.

Building Your Documentation Map

Your QMS follows a hierarchical structure—Quality Manual at the top, then SOPs, then Work Instructions and Forms, and finally Records at the base. Each level should have a clear “home” that everyone knows.

Here’s how to fix it:

Define storage locations for each document type: Where does it live? Who can access it? How long is it retained?

Create retrieval procedures specific enough that a new employee or inspector could follow them: “Batch records are stored in SharePoint > Manufacturing > Batch Records > [Year] > [Product Code].”

Establish naming conventions that include document type, subject, version, and status. Example: SOP-CleaningProcedures-v3.2-APPROVED

Assign ownership so someone is responsible for maintaining organization, version control, and access management.

The Inspection Readiness Test

Can anyone on your quality team retrieve a randomly selected document in under 2 minutes? Can a new employee find what they need using only your documented procedures?

If not, your documentation map needs work.

Start small. Pick one document category—maybe SOPs or batch records—and map it completely. Document where it lives, how it’s organized, and who’s responsible. Then expand to the next category.

Within a few months, you’ll transform from “I think it’s somewhere in the Quality drive” to “It’s in SharePoint > QMS > SOPs > Equipment, version 2.1.”

That’s the difference between inspection anxiety and inspection confidence.