How to Write QMS Procedures People Actually Follow

Most organizations have at least one procedure that nobody reads.

It is often long, written in formal language and stored somewhere few people visit. It describes how the work was meant to be done when it was written. Meanwhile, the people doing the work rely on experience, a marked-up drawing, a note taped to the machine or a quick question to a colleague.

When this happens, the procedure is not supporting the work. It is competing with it. And during an audit, the gap between what is written and what is done becomes a finding.

Start with who will use it

A useful procedure is written for the person who needs it, at the moment they need it.

Before writing, ask:

Who will use this, and how experienced are they?
Where will they use it: at a desk, on the shop floor, at a machine?
What decisions or steps are most likely to go wrong?
What do they need that they cannot already be expected to know?

A procedure for a new operator setting up a critical job will look very different from one describing how managers review customer contracts. Both can be appropriate.

Write down what is actually done

The best starting point is the work itself. Observe the task, speak with the people who perform it and identify the checks and judgements experienced employees make, including those they may not consciously describe.

Then compare current practice with customer and other applicable requirements, intended process outcomes and identified risks. Where the practice is sound, document or support it in a useful form. Where it is inadequate, improve and approve the method before establishing the revised information as the expected way of working. Documenting an ineffective practice simply makes the weakness more formal.

Writing an ideal process that nobody follows only creates a document that will not hold up under audit or under pressure.

Keep it as simple as the work allows

Some practical principles help:

Use plain language. Write the way people speak at work, with clear actions: "Check the drawing revision against the order."
Focus on what matters. Give most attention to the steps where mistakes are likely or costly, and to what must happen when something is not right.
Use the right format. A flowchart, checklist, table, photo or short video may work better than paragraphs of text.
Put it where the work happens. A one-page instruction at the workstation is often more useful than a complete manual on a shared drive.
Refer rather than repeat. If information already exists in a drawing, a specification or a system, point to it rather than copying it.

Not everything needs a procedure

Documentation matters when it helps people perform the work consistently, reduces the risk of error or supports training. It does not need to describe every task in detail.

The level of detail depends on the complexity of the work, the consequences of getting it wrong and the competence of the people doing it. An experienced machinist may not need a procedure explaining how to use a micrometer, but may need clear instructions on which features to measure, which approved criteria apply, when to record results and what to do if a measurement falls outside tolerance.

If your organization is pursuing ISO 9001 certification, the standard requires documented information to the extent necessary to support the operation of its processes and provide confidence that they are carried out as planned. It also specifies particular documented information that must be maintained or retained. The organization determines the appropriate form and level of detail within those requirements. Information it relies on must be controlled, available where needed and kept current.

Test it with the people who use it

Before releasing a procedure, ask someone who does the work to follow it. Where they hesitate, ask a question or do something different, the procedure needs attention.

After release, keep listening. When people work around a procedure, it usually means the procedure no longer matches the work, or never did.

The bottom line

A good procedure helps people get the work right. It is clear, focused on what matters, available where the work happens and consistent with what is actually done. Documentation that supports the work will be used. Documentation that competes with it will be ignored. The right documentation is the information people need to perform and control their work reliably.