In the weeks before an audit, many organizations go through the same ritual. Someone searches shared drives for records. Missing signatures are chased. Forms are completed from memory. Spreadsheets are updated all at once.

This effort is a signal. It usually means evidence is being treated as something to assemble for the auditor, rather than something created as the work is done.

Evidence created after the event is weaker, takes more effort and can be misleading. It can also hide the very problems the system is meant to reveal.

Why evidence matters beyond the audit

Records are not only for auditors. Good evidence helps the business:

  • confirm that a product or service met requirements before it was released;
  • trace what happened when a problem is found, and which other products may be affected;
  • show customers that their requirements were met;
  • see trends, recurring problems and opportunities to improve;
  • make decisions based on facts rather than memory.

When evidence is reliable and easy to find, it becomes useful long before anyone asks to see it.

Design evidence into normal work

The most reliable evidence is created at the moment the work is done, by the person doing it, as a natural part of the task.

Some practical ways to achieve this:

  • Use what you already have. A completed traveler, an approved order in your ERP system, an inspection result on the drawing or a dated photo may already be all the evidence you need.
  • Capture it at the point of work. Make it easier to record a result immediately than to remember it later.
  • Record what matters. Capture the result of a check or decision that matters, not every step of every task.
  • Make it clear what is expected. People should know what needs to be recorded, where and when, and what an acceptable result looks like.
  • Keep it findable. Agree where records are kept, how they are identified and how long they are retained.

Check that evidence is genuine

A record is only useful if it accurately reflects what happened. Warning signs may include multiple entries completed in one batch after the work, unexplained identical timestamps, repeated results that do not reflect the process, missing traceability or records completed by someone who did not perform or verify the activity. None of these signs proves by itself that a record is false; each should prompt a proportionate check of the process, the record’s origin and the available supporting evidence.

Investigate the circumstances before drawing conclusions. The cause may be an impractical form, a poorly designed capture process, unclear expectations, retrospective completion or deliberate misrepresentation. Address the underlying issue, protect the integrity of the evidence and take appropriate action based on the facts. Improving the process does not remove the need to address intentional falsification when it is established.

What ISO 9001 expects

If your organization is pursuing ISO 9001 certification, the standard requires you to retain documented information as evidence in specific areas, such as monitoring and measurement results, competence, product release and nonconformities, and to protect it from loss or unintended change.

The auditor will look for evidence that your system is operating as planned and achieving results. Evidence that has been created naturally over time is far more convincing than records assembled in the weeks before the visit.

The bottom line

If you need to search for proof that your system works, the evidence is not yet part of the process. Design records into the normal flow of work, keep them simple and findable, and use them to manage the business. Then audit preparation becomes much simpler, because the evidence is already there.

Want a starting view of how well your system produces reliable evidence today? The free QMS Readiness & Maturity Scorecard gives you an initial picture of how well your system produces reliable evidence. Use it as a starting point, then validate the results against actual work and records. QMS Made Real™ helps organizations design practical arrangements in which controls, responsibilities and evidence are built into everyday operations rather than assembled for an audit.