Equipment dispatching that never double-books
Your crews share bucket trucks, trailers, and specialty tools across dozens of jobs. FieldCamp schedules equipment alongside routes, no double-bookings, handoff buffers built in, and every conflict caught before the day starts.
Equipment Dispatch Software That’s Part of the Solve, Not an Afterthought
Equipment conflicts don’t show up in a spreadsheet until someone’s already standing idle in a driveway. FieldCamp’s optimizer treats your gear as a hard constraint in the solve, not a visual overlay you check afterward.
Tag jobs with the equipment they need
Every job can carry a list of required equipment. A tree removal needs the 65-foot bucket truck. A panel swap needs the metering kit. Tag it once, and the optimizer knows what to look for on every route.
Equipment profiles that match reality
Each piece gets a full profile: type, whether it can be transferred between crews mid-day, Home Depot location, whether it needs post-use inspection, and whether it’s a single unit. Same depot logic powers capacity routing for tank-based fleets. The solver treats the entire input, not just a spreadsheet column, as a real constraint.
Handoff scheduling with buffer time
Two crews share a bucket truck. Someone has to drive it across town between jobs. The system models this. Set a handoff strategy and buffer in minutes. The optimizer slots the transfer into the route, so Crew B isn’t standing idle waiting.
The optimizer sees your entire inventory
Your full equipment list is fed directly into the solver alongside vehicles and visits. The engine prevents double-booking, respects handoff buffers, routes around single-unit constraints, and ties into workload balancing across crews. This is a constraint in the optimization math, not a visual overlay.
Spreadsheet Equipment Tracking vs. Equipment Scheduling
One hopes nobody double-booked the bucket truck. The other makes it mathematically impossible.
Spreadsheet Equipment Tracking
- Scan the board and hope you catch it
- “Text me when you’re done with the truck”
- Everything looks the same in a cell
- Falls apart around crew 4
- Conflicts found in the field
Equipment Scheduling
- Solver rejects double-bookings before you see the schedule
- Buffer minutes built into the route as a hard constraint
- Each job flags whether equipment is mandatory or preferred
- Same solve whether you have 3 crews or 30
- Equipment conflict prevention at planning time
2 Bucket Trucks, 5 Crews, Zero Conflicts
Same logic applies to electrical crews with shared lifts. A tree service runs 5 crews from one yard. Two need the 65-foot bucket truck for canopy removals.
Each was tagged with the required equipment plus the matching qualified tech: bucket truck, chipper, stump grinder. 8 jobs are a hard requirement for the bucket truck.
It knows there are only 2 bucket trucks. Both single-unit, transferable, 20-minute handoff buffer.
Downtown crews pick up a 6th job. Suburban crews drop to 4 with longer buffers.
Bucket Truck #1 routes to Crew A for 3 morning removals, then hands off to Crew C at 12:40 PM with a 20-minute buffer. Truck #2 stays with Crew B all day, 4 jobs, no handoff. The other 15 jobs (ground work) are spread across all 5 crews by proximity.
Works with what you already run
ServiceTitan
Push equipment assignments through webhook. Job-equipment pairings flow into the solver.
Jobber
Sync equipment list and job requirements. Solver picks up constraints when building routes.
Housecall Pro
Connect equipment profiles to scheduled visits. Requirements carry through to optimization.
REST API
Full control over equipment profiles, handoff strategies, and buffer configs. Full docs available.
Your Equipment Shouldn’t Need a Dispatcher of Its Own
Tag your gear, set your buffers, hit optimize.
No credit card required · Live in 30 minutes · Cancel anytimeFrequently Asked Questions
How is this different from adding equipment to a job note?
Notes are visual — a dispatcher has to read every cell and remember. Here, equipment is a hard constraint inside the solver. The optimizer sees the entire equipment inventory at once and refuses to build a schedule that double-books an asset.
Can the same piece of equipment be handed off between crews?
Yes — if marked transferable. The solver plans a handoff with a configurable buffer (e.g., 20 minutes) between crews so the gear physically arrives before the next crew needs it.
What if a job only “prefers” certain equipment but can run without it?
Set equipmentIsHardRequirement: false on that job. Solver tries to assign preferred equipment but won’t fail the job if gear isn’t available
Does it scale from small fleets to large?
Same solver, same constraints — 3 trucks or 30. Equipment double-booking prevention is built into planning logic, not a UI rule.
What types of equipment can it track?
Anything with an ID, capacity, and location: bucket trucks, augers, cranes, vac trucks, generators, specialized testing kits, mobile labs. Each piece gets depot location, transferable flag, handoff strategy, inspection requirement.
Does it require ServiceTitan, Jobber, or Housecall Pro?
Native connectors for Jobber, Housecall Pro, and ServiceTrade — REST API for anything else. Works standalone if you don’t have an FSM. (Note: confirm with dev team whether ServiceTitan listed on the page is actual or planned.)
What happens if equipment needs inspection before next use?
Set requiresInspection: true on the equipment record. Solver won’t assign it to a job until inspection is marked complete, preventing dispatch of out-of-service gear.
Can equipment have its own depot location separate from the technician’s home base?
Yes. Equipment carries its own depotLocation, independent of any tech. The solver factors return-to-depot transit into the route after the last job using that asset