Flow: Pre-Exit Check and Delivery
Pre-Exit Check
Trigger: Vehicle repairs done, QA needed before exit Device: Web or phone Action type: Full-screen (complex checklist)
Steps
Dashboard → "Ready for Action" queue → tap vehicle
Vehicle Detail View → Quick Action: "Pre-Exit Check"
Full-screen checklist opens with "← Back to Vehicle" breadcrumb:
Cleanliness: Exterior wash, interior clean, floor mats, glass
Systems: Lights, AC, audio, windows, central lock
General: "Who left with" field, exit photos
If ALL checks pass → vehicle status moves to "מוכן ליציאה" (ready for exit)
If ANY check fails → vehicle stays "בטיפול" (in repair) for fixes
"← Back to Vehicle" returns to the vehicle view
Car Delivery
Trigger: All mokeds complete, vehicle ready to return to customer Device: Phone (driver at customer location) Action type: Full-screen (signature capture required)
Steps
Dashboard → "Ready for Action" queue → tap vehicle
Vehicle Detail View → Quick Action: "Deliver"
Full-screen flow opens with breadcrumb:
Step 1: Verify all mokeds show "הסתיים" (completed)
Step 2: Enter receiver details (name)
Step 3: Capture delivery photos
Step 4: Customer signature (signature pad)
Step 5: Confirm delivery
Submit → ALL mokeds update to "הסתיים חזר ללקוח" (returned to customer)
Vehicle disappears from active queues on dashboard
Why Full-Screen
Both flows involve multi-step checklists or legal requirements (signatures) that need dedicated screen space. Slide-in panels would feel cramped. The breadcrumb ensures the user can always return to the vehicle context.