How do I coordinate crew schedules across multiple job sites?

To coordinate crews across several job sites, put every job and every crew on one schedule that everyone can see, plan by crew and by day, confirm that each site is ready the day before, and treat every change as a move on that schedule, never as a text message. The schedule has to be the one place where the answer to "where am I tomorrow?" lives.

Why whiteboards and group texts stop working

A whiteboard is correct only until the first change after someone last looked at it. A group text has no memory: by Thursday nobody can tell which of Tuesday's messages still stands. With three crews and five jobs that is annoying. With six crews and twenty jobs it produces double-booked foremen, a crew at a site that is not ready, and another site with nobody on it.

Plan by crew, not by person

Start with crews as units: a foreman and the people who normally work with them. Jobs are assigned to crews. Moving one person for one day is an exception you note, not the way the plan is built. It keeps the plan readable, and it keeps people working with the foreman who knows them.

Give every visit a real duration

"We'll be there next week" is not a plan. Each visit needs a start day and a number of crew-days, taken from how long that kind of work actually takes your crews. If 1,000 square feet of your work takes a four-person crew two days, the schedule should say two days, and four days when the job is twice the size. Durations you made up on Monday are why the plan falls apart by Wednesday.

Look two to three weeks ahead

• This week is fixed. Changes happen only for weather, a site that is not ready, or an emergency.
• Next week is firm. Materials are ordered and the general contractor has been told.
• The week after is planned in pencil.

One standing meeting a week, even fifteen minutes, where the next two weeks are walked through job by job, saves a dozen calls.

Confirm the site before the crew rolls

The most expensive day in a subcontractor's week is a crew arriving at a site that is not ready. The afternoon before, someone confirms:

• The trade ahead of you has finished and passed inspection.
• Material and equipment are on site, or on the truck.
• There is access, power and somewhere to park.
• The superintendent knows you are coming.

Keep a list of fill-in work

Every company has small jobs that can be done any day: punch lists, warranty calls, a half-day repair. Keep them on a visible list. When a site falls through at 6:30 in the morning, the crew goes to the next thing on the list and the day is not lost.

Group jobs by geography

Two jobs ten minutes apart can share a crew, a delivery and a foreman's attention. Two jobs an hour apart cannot. When you choose which crew takes which job, the map matters as much as the calendar.

One change, one place

When a date moves, change it on the schedule first. Then the people affected hear about it from the schedule: the crew, the office, and the customer or GC if their date changed. A change that lives only in a phone call will be remembered differently by each person on that call.

Measure what happened

After each job, compare the days you planned with the days it took. Without that, the durations never improve and the schedule keeps being wrong in the same direction.

Where ConstructStream fits

In ConstructStream the schedule is a timeline with a row for each crew. Each product knows its phases and crew-days, so booking a job lays out its visits on the first open start, and moving the first visit of a job moves the ones that follow it. Crews see their own schedule on the phone, equipment sits on the same timeline as the crews, and a planned versus actual report shows which durations to fix.