Daily walk-around — Excavator
Loading submission… (skeleton shimmer pauses under reduced motion)
Issues reported during fill-out become tasks linked to the exact question — they exist the moment they're reported, and they survive submit because the draft and the submission are the same record. Untriaged = open with no assignee; assigning it is the triage act.
Approving records who reviewed it and when — it never blocks the field work that already happened. Evidence for this card: in V1 production, 25 inspections sat stuck in "pending review" with no queue to drain them. The review queue is that drain.
Edits re-open the runner over these answers after a confirm step (shipped). DQ-04 RULED (founder, 2026-07-13): edit-in-place stays for launch, with this visible who-changed-what record; amendments deferred until audit/compliance demand earns their cost. Deleting a submission has no user-facing control today — archive/delete is a design-ahead admin affordance.
Shipped behavior matched on this screen: snapshot-pinned answers (immutable template snapshot), Reported-Issues strip w/ untriaged badge, threaded comments on submissions, share via tokenized public link (identity prompt + IP disclosure on the recipient page), edit-answers behind a confirm, meter + location write-back on submit only, yes/no/n-a custom button labels.
Designed ahead (◇, tagged inline): review card + status (DQ-25 proposal), PDF export, per-answer-note authoring, submission archive/delete. DQ-04 RULED (founder 2026-07-13): edit-in-place + visible change record for launch; amendments deferred.
← Prototype home · Inspections · Review queue