There are two ways to get certified. One produces a working management system. The other produces a binder. Both pass the audit. Only one is worth what it costs.
The binder problem
The pattern is familiar. A consultant supplies a documented system written for a generic company. Staff sign that they have read procedures describing work they do not recognise. The certificate arrives, goes on the wall, and the organisation carries on exactly as before — now carrying the extra cost of maintaining a fiction each surveillance visit.
The tell is simple: if nobody consults a procedure between audits, the system is decorative.
Write down what you already do
Start from the actual process, not the standard. Sit with the people doing the work and document the sequence as it happens, including the informal checks experienced staff perform without being asked. Those checks are usually your real quality controls, and they are the part that disappears when an experienced person leaves.
Then compare that description against the standard’s requirements and close the genuine gaps. You will find fewer than you expect, and the ones you find will be worth closing on their own merits.
Make the audit boring
A system that reflects reality makes certification uneventful. Records exist because the work generates them, not because someone assembled them in advance. Staff can describe what they do, which is all an auditor is really testing.
Two habits keep it alive: treat nonconformities as information rather than failures, so people report them; and hold the management review as a real meeting about real data, rather than minutes written to satisfy a clause.
The point of the certificate is that a customer can rely on your consistency. That is only true if the system underneath it is the one you actually use.