<aside> ⚡

With NCRs you can:

• Record any non-conformance with a clear Type, Sub-type and supporting details
• Have type-specific evidence pre-attached for you (fatigue, GPS, mass, maintenance)
• Link the NCR to the risk controls that should have prevented it
• Optionally risk-rate the NCR against your 5×5 matrix
• Raise a corrective action, assign it to a user, and require acceptance and a response before closing the NCR out
• Maintain a full audit trail from creation to close-out </aside>

A Non-Conformance Report (NCR) records a breach of policy, procedure or regulation. Most are created with one click from the source event with evidence pre-filled — see below. NCRs and their corrective actions feed the central Actions Register and Risk Register.

Overview

• Create the NCR — one-click from the source event (evidence pre-filled) or manually
• Link to risk controls
• Risk rate (optional, but strongly recommended for serious NCRs)
• Raise and assign a corrective action
• Capture acceptance and response from the assignee
• Close out

Prerequisites

• Safety Org Chart configured — so NCRs route to the right Category Leader (see Setting Up Your Safety Org Chart)
• 5×5 Risk Matrix configured — for the optional risk rating step (see Configuring the 5×5 Risk Matrix)
• Escalation rules set — so risk-rated NCRs notify the right people (see Setting Up Escalation Rules)
• Risk Controls Library populated — so you have controls to link the NCR to
• Drivers, fleet managers and other users added to Hubfleet — so corrective actions can be assigned

Who gets notified

• The user who created the NCR receives an email notification for every status update on the NCR.
• Anyone added as a Notifiable Stakeholder on the corrective action receives the same email notifications — use this to keep operations managers, compliance leads or external parties in the loop.
• The Assignee receives in-app and email notifications when the corrective action is assigned, and as the NCR moves through to closure.