Back to guides
Operations

From a crack to an 8D without leaving chat

The complaint came in. Someone has to do 8D, A3 or 5 Why, and the source is article, supplier and drawing, not a blank Word page. The value is a report you can send or file, with the right product underneath, the same day.

The report should start from the article, not from a blank document.

Quality has to write an 8D. The customer is waiting. The source sits in the drawing, the supplier line and how you usually handle a deviation. Starting in a blank template is guessing the article number twice. Colleag.ai drafts against the product file and the process document. You choose Word, Excel or PDF, and whether the file stays or is sent. You will recognise the evening when the 8D is a merge of three emails.

A customer complaint that must be sent

“Write an 8D on the cracked housing for article 991203. Fetch the latest supplier, the drawing tolerance and our NCR procedure, and give me Word plus PDF.” The report is written as markdown first, that is the document you can search later, and rendered to Word and PDF. You press Save, link the article, and it lands under Quality records in the QMS. Not under a product picked at random.

The same data, a different envelope

“Compile the pack for the supplier in Shenzhen: what deviated, which shipments are affected, and what we ask for.” Same article, same crack, different recipient. Purchasing gets a send-out. Quality gets the record. Nobody rewrites from scratch.

When you do not know yet

“Do a 5 Why on this, Word only. I do not know if it should be filed.” Download takes the file. Save asks for shelf and article. An 8D sent once should not be forced into git; an 8D that becomes a record should not vanish after 24 hours.

Key benefits

  • Word, Excel and PDF from chat, with nothing to enable in Settings
  • Filed against an article, not a product
  • An ephemeral file when that is enough
  • A pack for customer and supplier from the same fetch

Read more

How do you write an 8D that matches the drawing and the NCR procedure, without copying between Monitor, Word and email? Colleag.ai fetches article 991203, supplier and procedure, writes the report as markdown and renders Word or PDF. It is filed against the article in the QMS, not under a product picked at random, the same part sits in several. A PLM files the drawing. An ERP may have the complaint as a transaction. Neither writes the 8D.

A complaint should become an 8D, A3 or 5 Why that matches the drawing and the NCR procedure. Colleag.ai fetches article 991203, the supplier and the procedure, writes the report as markdown and renders Word, Excel or PDF. Save files it against the article in QMS. Download only sends the file.

A PLM files the drawing. An ERP may have the complaint as a transaction. Neither writes the 8D. And the report must not land on the wrong product, the same part sits in several, so the shelf is QMS against the article, not a random folder in the product tree.

How this differs from ERP, PLM, LCM and project systems

ERP
ERP may hold a complaint as a transaction. It does not write an 8D against drawing and NCR procedure, and Monitor v1 often has no quality module at all.
PLM
PLM files the drawing. The 8D belongs against the article, not a product folder.
LCM
LCM closes a change object. It does not create Word and PDF for customer and supplier from the same fetch.
Project management systems
“Write an 8D” as a task is coordination. The report, with article and procedure filled in, is Colleag.ai.

What Colleag.ai does here that those systems do not

  • A report from chat with nothing to enable in Settings
  • Save against an article in the QMS, or Download only
  • The same pack for customer and supplier

See it in action

Book a 30-minute demo and see how Colleag.ai handles this for your team.

Book a demo