Use cases by role
If you run quality single-handed
A system designed for a department, held up by one person who also does three other jobs.
In most mid-sized companies, quality is one person. Often the same one covering health and safety, environment and part of purchasing. The system, meanwhile, is written as if a team stood behind it — and that gap is to be managed, not denied.
Where the time goes, and what can be taken off your plate
| Task | Who can really do it | What is left for you |
|---|---|---|
| Chasing supplier documentation | The system, with alerts | Looking at the exceptions |
| Remembering expiry dates | The system | Deciding what to do when they fire |
| Recording what happens on the floor | Whoever is on the floor | Making it easy to record |
| Analysing causes and closing actions | You | The one thing that cannot be delegated |
| Preparing the audit | It prepares itself if the above works | Reviewing and presenting |
Important
The trap of the job is the third row, and it is hard to admit: **when recording something is awkward, you end up doing it yourself, late and second-hand**. Someone tells you on Thursday what happened on Monday and you write it down from their memory. That record exists, but it no longer describes what happened — it describes what is remembered three days later. Lowering the friction of recording — two fields and a photo from a phone — is not about comfort: it is what makes the data real.
The three things that hold the system up when there is nobody else
Watch out
There is something about the job nobody explains at the start: **if the system works, it becomes invisible, and so does your work**. Nobody thanks you for the audit with no findings or the certification renewed without drama. It is worth keeping a short list of what was avoided — what was caught in time, what never reached a client — because at the annual review that list is the only thing translating your work into something management can see.
What to do when you genuinely cannot keep up
- 1
Prioritise by risk, not by standard
What can harm a client comes before what a document requires.
- 2
State in writing what will not get done
An email to management turns an omission into their decision.
- 3
And take what slipped to the annual review
It is the only forum where that can turn into resources.
Worth knowing
What exactly your certification scheme requires, and what latitude each requirement allows, is set by the applicable standard and your auditor. **Check with them or your adviser**; here it is about holding the system up without burning out the person who runs it.
›Can it all be run without help?
It can be held up; doing it all by hand cannot. The difference is what is automated.
›What if nobody records anything?
It is nearly always friction, not indifference: count the steps to record.
›How do I ask for more resources?
With what was avoided and what went undone, in writing, once a year.
A real case
The situation
A quality manager logs floor incidents days later, from hearsay.
What you do
- Reduces recording to two fields and a phone photo by whoever sees it
What you get
Incidents get logged the same day and the analysis starts from what happened, not from memory.
The situation
One person runs quality for the whole company.
What you do
- Automates the requests that repeat
What you get
Time goes on reviewing.
The situation
An audit arrives and everything has to be prepared.
What you do
- Keeps the file current through the year
What you get
Preparation is a review.
The situation
Certificates expire unnoticed.
What you do
- Records expiries with warnings
What you get
Renewal happens with time to spare.
The situation
They go on holiday and everything stops.
What you do
- Keeps the file accessible to the team
What you get
The work does not depend on one person.
The situation
Suppliers are chased one by one.
What you do
- Requests and chases automatically
What you get
Chasing stops taking up the week.
This article answers
- I am the only quality manager
- running iso 9001 alone
- no time to maintain the quality system
- quality in a small company