Managing Multiple Projects

Running two projects is hard. Running five with the same systems you used for two is how good builders have bad years. The transition from single-project to portfolio builder is less about getting better at construction and more about building the infrastructure around your work.

The Scaling Inflection Point

There's a moment in every growing builder's career when the systems that worked for two projects stop working for four. It's not a gradual degradation — it's usually a sudden crisis. A draw request falls through the cracks. A sub who's supposed to be on the Henderson remodel is over at the Elm Street job because nobody tracked the conflict. A homeowner complaint sits unanswered for three days because nobody owned it. The builder who was on top of everything at two projects is drowning at four, using the exact same systems.

The inflection point typically hits around 3–5 simultaneous projects for a solo builder, and around 6–10 for a builder with one dedicated project manager. Every builder's threshold is different — it depends on project complexity, geographic spread, and how much of the field work you're still touching personally. But the pattern is consistent: growth feels manageable until it suddenly doesn't. The builders who navigate it well are the ones who saw it coming and built systems before the crisis, not after.

Know your number. Be honest about it. If you're at capacity at three projects, running four is not a business opportunity — it's a reliability problem. Growing your capacity means building the systems and team to support more projects, not just saying yes to the next contract. The builders who get into real trouble are the ones who take on work they can't deliver, fund one project with another's cash, and end up with five jobs none of which are done right.

The Systems That Don't Scale

The first thing that breaks is memory. You can hold the status of two projects in your head — which subs are coming Thursday, where you are in the draw schedule, what's still open on the punch list. You cannot hold four projects' worth of that information with any reliability. You start dropping things: a material delivery date, a homeowner question you said you'd follow up on, a lien waiver you forgot to collect. Memory is a single-project tool. At scale, you need external systems that hold the information so your brain doesn't have to.

Phone and email are the second casualty. On one project, you're the communication hub and it works. On four projects, every homeowner, sub, supplier, inspector, and team member is routing through you, and you become the bottleneck. Things sit in your inbox. Your voicemail fills up. You respond to whoever's loudest, not whoever's most urgent. At scale, you need communication structures that don't route everything through you — defined reporting lines, a superintendent who handles field communications, a clear protocol for what goes to you versus what gets handled downstream.

Spreadsheets, paper folders, and truck-cab filing systems all share the same problem: they work when you can hold the context in your head to navigate them. Across multiple projects with different subs, draw schedules, CO histories, and inspection timelines, a spreadsheet per project is five spreadsheets you have to open, cross-reference, and update separately. Paper job folders in your truck mean you don't have the right folder when you need it, or the right document within the right folder. What replaces them is searchable, organized digital storage that lives in the cloud and is accessible to your team — and a project management structure with consistent field definitions so you can actually compare across projects instead of translating between different systems.

Daily site visits stop being viable, too. Visiting one site every day is normal. Visiting five is impossible — or it means you're spending your entire day driving between sites and not doing the strategic work that only you can do. You need a superintendent who owns the field, a structured daily reporting rhythm, and the discipline to manage by exception rather than by presence. If you're still trying to personally observe everything across a five-project portfolio, you're both inefficient and unavailable for the decisions that actually need your judgment.

Financial Management Across a Portfolio

On a single project, you can track budget versus actual in your head or in a simple spreadsheet. Across multiple projects, you need visibility into four things: total cash position today, what's outstanding from owners (draws submitted but not yet paid), what's owed to subs and suppliers, and projected cash needs for the next 30–60 days. Without this picture, you're guessing about your own financial health. That's a dangerous position for a business that operates on thin margins and timing-sensitive cash flows.

A weekly financial review — even 30 minutes — is non-negotiable once you're running more than two projects. Sit down every Monday morning and look at outstanding draws by project, outstanding payables by project, committed costs that haven't been invoiced yet, and what needs to be paid this week versus what can wait until your next draw funds. This review isn't glamorous, but it's the difference between a builder who knows their position and one who's perpetually surprised by it. The builders who skip this review are the ones who call their accountant in a panic at the end of the month wondering where the money went.

Cost tracking at the portfolio level requires consistent category structures across projects. If one project tracks plumbing under "mechanical" and another tracks it under "plumbing rough," you can't compare them or aggregate them meaningfully. Pick a cost category structure — phases, trades, whatever works for your business — and use it consistently across every project. This discipline pays dividends when you start analyzing your actual versus budgeted margins by trade, when you're doing the post-project review that makes your next bid more accurate, and when your accountant needs to produce financial statements that reflect how the work actually happened.

The Cash Flow Danger Zone

The most common multi-project financial failure is also the most avoidable: cash from one project subsidizing another. You're short on the Morrison project because the owner is slow paying, so you pull forward materials purchases using cash from the Riverside draw you just received. Then the Riverside project hits a problem and you need that cash for its own costs. Now you're behind on both, and the next draw on either project is two weeks out. This is not a hypothetical — it's how builders who are nominally profitable go bankrupt.

The discipline is this: every project's cash must be tracked separately, and ideally held separately. If you can manage it operationally, a separate bank account per project is the cleanest solution. If that's too cumbersome, at minimum maintain a running tally of each project's cash position — what's been received, what's been paid out, what's committed but not yet due — so you know at any moment whether each project is cash-positive or cash-negative on the funds received so far.

If a project is cash-tight, you have two legitimate options: submit a draw request (or an early draw request if your contract allows it), or have a direct conversation with the homeowner about the payment schedule. What you don't do is quietly paper over the gap with another project's funds. The moment you start doing that, you've lost visibility into your actual position — because you're now tracking a shadow liability (what you owe back to Project C) that doesn't show up anywhere formal. Know your draw schedule on every project, every week. Know when money is coming in, what it needs to cover, and what surplus (if any) exists.

