← Service Monkey homeSchedule jobs

A daily dispatch checklist for your HVAC office

Prepare technicians for the right job, keep customers informed, and make sure unfinished work has a clear next step.

Prepared by Service Monkey · October 11, 2026 · Updated October 22, 2026 · 7 minute read

Give every job a clear next step

A good dispatch process helps your technicians arrive prepared and helps your office know what happens next. Start with one checklist for new jobs, a short list of job statuses, and a quick review before the day begins.

Your software can support the process, but the office and field team still need to agree on the rules. This guide covers scheduling and job information. Adapt it to your company's approved services, staffing, customer promises, and rules for getting help with unusual situations.

1. Check the job details before scheduling

A customer name and a calendar slot do not tell a technician everything they need. Before scheduling a routine visit, confirm the details below. If something is missing, name the person who will get it.

Job detailWhat to record
Customer and propertyContact information, service address, access instructions, and who can approve the work.
Reason for the visitThe customer's description, equipment records, and notes from previous visits.
Arrival timeThe time window promised to the customer and any access restrictions.
Technician preparationSkills, equipment, and parts needed, plus an initial estimate of the time required.
What the customer has approvedThe agreed work, service agreement, and status of any estimate or approval.
Who handles the next stepWho will schedule the visit and what must be checked first.

Dispatchers should record what the customer says and follow company rules for referring questions to a qualified person. They should not guess a technical diagnosis to fill an empty field.

2. Make each job status mean one thing

Use a short list of statuses that the office and technicians understand the same way. Tie each one to something that has actually happened.

  • Needs information: a required detail is missing. Someone is assigned to get it.
  • Ready to schedule: the required details and approvals are in place.
  • Scheduled: a technician and arrival window have been assigned and communicated.
  • In progress: the technician has started the visit.
  • Waiting: the job needs something specific, such as a part or customer approval. Someone is responsible for that next step.
  • Ready for the office: the technician has supplied the work notes, time, materials, and other information the office needs.
  • Closed: the office has completed the agreed invoicing and follow-up steps.

A status called "done" causes confusion when one person means the work is finished and another means the invoice is paid. Keep those events separate if the business needs to track both. Give every waiting job a person responsible and a date to check it again.

3. Review the schedule before the day starts

A short daily review catches missing information before it becomes a phone call from the field. Look at today's jobs, unfinished work from yesterday, and anything that could prevent tomorrow's jobs from starting.

Check customer arrival windows, technician skills, parts, equipment, travel, and office follow-up. Group jobs by location when it fits the customer's promise and the technician's assignment. A convenient route does not make an unprepared visit ready.

Leave a clear way to handle overruns and changes. For every problem found in the review, record what will happen, who will handle it, and when someone will check again.

4. Give the office what it needs after each visit

Agree on what technicians must record before a visit is ready for the office. That may include work completed, time, materials, photos, customer approval, recommended next steps, and anything still unresolved.

Illustrative example: a technician completes a diagnostic visit but needs a part for the repair. The job moves to "waiting." A parts coordinator checks availability, the office updates the customer, and dispatch schedules the return when the part and required approval are ready. Adapt these responsibilities to your team; this is a proposed example, not a client result.

Keep this information in the job record where the next person can find it. A note in one employee's text messages is easy to miss.

5. Watch a few useful numbers

Number to watchHow to count itWhat to check
Arrivals within the promised windowVisits arriving within the recorded window divided by visits with a recorded window.Jobs running long, travel estimates, and late customer updates.
Scheduled jobs missing detailsVisits scheduled without at least one required job detail.Which detail is missing and who should have supplied it.
Time spent waitingTime from marking a job waiting to completing the next required action.Parts, approvals, or office follow-ups that nobody is handling.
Unplanned return visitsVisits counted as an unplanned return under one agreed definition.The agreed work, parts preparation, job notes, or quality problems.

Find out what is happening now before setting targets. A planned second visit for a multi-stage job is different from a callback. Use the same definitions and account for differences in job types when comparing teams.

Try it with one crew first

Choose one crew or one job type. Review a few recent jobs, note the recurring missing details, and agree on what must be recorded. Then walk one real job through each status with the office and field team.

During the next working week, check problems daily and adjust the instructions. Expand the process when the team can use it without guessing.

Daily dispatch checklist

  • Today's jobs have the required customer and job details.
  • Technician assignments match the work.
  • Promised arrival windows and access instructions are recorded.
  • Parts and equipment are ready.
  • Waiting jobs have a person responsible and a next step.
  • Yesterday's technicians have given the office what it needs.
  • Someone is handling anything that could delay tomorrow's work.

Sources and context

These instructions and examples describe a suggested way of working. They are not client case studies or a trade standard. Adapt them to your business and the requirements of your work.

Work with Service Monkey

Book a session.

Bring us a decision or a problem in your service business. We’ll use the session to work through it with you and agree on a next step.