← muthari.com

Quality that leaves a record

Muthari OS · the Project Operating System for Specialist Contractors

Quality in Muthari OS is a record at every point where material or work is judged, for contractors who fabricate what they install. Incoming QC approves or quarantines a batch — a 450/50 split has to add up — and quarantined stock cannot be issued; it goes back to the supplier under a return note and an NCR reference. Factory QC passes or rejects with a reason that cannot be left blank. Site inspections are raised as MIR and WIR with A/B/C/D verdicts. Anything that fails opens a typed rework round, and an NCR carries its root cause, corrective action, assignee, due date and closure. Every decision keeps the inspector’s name, role, time and, at the factory and on site, photos.

Incoming QC: approve, quarantine, return

The approve/quarantine split must sum to the batch quantity; each decision is a ledger line with the inspector and remarks. Only approved stock is issuable. Return-to-supplier records the return note number and the NCR reference, closes the batch and reopens the balance on the purchase order.

Factory QC before dispatch

Pass or reject, with a mandatory reason and photos. A reject rolls the zone back to the chosen stage and notifies production. Nothing ships without a pass — dispatch of an unpassed zone is refused, not warned about.

Rework rounds with typed causes

QC reject, site return, NCR or damage — one of four causes, never free text. Rounds are counted, stages are rolled back through a picker, photos and documents attach. Rework cost is reported as costed or not yet costed, so an uncosted round is never mistaken for a free one.

NCR as a record, not a label

An NCR carries its root cause, corrective action, assignee and due date, and it has a closure step — with the photos and documents behind it, so the consultant sees a record rather than a reason typed into a box.

Site inspections and reinspection

MIR and WIR on the zone with verdict codes, the raiser’s identity, comments and photos. A rejected zone goes round again: repeat inspections are stamped as repeats, rounds are counted and the same gates re-apply, so the record shows how many times it took.

Honest limits: Muthari OS records inspection events; it does not hold inspection engineering. There is no ITP structure, no checklists or measured values, and no hold or witness points — each verdict is a decision plus remarks plus photos. Incoming QC decisions carry the inspector and remarks but not photos. Inspections are zone-level: they do not carry a partial quantity, and they do not link to the material batch inside the installed work. Your ITP stays in its own document; Muthari holds the evidence trail beside it.

Next in the chain

Incoming decisions release stock in the Store; factory verdicts gate Production; approved inspections gate handover on Site. Muthari OS is built by contractors in the trade.

Book a free demo  See the whole system →