How to manage multiple building projects at once

Most builders and contractors don't plan to end up running eight jobs off the side of a desk. It happens gradually - you win the work, you're good at it, and one day you look up and you've got sites in three different postcodes, four WhatsApp groups, a stack of paper day sheets and a nagging feeling you've forgotten something. None of that is a character flaw. It's what happens when the way you manage one job doesn't scale to managing several. Here's how to fix it.

Get everything in one place

The single biggest cause of dropped balls on a multi-site operation is that the information about each job lives somewhere different. The quote's in email. The variations are in a WhatsApp thread. The site diary is in someone's head or a paper pad in the van. The programme is a spreadsheet that's three weeks out of date because whoever updates it is also the one running around site all day.

You don't need anything fancy, but you do need one place that everyone - office and site - treats as the truth. If a decision, a variation, a photo or a date change isn't in there, it didn't happen. This is the difference between job management software for project-based trades and a folder full of spreadsheets: it's not about the tool, it's about having a single record that doesn't depend on someone remembering to forward an email. Have a look at what a proper single source of truth looks like if you're still running this out of five different apps.

Build yourself a portfolio view

When you're on one job, you know its status because you're stood in it. When you're running several, you need a way to see all of them at once without driving to each one. That means a simple overview - every live job, its current phase, whether it's on track, behind, or at risk, and who's on it - that you can glance at on a Monday morning and know exactly where your attention needs to go first.

Keep the statuses simple. Green, amber, red is enough. The point isn't precision, it's speed - you should be able to scan ten jobs in under a minute and know which two need a phone call today.

Run a weekly look-ahead for every site

A full programme is useful for planning the job at the start and re-planning it when it goes wrong, but day to day it's too much detail to be useful. What you actually need for each live site is a short-term look-ahead - the next one to two weeks, updated weekly: what's happening, who's booked in, what materials need to land, and what needs deciding before work can start.

Get whoever's running each site into the habit of producing this themselves, even if it's rough. It forces them to think ahead rather than just reacting to what's in front of them today, and it gives you, as the person juggling several jobs, a genuine early-warning system rather than a surprise when a delivery doesn't show.

Schedule people and materials across the whole portfolio

This is where most multi-job operations actually lose money. Not on any single job, but in the gaps between jobs - the labourer pulled off site A to firefight on site B, the materials ordered for job three that quietly get used on job one because they turned up first. Robbing Peter to pay Paul feels efficient in the moment and is almost always a false economy: it just moves the delay and the cost onto a different job, usually without anyone writing it down.

Plan crew, subcontractors and material deliveries against all your live jobs together, not one at a time. Before you commit a trade or a delivery slot to a job, check what else is booked that week across the whole portfolio. If two sites need the same electrician on the same Thursday, you want to know that on Monday, not find out when neither site gets him.

Put one person in charge of each site

You cannot run eight jobs yourself and you shouldn't try. Every live job needs one named person who owns it day to day - makes the small calls, keeps the client updated, chases the trades, flags problems early. Your job is to run the portfolio: allocate resource, unblock the things they can't unblock themselves, and step in on the two or three that are genuinely at risk.

Delegating properly means giving that person real authority, not just the workload. If every decision still has to come back to you, you haven't delegated the site, you've just added a layer between yourself and the problem. Be clear on what they can decide alone and what needs sign-off - variations above a certain value, anything affecting the programme end date, anything involving the client's money - and then let them get on with the rest.

Set a communication rhythm instead of firefighting

Constant ad hoc phone calls and WhatsApp messages feel responsive but they're exhausting and they mean you only ever hear about problems once they're already problems. A better pattern is short, regular check-ins - a five-minute call with each site lead once or twice a week, at a set time, covering progress against the look-ahead, anything blocking them, and anything they need from you.

Keep these tight. The aim isn't a status meeting, it's a habit that surfaces small issues while they're still small and cheap to fix, rather than three weeks later when the only options left are expensive ones.

Watch the numbers so you catch a slipping job early

The jobs that go badly wrong rarely do so overnight. There's usually a stretch of weeks where the costs are creeping past what was quoted, or the programme is quietly sliding, and nobody flags it because everyone involved is too close to it, or too busy, or hoping it'll come right on its own.

Two numbers tell you most of what you need to know on any live job: cost to date against what you expected to have spent at this point, and actual progress against the programme. Check both regularly, across every job, not just the ones you're worried about - the ones you're not worried about are exactly the ones that catch you out. A job that's five percent over cost and a week behind in week three is a conversation. The same job in week nine is a crisis.

Get it out of your head

If the only place your priorities, deadlines and problem jobs exist is your own memory, you are the single point of failure for the entire operation - and you will drop something, because nobody can hold eight live jobs' worth of detail in their head reliably, however experienced they are. Write it down. Put dates, decisions and next actions somewhere that survives you being on annual leave, on another site, or simply having a bad week.

This isn't about bureaucracy for its own sake. It's about being able to hand a job to someone else for two days without everything grinding to a halt, and about sleeping at night without running through every site in your mind before you drop off.

Standardise how every job gets set up

Every job that gets set up differently is a job that takes longer to understand when something goes wrong or when someone new needs to pick it up. Use the same structure every time: the same way of naming and numbering jobs, the same categories for costs, the same format for a look-ahead, the same place for photos and documents. It sounds like a small thing, but it's what lets you - or anyone else in the business - jump into any live job and orient themselves in minutes rather than an hour of asking around.

Standardising also makes it far easier to compare jobs against each other, which is exactly what you need to do when deciding where your attention goes this week. It's worth doing this properly once rather than patching it job by job - most job management software prices per user rather than per project, so getting the setup right doesn't cost more as your live job count grows; it's worth checking how that scales before you settle on a way of working. Whatever system you land on, the goal is the same: every job run the same way, so running several at once is a matter of process, not memory.