The planning engineer job role is not about producing a tidy bar chart for the monthly review. It is about owning the one document the contract uses to decide who pays for lost time. The planning engineer builds the baseline programme, measures progress against it, and keeps the dated record that an extension-of-time claim is argued from — and on an Indian contract that record is usually worth more than the schedule itself.

Walk into the site office on a job that is four months behind and you can usually tell within a minute whether anyone owned the programme. Either there is a baseline, approved and dated, with progress tracked against it and a file of correspondence tying each slip to a cause — or there is a bar chart somebody updated last quarter and a disagreement about whose fault it all is. The second site is going to lose that argument.

What the planning engineer job role covers day to day

The work splits into three layers, and only the first is what people picture.

The first is building the programme. That means breaking the scope into activities at a level that can actually be measured, sequencing them with real logic rather than dates typed in by hand, loading resources and durations that the site can defend, and getting the result approved as the baseline. An activity list with no logic between the bars is not a programme; it is a wish, and it collapses the first time anyone asks what the critical path is.

The second is measuring. Each cycle the planning engineer collects actual progress, updates the schedule, recalculates the critical path and float, and reports the variance. The useful output here is not the percentage complete. It is the explanation: which activities slipped, by how long, and what the cause was.

The third is the one that pays for the seat. Every cause of delay gets recorded at the time it happens, with the correspondence that supports it, so that months later the contractor can show which delays were his and which were the client’s. Drawings issued late, a site handed over in parts, a decision that took six weeks — none of these help you unless somebody wrote them down against the programme while they were happening.

Why the programme decides who pays for delay

This is where the role stops being administrative. An Indian construction contract typically gives the client liquidated damages for late completion and gives the contractor an extension of time where the delay was not his fault. Both of those turn on the same question: against what were we late, and why?

Without an approved baseline there is no credible answer. The contractor says the client’s drawings were late; the client says the work was slow anyway; and the party without dated records loses. The mechanics of that exposure — how the damages are capped, and why an extension of time is the real defence — are set out in liquidated damages in a construction contract.

The same records matter when payment stalls rather than time. A certified delay that sits on the client’s side of the line is what converts a stalled running bill into a claim with a basis, and the path that takes on government work is covered in contractor payment delay on government work.

Where planning sits against billing and execution

Three seats sit in the site office and owners routinely merge them on smaller jobs.

Seat Governs Primary document
Planning engineer Time Baseline programme and progress updates
Billing engineer / quantity surveyor Quantity and money Measurement book and the running account bill
Site engineer Execution Drawings, levels and the day’s work

The planning and billing seats feed each other. Progress claimed in a running bill has to be consistent with progress shown in the programme, and a mismatch between the two is the first thing a client’s engineer looks for when he wants to cut a bill. The quantity side of that chain, and the register it runs on, is explained in the measurement book in construction.

On a job small enough that one person does both, the risk is predictable: billing is urgent every month and planning is urgent only once, when the delay claim is finally made and the records are not there. If you are going to combine the seats, protect an hour a week for the programme update and treat it as unskippable.

Tools, and how much they matter

Primavera P6 is the default on large infrastructure, metro, highway and EPC contracts in India, and many tender documents name it. MS Project is common on building work and mid-size contracts. Excel still does the resource histograms and the cash-flow curve on most jobs.

Learn one scheduling tool properly rather than three badly, because what an employer is actually buying is your understanding of critical path logic, float, and the difference between a delay that moves the end date and one that eats slack. A planner who knows P6 menus but cannot explain why an activity has twelve days of float is not much use in a claim meeting, and that is the meeting the seat exists for.

The route into the seat, and what it pays

The usual entry is a civil engineering degree or diploma, two to four years on execution or billing, then a move across. That order matters. A programme written by somebody who has never sequenced a real pour, waited on a crane or watched a pile rig move tends to be internally consistent and practically wrong, and site teams stop believing it within a month.

On money, the planning seat sits in the same office band as billing and quantity surveying rather than execution, and the gap between the office band and the site band is the reason the crossover is the most common career move in Indian contracting. The current bands for the neighbouring roles are set out in what a quantity surveyor earns in India, with the execution side in what a site engineer earns and the rung below in what a site supervisor earns.

The bottom line

Judge a planning engineer by the evidence file, not the bar chart. The seat earns its cost on the day a job runs late and the contractor can show, with dated records against an approved baseline, which part of the delay was not his. Everything else the role does is in service of that one capability, and a contractor who treats planning as reporting rather than as claim preparation is paying for the chart and throwing away the protection.

Contractors building out a site office for the next project should size the work before the staffing. See which contracts are currently open for bidding, and if the job needs plant as well as people, what equipment finance costs against hiring it in.

Rates, schemes, specifications and prices change — confirm current terms with the OEM, dealer, bank or insurer before deciding. Pay bands and role boundaries vary by employer, contract type and region, and nothing here is legal or career advice.