Wireframe — Tasker Execute + Batch Verify Review

Annotations

1. A1 Execute header. Task title, reservation context, elapsed timer, overall completion progress. Always visible. Back button returns to task detail without stopping the timer.
2. A2 Completed section. Clear "Done" badge. Progress bar full. Stays visible so the Tasker can revisit without scrolling back through items.
3. A3 In-progress section. Warning color on the progress bar signals "not done yet." Tap to drill into the section detail.
4. A4 Bottom CTA — disabled until gate passes. "Review & complete" wakes up when all required items and photos are logged. The button does NOT complete the task directly — it opens the Batch Verify Review (screen 3).
5. B1 Reference photo card. What "done" looks like for this section, from the template. Collapsed by default in some cases; expanded here for clarity. Principle 1 — Tasker delight (zero-ambiguity expectations).
6. B2 Item with photo requirement. Large touch target (gloves friendly). Photo capture opens camera with client-side compression (Principle 11 — device empathy). AI verification runs in the background after upload; result shown inline when ready (violet chip on completed items above).
7. B3 Section-level CTA. "Finish section & batch-verify" — the new pattern. Lets the Tasker complete the physical work first, then rapidly review all checked items in a batch pass (Principle 5 + validated T-11 behavior). If the section still has incomplete required items, this button is labeled "Finish remaining first" and disabled.
8. C1 Batch Verify Review — hero. Tasker has finished a big chunk of work and wants to quickly confirm "yes, I did all of this." Two buttons: "Mark all verified" (commits everything), "Flag any" (enters per-item review mode). The UX respects the validated pattern: users do the work, then click through at the end (Q11 validation).
9. C2 Grouped item list. All items across all sections, grouped by room, with big obvious check-marks. Scroll-friendly. Tapping an item un-checks it (mistake recovery). A "+ 23 more" collapsed row hides completed-and-already-verified items to avoid fatigue on 100+ item tasks — the rare long-tail case.
10. C3 Complete CTA. Final commit. Green signals positive, celebratory action. Sub-text is a concrete summary: items verified, items flagged, time elapsed. Tap → Review & Complete screen (not shown: a 2-stat celebratory summary with an optional comment field and "Submit for payroll" hand-off).
11. Persistent Report Issue button (top-right, red, on both screens 1 and 2). Reachable from anywhere in Execute. Opens a bottom sheet that preserves the current scroll position (Principle 6 — report-and-return). Submitting spawns a new standalone task with source context (current task / property / reservation / reporter).
12. Offline behavior. Every interaction on all three screens is offline-safe. Checkmarks commit locally; photos queue; AI verification runs when online. The UI never shows a "please reconnect" state (Principle 4).