The builders who manage cash best at scale treat their draw schedules the same way they treat their construction schedules — as documents they actively manage and update, not passive records of what was agreed to eight months ago. If your construction pace is ahead of the draw schedule, submit an early draw. If you're behind, communicate proactively with your owner before the next draw date. Cash flow surprises come from inattention, not from the construction business being inherently unpredictable.

Scheduling Multiple Projects: Resource Conflicts

Your subs don't work exclusively for you. Your framing crew has other builders. Your plumber has other jobs in the queue. When you have three projects in framing simultaneously, you may not be able to get all three crews on site when you need them — and if you haven't thought about this in advance, you'll discover it the hard way when one of your projects sits idle for two weeks waiting for a framer who's tied up elsewhere.

Resource conflicts have to be planned for, not discovered. Build a simple resource calendar — it doesn't have to be sophisticated. List your key subs across the top and your projects down the side. For each four-week window, mark which projects need which subs and when. When you see two projects needing the same electrical sub in the same two-week window, address it now: either adjust one project's schedule to sequence the work, confirm that the sub has two crews available, or identify a backup sub you'd use. The earlier you surface this conflict, the more options you have.

The same resource constraint applies to your own leadership bandwidth. A superintendent who's managing four simultaneous projects is effectively managing none of them — they're triaging, not leading. A project manager stretched across a portfolio without clear prioritization ends up reactive everywhere and proactive nowhere. As you scale, be explicit about how many projects each person on your team can effectively manage, and staff accordingly. Trying to stretch existing capacity by a third or half to avoid hiring is a trade-off that always costs you in quality, speed, or both.

What to Check Every Morning

At scale, your morning review is your steering wheel. Without it, you're reacting to whoever calls you first. With it, you're setting the day's priorities based on what actually matters across your portfolio. Build a 20-minute morning habit and protect it from interruption — it saves more time than it costs.

You can't run a five-project portfolio from your truck and a phone. You need a dashboard — a single place where these questions get answered without calling five supers, opening five spreadsheets, or scrolling through a hundred text messages. The morning review only works if the information comes to you organized; if you have to go hunting for it, you'll skip the review and go back to reacting.

The 20-minute number is realistic only if your team is keeping project data current. If your supers aren't logging daily progress, if your budget data is weeks stale, if tasks aren't being updated as they complete — your dashboard is a fiction and your review is guesswork. The morning review habit requires a corresponding discipline from your team: the data has to be live. This is worth enforcing. A super who won't update the daily log is giving you a project you can't see.

Delegation Without Losing Control

The builder who tries to be in every detail across six projects fails at scale. They become the bottleneck, decisions stack up waiting for them, and the projects slow down. But the builder who delegates everything and doesn't inspect loses quality and homeowner trust. The right model is neither extreme — it's selective engagement based on consequence and reversibility.

Here's the principle: you own what can't be undone, and you delegate what can. You make the call on structural changes, foundation decisions, any scope change that affects future work, and anything that touches your homeowner relationship directly. Your superintendent owns daily field execution, sub coordination, inspection scheduling and oversight, and daily logs. Your office manager or PM owns draw requests, invoicing, sub payment releases, and documentation. When these roles are clear and written down — even a single page — everyone knows what they own and what to escalate.

Hold weekly check-ins with your supers and your office: 20–30 minutes each, structured around the same questions every time. What moved forward? What's blocked? What do you need from me? What's coming up next week that I should know about? This rhythm catches problems before they compound and builds the trust that makes true delegation possible. Manage by exception: if a super is handling things well, stay out of the details and let them own it. Step in when something deviates from what was planned or when a decision is outside their authority. Inspecting everything signals distrust and undermines the delegation you're trying to build.

The Portfolio Reports That Matter

When you're running a portfolio, you need aggregate visibility — not just project-by-project status, but patterns across your whole book of work. The reports that matter are the ones that surface problems before they become crises. Budget variance across all projects tells you which jobs are healthy and which are bleeding before the final reckoning. Overdue task reports tell you which projects are falling behind before the homeowner notices. Outstanding draw and payable summaries tell you your actual cash position. Punch list status by project tells you which jobs are in closeout and whether any are stalled.

These should be answerable in under 10 minutes from your management system — not from phone calls, not from opening five separate files, and not from asking your super to send you a summary. If you can't get a clean portfolio view quickly, you're working with systems that don't scale. The investment in getting your team to keep data current, and in using software that surfaces aggregate reporting, pays back every week in the form of decisions made from real information rather than instinct and memory.

In Baulit

Baulit's main dashboard is built for the portfolio view. Every project you're managing shows its progress percentage, budget status, task counts, and any overdue or blocked items — all on one screen. You don't have to open each project to know which ones need attention today. Red and yellow indicators surface problems automatically; a clean project stays out of the way.

The Portfolio Report aggregates schedule and budget health across your entire book of work: tasks complete versus total, budget used versus contracted, draws submitted, and project phase by project. It's designed to be the printout you review in your weekly financial meeting. The Overdue & Blocked report surfaces tasks that are past their expected completion date across all projects simultaneously, so your morning review starts with the right list instead of you having to hunt for it.

For builders running multiple projects with different team members assigned, Baulit's multi-project management features let you organize projects into groups, filter across projects by status or team member, and see resource assignment patterns at a glance. The goal is the same as this article: give you the information you need to steer the portfolio without requiring you to be physically present everywhere at once.