How Doctilla QM works

You talk to Doctilla like you'd talk to a colleague who knows ISO 9001. It asks questions, takes notes, and builds your quality system as you go.

Try it yourself

Have a conversation with Doctilla

Type a reply and see how Process Mapping works in real time. This is a live AI demo — no account needed.

Try it yourself — Process Mapping demo

Hi there! Let's start mapping out your business. What does your company do, and what teams or departments do you have? Tell me in your own words — no jargon needed.

Voice input is not available in this browser. Try Chrome or Edge.

Mode 1

Process Mapping

Doctilla starts by learning how your business actually works — not how ISO says it should work. It asks about your teams, functions, and workflows, then builds a process map in your language.

What happens

1Doctilla asks what your business does — sales, manufacturing, service — and who does what.
2It identifies 5–9 macro-processes that cover your core activities, suggested from your answers.
3For each macro-process, it walks through 5–9 subprocesses — asking you to describe them in your own words.
4The result: a structured process map that feeds directly into Audit Mode and 8D Report Mode.

A real conversation — Process Mapping

Let's map out your business processes. What are the main functions your company does? Think of them as the big buckets of work — like sales, manufacturing, delivery. You can use whatever names feel natural to your team.

We do sales, install kitchens, and then provide aftercare. The office team handles purchasing and scheduling.

That's a great start. I can see: Sales, Purchasing & Scheduling (office), Installation (your core delivery), and Aftercare. Do you also do any design work before installation, or is that part of sales?

Yes, we have a designer who measures up and produces CAD drawings. That's separate from sales.

Perfect. So we have: **Sales & Enquiry Handling**, **Design & Survey**, **Purchasing & Scheduling**, **Installation**, and **Aftercare & Warranty**. That's 5 macro-processes — a good foundation. Shall we dive into Sales first and break it into subprocesses?

Mode 2

Audit Mode

Doctilla runs conversational internal audits against your stored process map. It checks real practice against what's documented, flags non-conformities with ISO clause numbers, and remembers what happened last time.

A real conversation — Audit Mode

I'm going to audit your Sales process against ISO 9001:2015. Last time we audited this area, there was an issue with quote approvals not being consistently documented. How has that improved since then?

We've put a template in place — all quotes go through a standard form now. But I'm not sure everyone's using it every time.

That's good progress. Let's check — can you show me a recent example? Do you have a quote from this week I can look at? If you can upload or describe the file, I can record it as evidence.

Yes — quote ref Q-2026-0389, issued to Acme Construction on Monday. I have it as a PDF.

Thanks. I've recorded Q-2026-0389 as evidence. That template looks solid. One observation though: your process map says quotes need manager approval before issue, but this one was sent the same day the enquiry came in. Is there a separate approval step, or does the salesperson authorise their own quotes now?

What happens

1You pick a process to audit from your stored process map, and choose the standard (ISO 9001, 14001, etc.).
2Doctilla asks about how the process works, checks it matches your map, and gently probes mismatches.
3It asks for evidence, records identifying details (PO numbers, file metadata), and auto-maps findings to ISO clauses.
4Previous audit findings are referenced — if the same issue reappears, Doctilla flags it as a systemic problem.

Mode 3

8D Problem Solving

When something goes wrong, Doctilla guides you through structured root-cause analysis. It pushes back on weak answers, helps build Ishikawa diagrams, and forces a clear separation between containment and corrective action.

What happens

1Doctilla asks if the issue came from an audit finding, a customer complaint, or an internal discovery.
2It explores possible causes using Ishikawa (fishbone) categories — then drills down with 5 Whys.
3If you say "training" or "human error" as a fix, Doctilla gently asks what evidence you have that it'll actually prevent recurrence.
4It separates short-term containment actions from long-term corrective and preventive actions, each with owners and dates.

A real conversation — 8D Report Mode

Let's start an 8D report. What happened? Describe the problem as you'd explain it to someone who needs to understand why it matters.

We delivered a kitchen to the wrong address last week. Customer is furious, and we had to do an emergency re-fit at the right address.

That's a serious one. Let's start with containment — what did you do immediately to fix the customer's situation?

We sent a crew the same evening to collect the wrong delivery and put the right kitchen in. It cost us overtime and a skip hire for packaging waste.

Good — that's your containment action. Now let's look at root causes. Using the Ishikawa framework, which areas might have contributed? The address mix-up could be in: People (someone misread the order?), Process (no address check before dispatch?), or Information Systems (how addresses are stored). What do you think?

Probably the process — the dispatch sheet pulls the delivery address from the order, but sometimes the office updates the address after the order is placed and doesn't tell the warehouse.

Interesting — so the 5 Whys would go: 1) Wrong address because dispatch used old data. 2) Old data because the address update happened after order confirmation. 3) Update wasn't communicated because there's no step in the process for flagging post-order address changes. 4) No step because nobody's defined a handoff between sales and dispatch. That's a process gap, not just a one-off mistake. Would you agree?

Everything in one export

When you're ready, Doctilla compiles everything into a Full QMS Pack — your process map, audit report, 8D report, clause map, evidence log, and revision history — as a Word or PDF document.

Process map with subprocess hierarchy
Audit report with ISO clause references
8D report with cause chain diagrams
Clause compliance map
Evidence log with identifying references
Sign-off and revision history

Ready to try it?

Doctilla QM is in development. Join the waitlist and we'll let you know when early access opens.

← Back to home