Because a report tells your document control officer what to do, and a working system does it. That is the entire difference, and it is the reason ISO automation, done properly, ends in software that runs your revision numbering, your registers, and your distribution matrix — not a PDF that describes how those things should theoretically work. We don't sell consulting, we ship working things.
This is not a jab at consultancies — good ones do necessary work, and plenty of Thai manufacturers need that work before automation makes sense at all. It is a distinction worth being precise about, because the two deliverables solve different problems, and buyers often do not find out which one they bought until months after signing.
What a report actually gives you
A gap analysis, a set of written procedures, a recommendations document — these are legitimate outputs of legitimate work. A consultant reviews your current document control process against ISO 9001 clauses, identifies where it falls short, and hands you a document describing what to change and how. For an organization that has never formally defined its document control logic, this is often the necessary first step: someone has to work out what the revision numbering rule should be, who sits in the distribution chain, and how retention periods get calculated, before anything can automate it.
The report's value is entirely in the thinking, and that thinking has to happen somewhere. What a report does not do is execute anything. After it is delivered, your document controller still opens the same spreadsheets, still retypes the same eight or ten fields by hand for every revision, still calculates the same retention date manually. The process is now correctly defined. It is not automated.
What ISO automation gives you instead
A working system takes that same defined process — whether it came from your own SOPs, a consultancy's documentation work, or years of accumulated practice — and executes the clerical steps automatically, every time, without a person retyping anything. The distinction matters because it changes what actually happens on a Tuesday afternoon when a document gets approved.
With a report alone: an approver signs off, and a document controller manually opens the amendment record, the master document list, the change register, calculates the retention date, and updates the distribution list — by hand, the same way it has always been done, just now against better-defined criteria.
With a working system: an approver signs off, and the system writes those same fields automatically, logs each write individually, and leaves an activity log that shows exactly what changed and when. The human decision — was this document adequate, is it ready — stays exactly where it was. What disappears is the retyping.
What we actually built, as a concrete example
The clearest way to describe this is the reference system built for a Thai manufacturer, ISO 9001:2015 certified across two sites. Their document control ran on paper change-request forms and a document controller manually retyping outcomes into several Google Sheets registers — a defined process, run entirely by hand.
We did not rewrite their process or tell them how document control should work. We built a system on n8n, using Google Sheets as the register and master-list backend, that runs the process they already had. It covers the full document lifecycle — new document, revision, cancellation, controlled copy, uncontrolled copy — and preserves their four human decision gates exactly as their own SOPs defined them: a reviewer marks the paper change-request form, an approver checks content adequacy, and a combined final gate completes master sign-off, covering external and support documents too.
Only after that final human sign-off does the system act. It writes eight fields that a document controller previously retyped by hand — revision number, effective date, amendment-record entry, a master document list row across a ten-department distribution matrix, change-register entry, the year-keyed request number, page count, and the calculated retention/disposal-due date. Every one of those eight writes is logged individually to an activity log, and the workflow is idempotency-keyed, so replaying the same approved event does not create duplicate entries. Document lifecycle state is mirrored by real Google Drive folders across a nine-step lifecycle — moving a folder is still a human decision; the automation only reacts to it.
Nineteen of nineteen acceptance criteria passed. All 51 pre-existing unrelated workflows on the same automation tenant were verified unchanged afterward, and all five original source documents were verified unchanged — same file IDs, names, formats, modification times. The build even surfaced a real latent bug: their paper forms mixed Buddhist and Gregorian calendar year conventions inconsistently, and the system standardized everything on dd/mm/yyyy, something the paper process alone had never forced them to reconcile.
None of that is a report. All of it is something you can watch run.
Report vs. working system, side by side
| Report / documentation | Working system | |
|---|---|---|
| What's delivered | Written procedures, gap analysis, recommendations | Software that executes the defined process |
| Who acts on it after handover | Your document controller, manually, every revision | The system, automatically, after each human sign-off |
| What proves it works | A review meeting or sign-off on the document | Acceptance criteria tested against real scenarios |
| What changes for the DCC's daily work | Clearer instructions to follow by hand | Fewer manual steps to perform at all |
| Ownership after the engagement | You own the document | You own the system and its logic, with no vendor lock-in |
Why this distinction is worth insisting on before you buy
Neither deliverable is wrong in isolation — the mistake is not knowing which one you are buying. If your document control logic is not defined yet, a report or a consultancy's implementation work may need to happen first, because automation has something to automate only once the process it is automating is actually settled. The build-versus-buy-versus-commission comparison goes deeper on how to sequence that decision.
If your process is already well-defined and the pain is the manual retyping itself, a report at that point does not solve the actual problem — you already know what to do, you just do not want to keep doing it by hand a hundred times a year. That is specifically what a working system is for. And if you are evaluating whether an off-the-shelf platform fits better than a custom build, comparing what different QMS software types actually solve and understanding the real difference between a software vendor, a consultancy, and a certification body are both worth reading before you decide which category of deliverable you actually need.
FAQ
Is a report ever the right deliverable?
Yes — if your document control process is not clearly defined yet, that definition work has to happen somewhere, and a consultancy's documentation output is often the right starting point.
Does a working system replace the need for defined procedures?
No. A system automates an existing process; it does not invent one. If your revision logic, distribution matrix, and retention rules are not settled, that has to be worked out first, whether internally or with a consultancy.
Can the system make judgment calls a human should be making?
No, and it should not. ISO 9001 requires competent human review of document adequacy. A legitimate working system only executes clerical steps after that human decision has been recorded — it never substitutes for it.
What platform is a working system typically built on?
Our reference build uses n8n as the automation engine with Google Sheets as the register and master-list backend, chosen to match the manufacturer's existing infrastructure rather than force a new one.
How do I know a working system actually works before I sign off on it?
Ask for acceptance criteria stated as a testable list, not an adjective — our reference build was verified against 19 named criteria, plus confirmation that everything outside scope stayed untouched.
If your document control process is already defined and you are tired of watching someone retype it by hand, book a free consultation with 1% EVO. We will show you a live demo of the system running against your own SOPs before any quote gets discussed.