Completing & Closing Jobs

Starting a job, finishing it, and closing it off are three separate actions in AxiomBlue. This article covers each one, the statuses a job can hold, and what completion sets in motion.

The statuses a job can hold

A job holds exactly one of eight statuses:

• Pending — created, not yet scheduled.
• Scheduled — booked into the calendar.
• In Progress — work has started.
• Paused — started, then stopped mid-shift.
• On Hold — parked, usually waiting on the customer or on parts.
• Completed — work finished, ready to bill.
• Cancelled — abandoned.
• Invoiced — billed.

You can edit a job's fields while it is Pending, Scheduled, In Progress or On Hold. Other statuses lock the fields.

Start a job

The button at the top right of the job detail page changes with the job's status. On a Pending or Scheduled job it reads Start Job.

1. Select Start Job.
2. Confirm in the dialog — it warns that the status moves to In Progress and assigned technicians are notified.

Once the job is running, the same button becomes a clock control. It reads Clock Out when you are clocked in, and Clock In when you are not. Mark as Complete sits in the chevron menu beside it. On a Paused job the button reads Resume.

Complete a job

1. Check the time entries and materials are recorded — see Time Tracking on Jobs and Materials & Expenses.
2. Select Mark as Complete, either as the main button or from the chevron menu beside it.
3. Select Confirm Completion.

A job must be In Progress or Paused to complete. From any other status the API refuses with Job must be in progress or paused to complete.

On the mobile app, completion adds a Completion Notes (Optional) field before you select Complete. The portal has no equivalent field — record the same detail as a job note instead.

What completion does

• Closes every time entry still running on the job.
• Records the completion time and moves the status to Completed.
• Notifies everyone who clocked in, everyone assigned, and the business owners.
• Raises the job.completed automation event.
• Puts a Generate Invoice button in the job header.

Two ready-made automations listen for that event. Job Completed — Send Customer Review Request waits two hours, then emails the customer for a review. Job Completed — Auto-Generate Invoice raises a draft invoice from the job and tells an admin to check it. Both stay off until you add them — see Templates & Suites.

Cancel, change, duplicate or delete

The rest of the lifecycle actions live in the Options menu in the job header.

• Cancel Job — asks for confirmation and moves the job to Cancelled. It offers no reason field, so record the reason as a note first. The item hides once a job is Completed, Cancelled or Invoiced.
• Change Status — an override. Pick any of the eight statuses from New Status and select Save Status. Setting Completed this way still raises the completion automation event.
• Duplicate Job — copies the job and opens the copy, ready for new dates and a new customer.
• Delete Job — permanent, and refused on an invoiced job.

What you should see

A completed job shows the Completed status, no clock control in the header, and a Generate Invoice button. Every time entry has an end time.

Next: Converting Jobs to Invoices.