What a job is
A job is the unit of operational work created when an estimate is sold. Every job carries exactly one status from a fixed list of ten values. A job moves between statuses two ways:- Automatically, in response to upstream events (a crew lead being assigned, a plan being approved, a schedule being published, an estimate being lost, and so on).
- Manually, when a user changes the status from the Jobs list.
The ten job statuses
Closed and Cancelled jobs can’t be scheduled
A job that is Closed Job or Cancelled is treated as a terminal state for scheduling: you cannot schedule new work against it. The other eight statuses can still be scheduled.How a job moves between statuses
A job starts at Requires Crew Lead when an estimate is sold
When an estimate is marked Sold and no job yet exists for it, the system creates the job at Requires Crew Lead.Assigning a crew lead advances to Plans In Progress
When a job at Requires Crew Lead gets a crew lead assigned, it automatically advances to Plans In Progress. If the crew is later cleared (no crew assigned) and the job is not closed, the job reverts to Requires Crew Lead.Moving a job back to Requires Crew Lead is destructive
Manually setting a job back to Requires Crew Lead resets the job: it clears the assigned crew and removes the job’s plan, plan days, item assignments, vehicle and equipment requirements, employee requests, and shifts, and it clears the scheduled date. Use this only when you genuinely want to start the job’s planning over. Because this can’t be undone, choosing Requires Crew Lead from a job’s status dropdown on the Jobs page opens a confirmation dialog — Move this job back to Requires Crew Lead? — spelling out that it permanently deletes the job plan, the crew’s logged hours, the assigned crew, and the scheduled date. The job’s status doesn’t change until you confirm with Delete plan and hours; choosing Cancel leaves the job exactly as it was. The prompt only appears when the job is moving into Requires Crew Lead from another status — a job already in that status has nothing left to clear.Completing and approving the plan advances the job
As the job’s plan progresses, the job advances automatically:- When the plan is marked complete, the job moves to Pending Review.
- When the plan is approved, the job moves to Requires Scheduling.
Publishing the schedule advances to Pre-Production
When shifts are published for a job, the job advances to Pre-Production and its scheduled date is set to the latest published shift’s start time. This advance only happens when the job is currently at Requires Scheduling, so publishing a schedule never overrides a status the job has already moved past.In Production, Production Complete, and Pending Payment are manual only
There is no automatic transition into In Production, Production Complete, or Pending Payment. A job reaches these statuses only when a user changes the status manually from the Jobs list.Closing a job (manual)
Closing a job is a manual status change. When a job moves into Closed Job:- The job’s closed date is set (you can record a back-dated close, so historical jobs bucket their bonuses to the real date).
- The salesperson is notified.
- An hours-saved win may be created automatically.
- Bonus payouts for the job are finalized.
Reopening a closed job
Moving a job out of Closed Job reverses the close: it clears the closed date, reverts the bonus payouts, and updates the affected earnings and performance figures for that date.Cancelling a job (manual) cascades the estimate to Lost
When a job moves into Cancelled, the linked estimate is updated to Lost. The reverse also happens from the estimate side: if an estimate is marked Lost, its job is set to Cancelled — but only when the job is not already Cancelled and not Closed Job.Re-selling an estimate resets the job to Plans In Progress
If a previously sold estimate is sold again and a job already exists, the job is reset to Plans In Progress — but only when the job is already past Requires Crew Lead and not Closed Job.Which transitions are allowed
There is no forced transition order
A user who is allowed to change a job’s status can move it to any of the ten statuses from any current status. The forward path described above is the intended flow, not an enforced state machine. Changing to the same status the job already has does nothing. The side effects described above (the destructive reset on Requires Crew Lead, the close/reopen handling, the cancel cascade) still run on the relevant transitions regardless of the order you move through statuses.Who can change a job’s status
Roles that can change job status
A user can only change the status of jobs in a branch they have access to.