Multi-day route planning for crews that work across days, not just hours
FieldCamp handles multi-day job scheduling for your entire crew, up to 14 days at a time, with optional 30-day horizon for multiple projects. Built for field service companies that need to plan weeks, not just tomorrow.
Multi-day scheduling software built for real field operations
Field jobs don’t fit neatly into single-day slots. Multi-day projects, travel days, PTO, and job dependencies all need to be planned together. FieldCamp Plan up to 14 days in a single pass, so your dispatcher plans one or two weeks in advance, instead of rebuilding it every morning.
Plan two weeks at once, not just tomorrow
Most dispatching tools optimize one day at a time. That falls apart when you have a project spanning Tuesday through Friday. The engine plans up to 30 days in a single pass, so Monday’s assignments already account for what needs to happen on Friday.
Shift schedules that handle real life
Your techs take a vacation. They call in sick. They have a half-day for training on Thursday. Set up weekly shift patterns, then layer in exceptions, PTO, sick days, training blocks, appointments, and the schedule routes around reality.
Travel days handled properly
When a tech needs to drive four hours to a job site, that changes everything. Four travel strategies: no travel, travel after shift, travel during shift, or a mix. Automatically reduces job count on travel days and enforces return-home rules.
Jobs stay in the right order
Inspection before installation. Demo before removal. The system enforces job dependencies automatically, which visits depend on which, minimum delays between them, and when the same tech is required.
An assistant that re-plans the next 3 days when Monday’s plan breaks
Set up a dispatch assistant to monitor multi-day plans and re-optimize when reality drifts. The agent checks for PTO changes, job dependency shifts, and capacity gaps, then re-runs the plan and flags what moved. Dependencies stay intact. Overtime limits still hold. Your dispatcher approves the updated week instead of rebuilding it job by job. And when nothing changed? The assistant stays quiet.
Day-by-day scheduling vs. multi-day scheduling software
One plans routes. The other plans routes, assigns techs, checks skills, respects customer preferences, and adjusts through the day — all in one pass.
Fixed schedules
- Tomorrow only. Rebuild every afternoon
- Travel between regions = manual guesswork
- PTO and sick days = scramble when it happens
- Job dependencies tracked in the dispatcher’s head
- Overtime discovered on the paycheck
Multi-day scheduling software
- Up to 30 days planned in one pass
- Four travel strategies with automatic job count reduction
- PTO, training, and sick days are built in from the start
- Dependencies enforced automatically with minimum delays
- Overtime capped, costed, and redistributed in advance
How an insulation company schedules 15 techs across 3 regions
Dispatcher loads 47 jobs across 3 regions. Retrofit project sequenced: vapor barrier Monday, insulation Tuesday-Thursday, inspection Friday. Same lead assigned across all 5 days when requiresSameTechnician is enabled.
Two eastern region techs have Monday marked as travel day. Job count is reduced automatically. They arrive on-site Tuesday morning, ready to work.
One tech is off on Wednesday. His 4 jobs were already routed to other crew members when the week was planned. No morning scramble. No calls.
Tuesday’s retrofit ran long. The Thursday phase is behind. The dispatch assistant re-sequences Friday’s inspection, shifts two non-urgent jobs to next Monday, and keeps overtime under 90 minutes. The dispatcher approves with one click.
45 of 47 jobs done. 2 pushed to next week with dependencies intact. Zero overtime violations. One dispatcher managed what used to take daily rebuilds.
The weekly plan at Friday EOD, 45 jobs completed, dependencies intact, zero overtime violations.
Works with what you already run
ServiceTitan
Pull jobs with dependencies, recurring schedules, and groupings. Multi-day plans push back with correct sequencing.
Jobber
Sync job list and crew availability. Week-long schedules write back so techs see the full picture.
Housecall Pro
Import jobs and time-off data. Multi-day assignments push back with accurate ETAs per day.
REST API
Build your own integration. JSON in, optimized multi-day schedule out. Full docs available.
Your dispatcher shouldn’t be a fortune teller
Drop in 1–14 days of jobs, pick a travel strategy, and let the engine plan around dependencies, PTO, and drive time.
No credit card required · Live in 30 minutes · Cancel anytimeFrequently Asked Questions
How many days ahead can FieldCamp plan multi-day routes?
FieldCamp’s standard dispatch run plans 14 days ahead by default (set in runDispatch.ts). The AI optimization engine itself supports problem windows up to 30 days, which we use for larger multi-region projects. Need a longer horizon? Contact us — it’s a config change, not a code rebuild.
What happens to my schedule when a technician calls in sick mid-week?
The Dispatch Assistant detects the change within ~30 seconds (changeMonitorInterval: 30s) during business hours and re-optimizes the next 3 days of work, redistributing the sick tech’s jobs across the remaining crew. Manual edits stay locked (respectManualEdits: true).
Will the AI keep the same technician on a multi-day project?
Yes, when you flag a job with requiresSameTechnician: true or chain visits with dependsOnVisitIds, the optimizer assigns the same lead tech across all days, with a configurable minimumDelayAfterDependency between phases.
Does the AI respect job dependencies across days?
Yes — every visit can declare dependsOnVisitIds (e.g., “vapor barrier before insulation before inspection”), and the multi-day planner enforces correct sequencing with the minimum delay you configure.
What if a tech’s max drive time is exceeded?
Each workspace sets maxDriveTimeMinutes (default 60–120 min depending on plan). Per technician you can also cap maxTravelDuringShiftMinutes and maxTravelAfterShiftMinutes. Jobs that would breach these caps either get re assigned, deferred, or surfaced in the unassigned-jobs queue.
Can dispatchers override AI suggestions on a multi-day plan?
Yes. Every AI suggestion has Accept/Reject buttons. Accepted suggestions persist in localStorage (and DB) and won’t be re-suggested. Rejected jobs go back into the pool for the next dispatch cycle. Manual edits are protected from auto re-optimization.