The Basics of Scheduling & Analysis
Getting the fundamentals right before chasing the advanced stuff
In project controls, there’s a temptation to jump straight into complex scheduling techniques and flashy reporting tools.
But the truth is… if the basics aren’t in place, everything else crumbles.
I’ve realised that the foundation of a good schedule isn’t about how sophisticated it looks, it’s about whether it can be trusted to guide the project.
1. Build with Structure, Not Just Dates
A schedule isn’t just a list of activities in chronological order. It needs a clear Work Breakdown Structure (WBS) that reflects how the project is actually delivered.
That WBS should make sense to anyone who picks up the programme, from design teams to management.
When the structure is right, logic flows more naturally, reporting becomes easier, and changes are far less painful to manage.
2. Logic Is King
Dates on their own tell you nothing. Logic tells you why things happen when they do. Without clean logic links, float analysis is meaningless, and impact assessments become guesswork.
When I review a schedule, one of my first checks is: can I follow the critical path without confusion? If not, we fix the logic before moving forward.
3. Duration Decisions Matter
It’s tempting to drop in “safe” durations, round numbers, or best guesses to keep things moving.
But every duration should be grounded in something, historical data, team input, or agreed assumptions. Small changes in durations ripple through a schedule.
A one-week activity that should be three days can quietly push milestones further than you think.
Recommended by LinkedIn
4. Analyse Before You Report
Analysis isn’t just for end-of-month dashboards.
It’s a continuous process of asking:
If you’re only looking at the schedule when a report is due, you’re reacting late. I believe good planners analyse constantly so surprises are spotted early.
5. Presentation Counts
A schedule is a communication tool, not just a technical document.
That means:
If your audience can’t read it quickly, they won’t use it, and that’s when bad decisions get made.
Final Thought
Scheduling and analysis are like building a house, the finishing touches only shine if the foundation is solid.
Get the WBS, logic, durations, analysis, and presentation right, and everything else you add will have more impact.
It’s not about doing more, it’s about doing the right things consistently.
