Skip to content
PCR
Tailor controls

Guided flow

Move from project theory to the next sensible action.

Each step gives you the minimum action, related templates, related tools, and common mistakes to avoid.

Tailor this project Browse templates

Shape the idea before it becomes a project

Turn an interesting idea into a clear project candidate with an outcome, sponsor, constraints, and first decision point.

Minimum sensible action

Write a one-page brief covering outcome, owner, users affected, rough scale, known constraints, and the next approval needed.

Why it matters

Weak starts create expensive control problems later. This step keeps the conversation focused on value and decision ownership.

Next actions

  • • Confirm sponsor accountability
  • • Name the first decision forum
  • • Run the project diagnostic

Related tools

  • • Project Diagnostic
  • • What To Do Next flow

Common mistakes

  • • Starting delivery before the sponsor can define success
  • • Confusing a preferred solution with the business outcome
Project BriefBusiness Case Lite

Choose the lightest control model that will still protect the project

Set governance, reporting, artefacts, and tolerances based on risk and complexity rather than habit.

Minimum sensible action

Select Lite, Standard, Enhanced, or Recovery control and record the reason.

Why it matters

Tailoring prevents both under-control and performative bureaucracy.

Next actions

  • • Complete the tailoring recommender
  • • Agree reporting cadence
  • • Choose required artefacts

Related tools

  • • Tailoring Recommender
  • • Template Selector

Common mistakes

  • • Using the full template set for a low-risk project
  • • Skipping tolerances because the project is moving fast
PID LiteGovernance CalendarHighlight Report

Create the initiation baseline

Bring scope, products, acceptance criteria, delivery approach, risks, roles, and controls into one agreed baseline.

Minimum sensible action

Create a PID Lite with outcome, scope boundaries, product list, milestones, controls, RAID setup, and approval record.

Why it matters

The baseline gives the PM a fair reference point for control, change, reporting, and escalation.

Next actions

  • • Define project products
  • • Set tolerances
  • • Open RAID and decision logs

Related tools

  • • Template Selector
  • • RAID Log
  • • Decision Log

Common mistakes

  • • Writing a long PID nobody can operate from
  • • Missing acceptance criteria for key products
PID LiteProject Product DescriptionRAID LogDecision Log

Control the current stage week by week

Run a weekly rhythm that tracks progress, risks, issues, decisions, benefits, changes, and reporting due.

Minimum sensible action

Review milestones, RAID, decisions, change pressure, next report, and any tolerance threats.

Why it matters

Control is a cadence, not a document. Weekly review makes exceptions visible early enough to act.

Next actions

  • • Open the weekly control room
  • • Prepare highlight report
  • • Escalate exceptions quickly

Related tools

  • • Weekly Control Room
  • • Highlight Report Builder
  • • Project Health Check

Common mistakes

  • • Reporting green while decisions are blocked
  • • Treating risks, issues, and changes as separate conversations
Stage PlanHighlight ReportException ReportChange Request

Review the stage boundary before continuing

Assess whether the project remains viable, whether the plan still holds, and what the next stage should control.

Minimum sensible action

Compare actuals to tolerances, update business case, summarise lessons, and present the next stage plan.

Why it matters

Boundaries are where sponsors make active continuation decisions rather than drifting into the next tranche of work.

Next actions

  • • Reforecast cost and time
  • • Update benefits confidence
  • • Ask for continue, pause, reset, or close decision

Related tools

  • • Project Health Check
  • • Decision Log

Common mistakes

  • • Treating the boundary as a reporting ritual
  • • Not giving the sponsor a real decision
Stage Boundary PackBusiness Case LiteStage PlanLessons Log

Recover, reset, or close cleanly

Decide whether the project needs recovery control, a reset baseline, or orderly closure.

Minimum sensible action

Run a recovery triage or closure check, then capture decisions, lessons, benefits ownership, and remaining actions.

Why it matters

Troubled projects need fewer assumptions and sharper controls. Finished projects need evidence, lessons, and ownership transfer.

Next actions

  • • Triage viability
  • • Reset controls or close
  • • Confirm benefits owner

Related tools

  • • Recovery Triage
  • • Project Health Check

Common mistakes

  • • Recovering without changing governance
  • • Closing before operational ownership is accepted
Recovery Reset PlanClosure ReportBenefits ProfileLessons Log