Quality Issue Register — BuildOrch by Soluture

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.

Severity and issue-type weightingEvery issue carries a severity and a type, each with its own weight — so a hairline crack and a structural defect never score the same.
Assigned, tracked and closed with evidenceAn issue belongs to a person and a date, and it cannot be closed on a claim alone — the closure carries the photo or measurement that proves it.
Escalation to NCR on closureWhere a closure needs formal non-conformance, approving it spawns the linked NCR automatically instead of relying on someone to remember.
Feeds the vendor quality ratingIssues raised against a subcontractor move that vendor’s quality score, so the next bid comparison already knows how they performed.
Recurring pressure surfaces as riskWhen the same issue keeps returning on the same package, BuildOrch raises it as a risk rather than letting it stay a list of open tickets.

In the product

Where quality becomes cost.

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

$Quality 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.

Catch it on site, not in the final account.