Intermediate project management is where most project-coordinator and junior-PM roles actually run. It is reading a schedule well enough to know what a slip actually does to the finish date, keeping a risk register that gets acted on instead of just written down, and running a communication plan that tells the right person the right thing instead of copying everyone on everything. It is genuinely useful — and it still assumes each of the five disciplines can mostly be handled on its own, one at a time.
What "Intermediate" Actually Covers
The centerpiece is the schedule: the critical path is the sequence of dependent tasks that sets the project's shortest possible duration, and a task on it has no float — slip it three days with nothing else adjusted, and the finish date slips by three days too. A task off the critical path has float, room to slip without moving the finish date, at least until that room runs out. You can also tell apart the two ways to compress a schedule: fast tracking, running normally-sequential tasks in parallel and accepting the added risk, versus crashing, adding people or resources to a task and accepting the added cost.
Alongside that: a risk register that actually functions, meaning each risk carries a probability, an impact, and a named individual accountable for watching it and triggering the response — not "the team," which in practice means no one. Mitigation means acting in advance to reduce the probability or the impact; it is different from acceptance (doing nothing, on purpose) and different from transfer (handing the exposure to a vendor or a third party).
And on the people and money side: a communication plan that defines who needs which information, how often, and through which channel — built around what decisions people are actually making with it, not a blanket weekly report sent to everyone regardless of use — plus budget variance, the tracked difference between what was planned to be spent and what actually has been.
Where It Breaks
- Assuming a task on the critical path carries its own hidden buffer, when by definition it does not — that is what makes it critical
- Responding to several sprints in a row of below-plan velocity by adding people or holding the original target, instead of re-baselining the plan against what the team has actually been delivering
- Sending the same detailed report to a stakeholder every week regardless of whether they use it for anything, rather than asking what decision it actually informs
- Rating a risk once at kickoff and never revisiting it, when the probability or impact can move as the project does
The pattern across all four: intermediate-level process is correct as long as nothing about the underlying situation changes. It starts to misfire the moment reality drifts from the plan — which is exactly the trade-off judgment the advanced tier is built around.
What to Put on a CV at This Level
"Schedule tracking and critical-path analysis, risk register maintenance, change control, stakeholder communication planning, budget variance tracking" is accurate, and it is what most "project coordinator" or "junior PM" postings are actually screening for.
What would overstate it: "risk management strategy" or "stakeholder management" implying ownership of the harder trade-off calls — deciding which risk gets the sponsor's attention, or which of two conflicting stakeholders wins — on the strength of running the mechanics alone. That judgment is the next tier's subject.
The Next Rung
Advanced project management is built around what happens when two or more of these five stop agreeing with each other at once — a project that is on budget but behind on deliverables, or a risk that is unlikely but would be catastrophic if it landed, or two stakeholders who each believe they have the final say.
The Project Management test scores schedule and risk as separate subscales across its 30 scenario questions in about six minutes, which is a fast way to see specifically whether a shaky score comes from the schedule mechanics or the risk-register discipline.
For the underlying skill of weighing one option against another correctly under a time limit, the Logical Reasoning test covers the more general version of what this tier is starting to apply to project decisions specifically.
Why This Tier Is Where Most Coordinator Roles Actually Sit
It is worth saying plainly: intermediate is not a consolation tier. Most day-to-day project-coordinator work runs entirely on tracking a schedule accurately, keeping a risk register current, and routing communication to the right people — without ever needing to adjudicate a genuine conflict between two of those disciplines, because most weeks nothing actually collides.
The honest reason to push into advanced is not that intermediate is insufficient — it is that any project running long enough eventually hits a week where the budget and the schedule tell different stories, and that week needs a different skill than tracking either one in isolation.