The PM Toolbox

A stakeholder register and communications plan checked: owners, overdue contact, and who the plan misses.

Supplier bids on the same footing: the same term, missing lines priced, and how narrowly the winner won.

A weighted scoring sheet: the ranking, what fits the budget, and how far a weight can move before it changes.

A Jira or Azure DevOps backlog checked for ready work: estimates, criteria, parents, sizes and duplicates.

Finished work's estimates against actuals: how far off, for which work, and a new estimate read through that.

The reserve a risk register really needs at 80% confidence, and why the expected value is not enough.

A work breakdown checked: codes that skip or repeat, the 100% rule as arithmetic, and oversized work packages.

Rules, not a chatbot: words nobody can test, TBDs, open-ended lists, and items with no acceptance criteria.

Demand against capacity by role and month, holidays and leave counted: the month the plan stops fitting.

Build or check a RACI matrix: one A per task, someone doing it, nobody carrying twice the load.

Hours of work to a finish date, with allocation, meetings, time off and holidays counted.

Finish dates, latest starts and working days between, and milestones that land on a holiday.

One task or a whole list, PERT and triangular side by side, and the total simulated honestly.

Long-lead items worked back from their need dates: what is late, what to order this week, what can wait.

Hours logged against the resource plan: unplanned work, starved assignments, and closed codes still charged.

A supplier's invoices against timesheets, the rate card and the contract, with the money to question.

A team's retro notes across sprints: what keeps coming back, how much it matters, and actions agreed twice.

A staffing plan and rates into cost by month on real working days, and the day the money runs out.

A go-live runbook checked: order, double-booked people, the outage window and whether rollback still fits.

Open a Primavera or Project file without the software, convert it, and pull a look-ahead.

Ranges on a real schedule, run through its logic: the chance of each date and what drives the finish.

Every project's assignments added up: who is booked past their hours, in which weeks, and on what.

Budget, actuals and commitments: a forecast that counts what is committed, and lines heading over early.

How long work takes, as percentiles, and which open items are older than most finished ones.

A risk register on its own matrix: counts per cell, inherent beside residual, and where the rankings disagree.

A RAID log read line by line: no owner, past due, untouched, duplicated, filed under the wrong letter.

The fourteen standard schedule checks on a Project or Primavera file, with every finding listed.

The critical path of a typed schedule or a Project or Primavera file, with float and a what-if.

One meeting priced in a line, or a whole calendar export with every recurring series counted.

A project's indicators across its reports: slow slides, sudden jumps, and green held over worsening numbers.

Each project's dependency log side by side: deliveries later than the need, and what only one side knows.

Several projects' status files into one summary, and where the files disagree about what a field means.

Whether a reported green, amber or red is supported by the numbers in the same report. Your rules, shown.

When the remaining work is likely done, or how much fits by a date, from the team's own throughput.

Approved change against the baseline, what is still waiting and for how long, and where change comes from.

Two versions of any register, matched by ID: closed, reopened, rescored, reassigned, and deleted while open.

Milestone forecasts over time: which dates keep moving, which never will arrive, how good forecasts were.

Two versions of a schedule: how far the finish moved, which path moved it, and why.

CPI, SPI and every estimate at completion side by side, with earned schedule over time.

A migration's source and target extracts, record by record: what is missing, extra, or changed on the way.

A lessons register across projects: the same lesson recorded again, themes, and lessons nobody will act on.

Benefits against the path from baseline to target, and the ones nobody can measure or two projects both claim.

Test runs and defects against your exit criteria, area by area, and when the rest would be done.

Requirements traced to tests: what has no test, tests that trace to nothing, and what changed after it passed.

A handoff or closure checklist checked: owners, acceptance, support, open issues and contracts still open.