How to Manage Multiple Construction Projects at Once

Why running two sites at once is harder than it looks

Most Thai SME contractors carry the status of two or three active projects in their head — and that works fine until one site accelerates while another stalls. The problem is rarely a lack of skill; it is a lack of visibility. The same mason crew, the same waterproofing sub, and the same project manager all serve more than one project, and when schedules shift, the single most dangerous thing is not knowing that a resource you need on Wednesday is already committed on Tuesday somewhere else. Contractors who manage multiple sites without a written plan per project spend their days firefighting, because surprises arrive faster than decisions.

Set up one Gantt per project, one platform for all of them

The foundation of multi-project control is one Gantt per active project, each with its own tasks, dates, dependencies, and progress tracking. What makes this practical — rather than just more file juggling — is having all those separate plans in the same system. In SiteBoard's Gantt planning view, each project is its own workspace and every foreman updates their tasks into the correct project automatically. The project manager switches between projects in one tap, sees this morning's updates across all sites, and identifies which bars are moving and which have stalled — without opening three different files or scrolling through three separate LINE groups.

The crew conflict you need to catch three weeks early

The most common multi-project failure is booking the same crew into two places on overlapping days, then discovering the conflict the morning it matters. Your waterproofing sub finishes the roof on Project A on Thursday and is due to start Project B the same week. Any overrun on A — a pour that needed extra time, an inspection that moved — pushes the crew into a double commitment you did not see coming. When both projects live on Gantts in the same system, the overlap is visible weeks ahead. A two-day extension on Site 1 becomes a scheduling adjustment you make proactively, not a crisis the sub announces by phone on the morning they are supposed to arrive.

A worked example: Khun Amara running three sites at once

Picture Khun Amara managing three concurrent builds: a 3.2-million-baht house in Pathum Thani at month four of eight, a shophouse fit-out in Nonthaburi at month two of five, and an office renovation in Bang Na at week three of eight. Her plastering sub works all three sites. Checking the Gantt planning view for each project, she spots that Pathum Thani enters intensive plastering in week fourteen and Nonthaburi hits that same phase in week sixteen — barely enough gap for the sub to clear one site before starting the other. She shifts Nonthaburi's plastering start by ten days. Without all three Gantts visible side by side, she would not have seen this until the sub called to say they could not make both.

How do you stop one project from robbing another?

The instinct when juggling multiple sites is to treat whichever project is loudest as the priority and quietly pull resources from the quieter one. That feels like crisis management but it is really scheduled neglect. The alternative is to check each project's critical path at the start of the week and answer one question: which task, on which site, blocks the most downstream work this week? If Project A's concrete pour happens Monday and nothing moves Tuesday without it, that is the priority — not Project B's standing request for an extra crew day. When priority is decided in the plan before the week starts, it is a strategy. When it is decided in the field on Wednesday, it is a scramble.

Getting daily updates from three sites without three site visits

A project manager cannot be on three sites at once. The practical alternative is a morning review of updates that arrived overnight — each foreman logs their tasks through the on-site progress update flow, and the project manager sees plan-versus-actual across all projects from one view. A task sitting at 40 percent for three consecutive days on Site 2 signals a problem before it becomes a week-long stall. With daily mobile updates flowing from each foreman, the morning sweep covers three projects in ten minutes and replaces what would otherwise require three phone calls, three drives, and three sets of incomplete information guessed from memory.

Keeping three owners informed without triple the report-writing

When you are running three projects, three owners are expecting progress updates. Preparing a separate report for each owner every week is an evening of work you do not have. The practical shortcut is to keep each project's owner sharing link live and current, so each owner checks their own page whenever they want without calling you. The Pathum Thani house owner sees their project; the Nonthaburi developer sees theirs. When a project hits a delay, you call before they see the page — not after. The owner sharing pages absorb the routine visibility load so your time goes to conversations that need your judgment, not to status updates a page can handle for free.

When is it safe to start a new project before the current one closes?

Starting a new site while a project is in its final ten percent is one of the most reliable ways to drag out a punch list for weeks. The closing phase — snag walks, defect negotiations, final payment draws — demands management attention that cannot be split from another site two hours away. A practical rule: do not mobilise a new project until the current one is past its punch list walkthrough and the final payment draw is agreed in principle. If the new project has a fixed start date, plan an explicit handoff of the closing work to a designated foreman before redirecting your own attention. An unmanaged close costs more in time and goodwill than a slightly delayed start on the new site.

Do I need a separate Gantt for each project?

Yes. Each project should have its own Gantt with its own tasks, dates, and dependencies. Combining multiple builds into one chart creates a tangle where a change to one project visually confuses the whole plan. In SiteBoard's Gantt planning, each project is a clean separate workspace and you navigate between them quickly. Keeping them separate means each plan stays readable, each foreman sees only their own site's tasks, and you avoid accidentally linking tasks across builds.

How do I know when a site needs urgent attention versus just monitoring?

A site needs urgent attention when a critical-path task has not moved in two days and was scheduled to. It needs only monitoring when all current-week tasks are progressing at or above their planned percentage. Daily on-site progress updates make this distinction automatic: the morning view shows which tasks are stalled below expectation, and you call only those sites. Sites updating normally tell their own story without a call — which is the whole point of building the daily update habit across every project.

What is the right number of concurrent projects for one team?

A project manager with a dedicated foreman per site and daily updates flowing can typically handle three to four concurrent projects without quality loss. Past that, the attention deficit shows in the work: punch lists get sloppy, subcontractors wait too long for decisions, and owners call because the progress page has not updated in four days. The real signal that you are past capacity is not financial — it is when a project goes three days without a progress update and nobody on your team noticed it had stopped.

How do you manage multiple construction teams across different sites?

A project is a build; a team is a trade crew or subcontractor that often serves several builds at once. The scheduling conflict you actually manage is rarely between projects — it is between the teams they share. Your formwork gang, your plastering sub, and your MEP crew each move between sites, and the question that matters every week is not "how is Project B doing" but "where is the plastering team committed for the next three weeks, and does any site need them on the same days." The practical method is to keep every active project on a Gantt in one system, then read each shared team's forward commitments across all of them. When a multi-site contractor tracks teams rather than just projects, double-bookings surface weeks early — while they are still a calendar adjustment, not a phone call on the morning the crew fails to arrive.

What should multi-site project management software actually do?

Most tools sold as construction software optimise a single project in isolation, which is not the problem a multi-site contractor has. The five things that matter across sites are: a separate Gantt per project inside one login, so plans stay readable but live together; a resource view that shows when a shared crew or subcontractor is booked across every project at once; mobile field updates that route from each foreman into the correct project automatically; a live owner-sharing page per project, so three owners inform themselves without three separate reports; and a single morning plan-versus-actual across all active sites. SiteBoard is built around exactly this shape — project-separate planning with portfolio-level visibility — because for a contractor running three or four builds, the software's job is not to plan one site beautifully but to stop the sites from colliding.