At one of the plants I oversaw, the entire quality department was one person, and that person also ran second shift and kept the label printer alive. If your shop looks like that, the documentation advice written for companies with a dozen people in quality doesn't fit you, and pretending it does is how a binder ends up on a shelf.
You need a smaller system, built on purpose, that one busy person can maintain without giving up a day a week to it. Here's what belongs in it.
What is the minimum documentation a small manufacturer needs?
Five things cover most small shops: a short list of the processes that matter, one procedure or checklist for each critical process, a way to control which version is current, a record that the work was done, and a note of who owns each document. Everything beyond that has to earn its place.
Notice what isn't on the list. You don't need a 60-page quality manual, a procedure for every task, or a policy for every possible failure. Those documents are expensive to write and more expensive to keep true, and a document that has drifted from the floor does more damage than no document at all, because people trust it.
The test I used as a CFO was blunt. If this document vanished tomorrow, what would break, and how soon? If the answer was "nothing, for months," it went to the bottom of the list. If the answer was "we'd ship a bad part to a customer who audits us," it went to the top.
Which processes should you write down first?
Start with the processes where a mistake reaches a customer, injures a person, or costs real money: final inspection, anything safety-related, setup for your most profitable product, and any step you've already had to redo. Rank by consequence, not by how easy the document is to write.
A useful exercise takes about an hour. Put the process names on index cards, then sort them into three stacks: the work that would hurt you if done wrong, the work that only slows you down, and the work everyone already does the same way. Write the first stack. Check the second stack against your scrap and rework numbers. Leave the third alone.
One failure mode shows up again and again. The owner asks the most articulate person to write the procedures, and that person documents what they find interesting, usually the elegant, rare tasks. Meanwhile the dull daily steps, the ones a new hire gets wrong in week two, stay in somebody's head. If you want the longer version of why this happens, why your best employee writes the worst documentation covers it.
How do you keep documents current when nobody owns quality?
Give every document one named owner, one effective date, and one official location, then review each on a fixed schedule tied to something that already happens, like a customer audit or the annual equipment service. Without a schedule, nobody reviews anything.
Small shops usually skip this part, and then the system rots. The fix doesn't need software. A shared folder, a naming convention, and a simple index sheet will do the work for a shop with fewer than a few hundred documents. I laid out the four controls in document control without buying software, and they hold up fine at your scale.
Ownership matters more than the tool. When a procedure has no name attached, nobody updates it when the machine changes. When it has a name, the person who runs that machine gets a quiet nudge every time the work shifts. Pick owners from the floor, not the front office, because they're the ones who notice first.
Tie reviews to a trigger. A new piece of equipment, a customer complaint, a changed supplier, or a near miss should each send someone back to the relevant page. That is cheaper than a calendar full of reviews nobody has time for, and it catches the changes that matter.
What do customers and auditors expect from a company your size?
They expect your documents to match what you actually do, and they expect you to produce records quickly. They don't expect a quality department. Size changes the volume of paperwork, not the question being asked.
Auditors ask three things in some order: what do you say you do, do you do that, and can you prove it. A two-page procedure that your operator follows beats a forty-page one nobody has read. When I sat through audits from the company side, the findings that hurt weren't thin documents. They were documents that described a process the floor had abandoned two years earlier.
If a customer or a registrar requires a particular standard, read what it actually demands before you hire anyone to build a system around it. The requirements are often shorter than the consulting proposal suggests. Will your SOPs hold up to an audit walks through what an auditor opens first.
The honest answer to the skeptical owner, who says "we're too small for this," is that you're right about the volume and wrong about the need. A shop of fifteen people still loses a customer over one escaped defect, and a short, accurate procedure is the cheapest insurance you can buy.
What does it cost to keep a small system alive?
Plan on a few hours a month of someone's time once the system exists, plus a modest effort each time equipment, product, or suppliers change. The building cost is a one-time project. The upkeep is what decides whether it survives.
Most owners budget for the writing and forget the keeping. A system that needs a day a week will be abandoned by spring, so design it to fit the hours you'll really have. That usually means fewer documents, shorter documents, and checklists in place of narrative where the task allows it. How to write work instructions for the floor shows how short a useful one can be.
If you inherit a pile of old procedures, don't start by rewriting them. Sort them first. What to do with 200 outdated SOPs gives the triage method, and it usually shrinks the job by more than half.
When does outside help make sense?
Outside help makes sense when the people who know the work have no time to write it down, when a customer deadline is fixed, or when you need documents that read cleanly to someone who has never seen your floor. It doesn't make sense for work you can finish yourself in a free week.
A technical writer earns the fee by doing what your one overextended person can't: watching the work, asking the questions an outsider asks, and turning what they learn into pages your operators will actually use. My background is in running the operations and writing the procedures myself, which is why I start on the floor and not at a desk. You can see how I approach it on the technical writing page, and the FAQ covers how projects are scoped. Pricing is quoted after a discovery call.
If you'd like to talk through which documents your shop truly needs, book a discovery call. Bring the list of processes that worry you most, and we'll start there.
Frequently asked questions
What documents does a small manufacturer actually need?
A short list of your key processes, one procedure or checklist for each process where a mistake reaches a customer or hurts someone, a way to control which version is current, records showing the work was done, and a named owner for every document. Add more only when a customer, regulator, or scrap number demands it.
Can a small shop pass an audit without a quality department?
Yes. Auditors check that your documents match what you do and that you can produce records quickly. A short procedure the operator follows beats a long one nobody has read.
How much time does it take to keep the documentation current?
Once the system exists, plan on a few hours a month plus a short review whenever equipment, product, or suppliers change. If upkeep needs a day a week, the system is too big for your shop.
When should I hire a technical writer?
When the people who know the work have no time to write it down, when a customer deadline is fixed, or when the documents need to read clearly to someone who has never seen your floor. Pricing is quoted after a discovery call.
