Guide
Drag and Drop Job Scheduling:Board Layout, the Unscheduled Queue, Conflict Checks, Mid-Day Reassignment and the Technician's Phone
Drag and drop job scheduling explained: board layout, the unscheduled queue, conflict checks, mid-day reassignment and what reaches the technician's phone.
Drag and drop job scheduling assigns field jobs by moving cards on a board: each job card is dragged from an unscheduled queue onto a technician's row at a start time, and dropping it writes the technician, the time and the arrival window to the job, runs conflict checks, and sends the change to the technician's phone and, where set up, to the customer.
The board makes a change look smaller than it is. One drag of a job from a sick technician to a colleague changes two technicians' days, a customer's arrival time and, by Friday, possibly the colleague's overtime. A card dropped onto a row where it fits visually may overlap the drive from the previous job, sit outside the window the customer was promised, or land on a technician without the certification the work needs. FieldRanger publishes this guide among its dispatching and scheduling guides. It describes the parts of a board in general terms first: the layout, the unscheduled queue, the record changes at a drop, the conflict checks, reassignment during the day and the technician's phone. It then covers dragging on touch screens and the accessibility rule that applies to it, jobs longer than a day, a sample morning rebuilt after a sick call, a checklist, and the features FieldRanger ships for the board.
Four terms carry the description. A job card is the block that represents one job on the board, sized by its expected duration. The unscheduled queue is the list of jobs that exist but have no technician or time yet. A drop is the moment a dragged card is released onto a row and time, which is when the system writes the change. A conflict is any condition that makes the dropped position impossible or costly to keep: an overlap, a missed window, a missing skill or a full day.
Board layout: technician rows, the time axis and job cards
A drag-and-drop board is a grid. One axis lists technicians, the other runs through the working day in time slots, and each job is a card whose length shows its expected duration. Color or a label shows the job's status, such as scheduled, en route, in progress or complete. The board answers two questions at a glance: who has room, and where the day's work sits.
The grid hides one quantity: drive time. A card placed straight after another on the same row looks continuous on the screen, yet the technician needs travel time between the two addresses. Some boards draw travel as its own block between cards; others leave it to the route that is calculated after the cards are placed. The dispatcher reads the board knowing which of the two it does.
The dispatch software page sets out the dispatcher's whole day around the board. The underlying plan, with windows and daily capacity, is covered in service scheduling, and the wider practice of job scheduling covers how jobs reach the board in the first place.
The unscheduled queue
The unscheduled queue holds every job without a slot. Jobs enter it when they are created from a won estimate or a service call, when a technician calls out sick and the day's work is pulled back, when a customer cancels a time but keeps the job, or when a job overruns and the next stop must be moved. The queue is the dispatcher's to-do list, and a job in it is a promise with no date.
A queue worked well is sorted before it is dragged. Jobs with a window already promised come first, then jobs whose required skill limits them to one or two technicians, then jobs that can go anywhere. Dragging the flexible jobs first fills the rows that the constrained jobs needed.
Job record changes at the drop
A drop is a write, not a picture. When the card is released, the job record takes the technician of the row, the start time of the slot, and an end time from the job's duration; if arrival windows are used, the window follows from the start time or is checked against the one already promised. The previous values are replaced, and on a system that keeps an audit trail, the change is recorded with the user who made it.
The write then fans out. The technician's job list changes, the route for the day is recalculated where routing runs from the schedule, and any customer message tied to the appointment, such as a confirmation or a reminder, goes out with the new details. The appointment confirmation template lists the fields a customer confirmation carries: date, window, technician and access instructions.
Conflict checks at the drop
A conflict check runs at the moment of the drop and warns before the change reaches anyone outside the office. Five checks cover the costly cases.
| Conflict | What the check compares | What it prevents |
|---|---|---|
| Double-booking | The dropped card's time against the technician's other jobs | Two customers expecting one technician at once |
| Missed arrival window | The new start time against the window promised to the customer | An arrival the customer was not told about |
| Missing skill or certification | The job's requirement against the technician's record | Work sent to someone not qualified to do it |
| Full day | The technician's booked hours against capacity for the day | A day that ends in overtime or a missed last job |
| Equipment already booked | The job's equipment against other jobs using it | Two crews planning on one machine |
A warning is a prompt, not a block. A dispatcher can accept a double-booking deliberately, for a ride-along or a quick stop that fits inside another job, and the board records the choice; a check that silently allowed it would leave the next dispatcher to find it.
Reassigning a job during the day
Reassignment is a drag from one technician's row to another's, and it changes three records at once: the job, the first technician's day and the second technician's day. The first technician's phone loses the job, the second technician's phone gains it, and the customer may need a new name and a new time. A reassignment made after a technician has set off toward the job also leaves a drive that was paid for and wasted.
The order of the drags matters during a disruption. A dispatcher who reassigns the constrained jobs first, those with a narrow window or a rare skill, then fills the gaps with flexible jobs, finishes with fewer conflicts than one who works top to bottom down the sick technician's row.
Technician phone updates: notifications, job list and status
A drop is complete only when the technician knows about it. On a board connected to a mobile app, a new assignment arrives as a push notification, the job appears in the technician's list for the day with its address, instructions and customer details, and a change of time or a removal shows on the same list. The technician opens directions from the job and updates its status as the work starts and finishes, which moves the card on the dispatcher's board.
The return path is what keeps the board accurate. A job marked in progress at 9:40 that was scheduled to finish at 9:30 is visible on the board as running long before the next customer calls, and the dispatcher can move the next card while there is still time to tell that customer.
Dragging on touch screens and the accessibility rule
Dragging is a precise movement, and not every dispatcher can perform it on every device. The W3C's Web Content Accessibility Guidelines 2.2 add success criterion 2.5.7, Dragging Movements, at level AA: "All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging", unless dragging is essential (W3C, Understanding SC 2.5.7, checked November 12, 2026). The W3C notes that people using "a trackball, head pointer, eye-gaze system" can find dragging difficult, and gives a Kanban board as an example of the remedy: "selecting the element with a single tap or click, and then activating an arrow button". It also states that "achieving keyboard equivalence for a dragging operation does not automatically meet this success criterion".
For a scheduling board, the rule describes a second way to move a card: tap the job, then tap the destination, or open the job and pick a technician and time from a form. The same alternative serves a dispatcher reassigning work on a tablet in a truck, where a long drag across a small screen drops cards in the wrong row.
Jobs longer than one day
A two-day install does not fit on a one-day row. Some boards let a card span several days; others represent each day as its own job, linked to the same customer and project, and each day is dragged, assigned and completed separately. The second model makes each day's technician and hours explicit, and it means a slip on day one is a drag of day two, not of the whole job.
In FieldRanger, each day is its own job; a single job card spanning several days is not built. A three-day install is scheduled as three jobs.
Sample morning: a sick call at 7:10
The sample is hypothetical: an HVAC company with four technicians, A to D, and 20 jobs on Tuesday's board. The job lengths, windows and the week's hours are sample inputs. The overtime rule is the Fair Labor Standards Act's: hours over 40 in a workweek are paid at "not less than time and one-half" the regular rate, the workweek is a fixed period of 168 hours, and "averaging of hours over two or more weeks is not permitted" (U.S. Department of Labor, overtime, checked November 12, 2026). The wage is the BLS median for HVAC mechanics and installers, $29.33 an hour in May 2025 (BLS Occupational Outlook Handbook, modified October 29, 2026).
At 7:10, technician D calls in sick, and D's five jobs return to the unscheduled queue.
| Job | Window promised | Length | Drag | Check at the drop | Result |
|---|---|---|---|---|---|
| 1 | 8 a.m. to 10 a.m. | 1.5 h | To A at 8:00 | Window kept | Customer told of new technician |
| 2 | 8 a.m. to noon | 2.0 h | To C at 10:30 | Window kept | Customer told of new technician and time |
| 3 | Noon to 4 p.m. | 1.0 h | To B at 1:00 | Full day: B's week reaches 41.5 h | Accepted; 1.5 h of overtime |
| 4 | Noon to 4 p.m. | 2.5 h | To C at 1:00 | Double-booking with C's 2:00 job | C's 2:00 job dragged to 3:30, inside its own window |
| 5 | Noon to 4 p.m. | 3.0 h | To A | Missing skill on B and C; A's afternoon full | Back to the queue; rebooked for Thursday by phone |
Six drags placed four of D's jobs, moved one of C's and returned one to the queue, and they reached further than the board showed. Three phones received new assignments, C's also a changed time, D's lost five jobs, five customers needed a message and one needed a call. Job 3's hour on Tuesday raised B's week to 41.5 hours, so 1.5 hours on Friday are paid at $44.00 instead of $29.33 at the median wage: $66.00 in place of $44.00. The board showed Tuesday; the overtime arrived on Friday, in a week that cannot be averaged with the next.
Drag and drop job scheduling checklist
- Sort the unscheduled queue by promised window, then by required skill, before dragging anything.
- Drag the constrained jobs first: narrow windows and rare certifications.
- Read every conflict warning at the drop, and record why any accepted conflict was accepted.
- Check each technician's weekly hours, not only the day, before adding work to a full row.
- Confirm that each changed job reached the technician's phone.
- Send the customer the new technician, time or window for every moved job.
- Return to the queue any job that cannot be placed today, and give it a date before the end of the day.
- Provide a tap-to-select alternative to dragging for any dispatcher on a touch screen or adapted input device.
- Verify: at day's end, compare the board's scheduled jobs with the completed jobs, and requeue every miss with a reason.
Drag-and-drop scheduling in FieldRanger
FieldRanger schedules jobs on a drag-and-drop calendar: jobs are assigned and rescheduled by dragging them on the calendar, and the multi-technician view shows every technician side by side with availability and current assignments. At the drop, conflict detection warns of double-bookings and scheduling conflicts, capacity planning prevents overbooking through capacity and workload balancing, and skill-based assignment matches jobs to technicians by certification and expertise. Arrival windows are set and tracked for on-time performance, and bulk scheduling places many jobs at once with batch assignment.
On the technician's side, real-time notifications alert technicians to schedule changes, new assignments and conflicts, and push notifications reach the mobile app. Digital work orders put the job details, customer information and instructions on the assigned technician's phone, one-tap actions start and complete the job and update its status, and job status is visible to dispatchers in real time. FieldRanger builds each technician's route for the day automatically, and routes adjust when priorities change or jobs are added. Audit logs keep a record of user actions and data changes. A won HubSpot deal becomes a job with its context carried over, so new work reaches the board from the sales pipeline.
Each day is its own job, as described above, and customers can book a visit online as well as by phone. The scheduling and dispatch page is where the board can be evaluated feature by feature, and plans are on pricing, with Start free trial for 14 days and no card.
Frequently asked questions
What is drag and drop job scheduling?
Assigning field jobs by dragging job cards from an unscheduled queue onto a technician's row at a time. The drop writes the technician, time and window to the job, runs conflict checks and sends the change to the technician's phone.
What happens when a job is dragged to another technician?
The job's technician and time change, the first technician's phone loses the job and the second's gains it, the route is recalculated, and the customer may need a new name or time.
What conflicts should a scheduling board check at the drop?
Double-bookings, arrival windows already promised, missing skills or certifications, a technician's full day, and equipment booked on another job.
Does drag and drop scheduling need an alternative to dragging?
WCAG 2.2 success criterion 2.5.7 requires that functionality operated by dragging can also be achieved with a single pointer without dragging, such as tapping a job and then tapping its destination. Keyboard support alone does not meet it.
Can a job span several days on a drag and drop board?
Some boards allow a multi-day card. In FieldRanger, each day is its own job, so a three-day install is scheduled and assigned as three jobs.
The sample's six drags touched four phones, six customers and one Friday payroll line. Drag and drop job scheduling is fast at the drop; the work that matters is checking what the drop wrote, to whom it went, and which week's hours it moved.
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