Crew Dispatch Is Not a Project Schedule
ServiceIQ dispatches crews. Procore and Primavera own the critical path. Confusing the two is how contractors end up maintaining two schedules that disagree.
Two things get called "the schedule" on a construction job, and they are not the same thing.
One is the project schedule: the critical path, the predecessors, the float, the thing that tells you slipping the steel delivery pushes closeout by three weeks. The other is who is on which truck tomorrow morning.
Confuse them and you maintain two schedules that disagree, which is worse than having one.
What does ServiceIQ actually schedule?
The second one. Crew scheduling, dispatch, a dashboard showing every job and every crew member, job status closed out from the field. Their own description is commanding the schedule by voice, by tap or by type, from a phone in a truck.
That is real and useful. It is also not a Gantt chart. ServiceIQ does not publish critical path scheduling, predecessors, float or resource levelling, and does not claim to.
What stays in Procore or Primavera?
The project schedule, and it should.
On commercial work the schedule is a contract document. Delay claims attach to it. Float ownership gets negotiated in the contract. A three week slip has a dollar consequence that somebody will argue about with a lawyer present. None of that belongs in a field dispatch tool, and a field tool that claimed to handle it would be a liability rather than a feature.
HubSpot has even less claim here. It tracks the deal, not the project.
Which question are you actually asking?
This is the whole decision, and it takes one sentence.
- "Who is working where tomorrow?" That is dispatch. A field platform answers it from a phone.
- "What does this delay do to substantial completion?" That is the project schedule. No field app answers it, and one that offers to is guessing.
Most contractors asking for better scheduling are asking the first question and buying for the second. They end up with a project scheduling tool nobody in the field opens, and the dispatch problem they actually had is still being solved by text message.
Where does the real cost sit?
Not in scheduling. In the handoff.
A bid gets won. Somewhere a project schedule is built. Separately, somebody works out which crew goes where on Monday. Those two activities usually happen in different systems, by different people, and the field finds out about the project schedule after something has already slipped.
What ServiceIQ closes is the deal-to-dispatch seam: a signed quote becomes a scheduled crew without re-entry. What it does not close is dispatch-to-critical-path. That one stays a human conversation, and probably should, because it involves judgement about float that nobody should automate.
What about subcontractor coordination?
Worth separating out, because it sits between the two and gets assumed into both.
Knowing that the drywall crew needs the electrical rough-in complete is schedule logic. Knowing which sub is on site Thursday is dispatch. A GC coordinating twelve trades needs the first in a project tool. A specialty contractor running their own crews mostly needs the second.
That distinction usually maps onto which product you need, more cleanly than company size does.
How to decide
Write down the three scheduling questions that cost you the most when they go unanswered. If they are mostly about tomorrow and this week, you need dispatch. If they are mostly about months and sequence, you need a project scheduler, and the field still needs something to tell a crew where to go.
Most contractors need both, connected, and that is a smaller project than replacing either.