The Schedule With Four Keepers and No Owner
The project schedule said steel erection started Monday. It had said that for five weeks. Steel had not started. Nobody had lied. Four people were maintaining that schedule in four separate files — and each one assumed the others were posting the true version. The overrun did not begin the day steel slipped. It began the day the schedule acquired its fourth editor and lost its last owner.
How a Well-Run Project Produced Four Conflicting Schedules
The project was not poorly managed. A mid-size civic build with a contracted scheduler, an experienced project manager, a site superintendent who had built half the town, and an owner's representative filing monthly reports. The master schedule sat in a shared folder. Anyone could open it. Anyone could save over it.
Which is exactly why nobody did. Saving over a file four others rely on feels reckless. So everyone did the polite thing: they kept a working copy. By month four there were four schedules — each defensible, each current in the way its keeper needed, none of them the actual project. The steel slip appeared in the scheduler's private file in week nine, on the trailer wall in pencil in week eleven, and never appeared in the shared folder at all. The owner's monthly report said the project was on programme until week fourteen, when someone walked the site.
The Tell: A Document That Belongs to Everyone Belongs to No One
When the review came, it asked one question: who updates this schedule, and when? Four people gave four answers. Every answer contained the word "usually." That is the diagnostic. A schedule with four editors and no keeper is not a plan — it is a rumour with a Gantt chart attached. It still gets quoted, printed, and pinned to a wall. But nothing in it is a commitment, because a commitment needs a name on it.
What did not fail here is worth noting. The scheduling software worked. The scheduler was skilled. Every person on the team was competent, busy, and acting reasonably given what they could see. That is precisely why this failure mode is so durable: there is no villain to terminate, no obvious moment of negligence. Shared access without clear ownership is invisible as a structural fault until the question arrives that nobody can answer.
The Remedy Is Not Better Software
You do not fix this with a new platform and you do not fix it with another weekly meeting. You fix it by naming one person as keeper before the first date goes on the document. One keeper. One file that is the schedule — everything else is a copy with no standing. Changes route to the keeper. The keeper posts a dated update on a fixed cadence, and posts it even when nothing has moved, because "no change this week" is information too.
The same failure hides wherever a document has many readers and no keeper: budgets, risk registers, drawing sets. The cost of assigning ownership is about twenty minutes a week. Set against that: eleven weeks of a civic build operating on the wrong version of reality.
Practical Takeaways for Project Leaders
Name a keeper before you name a date. Document ownership must precede schedule entry, not follow it.
Treat cadenced null updates as information. A keeper who posts "no change this week" prevents four people from drawing four different conclusions.
Demote every other copy to read-only. The working copy on the consultant's laptop is not the schedule — it is research material for the keeper.
Apply the same rule to every governing document. Budget, risk register, drawing register — each one needs a single keeper and a single authoritative file.
The Bottom Line
The slip itself was survivable. Eleven weeks of reacting to the wrong version of reality was not. The structural fix costs twenty minutes a week and predates any software decision: assign one keeper, create one authoritative file, and treat everything else as a downstream copy. A schedule with four editors and no owner is not a plan — it is collective faith, and faith does not update when steel slips.
This content was generated by AI.
Comments