Completions, work plan & snags

Recording that work is done, day by day, and flagging own-work snags on the same gesture — self-certified, photo-gated, and honest about the last 2%.

Getting to "done" on a construction site is rarely a clean 100%. SimOps lets each team record that a token's work is complete for the day, and — riding the very same gesture — flag its own Snags: the bits that aren't quite to spec yet. Both are self-certified and own-work only: nobody signs your completion off, and a problem that stops another trade isn't a snag at all — it's a Blocker.

Termglossary

Snag →

A contractor's own-work defect caveat — work not constructed to spec, flagged by the team that built it while recording work completion (the "wee box" riding every record-work-completion gesture, daily or closing; there is no standalone raise button). A snag can never be raised against another trade: a cross-trade grievance is a Blocker. Substrate: a WorkGroup sibling (SnagDetail), anchored by a polymorphic token ref + work_line_id snapshotted at raise. Two stored states, open → closed; the *"complete · N snags open"* caveat (Tony's "98%, not 100%") is derived, never stored — the roll-up to 100% is the join emptying. Close is a per-snag human tick — via a Resolving token's wee box or a direct tokenless close — and both paths sit behind a hard photo gate (422 snag_closeout_photo_required; the completion photo is dual-purposed). Close self-certifies: no verification state — a deliberate departure from industry two-step close (verification migrated to blockers). Soft-delete is the mistake path; no reopen edge — a resurfaced defect is a fresh snag, fresh clock. Snag clocks (raised_at → closed_at) are responsiveness metrics and never feed lost time. Visibility: owning team + principal side (HSE deliberately out — snags sit on the commercial axis, not the safety axis). See docs/decisions/2026-07-17-snag-own-work-caveat.md. _Avoid_: defect (Defect is now a first-class contractual noun — different parties, register and legal weight; no promotion path either way) / punch item / NCR (industry imports with heavier workflow); snag list / snag board (there is no standalone board — snags live inside the Completions view); blocker (obstruction, not defect).

What it does for you

Complete, honestly. A Completion record is a per-day "this work is done" mark you can set and revert in place — no approval chain, no verification band. The platform makes the last 2% visible rather than gating it.
Snags where the work is. Flag your own not-to-spec work through the completion "wee box" — there's no standalone snag board; snags live with the work they caveat, and the derived "complete · N snags open" caveat clears itself as the last snag closes.
A photo is the proof. Closing a snag is a single human tick behind a hard photo gate — self-certifying on the evidence, not a two-step inspection. See snag-own-work-caveat.
Own-work only, enforced. A member can only snag their own contractor's work; cross-trade problems escalate to a Blocker, never a snag — so the two records never blur.

See it / try it

Where to go next

Snags & work close-out — the how-to: mark completion, flag a snag, the photo-gated close, and scheduling a fix.
Blockers & delays — where a cross-trade grievance goes instead, and how lost time is counted.