← Back to project overview Mobile wireframes

Service Location & Work Order

Commercial hub · before execution
SCREEN 02Reference

Service Location

Read-only location reference with tabs for Overview, Customers, Contacts. Tech can link or add customers & contacts — core location fields stay back-office-only.

customerscontacts
Open →
SCREEN 06Home

Work Orders

Grouped list of assigned work orders — "Needs your action", "Open", "Completed" — with search, status filter chips, and a callout clarifying the no-create rule for v1.

listfilter
Open →
SCREEN 17Hub

Work Order

The hub. Hero + service context + commercial snapshot, then a jig.list of work streams — Estimates, Tasks, Materials, Prepayments, Tickets, Notes, Invoices. AI brief on top.

summaryAI brief
Open →
SCREEN 182 states

Estimates

List of estimate lines with total, sharing state, and cost/margin per line. Add a new line from inventory or a template pack; share with the customer via email/print/preview.

inventoryshare
Open →
SCREEN 19Read-only

Tasks

The tasks that drive scheduling. Read-only on mobile in v1 — tech can open each task to see its checklist and linked ticket but can't create or reschedule.

checklistevents
Open →
SCREEN 202 states

Planned Materials

Planned material list + add-item form with a required "needed-by" date. Callout explains planned (WO-level) vs actual (ticket-level) so they don't get confused.

needed-bypull from estimate
Open →
SCREEN 133 states

Prepayments

Collect a deposit — cash, check, card or ACH. Three linked states: choose method, capture (card form or reference #), success with receipt-send (email / SMS).

cashcheckcard
Open →
SCREEN 22Sheet

Work Order Actions

Bottom-sheet action menu grouped by Money / Work capture / Communication. Back-office-only actions are visible but disabled with a "v2+" pill so the tech sees what's possible.

action menuv1 scope
Open →

Plan the Day

Dispatcher & Technician
SCREEN 25Dispatcher

Calendar Board

Week strip, technician strip, and a day schedule. Drag to reassign, tap to open a work event. Uses jig.composite with three stacked jig.list sections.

weektechnicians
Open →
SCREEN 27Technician

My Day

Map-backed home hub with next stop, the day schedule, and a billable rail. jig-header map, list-item stops, bottom tabbar.

maptabbar
Open →
SCREEN 26Prep

Work Event Details

Visit context — customer, location, window, assignment, readiness checklist. jig-header hero, field-row pairs, jig.list readiness.

visitchecklist
Open →
SCREEN 28Task

Work Event Task

The task detail opened from a work event — template, duration, checklist, and expected materials. One dock CTA: create a work ticket. Drives Screen 32 (Guided Tasks).

checklistpre-exec
Open →
SCREEN 292 states

Confirmed & En Route

State A is the confirmation summary, State B hands off to Maps. Shows the Jigx pattern of a confirmation card + location widget + primary dock.

confirmlocation
Open →

Execute the Ticket

Time · Tasks · Materials · Expense · Notes
SCREEN 30Home base

Work Ticket Home

Single execution surface — status, live timer, verb rail, voice capture, tabbar. Everything the tech needs starts here.

timerverbsvoice
Open →
SCREEN 312 states

Timesheet

State A is the live time-clock, State B is a manual entry form (duration-picker + entity-field + labour category).

clockmanual
Open →
SCREEN 32Guided

Guided Tasks & Evidence

Checklist with missing-item highlighting, choice-pair pass/fail, jig.gallery for before/after photos. "Capture next required" is the primary action.

checklistphotos
Open →
SCREEN 342 states

Inventory Lookup

Truck-stock + warehouse list with scan, then a qty confirmation form with live line total in the primary button.

scantruckwarehouse
Open →
SCREEN 352 paths

Expense Receipts

Two paths for capturing an expense: take a photo and let AI detect merchant, date, total & line items, or enter it manually for cash, mileage, or a missing receipt.

photo + AImanual
Open →
SCREEN 36Thread + AI

Notes

Ticket notes as a chat thread with alternating self/other alignment, plus an AI summary tab with TL;DR, timeline of key events, open items, and people.

chatAI summary
Open →

Closeout

Customer-facing
SCREEN 48Customer

Work Summary & Sign-off

State A is the bundled summary the customer reviews; State B is the signature pad with confirmation checklist and "email a copy" entity field.

signaturePDF
Open →

What changed vs v1

Design rationale
RATIONALE · 01Consistency

One CSS toolkit

v1 was hand-styled per screen so colors, radii, fields, and pills drifted. v2 has a single jigx-mobile.css that maps each class to a Jigx primitive, so every screen inherits the same visual vocabulary.

RATIONALE · 02Usability

Thumb-first dock

Primary actions live at the dock in a button block that names the outcome (and often carries a live total). No more "Next" at the top-right.

RATIONALE · 03Voice

Voice is a surface, not a feature

Dictation lives at the dock or as a field-level mic — not as a modal. Every input-heavy screen can be completed by speaking.

RATIONALE · 04Jigx fit

1:1 component mapping

Each screen's notes panel calls out the exact Jigx primitives used — jig-header, card (isContained), list-item, field-row, signature, open-scanner — so translating into a Jigx solution is lift-and-drop.