Review queue ◇ Designed ahead
Loading the queue… (skeleton shimmer pauses under reduced motion)
Queue's empty — everything's been looked at
New submissions land here automatically, oldest first. Clean ones take seconds; the ones with issues deserve the minute they get.
Opens a confirmation that lists every submission it will mark reviewed — clean ones only, never anything with an issue or a flagged answer. Nothing bulk-approves silently.
Daily walk-around — Excavator
Approve = "a supervisor looked at this" — recorded with your name and time on the submission. Flag sends it back into Marco's notifications with your note. Neither blocks the work: T-2205 is already in the task queue either way.
Triage from here: reviewing the inspection and owning its fallout are one sitting, not two tools.
Submissions that nobody looks at teach crews that nobody's looking. The queue is oldest-first, the clean ones drain in bulk, and the two-role rule holds — any admin can review; members see their own results. No per-reviewer routing, no approval chains — that's deliberate.
This entire screen is DESIGNED AHEAD OF BUILD (◇): the product has no submission review status — proposal logged as DQ-25 (single pending→reviewed status + optional flag, admin-role reviewers, never gating field work), pending the data-model session.
Shipped today and reused here: the submission preview (snapshot answers), produced-task links, untriaged (open + unassigned) issue lens. Evidence (V1 production, directional): 25 stuck pending review · ~25% of submissions carry issues (~2.3 issue fields each).
← Prototype home · Inspections · Submission #4471