Problems we solve

The warning signs of an underused QMS

QMS drift rarely announces itself as a neat “QMS problem.” It appears as duplicated work, inconsistent decisions, outdated procedures, audit findings, project failures and excessive administrative effort.

Inaccurate

It no longer reflects how work actually happens, so people stop trusting it.

What it looks like: Documented steps refer to systems, roles or suppliers that have changed. Teams keep private versions of the 'real' method alongside the official one.
Why it happens: Change happens continuously, while QMS maintenance happens in bursts. Nobody owns the routine of keeping content aligned to reality.
The operational consequence: Once people find one thing that is wrong, they discount the whole system. Trust falls faster than accuracy does.
How we diagnose it: We compare documented processes with actual practice in a sample of high-traffic areas and look at how, and how often, content is reviewed.
Normally relevant service: Managed QMS Service

Incomplete

Important answers are missing, so people still have to ask someone, rely on a local document or guess.

What it looks like: Coverage is strong where an audit once focused and thin everywhere else. Common questions are answered by a colleague, not the QMS.
Why it happens: Content is created around compliance milestones rather than around the questions people actually ask at work.
The operational consequence: Critical knowledge stays tacit and locally held, and leaves the organisation when people do.
How we diagnose it: We map the questions people need answered against what the QMS actually contains, and identify the gaps that force workarounds.
Normally relevant service: Embedded QMS Support

Incomprehensible

It is written for compliance rather than for the person trying to perform the work.

What it looks like: Long documents in clause language, with the operational instruction buried several pages in.
Why it happens: Content is written to satisfy an assessor rather than to be used at the point of work.
The operational consequence: People read it once, find it hard work, and default to asking a colleague instead.
How we diagnose it: We review sample content for clarity, structure and task orientation, and observe how easily a non-specialist can follow it.
Normally relevant service: Embedded QMS Support

Unfindable

The answer may exist, but people cannot locate it quickly enough to make the QMS useful.

What it looks like: Search returns too much or nothing useful. Navigation mirrors the organisation chart rather than the flow of work.
Why it happens: Structure follows document ownership rather than the end-to-end processes people are trying to perform.
The operational consequence: The system loses to the fastest available answer, which is usually a colleague or a local file.
How we diagnose it: We test realistic user journeys: can a named role find the right answer in a reasonable number of steps?
Normally relevant service: Adoption Diagnostic

Unembedded

The system is available, but leadership, communications and everyday working practices do not make its use habitual.

What it looks like: The QMS is referenced at induction and at audit, and rarely in between. Managers do not point to it when answering questions.
Why it happens: Adoption is treated as a launch event rather than an ongoing behaviour supported by leadership.
The operational consequence: Usage decays quietly, and the investment in the system stops returning value.
How we diagnose it: We assess communications, leadership reinforcement, role-level expectations and whatever usage data exists.
Normally relevant service: QMS Adoption Programme

What usually prompts the call

These situations bring the cost of drift into view. They are symptoms of the five causes above rather than separate problems, and each points towards a different first intervention.

Quality administration is consuming too much time.
The QMS is maintained but rarely used.
A safety or quality incident exposed outdated working practices.
A major project failure exposed inconsistency in how work was performed.
A customer or procurement process requires stronger evidence of quality management.
Employees cannot quickly find reliable answers.
An audit revealed that documented processes and actual practice have diverged.
Leadership wants a return on its investment in the QMS.

We cannot promise that any system eliminates mistakes or that adoption is guaranteed. What we can do is find the specific reasons your QMS is not being used, and address them in a prioritised order.

Ready to talk about your QMS?

Whether your QMS is drifting, you are preparing for an ISO audit, or you want practical help with your process content, the fastest way forward is a conversation.

Let's talk