Schedule Accepted Work in V2 Mobile

Clean Estimate V2 mobile lets an authorized Road teammate schedule work after the customer accepts the estimate and any required deposit is handled. Open Home > New job or Create > New job.

This focused workflow does not create an unrelated manual job. Customer acceptance creates the job through the same exactly-once backend workflow used by web. Mobile then schedules that accepted work through the existing job status, payment, location, crew, checklist, and notification rules.

Who Can Schedule

• Owners, admins, office teammates, and sales representatives can open the V2

Road workflow.

• A sales representative sees accepted work from estimates assigned to them.
• Owners, admins, and office teammates see eligible work inside their permitted

location scope.

• Crew-only teammates cannot open or call the scheduling workflow. They work

jobs already assigned to their crew from Today or Schedule.

Schedule a Job

1. Connect the phone to the internet.
2. Open Home > New job or Create > New job.
3. Select an accepted estimate. The card shows the customer, service address,

selected proposal option, scope, accepted date, location, and job value. Maintenance-plan visits also show their own season and visit-specific scope so similar visits from the same plan cannot be confused. Holiday takedowns and maintenance visits show their existing Target month as scheduling guidance.

1. Confirm the job date with the phone's native calendar.

The minimum is today at the job location, even when the phone is currently on a different calendar day. It refreshes while the screen stays open and when the app resumes; the server applies the same location-timezone check.

1. Optionally choose both a start and end time with the native time pickers.

Leave both blank for an untimed job. On Android, use Clear time beneath a selected optional time to return it to blank.

1. Keep Assign later or choose an active crew offered for the job's fixed

location.

1. Select the pinned Schedule accepted job action.

The surface follows the V1 mobile scheduler's compact card-and-field layout: the estimate context appears first, start and end time controls share one row, and the primary action stays pinned above the system navigation area. V2 uses the safer label Schedule accepted job because acceptance has already created the canonical job; the button does not create a second record.

After the server confirms the schedule, the app waits for that newly scheduled row to reach the phone, then automatically opens the exact job's Road summary. This short confirmation prevents a successful schedule from opening a local summary before its first PowerSync update has arrived. It compares the synced schedule revision and row update time with the server confirmation rather than accepting an older cached copy. The current job still opens if dispatch has superseded the first schedule or changed its assignment, or if the crew has already started or completed it. The job also appears on the synced day schedule.

While that confirmation is visible, the app also checks the same authorized job on the server. If dispatch unschedules or cancels it before its first local delivery, the app returns to accepted work with a clear message instead of waiting for a row that no longer belongs in the mobile schedule stream. It also leaves confirmation if an administrator deactivates the teammate or changes their location scope, because the protected job can no longer arrive through that teammate's local stream.

Eligibility and Safety Rules

A job appears in this workflow only when:

• it was created from a valid customer acceptance;
• the estimate remains accepted;
• the job is still unscheduled;
• a required deposit is paid or waived; and
• the signed-in teammate may act on that estimate and location.

The customer, service address, and location shown in the picker come from the accepted proposal snapshot when available. A later CRM rename or address edit does not silently rewrite the identity the customer accepted.

The accepted estimate fixes the job location. Mobile offers only active crews from that location, and the server validates the crew again while saving. V2's current job model does not have a safe mobile truck assignment input, so truck assignment remains in dispatch.

If another teammate schedules the job first, the mobile request does not overwrite the newer slot, crew, or duration—even when they happened to choose the same date and time. The server uses the revision loaded with the picker and permits only an exact lost-response replay. Refresh the accepted-work list and open the current job from Schedule.

Connection Requirements

Loading accepted work and selecting Schedule accepted job are online-only actions. The app never queues this write while offline, because a live server check is required for acceptance, deposit, ownership, status, and crew availability.

Already synced scheduled jobs remain available in More > Schedule while offline. Reconnect before creating a new schedule.

What This Workflow Does Not Include

The focused mobile workflow does not add full dispatch, routes, manual customer-free jobs, rescheduling, multi-truck booking, or recurring-plan administration. It also omits V1's separate multi-day end date and editable job notes because the current V2 job contract has one scheduled date and preserves acceptance/visit scope on the canonical job. Use the supported web workspace for those office workflows.