Ready Isn’t a Date

When a construction activity gets started on a project, the trigger is often the schedule. The date on the plan says it’s time. So the activity begins.

But the schedule is a forecast of when. It’s not a verdict on whether the collective conditions to start that activity are actually in place.

Materials staged. Predecessor's work signed off. Inspections passed. Drawings current. Crew briefed. Any of those can still be open when the date arrives. And the activity often starts anyway.

The gap between scheduled to start and ready to start is a small one in any given moment. Over the life of a project, it accumulates.

Two Definitions of Ready

In military operations, “ready” for a specific action has a defined meaning. The conditions get checked. The verification isn’t optional, and it isn’t a formality. The check is what the word ready actually refers to.

Before a unit moves into a specific tactical action, someone confirms the team has what it needs. Equipment functional. Comms working. Personnel briefed. Constraints removed. If something is missing, the action either waits or starts with the gap acknowledged explicitly.

In construction, the equivalent moment doesn’t always get the same treatment. The crew shows up. The activity begins. The constraints get checked, if they get checked, while the work is already in motion. By the time someone notices the gap — drawings out of date, predecessor work not signed off, materials not staged where they should be — the activity is already incurring cost.

The schedule said it was time. So it started. Whether it should have started is a different question.

Why the Gap Exists

The reason construction doesn’t always make that check explicit isn’t lack of awareness. It’s structural.

A single construction activity often depends on dozens of trades and material suppliers — typically from different companies, each operating with their own priorities, coordinating across office and field teams that don’t always share systems or cadences. The collective readiness for that activity sits at the intersection of all those parties. The visibility of that intersection isn’t usually owned by any one of them.

The crew about to start drywall doesn’t have full visibility into whether the inspector signed off, whether the drawing revision propagated, whether the materials shipped from the right vendor on the right date. They have their piece. The other parties have theirs. The collective picture lives somewhere between them — often as a phone call, an email thread, or someone’s memory of a conversation from last Friday.

That’s not a failure of any individual company. It’s the structural condition of an industry built around independent specialists who need to coordinate without owning shared infrastructure.

The teams pulling ahead aren’t trying to remove the fragmentation. They’re building the verification layer on top of it.

Where the Cost Lives

This pattern doesn’t show up as a dramatic failure. It shows up in places the industry already knows well.

It shows up in rework, when an activity proceeds despite a constraint that wasn’t removed — and the work has to get redone once the constraint actually closes. It shows up in slips, when day one of a planned activity gets spent on what should have happened the day before. It shows up in claims, when delays cascade and the question of who was responsible for verifying readiness becomes the centerpiece of a legal dispute. It shows up in margin erosion that no one books under its real name — because nobody writes “started before ready” on a job cost report.

Last week’s standalone called this the ambiguity tax. Activity-level readiness is one of its most expensive forms. The date arrives, the schedule signals start, and the question of are we actually ready gets answered after the fact rather than before.

What the Teams Pulling Ahead Are Doing

The teams that have closed this gap aren’t running more disciplined people. They’re operating inside systems that surface readiness criteria at the activity level and force verification across parties before the activity begins.

Three patterns keep showing up.

They define what “ready” means for each activity in advance. What has to be true before drywall hangs? Before MEP rough-in starts? Before pour day? The criteria get specified upstream, when the team has time to think clearly — not at the moment the date arrives and there’s pressure to begin.

They verify the collective constraints have been removed before the activity starts. Someone is responsible for the check across all the parties involved. The check is documented. If a constraint isn’t closed, the team makes a deliberate decision — wait, work around it, or start with the gap explicit — instead of stumbling into the consequences.

They treat the schedule as a forecast, not a verdict. A date on the plan is what the team is aiming for. It’s not what determines whether the activity is actually ready to begin. The schedule predicts when; readiness verification answers whether.

That’s not a discipline problem at the individual level. It’s an infrastructure one — the same shift this series keeps returning to. Build a system that makes readiness criteria visible across parties and forces verification before activities start, and the behavior follows. Skip the system, and the date does the work it was never meant to do.

Ready isn’t a date. It’s a state.

The construction teams that learn the difference get faster. The ones that don’t pay the same tax twice — once in the rework, once in the slip.

---

*Field Notes No. 02 — Commander’s Intent — covered the related question of decision rights. No. 04 lands next week.