Skip to main content

Quality

Request an inspection before work is covered up, run its checklist with hold points, record pass or fail, and raise an NCR that is tracked through rework to verification.

Where
  1. Projects
  2. open a project
  3. Quality
Who
  • Company Admin
  • Project Manager
  • QA/QC Engineer
  • Site Engineer

Quality has two registers on one tab. Inspections are requests to check work โ€” a slab's reinforcement before the pour, waterproofing before the screed. Non-conformances (NCRs) record work that is not to spec and track it until the fix is verified.

๐Ÿ“ท Screenshot spot โ€” an inspection request in progress, with its checklist, one line marked as a hold point, and the Overall result drop-down

Save as static/img/screenshots/site-quality.png and replace this box with ![Quality inspections](/img/screenshots/site-quality.png)

Request an inspectionโ€‹

  1. Open the project and go to the Quality tab.
  2. Click Request inspection.
  3. Enter a Title ("Level 3 slab reinforcement") and pick the Type: internal, client, consultant, third party or statutory.
  4. Pick the Location, add a Description, and set Ready for inspection at.
  5. Tick Client witness required if the client must attend.
  6. Build the checklist: one line per Check, with its Acceptance criteria ("150 c/c ยฑ 10"). Tick hold on any check the work cannot pass without. Click Add check for more lines.
  7. Click Request inspection.

The request is numbered for the project (โ€ฆ/IR/0001) and starts as Requested. You can change the checklist with Edit checklist until the inspection starts.

Schedule and run itโ€‹

  1. Open the request from the list.
  2. Pick the Inspector and the Date and time, then click Schedule (later, Reschedule).
  3. On the day, the QA/QC Engineer clicks Start inspection. The checklist is now fixed.
  4. For each line, set the Result โ€” pass, fail or not applicable โ€” and note what was Measured and any Remarks.
  5. Choose the Overall result and add Remarks.
  6. Click Record result.

The app stops a result that does not add up:

  • Every hold point needs a result first โ€” the screen lists the ones still blank.
  • If a hold point failed, the inspection can only be recorded as failed.
  • If any check failed, it cannot be a clean passed โ€” the most it can be is passed with observations.
Hold points are where quality has teeth

A hold point is a check the work must pass before it goes on. Mark the critical ones โ€” cover to reinforcement, slope of a waterproofing layer โ€” as hold points when you request the inspection, because once the inspection starts the checklist is locked.

A recorded result is final. If the work is redone, request a fresh inspection.

To call off a request, type a reason in Cancel with reason and click Cancel request.

How an inspection movesโ€‹

RequestedScheduledIn progressPassed
In progressPassed with observations
In progressFailed

A request can also be Cancelled from Requested, Scheduled or In progress. The result can be recorded straight from Scheduled if the inspector does not press Start inspection first.

Raise an NCRโ€‹

From a failed (or passed-with-observations) inspection, click Raise NCR from this inspection. The form opens on Non-conformances with the description, location and inspection filled in, and severity set to major if a hold point failed, otherwise minor.

To raise one from scratch, switch to Non-conformances and click Raise NCR. Fill in:

  • Description โ€” what is wrong (required).
  • Severity โ€” minor, major or critical.
  • From inspection and Location, if they apply.
  • Target close date โ€” the NCR shows as overdue in red after this date.
  • Responsible vendor and Responsible person โ€” who has to fix it.
  • Root cause, and Cost impact (โ‚น) if you see costs.

Click Raise NCR. It is numbered โ€ฆ/NCR/001 and starts Open.

Close and verify an NCRโ€‹

OpenIn progressClosedVerified
  1. Open the NCR and click Start rework when the fix begins.
  2. Record the Disposition (rework, repair, accept as is, reject, or use as is with concession), the Corrective action, and the Preventive action and Root cause if known. Click Save as you go.
  3. When the fix is done, click Close NCR. Closing needs a disposition and a corrective action.
  4. A Project Manager or Company Admin who did not close it checks the work and clicks Verify.

If the fix is not good enough, the verifier types what is still wrong in Reopen โ€” what is still wrong and clicks Reopen. The NCR goes back to In progress.

The closer never verifies

The person who closed an NCR cannot verify it โ€” the Verify button is greyed out and the app says You closed this NCR, so another approver verifies it. The person who fixed a defect is never the one who signs it off.

Who can do whatโ€‹

JobWho
Request an inspection, edit its checklist, cancel itSite Engineer, Safety Officer, QA/QC Engineer, Project Manager, Company Admin
Schedule an inspectionAny of the above
Start an inspection and record the resultQA/QC Engineer, Company Admin
Raise, work on and close NCRsQA/QC Engineer, Project Manager, Company Admin
Verify or reopen a closed NCRProject Manager, Company Admin

QS / Estimators see the Quality tab but cannot change it. The Cost impact column only shows for roles that see costs, or for team members marked Sees financials on the project team.

The numbers at the topโ€‹

Open requests (with how many are scheduled), Failed, last 30 days, Open NCRs by severity, and NCRs overdue past their target close date.

AI

Quality, Snag & Safety Watch reads inspections and NCRs with snags and safety events, finds what keeps recurring, and names the three things to fix this week. The Assistant can draft an inspection request with its checklist for you to confirm.

  • Snags โ€” finishing defects at handover, with their own verify step.
  • Safety โ€” safety events are tracked separately.
  • Project team โ€” the Sees financials flag and who is on the job.