Guide
ISO 9001 Continual Improvement Through Process Automation
Clause 10.3 asks for continual improvement. Most SMEs show the auditor a form. An automated process with a log and an SOP is stronger evidence, and it saves staff hours every week. Which clauses it satisfies, four examples, and how to present it at the surveillance audit.
7 min readISO 9001 clause 10.3 says the organisation shall continually improve the suitability, adequacy and effectiveness of its quality management system. Automating a process is one of the clearest ways to do that. The manual steps go, the errors go with them, the process runs the same way every time, and the system produces its own records. For most Singapore SMEs it is the best continual improvement evidence they will ever put in front of an auditor.
Key takeaways
- Continual improvement is a requirement, not a suggestion. Auditors ask what improved since last year and what proves it.
- An automated process gives before and after numbers, a log, and a controlled SOP. That covers clauses 9.1, 7.5 and 10.3 in one project.
- Start with the process that produces the most errors or the most hours. Quotes, orders, supplier invoices and enquiries are the usual four.
- Record it as a quality objective, measure it, and table it at management review. Then it counts.
- Automation projects are an EDGE grant activity from 30 September 2026. ISO consultancy itself is not.
The clause 10.3 problem
Every surveillance audit includes the same question. What has improved since the last audit, and how do you know?
Most SMEs answer with a corrective action form, a training record, or a new procedure. These are fine. They are also weak. They show that something was written, not that something got better.
The auditor is looking for three things.
- A change to how work is done, not only to a document.
- Numbers before and after, from clause 9.1 monitoring.
- Evidence it stuck, meaning the new way is still running months later.
Why automation is strong evidence
An automated process produces all three without anyone preparing for the audit.
| What the auditor wants | What an automated process gives |
|---|---|
| A real change to the process | Manual steps removed. The process map shows the old flow and the new flow. |
| Before and after numbers | Time per quote, errors per month, missed enquiries. Counted before, counted after, on the same basis. |
| Evidence it is still running | The log. Every run is timestamped. The auditor can pick any week. |
| Controlled documented information | One SOP per workflow, with an owner, a version and a review date. |
| Competence | Training record for the workflow owner, and the session for the team. |
Which clauses an automation project touches
One well documented workflow supports more of the standard than most SMEs realise. Use this table when you write it up.
| Clause | Requirement | How the automation satisfies it |
|---|---|---|
| 4.4 | Processes, their inputs, outputs and interactions | The mapping session produces the current and future process map with inputs and outputs named. |
| 6.1 | Actions to address risks and opportunities | The risk of a missed enquiry or a retyped order is named, and the automation is the action. |
| 6.2 | Quality objectives | "Quotes out same day" or "zero retyping errors" becomes a measurable objective with a target. |
| 7.1.3 | Infrastructure, including software | The tools and connectors are listed as infrastructure, with an owner. |
| 7.2 | Competence | Training record for the workflow owner and the team session. |
| 7.5 | Documented information | One SOP per workflow, controlled, versioned, in the shared drive. |
| 8.2.1 | Customer communication | Enquiries acknowledged in seconds and logged. Nothing is lost in a phone. |
| 9.1 | Monitoring, measurement, analysis, evaluation | The automation log is the measurement. Monthly counts come out of it without anyone compiling. |
| 9.3 | Management review | Process performance and improvement results tabled from the log. |
| 10.2 | Nonconformity and corrective action | When a step fails, the workflow stops and alerts the owner. The failure is logged, which is the NCR trail. |
| 10.3 | Continual improvement | The project itself, with before and after evidence. |
Four examples that pass
These are real builds, from our own businesses and our clients. Names are withheld. The numbers are the ones we would show an auditor.
Enquiry to logged lead. Web, Facebook and WhatsApp enquiries are read into one tracker with an alert to the owner. Before: enquiries sat in one person's phone, some never answered. After: 100% logged, first reply in seconds. Clauses 8.2.1, 9.1, 10.3. Objective: no enquiry unanswered past one working day.
Supplier invoices to accounting software. Bills are read, coded and drafted for approval. Before: half a day a week of keying, with coding errors found at month end. After: staff approve instead of typing, errors caught at entry. Clauses 8.4 supplier control, 9.1, 10.2. Objective: month end closed within 5 working days.
Order message to draft order and billing. Orders sent as chat messages become draft orders with stock reserved and a billing message back. Before: retyped, wrong quantities, oversells. After: one record per order, stock reduced once. Clauses 8.2, 8.5.1 controlled production and service provision, 9.1. Objective: zero wrong-quantity shipments.
Incident and risk assessment drafting. A photo and three lines from the supervisor become a draft incident report or a draft RA in your template, for the competent person to review and sign. Before: written from memory a week later. After: same-day drafts, complete fields. Clauses 7.5, 10.2, and for ISO 45001 clauses 6.1.2 and 10.2. Objective: incident reports raised within 24 hours.
How to present it at the surveillance audit
- Record it as a quality objective under 6.2 before you build, with the baseline number.
- Keep the before and after on one page. Process map old and new, the two numbers, the date it went live.
- Show the log, not a screenshot. Let the auditor pick a week.
- Table it at management review as process performance and as an improvement result. Minute the decision on the next workflow.
- File the SOP and the training record where your other controlled documents live.
Done this way, one automation project answers the continual improvement question for the year, and gives you the next one for the year after. See what happens during an ISO audit for how the surveillance visit runs.
How we do it
We are the same consultant on both sides. We prepared your ISO 9001 system, so we know which process the auditor will ask about, and we build the automation so the records fall out of it. See business process automation for SMEs for how a project runs, and our business automation page for the builds already live.
Automation and digitalisation projects are an EDGE grant activity from 30 September 2026, with support of up to 70% for SMEs. ISO consultancy itself has historically not been grant supported. We check the live activity list. See the SME grants guide.
Frequently asked questions
Does an auditor accept automation as continual improvement?
Yes, when it is written up as an objective with a baseline, a result and a controlled SOP. Auditors look for a real change to the process with evidence it stuck. An automation with a log is exactly that.
Which process should we automate first for ISO 9001?
The one with the most errors or the most retyping. For most SMEs that is quotes, orders, supplier invoices or customer enquiries. It should also be one the auditor already asks about.
Do we need to change our procedures?
Yes, the affected procedure is updated to describe the new flow, and the SOP for the workflow is added as controlled documented information. That update is itself evidence of clause 7.5 working.
What if the automation fails during the year?
Every workflow is built to stop and alert the owner rather than send something wrong. The failure and the fix are logged, which becomes your nonconformity and corrective action record under 10.2.
Does this work for ISO 45001 or 14001 too?
Yes. Incident reporting, permit tracking, training expiry and inspection records are the usual candidates. The same continual improvement logic applies in clause 10 of both standards.
Is the automation project grant supported?
From 30 September 2026 automation and digitalisation are EDGE activities with support of up to 70% for SMEs. The ISO consultancy part has historically been excluded. We check the live list before you commit.
Can we do this before our first certification audit?
Yes, and it helps. A process that already runs the same way every time is easier to document and easier to audit. It also gives you the first improvement record for the year after.
Talk it through with Nachi
Tell us your industry and headcount, and get a quote and a realistic timeline, free, same day.
WhatsApp us: 8901 2255Prefer email? Leave your details and Nachi replies within one working day:
ZES Consulting · 20+ years · 268+ projects · contact page