At the manufacturing company I ran finance for, I once watched two shifts catch different defects on the same part because they were running inspection off two different revisions of the same procedure. Nobody had broken a rule. Nobody owned the document, so every laptop copy counted as official, which meant none of them were. That's the whole problem document control exists to solve, and it doesn't take software to solve it.
What does document control actually mean?
Document control means everyone working from a given procedure is working from the same version of it, and you can prove which version that was on any date you're asked. It isn't a filing system, and it isn't a compliance exercise you run to make an auditor happy. It's the answer to one practical question: if two people open the same document right now, on two different machines, do they see the same words?
At most small and mid-size manufacturers, the honest answer is no. Somebody printed a copy eighteen months ago and taped it above a workstation. Somebody else has a PDF saved to their desktop from before the last revision. A supervisor keeps the "real" one in a binder in the office, updated whenever she remembers to swap the page. All four people believe they're compliant. Three of them are wrong, and there's no way to tell which three without checking dates nobody wrote down.
What are the four controls that actually do the job?
Four elements make a document control system work: a version number that changes every time the content changes, a named owner accountable for that document, a printed effective date, and one official location everyone is trained to check before they trust a copy. Software can track these for you. It can't replace them, and a spreadsheet with all four is a functioning system while software missing any one of them isn't.
The version number doesn't need to be elaborate. A whole number that increases by one at every real revision does the job: Rev 4, not Rev 3.2.1.b. The owner is a name, not a department; "Quality" isn't accountable for anything, but Maria is. The effective date sits at the top of the page in the same spot on every document, so a reader can tell at a glance whether what they're holding predates the last change. And the official location is wherever you tell everyone, in writing, that the current version lives: a specific shared drive folder, a specific binder, a specific page on your intranet. Not "wherever's easiest."
On the page itself, this is usually a single line at the top or bottom, something like:
- Document: Incoming Inspection Procedure
- Owner: Maria Chen
- Rev: 6
- Effective: 03/14/2026
Four short fields, and an auditor, a new hire, or a second-shift supervisor can all answer the same question from the same page: is this the version I'm supposed to be using right now.
Where should the official copy actually live?
The official copy lives in exactly one place, and every other copy (printed, saved locally, emailed as an attachment) is understood by everyone to be uncontrolled the moment it leaves that place. A shared drive folder with edit access locked to the document owner works. So does a binder in a specific office, if you're small enough that paper is still how the floor reads instructions. What doesn't work is "check with Maria" as the retrieval method, because Maria goes on vacation and the procedure doesn't stop running.
Printed copies are where this breaks down first. A page taped to a machine is useful, and the moment it's printed, it starts drifting out of date. The fix isn't banning printouts. Floors need paper. It's stamping every printed page "UNCONTROLLED COPY, VERIFY CURRENT REVISION BEFORE USE" and training people to check the official source before they trust what's on the wall, especially before an inspection or an audit like the ones described in what ISO 9001 actually requires you to document.
How do you version documents without buying software?
A simple numbering convention plus a one-page changelog does what document control software does, at zero cost, for a company running fewer than a few hundred controlled documents. Number every document with its own revision count. Keep a single changelog page, one line per revision: date, document, what changed, who approved it. That log is what an auditor actually wants to see: not proof you own software, proof you can account for every change.
A changelog line doesn't need to be more than a sentence:
- 03/14/2026, Incoming Inspection Procedure, Rev 6, added second gauge check per customer complaint 2026-11, approved M. Chen
One line answers three questions an auditor asks in sequence: what changed, why, and who signed off. A spreadsheet with thirty rows like that one is a complete revision history. A binder full of undated redlines isn't, no matter how thorough the redlines are.
The changelog is also where document control and "who's allowed to change a procedure" meet, and they're not the same question. Anyone can suggest a change. Only the named owner approves one, and the changelog is where that approval gets a timestamp instead of living in someone's memory.
What do you do when you find an old copy still in use?
Treat it as a retrieval problem, not a discipline problem: find every copy in circulation, replace it with the current revision, and log why the old one survived instead of assigning blame. I've watched managers turn this into a lecture about carelessness, and the lecture accomplishes nothing except teaching people to hide the copies they're not sure about instead of asking.
The better move is a standing rule: any employee who finds an undated or uncontrolled copy hands it to the document owner, no explanation required, and gets the current version back within the day. Do that consistently for a few months and the printed-page drift mostly stops on its own, because people learn that flagging a stale copy costs them nothing and using one by accident does.
Do you need software for this, or can you build it yourself?
Most companies under a few hundred controlled documents don't need document control software; they need the four controls above, applied consistently, and a person accountable for enforcing them. Software earns its cost once you're managing distribution to multiple sites, tracking read-and-acknowledge training records at scale, or a customer specifically requires an electronic quality management system as a condition of doing business. Below that line, a shared drive, a changelog, and clear ownership will pass the same audit a platform costing thousands passes, because auditors check whether your documents match what you actually do, not what system hosts them.
If you're at the size where software makes sense, the harder problem usually isn't the software. It's that nobody's actually written the SOPs the software is meant to control, and a platform can't invent content that doesn't exist yet. Common questions clients ask before we start are in the FAQ. I write the procedures small manufacturers need before that question is even worth asking, and a short call is the fastest way to find out whether this is a spreadsheet fix or an actual project. Book one here.
Frequently asked questions
Do I need document control software to pass an ISO audit?
No. Auditors check whether the current, correct version of each procedure is being followed and whether you can account for past revisions. A version number, a named owner, an effective date, and one official location satisfy that for most small and mid-size manufacturers without buying anything.
How many versions of a procedure should be in circulation at once?
One. Every other copy, whether printed, saved locally, or emailed, should be treated as uncontrolled the moment it leaves the official source, and replaced the moment someone finds it still in use.
Who should own document control at a small company?
One named person, not a department. Quality or operations can house the role, but the person's name needs to be on it, because a title isn't accountable for approving revisions and a person is.
What's the difference between document control and version control?
Version control is the numbering and changelog. Document control is the whole system around it: who owns each document, where the official copy lives, and how outdated copies get found and replaced. Version control is one of its four required parts.
