Guide
Job Scheduling:Priority Classes, Job Durations, Capacity and Backlog, Dig-Notice and License Dependencies, Recurring Visits and Tracking Practices
Job scheduling for service businesses: priority classes, durations, capacity and backlog, dig-notice and license dependencies, recurring visits and tracking.
Job scheduling is the assignment of each customer job to a date, an arrival window and a qualified technician, in an order that keeps every promise made to a customer. A service business schedules by sorting jobs into priority classes, estimating each job's duration, checking capacity and backlog, clearing dependencies such as dig notices and licensed testers, and placing recurring visits first.
When any of those steps is skipped, the failure lands on a named day. An installation is booked for Wednesday and the utility locate is not valid until Thursday. A backflow test goes to a technician who is not licensed to sign the report. An emergency displaces three planned jobs, and none of the three customers is told. This page belongs to FieldRanger's dispatching and scheduling guides. It separates the field and computing senses of the term, then works through priority classes, durations, capacity and backlog, dependencies, recurring visits, arrival windows and changes, sets out tracking practices for crews, and schedules one sample week with sourced rules and wages.
Four terms carry the method. A priority class groups jobs by how soon they must be served: emergency, urgent, planned or recurring. Duration is the paid time a job takes, on site and in the truck. Backlog is the booked work not yet done, counted in technician hours or in days of capacity. A dependency is a condition that must be met before a job can start, such as a valid locate ticket, a permit or a part on the shelf.
Job scheduling in field service and in computing
The phrase has two senses. In computing, a job is a program run without a person at the keyboard, and job schedulers such as cron decide when it runs. In field service, a job is a visit to a customer's site, and scheduling decides when it happens and who does it. The job scheduling software glossary entry sets the two side by side. This page uses only the field sense.
Scheduling also differs from its neighbours. Dispatch is the hour-by-hour work of sending technicians and handling the day's changes. Routing orders one technician's stops to cut drive time. Scheduling comes first and works days or weeks ahead: it decides which jobs go into which days at all.
Job priority classes: emergency, urgent, planned and recurring
Every incoming job is classed before it is placed, because the class decides which other jobs it may move.
| Class | Example | Placement rule | May displace |
|---|---|---|---|
| Emergency | Burst main line, no heat, active leak | Same day, from the emergency reserve | Planned and recurring jobs |
| Urgent | Failed component with a temporary workaround | Next open window within the company's stated response time | Recurring jobs only |
| Planned | Repair, installation, replacement | First window with capacity after dependencies clear | Nothing |
| Recurring | Seasonal start-up, maintenance visit, annual test | Placed first, weeks ahead, grouped by area | Nothing |
The response time for each class is the company's own promise, written into its service terms and kept as a number that can be measured. Two rules make the table work. Only an emergency may displace planned work, and every displaced customer is told the new time before the original window opens.
Job durations from completed jobs
Duration is the input every later step depends on. A capacity figure built on a wrong duration is wrong by the same margin on every job of that type.
The source is the company's own record: clock-in and clock-out times logged against each job, grouped by job type. Three rules keep the figure honest:
- Paid time, not wrench time. The drive to the job and the time to close it out belong in the duration that capacity uses.
- A typical figure and a long figure. The middle of the recorded times sets the plan; a longer figure, such as the time eight jobs in ten finish within, sets the buffer before a fixed appointment.
- One type per duration. A spring start-up and a zone repair are separate job types even when the same technician does both.
A new company without records starts from a stated assumption and replaces it with the recorded figure once each job type has enough completed jobs to measure.
Capacity, backlog and the booking horizon
Capacity is the paid technician hours available in a period, less the hours held back for emergencies. Backlog is the hours already booked. Their ratio is the booking horizon: the number of days before the first open slot for a new job of a given type.
A company with 200 start-up requests and capacity for 60 start-ups a week has a backlog of 3.3 weeks, or about 17 working days. The horizon is the number a customer hears when calling, and it is the number to watch: a horizon growing week by week means demand has passed capacity, and adding a technician or narrowing the service area is a decision for that week, not the season's end.
Backlog is counted by skill as well as in total. A team with spare hours can still have a five-week horizon for the one job type that only one technician is licensed to do, as the sample shows.
Dependencies before the first visit: dig notices, permits, parts and licensed testers
A job with a dependency is scheduled from the date the dependency clears, not from the date the customer asks.
Dig notices. Any job that breaks ground, from an irrigation line to a fence post, waits for the utility locate. Michigan's MISS DIG statute requires an excavator to "provide a dig notice to the notification system at least 72 hours, but not more than 14 calendar days, before the start of any blasting or excavation" (MCL 460.725, checked November 13, 2026). The count runs from the time of the notice during business hours; a notice given before 7 a.m. starts at 7 a.m., a notice after 5 p.m. or on a nonbusiness day starts at 7 a.m. on the next business day, and "all hours of nonbusiness days are excluded". A ticket is valid for 21 days from the start date, or 180 days where the notice says the work will run longer, and an emergency follows its own prompt-notice rule.
Licensed testers. Some recurring work can only go to one kind of technician. Grand Rapids, Michigan states that backflow preventers "are required to be tested by a licensed plumber who is employed by a plumbing contractor and is ASSE certified to test backflow preventers", and that "the Michigan Plumbing Code requires all backflow preventers to be tested annually" (City of Grand Rapids, Residential Irrigation Backflow Testing FAQs, checked November 13, 2026). An irrigation technician without those credentials cannot take the job, however close to the address.
Permits and parts. A permit is applied for, and a special-order part is ordered, when the job is sold; the job is placed in the first window after the permit is issued or the part is received, and the date of each is recorded on the job.
Recurring visits and deadline-driven work
Recurring work is known in advance, so it is placed before anything else and grouped so that each day's visits sit near each other. Seasonal work, such as irrigation start-ups in spring and shutdowns in autumn, arrives as one wave that fills weeks of capacity at once.
Deadline-driven recurring work adds a date that cannot move. Grand Rapids divides its water system into five residential backflow test zones and requests a current-year test report from each zone once every five years: Zone 5, from 36th Street south to 60th Street, in 2026, and Zone 1, from 4 Mile Road south to Leonard, in 2027. A company with customers in the reporting zone schedules those tests early in the season, ahead of the start-up wave, because the licensed tester is the bottleneck for every one of them.
Arrival windows and confirmations
The window is the promise the customer hears; the confirmation is where it is written down. A confirmation carries the date, the window, the technician's name, what the customer prepares (gate unlocked, controller accessible, pets inside) and how to reschedule. Its fields are laid out in the appointment confirmation template.
A second message on the day, sent when the technician leaves the previous job, narrows the window to an arrival time. Window width and the capacity of each window are set out in service scheduling; this page treats the window as one more constraint a job must fit.
Schedule changes: cancellations, overruns and emergencies
A schedule changes every day, and the rules for changing it are set before the day starts. A cancellation releases hours to the next job in the backlog of the same type and area. An overrun moves the technician's later jobs, and the office decides by mid-morning whether the last job of the day moves to another technician or another day. An emergency takes the reserve first and displaces a planned job only when the reserve is spent.
The mechanics of moving a job, from the unscheduled queue to the board and the technician's phone, are in drag and drop job scheduling. The dispatcher's day, with its reassignments and live changes, is covered under dispatch software.
Crew scheduling and job tracking best practices
Crews add one question to scheduling: who answers for the job. Crew composition, the skills matrix and crew-hour capacity are set out in crew scheduling; the practices below keep the answer to that question on the record.
- One accountable technician per job. Each job names the technician responsible for it, even where a crew works the site.
- One job per day of work. A two-day installation is scheduled as two dated jobs, so each day has its own hours, status and notes.
- Status at each change. Arrived, started, paused for parts and completed are recorded when they happen, not in one batch after the last job.
- Time against the job. Clock-in and clock-out are logged against each job, which is the record that later sets durations.
- A closing photo and note. The last record on each job shows the finished work and anything the next visit needs.
- An end-of-day review. Unfinished jobs are re-placed that evening, and their customers hear the new time before morning.
- Two measures each week. On-time arrival against the window, and the share of jobs finished on the first visit, both by technician and by job type.
Sample week: an irrigation company in Grand Rapids, Michigan
The sample is a hypothetical irrigation company that also holds a plumbing contractor license, with four technicians on 40-hour weeks in a spring week with no holiday. One technician is a licensed plumber with ASSE backflow certification. Job counts and durations are sample inputs, labelled as such; the wages are BLS 2025 data for the Grand Rapids-Wyoming-Kentwood metro, where landscaping and groundskeeping workers earned a median of $18.01 an hour and plumbers, pipefitters and steamfitters $38.67 (O\*NET OnLine, Michigan wages for 37-3011.00; O\*NET OnLine, Michigan wages for 47-2152.00).
| Job class | Jobs (sample) | Paid hours each, with drive (sample) | Hours | Who can do it |
|---|---|---|---|---|
| Spring start-ups, recurring | 60 | 1.0 | 60 | Any technician |
| Backflow tests for the 2026 zone, deadline | 24 | 1.0 | 24 | The licensed plumber only |
| Repairs, planned | 10 | 2.0 | 20 | Any technician |
| New zone installation, two days | 2 dated jobs | 8.0 | 16 | An install-trained technician |
| Emergency reserve | — | — | 20 | Any technician |
| Total | 140 | Of 160 available |
The total fits; the skill does not have slack. The week needs 140 of 160 hours, but the 24 test hours are 60 percent of the plumber's 40. If the plumber is given 16 start-ups because the plumber's route passes those addresses, the plumber's week is full and any emergency that needs the plumber pushes a test into the next week. The 16 start-up hours also cost $38.67 an hour in the plumber's wage against $18.01 for a groundskeeping technician, $20.66 more per hour or $330.56 for the week, before payroll taxes. The tests are therefore placed on the plumber's calendar first, and start-ups fill the other three calendars.
The dig notice sets the installation date. The installation is wanted to start at 8 a.m. on Wednesday. A dig notice given at 8 a.m. on the Friday before starts counting at once: 24 hours to Monday 8 a.m., with Saturday and Sunday excluded, 48 to Tuesday, 72 to Wednesday at 8 a.m. The same call made at 5:15 p.m. that Friday starts at 7 a.m. Monday and clears at 7 a.m. Thursday. Nine hours of delay in placing the call cost the installation its Wednesday, so the notice is placed the morning the job is sold, and the first day's job is not booked until the ticket's clear time is known.
The backlog sets the horizon. With 200 start-up requests outstanding (sample) and 60 start-ups a week, a new start-up request has a horizon of 3.3 weeks. A customer told "about three and a half weeks" on the phone hears a date the schedule can keep.
Job scheduling checklist
- Every job is classed as emergency, urgent, planned or recurring before it is placed.
- Response times for each class are written and measured.
- Durations come from clock records by job type, with a longer figure held for buffers.
- Capacity is counted in paid hours, less the emergency reserve, and by skill.
- The booking horizon is calculated weekly for each job type.
- Dig notices, permits and parts are requested when the job is sold, and the job is placed after each clears.
- Licensed work, such as backflow testing, is matched to credentials recorded per technician.
- Recurring and deadline work is placed first, grouped by area.
- A confirmation states the date, window, technician and the customer's preparation.
- Displaced customers hear the new time before the original window opens.
- Verify each Monday: compare last week's scheduled hours with clocked hours by job type, and correct any duration that missed by more than the buffer.
Scheduling records in FieldRanger: priorities, skills and windows
FieldRanger schedules field work on the same HubSpot records the sale was made on, and a won HubSpot deal becomes a job with its context carried over. The office assigns and reschedules jobs by dragging them on the calendar, with every technician side by side and their availability and current assignments shown. Skill-based assignment matches jobs to technicians by certification and expertise, so the backflow credential is a matching rule rather than a memory. Capacity planning prevents overbooking with workload balancing, conflict detection warns of double-bookings, and bulk scheduling assigns many jobs at once, such as a spring wave of start-ups. Recurring job templates generate maintenance and seasonal visits, arrival windows are set with on-time performance tracked, and real-time notifications alert technicians to changes and new assignments.
Technicians clock in and out with time logged against each job, and job status updates are visible to dispatchers as they happen. FieldRanger builds each technician's route for the day automatically. Customers can book a visit online, and one job can carry several technicians when a crew works together. A weather feed is not built, and neither are multi-day jobs: each day of a longer job is its own job. The scheduling and dispatch page shows the calendar step by step, and plans are on pricing, where Start free trial runs 14 days with no card.
Frequently asked questions
What is job scheduling?
In field service, the assignment of each customer job to a date, an arrival window and a qualified technician. In computing, the same phrase names batch schedulers such as cron that decide when programs run.
How do service businesses schedule jobs?
They class each job by priority, estimate its duration from completed jobs, check capacity and the booking horizon, clear dependencies such as dig notices, permits and parts, place recurring visits first, and confirm the window with the customer.
How far ahead is a dig notice needed before an excavation job in Michigan?
At least 72 hours, and no more than 14 calendar days, before excavation under MCL 460.725, with hours of nonbusiness days excluded and notices after 5 p.m. counted from 7 a.m. the next business day.
How are emergency jobs scheduled without breaking planned appointments?
From a reserve of hours held back each day. An emergency takes the reserve first, displaces a planned job only when the reserve is spent, and the displaced customer hears the new time before the original window opens.
What are crew scheduling and job tracking best practices?
One accountable technician per job, one dated job per day of work, status recorded as it changes, time logged against the job, a closing photo and note, an end-of-day review of unfinished jobs, and weekly on-time and first-visit completion measures.
How is job duration estimated for scheduling?
From the company's own clock-in and clock-out records grouped by job type, counting paid time including drive, with the middle figure used for planning and a longer figure for buffers.
In the Grand Rapids week, the schedule had 20 hours to spare and still depended on one licensed plumber's 24 tests and on a dig notice placed by 8 a.m. on a Friday.
Run field service on HubSpot with FieldRanger
Estimates with e-signature, scheduling and dispatch, a technician mobile app and invoicing, synced to the HubSpot deals and contacts the business already keeps.
Book a demo