Inspection runner
Phone frame: the runner is a one-hand, gloved-thumb surface — 48px result buttons, camera first. Desktop shows the same runner at full width; nothing here is phone-only.
EX-214
"Save & finish later" parks this draft in Inspections → Pick up where you left off. Required questions left blank stop "Review & complete" with a what's-missing list — nothing submits partially by surprise (OQ-1 RULED: block, founder 2026-07-13).
EX-214
Auto-save runs a couple of seconds after each change once a draft exists; "Save & finish later" parks the draft in Inspections. ◇ Design-ahead: starting the draft on the first answer (today it starts on resume or first reported issue) — the anti-stall fix.
Reloading replaces these answers with the other session's version. If it was already submitted over there, submitting here is blocked the same way — one record, no forked history.
Out of signal? The runner switches to its offline mode by itself — cached templates keep working. ◇ design-ahead (Mobile pillar)
Shipped behavior matched on this screen: card-per-question with swipe + Previous/Next, sections ("Section 2 of 3"), 12 field types incl. Yes/N-A/No with template-renamed buttons, per-answer camera photo + video + files (big uploads chunked), per-question Report-an-issue (creates the linked task immediately and starts the draft — drafts and submissions are one record), unresolved-issue notice per question, draft resume + 2s auto-save + edited-elsewhere conflict stop, meter/location write-back on submit only, unfinished-upload check at submit.
Designed ahead (◇, tagged inline): on-device offline queue incl. offline issue capture (Mobile pillar), "Save & finish later", draft-on-first-answer, per-answer note input. Evidence: ~50% of V1 inspections stall in draft — the park/resume affordances are the fix.
← Prototype home · Inspections · Submission #4471