Required Skills & Knowledge of Planning & Scheduling
A schedule is a model of how a project will be built — and modelling is a skill. This lesson is the craft behind a credible schedule: structuring scope, getting the logic right, sizing durations, computing the critical path, and reading reality back into the model each period. Built on AACE 14R-90.
What scheduling expertise means
This is the deep dive into the scheduling branch of cost engineering (Lesson 5). Like estimating, it's part technical knowledge, part hands-on skill, and part judgment. The full depth is the Planning & Scheduling track (26 lessons); this lesson is the overview of what that depth contains.
Scheduling knowledge areas
The subject matter a scheduler must understand:
- Scope & WBS — Breaking the project into a work breakdown structure and well-defined activities.
- Network logic & CPM — Relationships, dependencies, the critical path method, float, and how the network calculates dates.
- Durations & calendars — Estimating activity durations (often from productivity and quantities) and modelling work calendars.
- Resources & cost loading — Assigning resources, resource levelling, and linking the schedule to cost where required.
- Statusing & control — Updating with progress, the data date, trending, forecasting, and recovery.
- Analysis & reporting — Reading the critical path, near-critical paths, variances, and reporting at every level.
The skills that matter
Beyond the technical knowledge, scheduling rewards a distinctive blend of analytical and people skills:
| Skill | In practice |
|---|---|
| Logical / systems thinking | Seeing how activities depend on one another |
| Scheduling software | Tools like P6 or MS Project, used correctly |
| Field knowledge | Understanding how the work is actually built |
| Eliciting input | Getting real durations and logic from the team |
| Communication | Reporting status clearly to every audience |
Field sense and judgment
The skill that separates good schedulers from great ones is field sense — knowing how the work actually gets built, so the model reflects reality rather than a tidy fiction. A scheduler who has never understood how crews sequence work will build logic that looks fine and fails on site. This comes from listening to the field and from experience, paired with the same honesty the role demands: a schedule must show the true position, not the comfortable one.
Nine things to remember
- Scheduling expertise is a distinct specialty within cost engineering.
- A schedule is a model of the project, not just a bar chart — think like a modeller.
- Knowledge areas: scope/WBS, network logic/CPM, durations/calendars, resources, statusing, analysis.
- The critical path is the heart of the specialty — almost everything serves managing it.
- Skills: logical thinking, software, field knowledge, eliciting input, communication.
- Software fluency is not scheduling skill — the tool is just a calculator for the network.
- A pretty schedule on bad logic is worse than a rough one on sound logic.
- Field sense separates good from great — the model must reflect how work is really built.
- Honesty applies here too — the schedule must show the true position, not the comfortable one.
Glossary
- CPM
- Critical path method — the technique that calculates dates and float.
- Critical path
- The chain of activities controlling the finish date.
- Data date
- The cutoff for a schedule update.
- Float
- Spare time before an activity delays the project.
- Forecast
- Projected completion based on current performance.
- Network logic
- The relationships linking activities into a sequence.
- Resource levelling
- Adjusting the schedule to fit resource limits.
- WBS
- Work breakdown structure — scope broken into manageable pieces.