On any construction site, before Primavera, before Power BI and before the minutes of the coordination meeting, there is oral tradition. Phrases repeated at the workface, in the changing room and in the site office, compressing decades of expensive lessons into a single line.
The problem is that they do not all say the same thing. Some encode real planning discipline, the kind that reduces delays and takes years to learn. Others are excuses: alibis that sound like popular wisdom but actually describe very precisely where your planning has broken down. After enough projects, you learn to hear both.
Cheap excuses
An excuse on site is not only a way of dodging responsibility; it is information. Every stock phrase tells you which link in the planning chain has failed. If you know how to read them, they stop being annoying and become data.
"The night shift did that." / "I don't know, it was like that when I arrived."
This is not bad faith; it is a lack of traceability. When two shifts hand over without a handover record, what was completed, what was left half-done, what remained pending and why, nobody is responsible for anything and the as-built is reconstructed from memory. The solution is not to look for culprits; it is a shift handover report and a daily record of real progress that does not depend on who was standing there at three in the morning.
"I didn't know I had to do that, nobody told me." / "The supervisor didn't explain what had to be done."
This is the excuse that the Last Planner System attacks head-on. It is almost always true: the commitment was never formulated clearly and verifiably. A weekly plan only works if each task has a responsible person who has explicitly accepted it, not if it appears in a Gantt chart that nobody at the workface has seen. This is where PPC (Percent Plan Complete) does its job: it measures fulfilled commitments against committed ones, and turns nobody told me into measurable data instead of a corridor argument.
"They don't pay me to do that." / "I can't now, I'm too busy." / "We'll finish it after the break."
A classic symptom of undefined priorities or overload. When everything is urgent, nothing is, and the operative decides for themselves what falls first. A lookahead that releases constraints and sequences the work with judgement prevents that decision, critical for the path, from being made by the person with the least context to make it.
"This is how things have always been done." / "It has always been done this way."
The zombie standard. Sometimes it hides a proven method that should be respected; other times, a procedure that survives only by inertia and that nobody has questioned again. The difference is whether there is a documented reason, or only a habit.
"That has been there for years and it still hasn't fallen."
The normalisation of risk, said with pride. The fact that something has not failed yet is not evidence that it is safe; it is evidence that you have been lucky so far. It is the perfect prelude to the saying: do not learn safety by accident.
"Not everything can go according to the design / the plan / the book."
This is half true, and that is why it is dangerous. A plan is a hypothesis, not a prophecy; no schedule survives contact with the site intact. But it is used as an alibi for not planning at all, which is exactly the opposite conclusion. The fact that the plan will change is precisely the reason to have one: without a baseline there is no way to know how far you have deviated, or why.
"A plan? We don't need a plan, we need to do the work."
The mother of all anti-planning excuses. And the best answer does not come from me: it comes from the construction site's own sayings. That is where we are going now.
The sayings that really are planning
If excuses describe where the system fails, many sayings describe how it should work. They are not decorative phrases: they are project management principles expressed in site language, often with more honesty than a manual.
"A well-planned project is half done." / "A job started is half finished."
The value of front-loading effort. Every hour invested in sequencing, releasing constraints and defining scope before moving a machine pays back several times during execution. With an important nuance in the second saying: starting is not the same as progressing. Many projects confuse the start percentage with real physical progress, and that is where an honest S-curve separates what appears to be happening from what is really happening.
"Good, fast, cheap: choose two."
Probably the most honest phrase in all project management, and it fits on a site office wall. It is the iron triangle, scope, time, cost and quality, with no decoration. Every time someone asks you for all three at once without giving anything up, they are not asking for a project; they are asking for a deviation with a date.
"The devil is in the details."
In planning, the devil is the activity nobody put in the schedule: the constraint discovered on the day of execution, the permit that took six weeks, the interface between disciplines that was not coordinated. A schedule that is too coarse hides all those devils; the right level of detail brings them to light while they can still be managed.
"The right tool for the right job." / "A good carpenter does not blame bad tools."
These two contradict each other on purpose, and the lesson sits in that tension. The tool matters, because good planning software gives you real control, but it does not replace the method. A bad plan in Primavera is still a bad plan, only with better typography. P6 does not plan for you; it organises and communicates what you have already thought through.
"Do not learn safety by accident." / "Helmet on your head saves your skin."
Safety as something planned, not something reacted to. If your first serious analysis of a risk comes after the incident, you did not have a safety plan; you had luck with an expiry date.
"Work smart, not hard." / "You are worth what you did on your last project."
Productivity and reputation. The first is a reminder that the solution is rarely to put more hours into a broken method. The second is the hardest of all: in this industry, your track record is not written by your CV, it is written by your last delivered project.
The foundation that makes any plan executable: the team
All of the above, traceability, commitments, the lookahead, the S-curve, is worthless without a team capable of executing it and leadership capable of sustaining it.
Good leadership, accompanied by a qualified and motivated team, is what turns planning into results. A competent leader does not merely point the direction: they communicate it clearly, build trust and create an environment where open communication and collaboration are the norm rather than the exception. That tone, that culture, is what allows problems to be solved efficiently, decisions to be made with information and construction delays to be reduced instead of accumulated.
A team of qualified and motivated people is the non-negotiable requirement for any successful execution. The right combination of skills, experience and good leadership is what ensures that constraints are released on time and that the weekly plan is achieved. And here it is worth remembering why that team is worth investing in, with the phrase often attributed to Henry Ford:
"The only thing worse than training your employees and having them leave is not training them and having them stay."
In the end, the construction site already knows almost all the theory. It has carried it encoded in its sayings since long before software existed. The planner's job is not to teach that wisdom, but to turn oral tradition into a system: moving from nobody told me to measured commitment, from it was like that when I arrived to traceable records, and from we do not need a plan to a schedule that, precisely because it will change, is worth having.