Building an ISO 9001 Quality System on Donesafe

A quality manager who inherits an ISO 9001 system usually inherits a folder structure, a handful of spreadsheets and a nonconformance log that only one person understands. Moving that onto Donesafe is mostly a mapping exercise: take each thing the standard expects you to do, decide which module or workflow carries it, and build it once. This article walks through that process in the order it tends to work best, for quality, compliance and WHS professionals who are audit bound and short on time.
ISO 9001 is the international standard for quality management systems. It does not tell you which software to use. It asks you to show that you control your processes, find problems, fix them and improve. Donesafe is the platform where that evidence can live.
What does an ISO 9001 system on Donesafe actually consist of?
It consists of the same parts an auditor looks for in any quality system: controlled documents, nonconformance records, audits, corrective actions and reporting, all held in one connected platform instead of scattered files. Donesafe offers almost 100 modules, including a Quality and Supplier group, so most of these parts have a home.
The KIS Group view of a WHSEQ system covers an ISO aligned framework, documentation and controls (policies, procedures, registers, version control), audits and inspections, corrective actions with an owner and a due date, and live role specific dashboards. For ISO 9001 specifically, the focus areas are nonconformance, audits and actions. The useful discipline is to start from your obligations, not from the module list. Picking modules first is how teams end up with a system that looks impressive and does not match how the site works.
Start with the process, not the platform
The first job is to write down how quality work really happens in your business today, including the workarounds. Auditors test whether your system describes reality, and a Donesafe build that copies an idealised process fails that test faster than a spreadsheet would.
Walk through a recent nonconformance from the moment someone noticed it to the moment it was closed. Who raised it? Who decided it mattered? Who approved the fix? Where did the evidence end up? Those answers become your workflow. This matches the first two steps KIS Group describes: Discover, where the aim is to learn your business, obligations and the way your people actually work, and Design, where workflows, forms and reporting are mapped to your process rather than a template.
It is also the stage to list the standards you answer to. Many sites hold ISO 9001 alongside ISO 45001 (occupational health and safety) or ISO 14001 (environmental management), and a connected build lets them share one document control approach and one action register instead of three.
Mapping ISO 9001 obligations to Donesafe modules
Most ISO 9001 obligations land on a small set of record types, and each needs a clear owner in the platform. As a working map, a quality manager would typically look at the following.
- Nonconformance and quality events: a quality and nonconformance workflow that captures what went wrong, where, and what was done about it.
- Audits and inspections: scheduled internal audits using templates, with reminders and evidence captured on any device.
- Corrective actions: every finding becomes a tracked action with an owner and a due date, so nothing depends on someone remembering.
- Suppliers and contractors: supplier and contractor management for the external parties whose work affects your product or service.
- Documents and records: policies, procedures and registers with version control, so staff only ever see the current version.
- Training and competency: learning records that show people were trained for the work they do.
This is a general mapping, not a checklist that fits every business. Which of these you need depends on your scope, your customers and your certification body, so confirm the details against the standard and your own certification requirements.
Why custom workflows matter more than module count
The workflow around a module decides whether people use it. A nonconformance form that asks forty questions will be skipped on a busy shift, while one that asks the right five and routes itself to the right person will be used.
Donesafe lets you change naming, colours, questions and, most importantly, workflows. KIS Group builds custom workflows for incident, form, contractor and approval processes, custom forms (almost any form you use today can be rebuilt, with the right workflow wrapped around it), and custom automations that send notifications, assign actions and set tags based on answers in a form or the state of a record. For a quality system that means a nonconformance can trigger the right notification without anyone chasing it by email.
A fair trade off to weigh: the more you customise, the more you maintain. Build for what auditors and managers genuinely need, and leave the nice to haves for a later release. Keeping it simple is a design rule here, not a slogan.
Moving from spreadsheets without losing your history
Decide early what comes across and what stays archived. Bringing every old record into a new system sounds thorough, but it slows the build and often imports data nobody trusts. A more practical approach is to migrate the live items, such as open nonconformances, open actions, current registers and current procedures, and keep older records accessible in a defined archive.
Three things tend to go wrong at this point:
- Two systems run in parallel for months, and staff are never sure which is the record.
- Document numbers change without a cross reference, so old audit evidence no longer points to anything.
- Open corrective actions are copied without owners, which recreates the exact gap the new system was meant to close.
Set a cutover point, name who owns each register after it, and tell the team plainly that the spreadsheet is now read only. The aim stated for a build like this is to replace the scattered spreadsheets with documents and controls built once and kept current.
Reporting that your next audit will actually use
Dashboards earn their place when each role sees only what it needs to act on. A site supervisor needs open actions assigned to them, a quality manager needs nonconformance trends and audit status, and executives need a short view they can read in a minute. Donesafe supports role specific dashboards and dedicated reporting views, and KIS Group builds them to suit.
Before the build, decide which questions management review will ask: How many nonconformances are open? Which actions are overdue? Which audits are scheduled? Which suppliers carry the most issues? If the dashboard can answer those, the data capture behind it is probably right, and if it cannot, the forms need rethinking, not the chart.
One caution: do not treat any dashboard figure shown in marketing material as a result you should expect. Your own numbers will come from your own records.
Support after go live, and when you already have Donesafe
A quality system is only as good as its upkeep, so plan for what happens after the build. The fourth KIS Group step is Support: training your team and staying on with reviews, updates and high level support. That includes training for users and administrators, plus an online course.
If you already run Donesafe but the quality side was set up loosely, the starting point is a review. KIS Group lists system review, custom modules, adding standard modules, integrations with your other systems and higher level support among the services for existing clients. A review will show where the quality workflows diverge from how you work and where an existing module could be configured better, rather than rebuilt.
As an independent HSI Donesafe Platinum Partner, KIS Group works alongside the platform, and it is not the vendor itself. You can read more about the platform side on the Donesafe services page. When you are ready to scope a full ISO aligned system across quality, safety and environment, the WHSEQ and ISO systems page explains what is included and how to start.
Frequently asked questions
Can Donesafe support ISO 9001 and ISO 45001 in the same system?
Yes. Donesafe brings health and safety, quality, risk and environmental modules into one connected platform, and KIS Group builds WHSEQ systems mapped to ISO 45001, 9001 and 14001. Shared document control and a shared action register are the usual benefits of keeping them together.
Do we need Donesafe to build an ISO 9001 system with KIS Group?
No. KIS Group builds WHSEQ systems on Donesafe or on a client's existing platform. If you are evaluating Donesafe, a free live online demonstration of 45 to 60 minutes is available.
We already have Donesafe. Can the quality side be improved without starting over?
Often, yes. KIS Group reviews existing systems, builds custom modules, adds standard modules and integrates Donesafe with other systems. What can be reused depends on what the review finds.
Does a Donesafe build guarantee ISO 9001 certification?
No software does. Certification depends on your processes, your records and the audit by your certification body. A well built system makes evidence easier to produce, but you remain responsible for meeting the standard.
Related pages
This article draws on the following pages.