BuildOrch
13 · Quality Issues

Catch it on site, not in the final account.

Raise, classify and close quality issues with severity and issue-type weighting behind them — escalate to an NCR where it matters, and let recurring pressure surface on the risk register instead of hiding in a folder.

Quality issue register
Raise it, weight it, close it

An issue with a number behind it.

Every issue carries a severity and an issue type, each with its own weight — so ten cosmetic snags never outrank one structural defect.

⚠️

Raise & classify

Log the issue against the project, section or WBS node, with severity and issue type.

⚖

Weighted scoring

Severity × issue-type weighting drives a quality-pressure score, not a raw count.

📜

Escalate to NCR

Close an issue as escalate and the linked non-conformance report spawns automatically.

The quality chain

Issue → inspection → risk.

Nothing sits in isolation. An issue can trigger an inspection, an inspection can raise an NCR, and a recurring pattern becomes a risk on the register.

Issue raisedA defect is logged on site against the project, section and subcontractor, carrying its severity, issue type and photographic evidence.
→
InspectionThe issue is verified through an inspection with its checklist, hold points and witness points — not closed on somebody’s word.
→
NCRWhere the defect is formal, approving the closure spawns the linked non-conformance report with its own approval and evidence trail.
→
Risk registerRepeat issues on the same package stop being tickets and become a tracked risk with an owner, a probability and a mitigation.
In the product

Where quality becomes cost.

The chain from a snag on site to a score on the vendor.

Quality dashboardQuality dashboard
Vendor quality rating

Quality that follows the subcontractor.

Issues and inspection pass-rates feed a derived vendor score with grade bands, an auto/manual override that demands a reason, and a full exportable ledger.

🏆

Derived score

A 0–100 quality score behind the familiar star rating — earned, not typed.

📝

Override with reason

Procurement can force a rating, but it writes a ledger line.

📋

Exportable ledger

Nothing moves the score without a visible, exportable entry.

Quality that shows up in the numbers.

From a snag on site to a score on the vendor.