Job states
Launching first, end of November
Mobile MechanicsRoadside help, maintenance and repairs, quoted before work starts. Winter Snow RemovalDriveway, walkway and steps, with snowfall updates and later-visit requests.
Coming soon
Garbage Bin CleaningNot bookable yet. Get notified when it launches.Coming soon Fall CleanupNot bookable yet. Get notified when it launches.Coming soon Lawn MowingNot bookable yet. Get notified when it launches.Coming soon Mobile Car Wash at HomeNot bookable yet. Get notified when it launches.Coming soon Roadside help & repairsMobile mechanic service menu Basic or PremiumBook when needed, or get monthly provider reminders Other jobsPost any job and get offers from local providers

Job states & rules

Clients, contractors and admins see the same job state, and payment is shown separately. Each rule links to the screen that shows it.

Job lifecycle

  1. 1Requested
  2. 2Open for bids
  3. 3Confirmed · funds held
  4. 4On the way
  5. 5Arrived
  6. 6In progress
  7. 7Pending your approval
  8. 8Approved

Exceptions

CancelledDelayedChange requestedDisputedWeather reviewNo provider available

Payment (separate state)

UnpaidAuthorized · funds heldCaptured · paid outPayment failedPartially refundedRefundedDisputed · funds held

A job with funds held is not paid out. Payment is captured and paid out only after the client approves the work; reminders, job creation and confirmed reschedules never trigger duplicate payment attempts.

Status, timing and exception rules

Requested / open for bids RequestedOpen for bids

Customer sees
The task, the target budget and the offers coming in; a boost raises pickup speed
System must do
Notify nearby approved contractors; show no-offers and no-provider fallbacks; keep the payment Unpaid

Confirmed with funds held Confirmed

Customer sees
Agreed contractor, price and window; “Funds held securely until you approve the work”
System must do
Authorize (hold) the payment with the secure processor; show Authorized in the payment chip

Change requested Change requested

Customer sees
Old window retained; proposed new window pending
System must do
Ask the contractor to confirm or decline without losing the old slot

On the way / arrived On the wayArrived

Customer sees
ETA freshness, trip map, message; arrival update
System must do
Active-trip location sharing only; contractor confirms arrival

In progress / revised quote In progress

Customer sees
Work update; an on-site revised quote needs your approval before extra work
System must do
Pause the extra work until the client approves the amended amount

Completed, pending approval / approved Pending your approvalApproved

Customer sees
Before and after photos, checklist; Approve and release payment or Report a problem
System must do
Require at least one before and one after photo; capture and pay out only after approval

Disputed Disputed

Customer sees
Funds stay held; the case and the decision are visible
System must do
Operations reviews evidence, then releases, refunds or splits the held amount

Acceptance scenarios

A guest prices a snow taskAddress, scope and a price range before any sign-in; the sign-in prompt appears only at Post task; the draft survives sign-in.
The budget is too lowBoost your bid shows the effect on expected pickup time; offers still arrive at the contractor’s own price.
Roadside breakdownProximity broadcast to nearby approved technicians; no scheduling; the first to accept is shown with an ETA.
Mechanic finds more work on siteA revised quote with the new amount; the client approves or declines before extra work; funds held change only after approval.
Contractor must prove the workThe completion report cannot be submitted until a before and an after photo are uploaded.
Work is contestedThe client reports a problem; payment shows Disputed; operations resolves it from the disputes queue.
A new contractor joinsIdentity, insurance, licence and mechanic certification are reviewed before they can see open jobs.

Acceptance checks

  1. A guest can explore scope and a price range; sign-in is asked for only when posting.See screen
  2. Only the two live services take tasks; locked services show Coming soon.See screen
  3. Show price and scope before confirmation; extra work needs approval.See screen
  4. Contractor status changes appear in the client timeline and notifications.See screen
  5. Weather rescheduling records a reason and does not duplicate jobs.See screen
  6. Completion needs before and after photos; an issue opens a disputes case.See screen
  7. Payment retries cannot create duplicate charges; failed payments stay visible.See screen
  8. Each role can access only its permitted records.See screen
  9. A new service can be configured without rebuilding the common workflow.See screen

Screens show the intended UI states with sample data. The behaviour behind each check is built separately.