Screen 19 — Work Order Tasks

Read-only list of tasks on a work order. Tasks drive scheduling — each one becomes a work event assigned to a technician. The technician reads this screen to understand what the order expects; they don't create tasks on mobile in v1 (scheduling is back-office only).

← Back

9:30

‹

TasksWO-000046 · Adriaan House

Tasks on this order

3 tasks · 6 h planned

Scheduled

Tasks

✓

Diagnose heat cycle

1 h · Maxwell · Apr 13

›

Replace control board

3 h · Maxwell · Apr 22

Active›

Post-install verification

2 h · unassigned

›

🔒

Read-only on mobile

Dispatch creates and schedules tasks. Each scheduled task becomes a work event the technician opens to capture the ticket.

Jigx component mapping

jig.default with a summary card (count + status) and a jig.list of tasks. Each task uses a list-item whose avatar doubles as a status indicator (green check for done, amber number for active, muted number for pending). A single callout explains the v1 read-only constraint and the task → event → ticket flow.

Primitives used

Summary card — count and hour budget, paired with a single status pill
jig.list of task list-items — avatar status, title, single-line sub (hours · technician · date)
One callout covering the read-only / how-tasks-work message
Dock: Open active ticket is the only real CTA — v1 tech can't create tasks

Cleanup vs prior pass

Removed the chunky 22px summary stat — read as too loud for a list page.
Each task is now a clean two-line list-item; the third "desc" line was crowding the right side.
Status pills on the right collapsed — done/pending are conveyed by the avatar, only "Active" keeps a pill.
Two stacked callouts merged into one.