Planning engineer career path
Last reviewed 9 September 2026928 words4 min read
🟩 In one line: The planning career runs from producing programmes, to owning the controls function, to directing it. It forks three ways — controls management, forensic and claims work, or moving between contractor, consultant and client side.
The ladder is short and the interesting decisions are the sideways ones.
No salary figures appear on this page. They vary too much by country, sector and year to be useful, and they would be out of date within twelve months.
The levels
| Level | Typical experience | What you own |
|---|---|---|
| Assistant / junior planner | 0–2 years | Look-aheads, progress collection, data entry, parts of the report |
| Planner / planning engineer | 2–5 years | A package or an area. Statusing, reporting, the narrative for your scope |
| Senior planning engineer | 5–10 years | The whole project programme. Baseline, submissions, delay assessment |
| Lead planner / planning manager | 8–15 years | Several projects or a large one. A team. Standards and templates |
| Project controls manager | 12+ years | Planning plus cost, risk, reporting and change. An integrated function |
| Head of project controls / director | 15+ years | The function across a business. Systems, capability, recruitment |
The ranges overlap heavily and the boundaries are not consistent between employers. Take them as shape, not as a timetable.
What actually gates each transition
The reason people stall is rarely technical skill in scheduling. It is the thing on the right of this table.
| Transition | The gate |
|---|---|
| Junior → planner | Owning a scope end to end without being checked |
| Planner → senior | Being able to defend the programme to a Consultant, in writing, and be right |
| Senior → lead | Managing other planners and setting standards rather than producing output |
| Lead → controls manager | Cost integration and commercial literacy — the part most planners never acquire |
| Controls manager → head | Capability building across a business, and credibility at board level |
The one to know about early. The lead-to-controls-manager step is where most planning careers stop, and the reason is consistent: planners are strong on time and weak on cost. If you intend to go past lead planner, start learning cost — earned value, cash flow, forecasting, change valuation — several years before you need it. It is the single highest-return thing a good senior planner can study.
The three forks
Fork 1 — project controls management. The default upward path. Time, cost, risk, change and reporting as one integrated function. Requires cost and commercial capability, and a shift from producing to managing.
Fork 2 — forensic and claims. Delay analysis, disruption, expert support, consultancy. Requires deep analytical skill, unusually strong writing, and comfort being challenged professionally. The technical base is choosing a delay method, time impact analysis and concurrent delay. Certification usually runs PSP then CFCC — see PMI-SP vs AACE PSP.
Fork 3 — changing side rather than level. Contractor, consultant, client, or specialist consultancy. The work is recognisably the same and the job is very different.
| Side | What the work becomes | Suits |
|---|---|---|
| Main Contractor | Building the programme, defending it, running the update cycle | People who like production and site |
| Consultant / PMC | Reviewing others' programmes, assessing claims, advising the Employer | People who like analysis and writing |
| Client / developer | Portfolio oversight, assurance, holding others to account | People who like breadth over depth |
| Claims consultancy | Retrospective analysis, expert support | People who like argument and evidence |
Moving contractor-side to consultant-side is common and generally straightforward — you already know how programmes are actually built, which is what makes a review useful. Moving the other way is harder than people expect: reviewing programmes for several years does not keep you sharp at producing one under a monthly deadline.
Skills that compound, by stage
Years 0–3. P6 fluency. CPM theory properly, not approximately. Construction sequence knowledge from site time. Excel.
Years 3–7. Duration justification and productivity. Delay assessment. Writing — narratives, responses, notices. Contract literacy around the programme and notice clauses. A certification if the sector values one.
Years 7–12. Cost integration and earned value. Risk analysis, including quantitative schedule risk. Managing people. Standards, templates and systems across projects.
Years 12+. Commercial judgement. Capability building. The ability to explain a controls position to people who do not want to hear it, at a level where that position affects real money.
Watch — the specialisation trap. Ten years on the same type of project, in the same role, at the same employer is ten years of experience for the first three and repetition for the remaining seven. The planners who progress fastest change one variable deliberately every few years: sector, side, project scale, or country. Changing all four at once is disruptive; changing none is the more common mistake.
Two things that compound more than anything else
A portfolio. Programmes you built, problems you found, analyses you produced, decisions you influenced. Kept as your own record, without confidential project information in it — a description of what you did and why, not the project's data. This is what gets discussed in senior interviews, and almost nobody has one.
Writing. At every level above senior, the output is a document that persuades somebody. The narrative, the response to comments, the delay submission, the board paper. Technical planners who cannot write plateau. Technical planners who can write clearly are unusually valuable and know it late.
Sources
Standards and references relied on for this page. Read them; this page is not a substitute.
- AACE International Recommended Practice 11R-88, Required Skills and Knowledge of Cost Engineering — The competency areas that distinguish practitioner from senior and management levels.
- AACE International Recommended Practice 29R-03, Forensic Schedule Analysis — The specialist body of knowledge underpinning the claims and forensic fork.
- PMI Practice Standard for Scheduling, 3rd edition (Project Management Institute, 2019) — The scope of scheduling practice as it broadens with seniority.
- AACE International Recommended Practice 37R-06, Schedule Levels of Detail — As Applied in Engineering, Procurement and Construction — The shift from level 3 production to level 1 and 2 ownership that accompanies seniority.
From the field
Experience from working planners. Unreviewed — read it as experience, not guidance.
Add what you know about planning engineer career path. What worked, what the consultant pushed back on, what you would do differently next time. A paragraph is plenty.
Contributors get their name and one link on the site — your own templates, course or consultancy. We take nothing and hold nothing.
Add your experience