The planner and the project manager
Last reviewed 16 September 202611 min read
Who owns the plan, who owns the dates, and what to do when the line gets crossed
🟩 In one line The project manager owns the plan — what will be built, in what order, with what resources. The planner owns the model of that plan and its arithmetic. The PM decides; the planner calculates and reports what the decision costs. Neither owns the dates: the dates are an output of logic the two of them agreed.
👤 Who this is for Planners in their first year, working out where their authority starts and stops. Mid-level planners being asked to change a duration they can't justify. Project managers who want a straight answer on what they should and shouldn't be asking the planner to do.
First, let's be honest about why this page exists
Because the single most common source of misery in a planning job is an unspoken disagreement about who decides what — and it almost never gets discussed until it goes wrong.
Two failure modes, and you will meet both:
The planner who thinks they own the dates. Refuses to change a duration because "the logic says so", treats every PM instruction as interference, and slowly becomes someone the team routes around. The programme ends up technically excellent and operationally ignored, which is worth nothing.
The planner who owns nothing. Changes whatever they're told, whenever they're told, with no record of who asked or why. Eighteen months later, the baseline has been quietly edited forty times, nobody can reconstruct what was submitted, and the planner is the person holding the file when the claim starts.
The line between those two is not a personality trait. It is a job design question with a clean answer, and the answer is easier to hold if you have said it out loud once, early, to the person you work for.
🟨 The standard — what "good" looks like
The project manager is accountable for delivery: scope, sequence strategy, resources, and the commitments made to the client. The planner is accountable for the integrity of the schedule model — that it faithfully represents what the PM and the team have decided, that its arithmetic is correct, and that what it reports is true.
A change to the plan is the PM's call. A change to the model that is not a change to the plan is a misrepresentation, and refusing it is the planner's job.
| Source | What it establishes |
|---|---|
| SCL Protocol, CP 1 and guidance §1.54–1.57 | The Contractor — not the Contract Administrator — controls the method and sequence of the works. Acceptance of a programme is not a warranty that it can be achieved. The decision sits with the delivery organisation; the programme records it. |
| SCL Protocol, guidance §1.59 | Every version of the programme must be saved separately and none overwritten, with a report describing revisions and the reasons for them. That requirement is what turns "who changed this" from an argument into a lookup. |
| GAO-16-89G, Best Practice 1 and 10 | The schedule should capture all the work and be maintained by someone accountable for its integrity, with changes controlled and documented. |
| AACE RP 11R-88 | Separates the planning and scheduling competency from the project management competency — they are different skill sets with different accountabilities. |
🟢 Rule: the PM can change the plan at any time and the planner models it without argument. The PM cannot change the arithmetic. If an instruction would make the schedule report something that isn't true — a duration nothing supports, a constraint that hides a slip, logic removed to flatter a date — the planner's answer is "I'll show you what that does to the finish date first", and the change gets a written reason attached to it.
How it actually works
The division, in practice
| Decision | Whose call | Planner's job |
|---|---|---|
| Build the podium before the tower, or in parallel | PM (with construction manager) | Model both, show the difference in weeks and peak manpower |
| Crew size assumed for blockwork | PM / section engineer | Record it, use it in the duration build-up, flag if the histogram says it can't be manned |
| Whether a duration is 12 days or 18 | PM decides, planner evidences | Show the quantity, the rate and the crew. If the PM picks 12 against a build-up saying 18, that's their call — and it gets written down |
| Whether the schedule shows negative float | Neither — it's an output | Report it and explain the cause. Do not remove it by hiding it |
| What the completion date is | Neither — the contract sets it, the logic forecasts against it | Report the forecast and the gap separately |
| Which revision is the baseline | PM / commercial, per the contract | Maintain it, protect it, refuse informal edits to it |
| What goes in the monthly narrative | Planner drafts, PM approves | Facts and driving path from the planner; commercial framing from the PM. Neither should overwrite the other's half |
| Whether to issue a delay notice | PM / commercial | Flag the trigger the moment the programme shows it. The planner is the early-warning system, not the decision-maker |
The sentence that resolves most of it
When a PM asks for a change that you're not comfortable with, the useful move is almost never to refuse. It is to convert the request into a decision with a visible price:
"I can do that. Before I do — it moves the finish to 12 August and it needs the blockwork gang at 22 rather than 14 in June. Still want it?"
Roughly half the time the answer is "no, leave it." The other half it's "yes", and now it's a decision on the record rather than an edit nobody remembers. Either outcome is better than a refusal, and both protect you.
What to do when the PM edits the file directly
It happens, particularly on smaller jobs where the PM has P6 access. The problem isn't the edit — it's that the schedule stops being reconstructable, and the person who suffers is whoever has to defend it in eighteen months.
The proportionate response, in order:
- Take the edit rights away quietly. One person writes to the live file. Everyone else gets a read-only copy or a layout. This is not a power move; it's version control, and every PM understands version control when it's framed that way.
- Run a schedule comparison every cycle against last month's archived file, and put the list of logic and duration changes in the narrative. Once changes are visible by default, undisclosed edits stop happening.
- Archive every submitted revision and never overwrite. SCL CP 1 requires it and it costs nothing.
Where the relationship actually breaks
Not over big disagreements. Over the slow ones — the duration shaved by two days each month because "we'll catch it up", none of which is individually worth a fight, all of which together mean the baseline no longer describes anything real. The defence is the same in every case: write down who asked and why, in the narrative, every time. Not as an accusation. As a record.
🟥 Where people go wrong
1. The planner treating the programme as theirs. It isn't. It belongs to the project and it describes the PM's plan. Your ownership is of its integrity, not its content. Planners who confuse the two get isolated, and an isolated planner cannot get progress out of anyone.
2. Refusing instead of pricing. "I can't do that" ends the conversation badly. "Here's what that costs" ends it with a decision. Same outcome when the answer is no, far better relationship.
3. Accepting a duration with no record of who chose it. The build-up says 18 days, the PM wants 12, the planner enters 12 and says nothing. Two years later the claim consultant asks where 12 came from and the only person who can be asked is the planner.
4. Letting the PM write the technical half of the narrative. The driving path, what moved and why, and the float position are factual. If those get softened into "progress continues in line with expectations", the document stops being a record and starts being a liability.
5. Escalating too early. Going over a PM's head on a two-day duration is a career-limiting way to be right. Escalate on things that change the outcome — baseline integrity, a missed notice trigger, a schedule being submitted that you believe is misleading. Not on preferences.
6. Escalating too late, or never. The mirror image, and more common. If you believe a submission misrepresents the position, say so in writing before it goes out. An email that says "I've submitted as instructed; my view is recorded here" takes four minutes and is the difference between being a witness and being a participant.
7. The PM using the planner as a typist. If the only instruction you ever get is "make it show X", the role has collapsed and the project has lost its early-warning system. That's worth one honest conversation, early, before it hardens.
⚖️ When you're challenged
"Just make the programme show the contract date." "I can get to that date three ways: change the sequence, add resource, or reduce scope. All three are real and I'll model whichever you want. What I can't do is shorten durations that nothing supports, because that becomes the baseline we're measured against for three years."
"Why do you need my sign-off? You're the planner." "Because it's your plan. I model it and I check the arithmetic. If I start deciding the sequence, you'll be held to a programme you never agreed — and neither of us wants that in month twenty."
"I've made a few changes in the file myself." "No problem — can you tell me which ones so they go in the narrative? Otherwise next month's comparison flags them as unexplained and the Consultant asks. Easier if we just say what we changed and why."
"That's too pessimistic. Take two days off each of these." "Two days each across eleven activities is twenty-two days off the forecast with no change to the work. If we're planning to recover twenty-two days, let's show how — extra gang, double shift, re-sequence — and I'll model that instead. Then it's a recovery plan rather than an assumption."
"You're being difficult about this." "I might be. But if I put this in and it's wrong, the person asked to explain it in a year is me, and the document that gets quoted is this one. Give me an hour to show you the alternative and if you still want the original I'll do it and note that you directed it."
📄 Related pages
- Planning vs scheduling vs project controls — the three job titles, and which one you actually hold
- How to become a planning engineer — the role, and the first ninety days
- Baseline approval and control — the thing the planner genuinely does own
- Justify a duration — how to price a request rather than refuse it
- Schedule narrative — the document where the record gets made
- P6 schedule comparison — how undisclosed edits become visible
- Notice requirements and records — what the planner has to flag, and to whom
✏️ Worked example
Month 14 of a 30-month hospital fit-out. The forecast has slipped to 22 days past the sectional date for the inpatient tower. The PM asks the planner to "tidy the programme up before the submission".
Three specific requests come out of the meeting. Here is what each one is, and what it deserves:
| The request | What it actually is | Response |
|---|---|---|
| "Re-sequence the ward fit-out to two floors in parallel instead of sequential" | A change to the plan. The PM's call, and a legitimate one | Model it. It recovers 9 days and pushes the finishing trades peak from 40 to 68. Report both numbers. |
| "Take the commissioning duration from 28 days to 20 — we did it in 20 on the last job" | A change to an assumption. Also the PM's call, but it needs a basis | "Happy to, if we can point at the last job. Send me the as-built and I'll cite it in the basis memorandum. Without that, 20 is an assertion and the Consultant will ask." |
| "Put a Finish On or Before on the sectional milestone so it stops showing late" | A change to what the schedule reports. Not the PM's call | "That won't stop it showing late — it'll show −22 as negative float instead of a late date, so it's actually more visible. If you want it invisible I'd have to use a Mandatory Finish, and that pins the milestone regardless of its predecessors. I'm not willing to submit that." |
The outcome. Requests one and two go in. Request three doesn't. The submission shows a forecast 13 days past the sectional date, with a recovery narrative describing the parallel-floor re-sequence and a commissioning duration cited to the previous project.
The line in the narrative that does the work:
"Inpatient tower forecast 13 wd beyond Sectional Date 2. Ward fit-out re-sequenced to two floors in parallel from Level 4 (recovers 9 wd; finishing-trades peak rises from 40 to 68 — subcontractor confirmation attached). Commissioning duration revised from 28 to 20 wd on the basis of as-built performance at [previous project], Appendix D. Remaining 13 wd is reported as a forecast overrun; no constraint has been applied to conceal it. Recovery options for the balance are at section 7."
Five sentences. It tells the client the truth, gives the PM credit for two real decisions, and leaves a record that protects both of them. That is the whole relationship working properly.
📖 References
- SCL, Delay and Disruption Protocol, 2nd ed. (February 2017) — Core Principle 1 and guidance §§1.54–1.64 on who controls method and sequence, programme acceptance, and version control
- US GAO, Schedule Assessment Guide (GAO-16-89G, 2015) — Best Practices 1 and 10, on schedule completeness and controlled maintenance
- AACE International RP 11R-88, Required Skills and Knowledge of Cost Engineering — planning and scheduling as a distinct competency
- PMI, Practice Standard for Scheduling, 3rd ed. (2019) — the schedule model, its components, and the discipline of maintaining it
From the field
Notes, corrections and additions from people who've done this on a real job. Everything is checked before it appears here.
Loading notes…
Checked before it appears. No client, project or employer names. Your name is shown; your email never is. Terms.