Skip to content

Quality system

Quality management system, audits and ISO 9001

I build and reorganise quality systems so that they support the work instead of blocking it, while still holding up to a customer audit. Documentation has to describe the process that actually runs — otherwise you end up with a second set of rules for the auditor.

When it makes sense to get in touch

  • The procedures exist, but people work differently and everyone knows it.

  • A customer or certification audit is coming and nobody knows where the weak spots are.

  • Documentation has grown to a size where nobody reads it.

  • Internal audits happen to tick a box, not to find anything.

  • Every site does the same thing differently, so results cannot be compared.

Scope of work

System

  • Reviewing the system as it actually is: what works, what exists only on paper
  • Trimming controlled documentation to a size that can realistically be maintained
  • Standardising processes across lines and sites
  • Tying the system to real metrics rather than a separate set kept for audits

Audits

  • Internal audits run so that they actually find something
  • Preparation for customer and certification audits
  • Handling nonconformities: from the record, through analysis, to confirmed effectiveness
  • Preparing the team for the conversation with an auditor

Compliance

  • Alignment with ISO 9001 and with additional customer requirements
  • Reconciling customer requirements when they contradict each other
  • Maintaining the system after certification so it does not decay before the next audit

What you are left with

  • A quality system documented to match how the work actually happens

  • Tidied controlled documentation with a clear owner for every document

  • An internal audit plan and trained auditors

  • A nonconformity list with actions and confirmed effectiveness

How we work together

  1. Understanding the problem and its context

    Talking to the team and management, mapping the constraints: people, systems, deadlines and budget.

  2. Analysing the data and the current process

    Mapping how the process actually runs, not how the procedure describes it.

  3. Setting priorities and a plan

    What gives the largest effect for the smallest cost, in what order, and who owns what.

  4. Delivering the solution

    Working with users, piloting, training, correcting based on what practice shows.

  5. Measuring effectiveness and stabilising

    Checking whether the change actually worked, then locking it into the standard.

Frequently asked questions

Do you prepare organisations for ISO 9001 certification?

Yes. As an ISO 9001 internal auditor I prepare the system and the team for the audit. I do not carry out certification itself — that is the certification body's job, and it is right that those roles are separate. My work ends when the system is ready and the team knows how to talk about it.

We are certified, but the system helps nobody. What can be done?

That is the most common case. It usually means the documentation describes a process invented for the audit rather than the one performed on the floor. I start by putting the two side by side and deciding which one changes — sometimes the process, sometimes the description. What matters is that one set of rules is left afterwards, not two.

Can documentation be reduced without losing compliance?

Usually yes. The standard requires control over documented information, not volume. Most of the growth comes from documents added after every nonconformity and never removed. A review asking who uses each document and for what typically shortens things considerably.

Do you audit across multiple sites?

Yes, and that is where the lack of standardisation usually surfaces: the same process described three different ways at three sites, so the results cannot be compared. Fixing that typically delivers more than the audit itself.

Tell me what you are working on

Describe what is happening in the process and what you have already tried. I reply within one business day.