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
| Section | What to write |
|---|---|
| Project name and ID | Short, unique name |
| Sponsor and project manager | Names and roles |
| Business problem or opportunity | Two or three sentences on why the project exists |
| Objectives and success measures | SMART objectives, with how success will be measured |
| Scope: in | High-level deliverables included |
| Scope: out | What is explicitly excluded |
| Key milestones | Five to eight dates with the approach (for example a phased go-live) |
| Budget and funding source | Estimate range and approval status |
| Assumptions and constraints | What you take as true and what limits the project |
| Top risks | The three to five biggest threats |
| Key stakeholders | Groups affected or with influence |
| Approval | Signature and date |
Full guidance: Project Charter and Project Initiation.
2. Stakeholder Register
| Name or group | Role | Interest in project | Power | Interest level | Current vs desired support | Engagement approach | Owner |
|---|---|---|---|---|---|---|---|
| Head of Operations | Receives the system | Needs stable run costs and support | High | High | Neutral to supportive | Monthly steering role; early input on handover | Project manager |
Update after every phase. See Stakeholder Identification and Analysis.
3. RAID Log
| ID | Type (Risk, Assumption, Issue, Dependency) | Description | Impact | Owner | Action and due date | Status |
|---|---|---|---|---|---|---|
| D-003 | Dependency | Network team must open firewall ports before integration testing | Testing delayed if late | Infrastructure lead | Request raised; needed by 10 Feb | Open |
| I-008 | Issue | Test environment down since Monday | Blocks two testers | Environment manager | Fix by Thursday; escalate if missed | Escalated |
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
| Section | Content |
|---|---|
| Header | Project, period, author, overall status (Red, Amber or Green) and trend |
| Summary | Two to three sentences in plain language |
| Status by dimension | Schedule, budget, scope, quality, risk with RAG and a one-line reason each |
| Achieved this period | Three to five outcomes, not activities |
| Planned next period | Key tasks and milestones |
| Top risks and issues | The most important three, with owner and action |
| Decisions and help needed | Specific asks, with who and by when |
| Key dates and budget | Next milestones; spent vs forecast |
Keep it to one page. See Project Communication Management and Project Health Checks, KPIs and Dashboards.
5. Change Request Form
| Field | What to write |
|---|---|
| Change ID and date raised | Unique reference |
| Raised by | Name and role |
| Description of the change | What is requested and why |
| Category | Scope, schedule, cost, quality, other |
| Business justification | Benefit or risk avoided |
| Impact analysis | Effect on scope, schedule, cost, quality, risks and resources |
| Options | Approve, reject, defer or modify, with consequences |
| Recommendation | Project manager’s view |
| Decision and approver | Approved, rejected or deferred; name; date |
| Baseline updates | Which documents were changed after approval |
See Scope Creep and Change Control.
6. Lessons Learned Register
| ID | Phase | What happened | Root cause | What worked or what to change | Recommendation | Owner for follow-up |
|---|---|---|---|---|---|---|
| L-004 | Testing | UAT started three weeks late | Test data not ready; no owner assigned | Assign a data owner at planning | Add test data readiness to the go-live checklist | PMO |
Add entries throughout the project, not just at the end. See Project Closure and Lessons Learned.
7. Go-Live Checklist Extract
| Area | Check | Owner | Status |
|---|---|---|---|
| Readiness | UAT signed off and no open critical defects | Test lead | Done |
| Operations | Support team trained and runbooks accepted | Service desk lead | In progress |
| Data | Final migration rehearsal reconciled | Data lead | Done |
| Communication | Users notified of downtime and new process | Project manager | Done |
| Rollback | Rollback steps tested and decision point agreed | Release manager | Done |
See Go-Live, Deployment and Cutover Planning.
Tips for Making Templates Work
- Put them where people already work, such as the project wiki or tool, so updates are quick.
- Review on a rhythm. RAID log weekly, stakeholder register at each phase, lessons register monthly.
- Limit the fields. If a field is regularly blank, remove it.
- Keep history. Version your documents so you can see what changed and when.
- 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.
- 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.