Project Planner

A project planner (often called a planning engineer or scheduler) builds and maintains the timetable for a large project — working out what tasks happen in what order, how long each takes, who or what is needed, and what happens to the end date when something slips. They do this using scheduling software, feeding off information from engineers, site teams and contractors, and they report progress to project managers, clients and senior management. The role is most common in construction, infrastructure, rail, energy, defence, aerospace and large IT or engineering programmes.

Approximate graduate salary

Typically somewhere around GBP 26,000-35,000 to start, though this varies widely. Major infrastructure, rail, nuclear, defence and London-based roles tend to sit at the upper end or above it, while smaller regional contractors sit lower. Site-based roles may add allowances, and salaries tend to rise fairly sharply once you can run a schedule unsupervised, because experienced planners are in persistent demand.

What you'd actually do

  • Building and updating a project schedule in planning software (Primavera P6 and Microsoft Project are the two most common; some employers use Asta Powerproject, particularly in UK building construction) — creating activities, durations, and the logic links that say which task must finish before another can start.
  • Chasing progress information: ringing or emailing site managers, engineers, subcontractors and package leads to find out what actually got done last week, because they rarely volunteer it and the numbers they give are often optimistic.
  • Running the 'critical path' analysis — identifying the chain of activities that directly determines the project's finish date — and flagging where a delay on one task will push the whole project late.
  • Producing the weekly or monthly progress report: updated schedule, S-curves and progress graphs, a list of key delays and their causes, and a short narrative explaining what changed and why.
  • Sitting in progress meetings and coordination meetings, taking the schedule implications away as actions, and sometimes being the person who has to say out loud that the promised date is no longer achievable.
  • Modelling 'what if' scenarios at a project manager's request — for example, what happens to the end date if a piece of plant arrives three weeks late, or if a second crew is added to a critical activity.
  • Keeping the underlying data tidy: work breakdown structures, activity coding, resource and cost loading, and baseline change control (recording formally agreed changes to the original approved plan so that later comparisons are honest).

How graduates get in

  • Engineering, construction or infrastructure graduate schemes — the most common route. Many contractors, consultancies and asset owners recruit graduates into a broad project controls or project management stream and rotate them through planning, cost control and risk before they specialise.
  • Direct entry as a graduate or assistant planner, often in a project controls team where you support a senior planner. This is common in rail, energy, water, defence and oil and gas, and in specialist project controls consultancies.
  • Sideways from another project role — quantity surveying, site engineering, document control, or project administration. Moving into planning after a year or two on site is a very well-trodden path because the site knowledge makes you a better planner, and some employers prefer it to hiring straight from university.
  • Placement years and summer internships with contractors or consultancies. A placement on a live project is one of the strongest things you can have on a graduate application here, partly because it proves you can cope with site or programme environments.
  • Defence, aerospace and government programmes recruit graduates into project controls roles that include planning; these often require UK nationality and security clearance eligibility.
  • Converting in from an unrelated degree via a project management or construction management master's, or via an apprenticeship-style route. This is possible but less common than the graduate-scheme routes above.

What employers ask for

  • A degree is usually expected but the subject matters less than people assume. Civil, mechanical or other engineering, construction management, quantity surveying, building surveying, project management, maths, physics and business are all common. Numerate and technical degrees make it easier to get shortlisted for engineering-heavy projects.
  • Typically a 2:2 or 2:1 minimum depending on the employer. Some large graduate schemes still filter on a 2:1 and on UCAS points or A-level grades; smaller contractors and consultancies are often much more flexible and weight relevant experience more heavily.
  • Genuine comfort with software and data. Employers rarely require Primavera P6 or Asta experience at graduate level — they expect to train you — but they do expect strong Excel and evidence that you pick up systems quickly.
  • Any live-project experience: placement year, site work, summer job with a contractor, or a university project where you actually managed a programme of work. This is often the deciding factor between similar candidates.
  • Professional qualifications come later, not before. Common ones are APM (Association for Project Management) qualifications such as the APM Project Fundamentals or Project Management Qualification, and chartered status routes via the APM (ChPP), ICE or CIOB. Some employers pay for AACE or planning-specific certifications. Which one you're pushed towards depends heavily on the employer.
  • For defence, nuclear and some government infrastructure work: eligibility for UK security clearance, which usually means UK residency history. This rules out some roles for some candidates, so check before applying.

