How I Keep 70 Active Jobs From Collapsing Into Each Other

Brittany Northup · June 6, 2026 · 5 min read
project managementAVoperationstrades

On a normal Tuesday I have around seventy jobs open at the same time. A casino floor getting new displays. Three taverns mid-upgrade. A tavern being built from bare walls. A custom home where the owner wants every room wired to do something different. None of them care about the other sixty-nine. Each one believes it is the only job I have.

People hear seventy and assume the answer is some heroic amount of hustle. It is not. Hustle is what you fall back on when your system fails. The whole point of a real system is that you almost never have to be a hero.

Here is how I actually keep seventy live jobs from collapsing into each other.

One place where every job is true

The first rule is boring and it is the one most people break. There is exactly one place where the real status of a job lives. Not my memory. Not a text thread. Not three different apps that each know a piece of it.

When a job's status lives in five places, it lives in zero places, because the moment two of them disagree you cannot trust any of them. So every job has one record, and that record is the truth. If it is not written there, it did not happen. Crews learn this fast. Clients feel it without knowing why, because they stop getting two different answers from two different people.

This sounds obvious until you are the person holding it together. Most of the chaos in this trade is not bad work. It is good work that nobody wrote down.

Triage by what is actually on fire

Seventy jobs do not get seventy equal slices of my day. They get triaged. Every morning I sort the whole list into three buckets.

That third bucket is the whole game. Anyone can react to the thing that is already burning. The job is to find the one that is about to.

The follow-up no tool will do for you

This is the part the software never gets, and I have used a lot of software. Teams and Planner are fine for a team of five doing one thing. They fall apart the second you are running dozens of different jobs with different crews and different clients who all need different things.

My boss even built a custom AI tool to help. It does help. It also has to be fed and maintained, which is one more job on top of the seventy, and that is its own quiet lesson: a tool that needs babysitting is not saving you as much as it looks like on the demo.

What no tool has replaced is the human follow-up. The call that goes "we are two days out, here is what I need from you so we do not slip." The read on a crew lead's voice that tells me a job is about to go sideways before the schedule shows it. You can automate the reminder. You still have to make the call. The software can tell me a job is quiet. It cannot tell me why, and the why is everything.

What this actually proves

I do not have a degree in any of this. I started in the warehouse and became a project manager in five years by doing the work, getting it wrong, and building the system that kept me from getting it wrong twice.

For a long time I treated that as a thing to be nervous about. The missing certificate. The fear that someone with the right paper would walk in and I would be exposed. I do not really feel that anymore, and here is why.

The certificate does not keep seventy jobs from colliding. The system does. The certificate is not there at midnight when a display wall goes dark the night before a casino reopens. The person who knows exactly where that job stands, and who to call, and what to do, is there. Paper says one thing. The job site says another. I trust the job site.

If you are doing the work and you are good at it, the track record is the credential. Nobody running seventy jobs at once is faking it. The proof is that nothing is on fire, and that is the quietest, hardest thing to pull off in this whole trade.

Get new posts from Brittany Northup