Screen 28 — Work Event Task

The task the scheduled work event is built from. The technician opens it from the work event (Screen 26) to see the checklist, required evidence, and estimated duration before creating a work ticket. The checklist then drives the Guided Tasks screen (Screen 32) once a ticket is open.

← Back

9:36

‹

Task · Replace control boardWO-000046 · task 02

⋯

Checklist

Workforce

Events 1

Template

MAINT-REPL

Duration

3 h

Planned start

Apr 22, 10:00 AM · Maxwell

📅

Work event

WE-00109 · confirmed

›

Checklist · 4 steps

Power-down & LOTO

Confirm breaker off · apply tag

Required

Before-photo of control board

Photo evidence · tagged to ticket

Evidence

Swap board (AX44)

Material · CB-AX44 · 1 EA

Required

Verify two heat cycles

Confirm stable cycle > 20 min

Required

Materials this task expects

CB-AX44 · HVAC control board

1 EA · planned · on PO-000112

En route›

AF-2025-1 · Air filter 20×25×1

2 EA · on truck

On truck›

ℹ

This task drives the ticket checklist

When you start the ticket, these four steps appear on Screen 32 (Guided Tasks) and each one records its own evidence.

Jigx component mapping

jig.composite with jig.tabs (Checklist / Workforce / Events). The top card holds template + duration + planned-start as field-rows. The checklist is a jig.list of numbered list-items. A second jig.list lists the materials the task expects so the tech can see if the parts are on the truck or still en-route.

Storyboard fit

The storyboard says: "Once the work event is created based on the task. The technician can open the task from the work event and see the details such as steps that need to be created." This screen is exactly that view — read-only checklist + context, plus the one CTA that matters: create a work ticket.

Primitives used

jig.tabs — Checklist / Workforce / Events
Meta card with template / duration / planned start / linked work event
Numbered jig.list checklist with a pill rightElement (Required / amber Evidence)
Second jig.list for expected materials with on-truck / en-route state
callout explaining that this checklist drives Screen 32
Dock: "Create work ticket" — the one action that carries the tech into execution