Defects

A Defect is a contractual quality event: work not in accordance with the Scope, notified between the two contracting parties under NEC4. It is not a site observation, and it is emphatically not a Snag — different parties, a different register, and different legal weight. Where the contract names a communication system for those notifications, that system is where a defect is raised and accepted; SimOps holds a derivative copy so the register can be read beside the permits, the snags and the day's diary.

What it does for you

• The register comes to you. A per-contractor export drops into the Imports panel and lands as rows — matched on (site, contractor, event reference), so re-uploading the same export updates what it holds and adds what is new. A row missing from the file is left alone: registers do not shrink.
• The upload scope is the truth. Every row is filed against the contractor confirmed on screen, never against a company name read out of the file. SimOps suggests one from the filename and a human confirms or overrides it.
• Status and closure stay two questions. corrected is one party's claim; the close, by a named person at a time, is the settlement. Open means not closed — which is exactly the query the site diary's QA/QC count runs.
• Everyone sees their own. The principal set (coordinator, site manager, admin and the QS — defects carry uncorrected-cost money) reads the whole site's register; a contractor's members read their own firm's rows and nothing else. A row outside your scope reads as "not found", never as a redacted hint.
• Subcontractors are pulled in, not shut out. Unlike the Site diary, the register is deliberately not main-contractor-gated: a sub reading their own defect list in SimOps is the point.

What it deliberately does not do

There is no raise, no correct, no certify and no close anywhere in the app — import is the sole intake, and the lifecycle happens in the named system. A native lifecycle is deferred by name, not forgotten. Nor is there any promotion path to or from a Snag: a snag that turns out to be contractually serious becomes a defect by being raised in the named system, and arrives here on the next import as its own row. And prevents completion is carried through and shown as a badge, but it never blocks a Completion record — a periodically-imported flag with a hard write-block behind it would let a stale download freeze real work.

See it / try it

Where to go next

• Defects — the contractual register — the how-to: importing an export, reading the register, and who sees which rows.
• Snags & work close-out — the own-work noun this is not.
• Blockers & delays — the comparison table that keeps all four quality/stoppage words apart.