Screen 26 — Work Event Details

The scheduled-event record the technician opens before they create a work ticket. Jig.default with a jig-header hero, one card of entity-fields, and a docked primary action to create the ticket.

← Back

9:41

‹

🎤 Voice

HVAC MaintenanceWork Event · Not started

Task-linked AL00026 9h estimated

Visit details

When

Tue, April 14 · 8:00 AM – 5:00 PM

📅

Location

1325 Park Ave, Hatfield, PA

📍

On-site contact

Adam Wilson · 206-145-4503

☏

Work order

WO-000046 · AACUSTOMER

›

Assignment

Maxwell Baker

Service Technician · solo

Confirmed

📋

Scheduled task

Maintenance Work · checklist attached

›

Pre-travel readiness

✓

Task package attached

1 technician task

✓

Materials planned

HVAC control system on order

Send on-the-way message

Optional · not sent

Jigx component mapping

A jig.default with a jig-header image as the hero. Inside, a card of entity-fields displays the event, then two jig.list blocks cover assignment and readiness. The primary action is a docked component.button type primary.

Primitives used

jig-header (image required)
card with entity-field rows
list-item with left check icon for readiness
pill chips in the title block
Docked button type primary

What improved vs v1

Hero image replaces the gradient band — matches Jigx's "hero photo" pattern on the reference Door Quote screens.
Entity-fields are used for display-only data (address, contact, order), not input fields — matches Jigx semantics.
Readiness is a checklist at the bottom, not an orphaned paragraph — action-driven, not informational.
Single primary action at the bottom; "Start travel" lives inside the readiness checklist rather than competing with Create ticket.