> For the complete documentation index, see [llms.txt](https://changelog.visilean.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://changelog.visilean.com/quality/quality-changelog/release-6.0-2026/non-conformance-reports-a-formal-record-when-work-misses-the-spec.md).

# Non-Conformance Reports: A Formal Record When Work Misses the Spec

Some issues are bigger than a snag. When completed work doesn't meet the specification, the project needs a formal record of the non-conformance, a defined route for reviewing it, and clear sign-off on how it's resolved. Release 6 introduces Non-Conformance Reports (NCRs) to the Quality Module: a formal record of their own, separate from any checklist, with their own review and approval stages.

#### Why This Matters

A non-conformance carries more weight than a routine finding. It may affect the design, the programme or the contract, and the people who need to review it are often different from those who sign off day-to-day inspections. Folding it into a checklist response makes it harder to give it the formal treatment it needs. Keeping NCRs as standalone records, each with its own approval route and visible on the dashboard, means serious non-conformances are reviewed by the right people and don't get lost among routine checks.

#### What's New?

* **NCRs as a formal record.** Raise a Non-Conformance Report as its own record, separate from any checklist.
* **Their own review and approval stages.** Each NCR moves through its own review and approval stages.
* **NCRs on the dashboard.** NCR counts and widgets on the dashboard put open non-conformances alongside your checklist work.
* **NCRs on mobile.** Raise and action NCRs from the mobile app on site.
* **Approver reminders.** Approvers who haven't yet acted get an automatic reminder email, so approvals don't sit unnoticed.

#### How It Helps: Three Example Use Case Scenarios

A Site Engineer finds that a poured slab is out of tolerance. They raise an NCR from the mobile app while still on the slab, creating a formal record of the non-conformance on the spot.

The NCR moves through its review and approval stages. When an approver hasn't yet acted, they receive an automatic reminder email, and the NCR keeps moving instead of waiting in an inbox.

A Quality Manager opens the dashboard and sees the NCR counts and widgets next to the checklist figures, giving a single view of open non-conformances and routine inspection work for the weekly quality review.

{% hint style="info" %}

#### Key Considerations & Caution Points

**Separate from checklists:** an NCR is a formal record in its own right, not part of a checklist response.

**NCRs and snags:** snags track issues raised against checklist answers, while NCRs are standalone formal records with their own review and approval stages.

**Reminders:** approvers who haven't yet acted receive an automatic reminder email.
{% endhint %}