Edit job
What it's for
Edit job changes an existing job's description, site, equipment, priority,
customer PO and project phase. Open Edit on the
job record, at /jobs/<job>/edit. Use
Dispatch or the record's visit
controls to manage individual visits on a multi-visit job.
Tabs
There are no tabs. The form is one page with Save changes and Cancel.
Panels and controls
- Summary names the job; Description holds the job notes.
- Service site selects a site. Leaving it blank keeps the current site.
- Equipment searches and links a unit, or clears the link.
- Priority offers Low, Normal, High and Emergency.
- Customer PO sets or clears the customer's purchase order number.
- Department, when available, changes cost attribution and can ask for a reason.
- Project phase links or clears the project phase.
- Assigned technician, Scheduled start and Scheduled end edit a single visit. When the job has more than one non-canceled visit, these fields are hidden; change each visit on the job record or Dispatch instead.
- The customer-window controls record whether and how you told the customer about the agreed time. A scheduling warning can offer Notify customer of the new time; the result reports whether a notice was queued or unavailable.
- Company-defined custom fields appear when configured.
- Save changes returns to the job record on success. Cancel leaves without saving; invalid inputs keep the form open with the entered values.
Refusals worth knowing
Scheduling changes check working hours, overlapping visits and technician certifications. A hard block refuses the save; a warning asks for confirmation. Overriding a certification mismatch or a gated phase requires a written reason and the necessary access. A staging-and-delivery job with no visit returns Schedule the staging delivery visit before assigning a technician.
What it accepts
| Field | Format | Required | Rule |
|---|---|---|---|
| Summary | Text | Yes | Blank returns Enter a one-line summary. |
| Service site | Pick a site | No change required | Blank keeps the existing site; unavailable sites return Service site not found or not authorized. |
| Description | Text | No | Blank clears the description |
| Equipment | Search and pick | No | Blank clears the link; unavailable units return Equipment not found or not authorized. |
| Priority | Listed choice | For a change | Unrecognized values fall back to Normal |
| Customer PO | Text | No | At most 80 characters; blank clears it |
| Project phase | Listed phase | No | Unavailable phases return Project phase not found or not authorized. |
| Assigned technician | Listed staff member | No | Unavailable staff return Technician not found or not authorized. |
| Scheduled start / end | Date and time in the company time zone | No change required | Invalid times are refused; end must be after start |
| Override reason | Text | For a gated phase or certification override | A reason is required to override a gated phase. / A reason is required to override a certification mismatch. |
| Custom fields | Configured formats | As configured | Invalid values reject the save |
Clearing the time fields does not remove an existing visit: its stored times are retained. Supplying a new start without an end uses the default visit length. Use the visit controls to remove or reschedule a visit deliberately. The form does not change job status, line items, billing type or job type.
How to configure it
Scheduling defaults and branch overrides set visit length and working hours. Company time zone controls the displayed and entered times. Staff certifications and required equipment/trade certifications drive placement checks. Project predecessors drive phase warnings. Departments and custom fields supply their respective choices and validation.
Who can see it
This screen sits behind the Jobs area. Owners, office managers and dispatchers can open it with the standard roles. Technicians use their assigned jobs in the field app. Custom roles and branch scope can narrow access. A direct link does not bypass those checks.
See Roles & permissions.