Skills that matter

Logical sequencing and dependency thinking

The core intellectual task is working out what genuinely must happen before what, and spotting when someone has given you a sequence that is physically impossible.

Scheduling software fluency (P6, MS Project, Asta)

Most of your output is produced in one of these tools, and a badly built schedule with broken logic produces confidently wrong end dates.

Extracting information from people who are busy and defensive

Progress data does not arrive on its own — you spend a lot of time politely pinning down site managers and subcontractors who would rather not commit to a number.

Numerical and data handling ability

You calculate progress percentages, earned value, resource histograms and productivity rates, and you need to notice when the figures don't reconcile.

Clear written and visual reporting

A director will look at your schedule summary for two minutes, so the delay, its cause and its consequence have to be obvious without explanation.

Holding a position under pressure

Planners are regularly asked to make a date look achievable when it isn't, and the value of the role depends on giving an honest forecast anyway.

Where it leads

  1. Graduate or assistant planner: you maintain part of a schedule under supervision, collect progress data and produce sections of the reports. Typically the first year or two, though this varies by employer and project size.

  2. Planner or planning engineer: you own the schedule for a project or a major work package, run the progress cycle yourself and present to the project manager and sometimes the client.

  3. Senior planner or lead planner: responsible for planning across a large project or several projects, setting the planning standards, checking others' schedules and mentoring juniors. How long this takes varies widely — on a fast-moving major programme it can be quick, elsewhere considerably slower.

  4. From there the path usually forks. One direction is project controls management or head of planning, overseeing planning, cost, risk and reporting together. Another is into project or programme management, which is a common move because planners understand how projects actually behave. A third is specialising in forensic or delay analysis — investigating who caused a delay and what it cost, used in contractual claims and disputes — which is a well-paid consultancy niche.

  5. Later-career options include commercial or contracts roles, PMO (project management office) leadership, independent consultancy, or expert work on delay claims. Timelines here vary enormously and depend more on sector and project scale than on years served.

What people get wrong

It's an administrative job — typing dates into software that someone else has decided.

The schedule is a technical model of how the work will physically be built or delivered, and the planner is usually the person who understands the whole project's mechanics best. Interrogating engineers' assumptions and telling a project director their date is unachievable is a core part of the job, not an occasional extra.

You need to be a qualified project manager, or have a project management degree, to get in.

Most planners come from engineering, construction or numerate degrees and learn planning on the job. Professional qualifications such as APM certificates are usually taken while employed and often paid for by the employer, rather than being an entry requirement.

It's a desk job, safely away from sites and factories.

In construction, rail and energy you'll spend real time on site in PPE walking the works, because you cannot verify progress from a spreadsheet. That said, this varies a lot: on IT, defence or aerospace programmes the role can be almost entirely office- or hybrid-based.

The plan gets written at the start and then followed.

Plans change constantly. Much of the job is the repeating cycle of updating, reforecasting and formally recording changes to the original agreed baseline, so that when the project finishes late there is a defensible record of why — which often ends up mattering contractually and financially.

Where this varies

The job differs a lot by sector. On building and civil engineering projects it is site-facing, fast, and closely tied to commercial and contractual matters — delay records feed directly into claims between client and contractor. In nuclear, defence and aerospace it is more process-heavy, with formal earned value management, strict baseline change control and long-duration schedules, and often requires security clearance. In IT and business change programmes the role often sits within a PMO and blends into general reporting and governance, sometimes with agile ways of working that de-emphasise long fixed schedules. Job titles are also inconsistent: planner, planning engineer, scheduler, project controls analyst and PMO analyst can all mean broadly similar work, and 'project planner' at some employers is a fairly junior reporting role while at others it is a senior technical specialism. Employer type matters too — working for a contractor means producing the schedule, working for a client or consultancy often means scrutinising someone else's.

General guidance about the role across the UK market, not about any specific employer. Entry routes and requirements vary — always check the individual job advert.