Deficiencies — from finding to verified closure
An inspection that finds a problem has done half the work. The other half — the part that decides whether the problem is fixed before it is buried, paid for, or litigated — is tracking it to verified closure against the party responsible. In most job files that half lives in a deficiency field on the inspection report: text, with no owner, no due date, and no state. The Deficiencies module is the flow that text was standing in for: every punch item its own record, raised from the inspection that found it, assigned to the responsible company, due-dated, and closed only when someone verifies the fix.
How a deficiency moves
Open → Assigned → Rectified → Verified → Closed. Raised by whoever found it — inspector, superintendent, safety officer. Assigned names the company responsible for the fix and the date it is due; an overdue deficiency surfaces on the dashboard like any other slipped commitment. Rectified is the responsible party’s statement that the work is done; Verified is a second pair of eyes confirming it, and it is the state the flow holds for approval — the record does not close on the word of the party who caused it. A genuinely disputed item is marked Disputed rather than quietly closed, and an item raised in error is Void, with the reason kept.
Why verification is a separate step
Alberta’s Builders’ Lien Act holdback and the progress-claim cascade both turn on whether work is actually complete and deficiencies actually cleared. A deficiency list that closes itself — contractor marks their own work rectified, nobody verifies — is the standard failure, and it surfaces at the worst time: at substantial performance, when the certificate depends on the list being honest. Separating Rectified from Verified, and naming who verified, makes the list evidence instead of assertion. The open count also rides the job’s progress panel and the client’s read-only view, so an uncleared list is visible to everyone with a stake in it while there is still time to clear it.
What good looks like
Every inspection finding becomes a record the day it is found, with the source inspection named on it. Assignment and due date set at raising, not at chasing. Verification by someone other than the party who rectified. The open count trending to zero before the completion walk, not after it.
In the worked example on this site, the City of Edmonton electrical inspection of grid C (record #97) found two junction boxes missing cover plates and conduit stub-ups uncapped. Deficiency record #98 was raised from that inspection, assigned to Prairie Grid Electrical Ltd with a 12 November due date, and walked to Rectified, Verified by the site superintendent, and Closed — on the same record the project manager and the client read.