Manufacturing

Catch the defect before it leaves the floor.

Run line inspections, log non-conformances and close them out with a tamper-proof audit trail — paperless, offline, and audit-ready for ISO 9001.

Log in
01
Fewer escapes
A failed check raises the issue on the spot and a hold point stops the job — problems are contained on the line, not discovered by the customer.
02
NCRs that close themselves out
Raise, issue, verify against the photo, and close in one place. Workflow rules chase the overdue ones so nothing stalls in someone’s inbox.
03
Audit-ready by default
Every inspection and NCR carries a timestamped, tamper-evident record — your ISO 9001 surveillance becomes an export, not a fire drill.
Quality inspections

Run the check on every shift, not just on paper.

Build a reusable inspection checklist once and run it at every station, batch and shift. Pass/fail with a tap, capture the fault with a photo, and mark the checks that are hold points — a fail raises the issue for you, linked to the check that caught it.

QA · todayLIVE
07:00Shift A — start-up check
08:30Station 4 · hold point failed
09:15NCR-0418 raised + photo
11:40Rework verified · check re-passed
14:00Shift quality report emailed
  • Reusable line inspection checklists
    Build the check once and run it on every shift, batch and station. Pass/fail with a tap, no clipboards.
  • Photo evidence on the floor
    Capture the fault with a photo, location and voice note in one tap — even on a tablet with no signal in the plant.
  • Hold points that stop the line
    Mark any check as a hold point and the job waits on it. Nothing moves on because someone was in a hurry.
  • Attributable sign-off
    Sign-off is a status only the right role can set, stamped with who set it and when. The line can never sign off its own rework.
  • A fail raises the issue for you
    Tick fail and the issue already exists, linked to the check that caught it — and it flips back to pass when that issue closes.
  • Exports the customer will accept
    Fifteen reports across PDF, Excel and CSV, filtered to the station, batch window or status you need.
Non-conformance

Every NCR, from the floor to close-out.

Anyone on the floor can raise a non-conformance with a photo and description. It is issued to a named person with a due date, disputed openly if they disagree, and closed only by someone allowed to close it — with the rework photo attached. If your question is how to run that digitally across a whole plant, we answered it step by step: how do you track non-conformities digitally in a factory?

NCR · this weekLIVE
MonNCR-0411 · weld porosity
TueIssued to Fab Shop
WedIn dispute · fixture wear
ThuRework photo attached
FriNCR closed · signed off
  • One-tap non-conformance capture
    Anyone on the floor can raise an NCR with a photo and description. No waiting for the quality office.
  • A lifecycle, not a status field
    Open, assigned, pending, fixed, completed, ready to inspect, closed — and each move is gated on the role allowed to make it.
  • Assign and auto-chase
    Route the NCR to the right person and let workflow rules chase overdue actions automatically.
  • Disagreement on the record
    A supplier or line lead who disputes a call says so in the record. The dispute is a state, not an argument in someone’s inbox.
  • Tamper-evident audit trail
    Every status change is logged and attributed — defensible for ISO 9001 audits and customer claims.
  • Scope containment fast
    Filter by station, location, type, priority, date range or who it is issued to, and see the match count before you export.
How a non-conformance flows
01
Operator flags it
A fault is caught on the line and logged in one tap — photo, station and description — without leaving the floor.
02
QA takes it on
The non-conformance lands with full context. Quality issues it to the right person with a due date, and the line knows where it stands.
03
Closed with proof
Rework is verified against the photo, the NCR closes with a named sign-off, and the audit trail is ready for your next ISO surveillance.
ISO 9001, on the record

What the surveillance auditor asks for, and where it is

Clause 8.7 wants documented information on every nonconforming output; clause 10.2 wants evidence of the nonconformity, the action, and the result. Most NCR software answers that with a form. IssuesId answers it with the record the floor already kept, so nothing is written twice and the audit is an export rather than a fortnight. Six things they ask for, and the line on the record that answers each.

8.7.2 a
A description of the nonconformity
The capture: photo with its own capture time, the station off the location tree, the dictated description, the classification from your own list.
8.7.2 b
The actions taken
The status trail, in order: issued to whom and when, marked corrected with proof photos, the work order if rework was booked as one, every step against a name.
8.7.2 c
Any concession obtained
A use-as-is decision is a comment on the record by the manager who made it, and the closure that follows is attributed to their role. It is not a separate field; we would rather say so than let you assume one.
8.7.2 d
The authority that decided
Role-gated transitions. The operator cannot close, the fitter cannot verify their own rework, and the sign-off carries the role and the time of whoever set it.
10.2.2 a
The nature of the nonconformity and subsequent actions
Type and classification separate a process fault from a customer return or a supplier issue; reports group by both, so the nature and the actions read as one line per record.
10.2.2 b
The results of corrective action
The verification photo beside the original, the verifier’s name and time, and the record’s state at close. Recurrences are raised as new records that reference the first.
NCR software

Two registers: the floor’s, and the quality plan’s

Most non-conformances are the floor’s: caught at the station, issued, corrected, verified, closed, on the register described above. A quality plan usually names a smaller set that need more than a fix, a formal Non-Conformance Record with management review, an approve-or-reject decision, and certification of the corrective action before close. IssuesId models that as its own register with a seven-state lifecycle and tighter gates: operators and trades have no part in it, users draft and submit, managers review, approve, certify and close. The two can exist for the same physical fault, each with its own trail.

Where that stands today, plainly: the formal NCR lifecycle is implemented and enforced on the API, but there are no NCR screens in the app yet. Teams running a formal process do it on the main register, using Type and Classification to mark the records that need review, with the register’s own disputes, evidence rules and reports. The model is documented at NCRs so you can see what is coming; ask us before you plan a rollout around it. For the step-by-step on running non-conformances across a whole plant with what exists now, see how do you track non-conformities digitally in a factory?

Also built for
Builders →Practical completion, the handover pack, and the month-eleven DLP call answered from the record.Real estate agencies →Tenants raise a maintenance request with a photo; it routes to the trade and closes with proof.Property managers →Maintenance and defects across a residential portfolio, with an audit-logged record for every owner.Strata & owners corporations →The common-property defect register: by unit and level, dated photos, and the trail the inspector reads.Facilities management →Reactive faults and condition walks in commercial buildings, logged by room and closed on evidence.Logistics & warehousing →Pre-trip, asset and facility inspections with photo proof of condition at the dock.
Built for the floor

Ready to make quality a tap, not a clipboard?

Inspections, non-conformances and corrective actions in one place — offline-capable, audit-logged, and ready for your next ISO surveillance. No extra seats for line operators. Workflow rules route each one automatically, the report catalogue covers what an auditor asks for, and if a warehouse sits next to the line, the same loop works there too. For chasing what a line check raised across several plants, and the honest line on what IssuesId does not schedule, read how do you track overdue inspection items across a large site?

IssuesId