Design mockup GearJot V2 · C2e·Straight · design target — not a screenshot
Synced · 2 min ago + New DW
Inspections

Inspections

Submissions, drafts to finish, and templates — one home. The runner is where inspections get filled out; the review queue is where they get looked at.
▤ Templates & builder + Start inspection

Loading inspections… (skeleton shimmer pauses under reduced motion)

No inspections yet

Inspections start from a template. Build one (or pick a starting point from the gallery), assign it to gear, and the first walk-around takes about two minutes on a phone.

Pick up where you left off
Daily walk-around — Excavator
EX-214 · Marco · started 7:15 AM
7 of 12 answered · cached on this device
Resume
Weekly service check
DT-330 · Marco · 2 days old
⏱ 2 days in draft
Resume

The full submission list needs a connection. Nothing queues from this screen — it's read-only while offline.

Submitted · 7 days
23
On pace
Open drafts
9
4 older than 2 days
◇ design-ahead
Needs review
25
Issues raised · 7 days
12
finish what you started
Pick up where you left off Cross-gear strip — design-ahead

Real-world evidence (V1 production): roughly half of started inspections stall in draft and never get submitted. This strip exists to make resuming easier than restarting — drafts surface here, on the dashboard, and on each unit until they're finished or discarded.

Daily walk-around — Excavator
EX-214 · Marco · started 7:15 AM today
7 of 12 answered · auto-saved just now
Resume
Weekly service check
DT-330 · Marco · 2 days old
⏱ 2 days in draft — finish or discard
Resume
Pre-hire condition report
SS-107 · Priya · 6 days old
⚠ 10 of 12 answered, 6 days old — two questions from done
Resume

Drafts are personal — you see yours; admins see the company's aging drafts here. A draft becomes the submission when it's completed: same record, same id, so anything linked to it (like a reported issue) survives submit.

Start an inspectiontemplate picker narrows to this unit's assigned templates
Start →

Templates are offered by assignment — type, make, model, or individual machine — so the right checklist shows up for the right unit. Manage them in the builder. Build note: the unit picker should ride the lightweight fleet name list — that endpoint exists for filters but isn't wired to this picker yet.

Submissions
#UnitTemplateSubmitted byWhenIssuesReview

Rows open the submission. The Review column is designed ahead of build (◇) — there is no review status in the product yet; the review queue screen carries the full proposal. Filters (template · unit · submitter) and saved views are shipped behavior.

◇ design-ahead
Due & scheduled Design-ahead
EX-214Daily walk-around due today · runs every working day Done 8:42
DT-330Daily walk-around due today Not started
WL-118500-hr service check meter-based · 4,986 of 5,000 h 14 h away

Scheduling attaches to the template (see Assign & schedule). Evidence note: in V1 production, preventive checks run on meter hours via forms, not calendar dates — the meter trigger is first-class here, not an afterthought.

Where inspections land
Runnerfill out · photos · report issues
Submission#4471 pinned to its template snapshot
TasksT-2205 linked to the exact question

Meters and location write back to the unit on submit — an inspection updates EX-214's hours without anyone re-typing them.

DESIGN MOCKUP — GearJot V2 · C2e·Straight · design target, not a screenshot.
Shipped behavior matched on this screen: submissions list with template/unit/submitter filters + saved views; start pickers on name lists; drafts resume (server-side, per-user). Designed ahead (◇, tagged inline): cross-gear draft strip w/ aging + discard, date/has-issues filters, review status column + queue, due & scheduled panel.
Evidence (V1 production, directional): ~50% of started inspections stall in draft; ~80% of all attachments live on inspections; 25 stuck pending review.
← Prototype home · Runner · Submission #4471 · Review queue · Templates & builder