The 47 Things Before Work Starts

The 47 Things: Why Before-Phase Planning Matters More Than the Phase Itself

Here’s the deal. Working through how to keep everyone genuinely on track on our own Aviator project, I landed on something that changed how I think about project delivery entirely. The preparation that happens before any activity starts is more important than actually standing there supervising the work once it begins.

Poorly run project delivery teams hand a trade a contract, tell them to go ahead and start, and then spend their time walking around watching. Genuinely great project delivery team leaders understand something different. There are roughly forty seven distinct things that have to happen, done well and done on time, before any single work package can actually begin.

Visualizing Where the Real Work Actually Sits

Here is the exercise that made this concept click for me. Take a construction schedule and isolate every first activity, every independent wagon, everything with a work package that has to be prepared in advance. Line those starting activities up on a diagonal, running from the top left down to the bottom right of your production plan. Now look at what sits in front of each one of those starting points, further to the left on the timeline. That is where you find roughly forty seven preparation activities that genuinely have to happen before that work package can begin.

Do this across an entire project and you end up staring at an enormous page covered in stickies. Each one represents a real piece of preparation work, and each one requires a genuine level of effort to complete. Here is where it gets difficult. Every human on your project delivery team only has a certain amount of capacity to actually do that preparation work, and that capacity has to account for PTO, doctor’s appointments, ordinary distractions, and everything else that eats into a normal week.

Why Projects Actually Fall Behind

Once you see it laid out this way, the real problem in construction becomes obvious. We are not starting these preparation activities soon enough. They need to move further to the left on the timeline, meaning they need to begin earlier, and most project teams simply are not doing that.

Watch for these signs your project is not moving preparation activities far enough ahead of when they are actually needed:

• Work packages arriving at their start date with prep activities still incomplete or barely underway.
• No visible tracking of preparation work separate from the visible construction schedule itself.
• Project delivery team members consistently overloaded right before a phase begins, rather than steadily working ahead of it.

Why the Back Third of Almost Every Project Suffers

Here is where this connects directly to something worth understanding about the human brain. At roughly the two thirds point of a typical project, CPM schedules already start hurting teams structurally, since that is usually where borrowed schedule slack finally runs out. On top of that structural problem sits a genuinely human one. The human brain is de-incentivized to do pre-planning and incentivized instead to fight fires. Firefighting feels urgent and rewarding in the moment. Quiet, unglamorous preparation work does not carry that same emotional pull, even though it matters just as much, if not more.

So exactly when a project needs more disciplined pre-planning, people naturally do less of it, because their attention gets pulled toward whatever fire is burning loudest right now. The final third of a project ends up suffering directly because of that missing before-phase planning, compounding on top of whatever schedule pressure was already building.

What We Actually Built to Fix This

On the Aviator project, I broke this preparation work into distinct categories. Supply chain. Contracting. Training. Pull plan preparation. Work packaging. Then I built a series of gates a project delivery team has to pass through, in sequence, before moving forward.

The first gate is the pre-mobilization meeting, and I want to personally be present in that meeting. The next gate sits before the pull plan itself, where I check that the team has genuinely completed all the necessary preparation activities leading up to it. Another gate sits before the pre-construction meeting for each trade. Moving from left to right across the project, each gate has its own checklist, and the exact count is not fixed at forty seven for every single situation. Sometimes it is thirty five. Sometimes closer to fifty. What matters is capturing every genuine preparation activity and looping it into the relevant gate, rather than letting any of it slip through unnoticed.

When I walk into a pre-mobilization meeting, I can check directly with the project delivery team. Are these specific things actually done? If yes, we move forward, and the next set of items becomes their active to-do list. When we reach the pre-construction meeting gate, I check the same way. Are these things ready? The gates move the team forward deliberately, one verified step at a time, rather than assuming preparation happened simply because the calendar says it should have.

Making This Genuinely Trackable, Not Just Theoretical

None of this works as an idea alone. It needs a real system behind it. We built templated checklists for every gate inside a project management tool, in our case ClickUp, so a team member entering a new phase has an actual template to work from rather than a vague understanding of what needs to happen.

Between gates, team members plan their own work using Fibonacci numbers through a Scrum style approach, which helps genuinely manage their available capacity rather than simply hoping everything fits. Our Takt software carries the same gates and timelines built directly into the production plan, so the entire system, software and checklist templates together, keeps everyone moving forward deliberately instead of discovering a gap only once it becomes urgent.

Why This Deserves Real Attention From Project Management Software Broadly

The honest takeaway here goes beyond one project. Most project management software tracks the visible scheduled activities well. Very little of it genuinely tracks the forty seven things sitting in front of each one, the real preparation work that determines whether that visible activity can actually start on time. We need project delivery systems built specifically to track and manage that preparation work, while genuinely accounting for the real human capacity available to complete it.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build exactly this kind of gate based preparation system, tracking the real work sitting ahead of every activity rather than only watching the schedule once work has already started.

So here is the challenge. Pick one upcoming phase on your current project and count the actual preparation activities sitting in front of it. Do not stop until you have genuinely captured all of them, however many that turns out to be. Then check honestly whether each one has already been started, or whether it is still sitting further to the right on the timeline than it should be.

Jason Schroeder said it plainly: “Before-phase planning is more important than actually the phase.” Build your systems around that truth, and the back third of your project stops absorbing the consequences of what never got prepared early enough.

On we go.

FAQ

Why does the exact number of preparation activities vary between thirty five and fifty rather than always being forty seven?

Because the real number of preparation activities depends on the specific work package, trade, and phase involved, and no single count applies universally across every situation. The number forty seven functions as a useful shorthand for the concept, a genuinely large volume of prerequisite work sitting ahead of any visible schedule activity, rather than a precise figure meant to apply identically everywhere.

Why does the human brain resist proactive pre-planning even when it clearly matters?

Because firefighting an active, visible problem feels urgent and rewarding in the moment, while quiet preparation work for something that has not gone wrong yet does not carry that same emotional pull. That mismatch means people naturally drift toward reactive work under pressure, even during the exact stretch of a project where disciplined pre-planning matters most.

How do gates actually prevent a project from falling behind on preparation work?

Gates create a specific checkpoint before a team can move forward into the next phase, forcing an honest verification that the required preparation activities are genuinely complete rather than assumed to be done. That verification catches gaps while there is still time to close them, instead of discovering a missing piece of preparation only once the phase it supports has already begun.

Why does human capacity need to be factored into a preparation tracking system rather than just listing the tasks themselves?

Because a list of preparation tasks alone does not account for the real, limited time each team member actually has available once PTO, appointments, and normal distractions are factored in. A system that ignores capacity can produce a checklist that looks complete on paper while quietly overloading the people responsible for actually completing it, which defeats the purpose of tracking preparation in the first place.