Project Management Templates Pack: Charter, RAID Log, Status Report and Change Request

Good project managers do not reinvent documents for every project. They keep a small set of templates, adapt them and use them consistently. This lesson gathers the essential ones in one place: the project charter one-pager, stakeholder register, RAID log, status report, change request form, risk register extract and lessons learned register. Copy any of them into a spreadsheet or document, then tailor them to your organisation. Each has a short guide on how to fill it in, with links to the full lessons.

How to Use These Templates

  • Start small. Delete columns you will not maintain. A short log that is updated beats a perfect one that is not.
  • Use one owner per template and agree where it lives, so there is one version of the truth.
  • Follow your organisation’s standards. If a PMO provides official templates, use those and treat these as a checklist.

1. Project Charter One-Pager

SectionWhat to write
Project name and IDShort, unique name
Sponsor and project managerNames and roles
Business problem or opportunityTwo or three sentences on why the project exists
Objectives and success measuresSMART objectives, with how success will be measured
Scope: inHigh-level deliverables included
Scope: outWhat is explicitly excluded
Key milestonesFive to eight dates with the approach (for example a phased go-live)
Budget and funding sourceEstimate range and approval status
Assumptions and constraintsWhat you take as true and what limits the project
Top risksThe three to five biggest threats
Key stakeholdersGroups affected or with influence
ApprovalSignature and date

Full guidance: Project Charter and Project Initiation.

2. Stakeholder Register

Name or groupRoleInterest in projectPowerInterest levelCurrent vs desired supportEngagement approachOwner
Head of OperationsReceives the systemNeeds stable run costs and supportHighHighNeutral to supportiveMonthly steering role; early input on handoverProject manager

Update after every phase. See Stakeholder Identification and Analysis.

3. RAID Log

IDType (Risk, Assumption, Issue, Dependency)DescriptionImpactOwnerAction and due dateStatus
D-003DependencyNetwork team must open firewall ports before integration testingTesting delayed if lateInfrastructure leadRequest raised; needed by 10 FebOpen
I-008IssueTest environment down since MondayBlocks two testersEnvironment managerFix by Thursday; escalate if missedEscalated

Review it in every weekly meeting and close items promptly. See RAID Logs, Issues and Dependencies and Project Risk Management for the fuller risk register with probability, impact and triggers.

4. Weekly Status Report

SectionContent
HeaderProject, period, author, overall status (Red, Amber or Green) and trend
SummaryTwo to three sentences in plain language
Status by dimensionSchedule, budget, scope, quality, risk with RAG and a one-line reason each
Achieved this periodThree to five outcomes, not activities
Planned next periodKey tasks and milestones
Top risks and issuesThe most important three, with owner and action
Decisions and help neededSpecific asks, with who and by when
Key dates and budgetNext milestones; spent vs forecast

Keep it to one page. See Project Communication Management and Project Health Checks, KPIs and Dashboards.

5. Change Request Form

FieldWhat to write
Change ID and date raisedUnique reference
Raised byName and role
Description of the changeWhat is requested and why
CategoryScope, schedule, cost, quality, other
Business justificationBenefit or risk avoided
Impact analysisEffect on scope, schedule, cost, quality, risks and resources
OptionsApprove, reject, defer or modify, with consequences
RecommendationProject manager’s view
Decision and approverApproved, rejected or deferred; name; date
Baseline updatesWhich documents were changed after approval

See Scope Creep and Change Control.

6. Lessons Learned Register

IDPhaseWhat happenedRoot causeWhat worked or what to changeRecommendationOwner for follow-up
L-004TestingUAT started three weeks lateTest data not ready; no owner assignedAssign a data owner at planningAdd test data readiness to the go-live checklistPMO

Add entries throughout the project, not just at the end. See Project Closure and Lessons Learned.

7. Go-Live Checklist Extract

AreaCheckOwnerStatus
ReadinessUAT signed off and no open critical defectsTest leadDone
OperationsSupport team trained and runbooks acceptedService desk leadIn progress
DataFinal migration rehearsal reconciledData leadDone
CommunicationUsers notified of downtime and new processProject managerDone
RollbackRollback steps tested and decision point agreedRelease managerDone

See Go-Live, Deployment and Cutover Planning.

Tips for Making Templates Work

  1. Put them where people already work, such as the project wiki or tool, so updates are quick.
  2. Review on a rhythm. RAID log weekly, stakeholder register at each phase, lessons register monthly.
  3. Limit the fields. If a field is regularly blank, remove it.
  4. Keep history. Version your documents so you can see what changed and when.
  5. Improve the template after each project based on what you actually used.

Common Mistakes

  • Filling in every field of a heavy template for a small project.
  • Creating documents to satisfy a process rather than to support decisions.
  • Letting logs go stale so nobody trusts them.
  • Keeping multiple versions of the same register in different places.
Key takeaways
  • A small set of well-used templates beats a large set of neglected ones.
  • The core set: charter, stakeholder register, RAID log, status report, change request, lessons register and go-live checklist.
  • Tailor to project size and your organisation’s standards.
  • Keep one owner, one location and a regular review rhythm for each template.

Related Lessons