Platform

Non-conformances, ITPs and corrective actions in one register

Quality runs on the same primitives as safety - a record, an owner, a due date and the evidence it was closed. Stop running it out of a shared drive and an email chain.

Join waitlist

Replaces: NCR spreadsheets, email chains
Covers: NCRs, ITPs, supplier quality
Frameworks: ISO 9001, client ITP regimes
Live in: 24 hours from your export

What is a quality register, and how is it different from a risk register?

A quality register is the list of non-conformances, inspection and test plans and corrective actions across a business, each with a responsible party and the evidence that closed it. Structurally it is the same thing as a risk register - records, owners, due dates and evidence - which is why Frontline runs both on shared primitives rather than as two products. In practice that means quality and safety share one people directory, one site structure and one permission model, and a non-conformance can be linked to the risk it evidences.

NCRs raised from the field, classified and assigned afterwards
ITP hold and witness points configured to each client's regime
Root cause recorded against a taxonomy you define, so recurrence is a query
Supplier and project roll-up for quarterly reviews

The problem

Quality data exists. It just doesn't add up to anything.

Every non-conformance is recorded somewhere. Almost none of them roll up into a number anyone can act on.

The NCR gets raised on a form, emailed to the responsible party, and tracked in a spreadsheet by whoever owns the project. Closure is a reply in a thread. Six months later, nobody can answer the only question that matters - are we making the same mistake repeatedly, and with which supplier.

The ITP has the same shape. Hold points are signed on paper, scanned, and filed by project. When the client asks for the pack, someone spends a day assembling it from folders.

One register across projects, sites and suppliers
Every NCR carries an owner, a due date and a closure record
Recurrence visible by cause, supplier and location - not by memory

What it does

The register, the inspection regime and the evidence

Non-conformances

Raised from the field in seconds - photo, voice, a few words. Classification, severity and the responsible party are applied afterwards rather than demanded at capture.

Inspection and test plans

Hold and witness points as scheduled records with sign-off against them. The pack is the register filtered, not a folder someone assembles.

Corrective and preventive actions

Actions hang off the NCR that caused them, with owners and due dates. Closing one requires the evidence, not just a status change.

Root cause, kept structured

Causes recorded against a taxonomy you define, so recurrence is a query rather than a hunch.

Supplier and subcontractor view

NCRs grouped by the party responsible, so the quarterly supplier review starts from data instead of anecdote.

Cost of quality

Rework hours and cost captured on the record, so the argument for fixing the upstream problem carries a number.

Why it's the same system

A quality register is a risk register with different columns

Frontline has no hard-coded modules. A register is a record type, a lifecycle, a set of relationships and a view - and that is as true of an NCR as it is of a risk. Which means quality does not arrive as a second product with a second login and a second admin burden.

It also means the two talk to each other. A recurring non-conformance on a critical process is a risk with evidence attached. Today that connection lives in someone's head, or in a slide once a quarter.

Same permissions, same sites, same people directory
Quality and safety actions in one list for the person who owns both
An NCR can be linked to the risk it evidences

Included

What you get on day one

Your NCR register imported, with your numbering preserved
Your severity and classification scheme, not a fixed one
ITP templates with hold and witness point sign-off
Corrective actions with owners, due dates and evidence on close
Root cause taxonomy you control
Supplier and project roll-up views
Recurrence analysis by cause, supplier and site
Client-ready quality pack generated from live records

Questions we get asked

Is this a separate module we have to buy?

No. Registers are configuration, not separate products. If you already run Frontline for risk or incidents, quality is a register you add - same login, same people, same permissions.

Can it match our client's ITP format?

Yes. Hold points, witness points and sign-off requirements are configured to the regime your client imposes. Different clients on different projects can run different regimes in the same account.

What about ISO 9001 audit evidence?

The register is the evidence. Every record carries its full change history - who raised it, who closed it, what changed and when - which is the part auditors actually test.

See it running on your own data.

Tell us what you run today. When your spot comes up you are looking at your own register, your own incidents and your own sites, not a canned demo environment.