How to manage multiple construction sites with one team
Start with one accountable lead per site and a short shared review of blocked work, decisions and crew movements. A portfolio overview helps only when each item links to an up-to-date site record and somebody owns the next action.
Separate site decisions from cross-site decisions
The site lead handles today's local sequence, reports and checks. The person coordinating several sites handles competing demands: where a shared crew goes, which delivery takes priority and which unresolved decision threatens more than one project. Write down that division before adding another reporting meeting.
Use the same site names and location codes in the schedule, tasks and reports. Two records called “north building” can be harmless within one project and confusing when a subcontractor works across three.
Run a short morning exception review
-
Check work that cannot start
For each site, list the task, blocker, owner and next decision time. Include access, materials, drawings and the preceding trade. Do not treat a booked crew as proof that the work is ready.
-
Resolve competing crew assignments
Review a single weekly crew plan across projects. If the same crew appears twice at the same time, agree a priority before either site promises the work to the next trade.
-
Record the decision at its source
Update the affected task and schedule. A decision recorded only in the coordination meeting leaves the site working from yesterday's plan.
-
Set the next review
Agree who will confirm that the blocker is removed and when. Escalate a missed decision time rather than repeatedly asking everyone for a full status update.
Example: one electrical crew, two sites
Fictional planning example. Site A needs the electrical crew on Tuesday, but the work area has not been released. Site B has a confirmed drawing and materials ready. The coordinator checks the effect on both programmes, agrees Tuesday at Site B and records the revised visit at Site A after the release is confirmed.
The useful record includes the change, its reason, the person who agreed it and the next confirmation time. “Crew moved” alone does not explain what the first site must do next.
Use the free weekly crew schedule to record assignments. Planned hours describe the allocation; keep actual attendance in the appropriate record.
Keep the overview small enough to act on
Review blocked work, overdue decisions and the next crew movement first. Open the detailed task record when a decision needs context. A count of open tasks alone does not distinguish a missing drawing that stops a floor from a minor finishing item.
At the end of the week, compare the agreed plan with what happened. Repeated changes caused by one missing input are a reason to change the readiness check, not to produce a longer dashboard.
Doing this in TerenIQ
TerenIQ keeps projects, tasks and the team schedule in one workspace. Review the schedule, then open the work item for its responsible people, comments and supporting files. Use the task management workflow to keep the agreed next action attached to the work.
Frequently asked questions
Should every site use the same checklist?
Use the same basic fields for coordination, then add checks specific to each project's work and risks. A shared format should not hide site-specific requirements.
How often should the cross-site plan change?
Review exceptions daily and the broader allocation weekly. Update a confirmed assignment when the decision changes, so the crew and both site leads see the same plan.