Mobile adaptation — Confirmed Work Event

The work event is still useful on mobile because it gives schedule context and readiness checks before the tech moves into execution. It should answer: where am I going, when, who is there, what work order is this for, and am I ready to create my work ticket?

What this screen simplifies

• The visit summary is operational, not administrative.
• The relationship is explicit: this work event belongs to a work order and drives the technician calendar.
• Readiness signals are visible before the tech creates or opens their ticket.
• The path into the technician's own work ticket is explicit, with customer-notification timing next to it.
• The address should behave as a travel action, with a clear handoff into Google Maps or another navigation app.

Navigation handoff

The work-event address is not just a reference field. It should be actionable. Tapping the address or the travel CTA should open Google Maps for turn-by-turn navigation, then allow the technician to return to the work event or work ticket once travel has started.