Skip to content

Non-Conformance Report Tracker with Corrective Action Routing

Example prompt: "When someone adds a row to our 'NCRs' Google Sheet, route it to the right owner by type — goods-in to the buyer, in-process to the production manager, customer complaint to sales. Draft a corrective-action form, log it on the 'NCRs' sheet, and chase any open action older than 7 days in #quality on Slack."

The Problem

A non-conformance — a part out of tolerance at goods-in, a scrap rate spike on the press, a customer ringing to say the order arrived damaged — is the kind of thing the team handles every week and writes down half the time. The QC inspector raises it on a paper form or in a quick shop-floor message; the buyer or the production lead is told verbally; the corrective action is agreed at the next stand-up but nobody writes down the due date; the customer's complaint gets answered by sales without the quality manager seeing it; the auditor at the next ISO surveillance visit asks for the corrective-action records and the team spends an afternoon reconstructing them from emails.

How GloriaMundo Solves It

We build a workflow that watches the NCRs sheet for any new row the inspector raises and turns it into a tracked case. A code step validates the row against the rest of the business — the SKU exists in stock, the supplier is on the master for a goods-in case, the SO exists for a customer complaint, the work order exists for an in-process case — and either routes the NCR or flags the row for the raiser to fix. An integration step allocates the next NCR number, renders a corrective-action form as a Google Doc in our NCRs folder pre-filled with the standing containment instructions for the type, and drafts the internal email to the correct owner with the quality manager copied. For goods-in NCRs, a second draft goes to the supplier — buyer's voice, our usual evidence-share defaults — for the supplier's own response. The Monday quality summary in Slack closes the loop: what was raised last week, what is due this week, what has gone overdue, and where supplier notes are still sitting in drafts. Glass Box preview shows the rendered form, both Gmails, and the row update before anything is created — the QM can correct a misrouted ncr_type before the supplier sees an unfounded note.

Example Workflow Steps

  1. Trigger (sheet row added): Any new row in the 'NCRs' tab of the quality Google Sheet.
  2. Step 1 (integration): Read the NCR Settings tab, Containment Actions tab, and the relevant cross-reference tabs (Stock, Suppliers Master, Purchase Orders, Sales Orders, Work Orders) for validation.
  3. Step 2 (code): Validate the row by ncr_type, allocate the next ncr_number and persist the new highest, and compute capa_due_date in working days.
  4. Step 3 (conditional): If validation fails, update the NCR row to 'Validation failed — see notes' with a populated validation_notes cell, post a tagged note in #quality on Slack, and exit without drafting.
  5. Step 4 (integration): Render the corrective-action form as a Google Doc in the NCRs Drive folder, pre-filled with the row's metadata, the evidence link, and the standing containment instructions for the ncr_type.
  6. Step 5 (integration): Draft the internal email to the owner from the type-to-owner map with the quality manager copied; for Goods-in, additionally draft the supplier email in the buyer's voice with the evidence link and an ask for the supplier's own corrective response.
  7. Step 6 (integration): Update the NCR row with ncr_number, ncr_status 'Routed — awaiting CAPA', capa_due_date, capa_form_doc_link, internal_email_draft_link, and supplier_email_draft_link where applicable.
  8. Step 7 (integration): On send-detection from the Gmail Sent folder for each draft subject, update the corresponding status and sent_at columns on the NCR row.
  9. Step 8 (integration): Every Monday at 08:00, post the weekly quality summary in #quality on Slack — raised last week by type, due this week, overdue, supplier notes still in drafts, and the calendar-month closure rate.

Integrations Used

  • Google Sheets — the NCRs, NCR Settings, Containment Actions, Stock, Suppliers Master, Purchase Orders, Sales Orders, and Work Orders tabs
  • Google Docs — renders the corrective-action form the action owner fills in
  • Google Drive — stores the corrective-action forms in the NCRs folder for the audit trail
  • Gmail — drafts the internal route-to-owner email and (for Goods-in) the supplier note, and provides send-detection on both
  • Slack — the #quality validation-failure pings and the Monday weekly summary

Who This Is For

The quality manager at a small manufacturer running an ISO 9001 quality system on Google Workspace and a spreadsheet rather than a dedicated QMS — anywhere with one or two NCRs a week, a buyer, a production lead, and a customer-facing salesperson who all need to know about the cases that affect their patch without the QM having to send three separate emails per case.

Time & Cost Saved

The manual version is fifteen to thirty minutes per NCR — pulling the right cross-references, writing the form, drafting the internal email, drafting the supplier note where it applies, and remembering to set a follow-up reminder. The workflow brings it to a few minutes of reviewing the drafts and the pre-filled form, and the audit trail accumulates by default rather than as an afterthought. The bigger gain is at the surveillance visit: every NCR has a corrective-action form, a due date, a route-to-owner email, and a closure entry — the file the auditor asks for is the one the workflow has been keeping all year.