You Can’t Schedule Information. You Can Only Schedule Its Delivery.

Every project has a programme.

It has milestones, deadlines, deliverables and carefully planned sequences of work. These establish when information is expected to arrive and when the next stage of production should begin.

But a programme does not produce information.

It cannot resolve an outstanding decision, confirm a design requirement or create the technical input a team needs to continue working.

A deadline can schedule the delivery of information. It cannot guarantee that the information will exist.

Production depends on decisions, not dates

Project programmes often assume that work will progress because the calendar says it should.

A package is due on Friday. A coordination milestone has been set for the end of the month. A drawing issue is scheduled before the next construction stage begins.

But production only moves when the information required to continue is sufficiently complete, coordinated and stable.

If a wall type has not been confirmed, a junction cannot be resolved. If the structural strategy is still changing, connected architectural and M&E information cannot be finalised. If equipment requirements remain unknown, the team cannot accurately coordinate space, services or asset data around them.

The deadline may be approaching, but the information required to meet it still does not exist.

No amount of pressure can replace a missing decision.

Deadlines measure expectations

Deadlines are useful. They establish priorities, create accountability and coordinate the activities of multiple teams.

But they measure expectations. They tell us when something should happen.

Information enables progress. It gives people what they need to make decisions, complete their work and release the next activity.

These are not the same thing.

When they are treated as interchangeable, delays are often framed as production problems: the team is moving too slowly, the model is not developing quickly enough or the drawings are not ready.

In reality, the work may be waiting for an unresolved decision, incomplete consultant input or information that has not yet reached the level of stability required for production.

The issue is not always how quickly the team is working. Sometimes the team simply cannot build information that does not exist.

Managing the flow of information

A reliable programme must do more than assign dates to deliverables. It should identify the information and decisions each deliverable depends on.

That means asking:

• What information is required to begin this task?
• Who is responsible for providing or approving it?
• Which decisions must be stable before production can continue?
• What other activities depend on this information?
• What happens to the programme if it arrives late or changes?

This turns the programme into more than a list of deadlines. It makes visible the flow of information that actually drives the project.

It also allows teams to distinguish between a production delay and an information constraint. That distinction matters because each problem requires a different response.

More pressure may accelerate production when the required information is already available. It cannot resolve an absent decision.

Schedule the delivery, manage the conditions

Projects need deadlines, but deadlines alone do not create progress.

Progress depends on whether the right information exists, whether it has been coordinated and whether it reaches the people who need it at the right moment.

The calendar can tell a team when a deliverable is expected.

The information determines whether that delivery is possible.

So perhaps the most useful question for a project team is not simply:

“What is due this week?”

But:

“What couldn’t your team build this week because the information didn’t exist yet?”