Filled-In Examples of Project Management Documents
An empty template tells you the shape. A filled-in one tells you the level of detail. These are worked examples from a fictional but realistic delivery programme.
Business Case Example: A Filled-In Cost and Benefit Case over Three Years
A worked business case from a fictional platform replacement: eighteen cost and benefit lines over three years, with owners, assum
Change Request Log Example: Sixteen Filled-In Entries from a Billing Migration
A worked change request log from a fictional billing migration: sixteen entries with cost and schedule impact, decision, decider a
Cutover Plan Example: A Timed Sequence for an ERP Go-Live Weekend
A filled-in cutover plan from a fictional ERP go-live: 20 timed steps from freeze to first business day, with owners, dependencies
Dependency Tracker Example: Sixteen Live Dependencies on a Cloud Migration
A filled-in dependency tracker from a fictional cloud migration: 16 dependencies with provider, consumer, needed and committed dat
Go-Live Checklist Example: Filled In Two Days Before Go/No-Go
A filled-in go-live checklist from a fictional ERP release: 20 criteria across technical, data, business, operational and governan
Hypercare Plan Example: A Filled-In Plan for an ERP Go-Live
A worked hypercare plan from a fictional ERP go-live: cover by area and week, named leads, escalation routes, exit criteria and st
Project Closure Report Example: A Filled-In Closure Checklist from a CRM Replacement
A worked closure report from a fictional CRM replacement: sixteen closure items with owner, status, date and the evidence recorded
Project Status Report Example: One Week of an ERP Migration
A filled-in weekly project status report from a fictional ERP migration: RAG lines, milestones, decisions required and next period
RAID Log Example: A Filled-In Log from an ERP Migration
A filled-in RAID log from a fictional ERP migration: 17 entries across risks, assumptions, issues and dependencies, with notes on
Risk Register Example: Sixteen Scored Risks on a Cloud Migration
A filled-in risk register from a fictional cloud migration: 16 scored risks with owner, probability, impact, response, action and
Rollback Plan Example: A Filled-In Reverse Sequence for a WMS Release
A worked rollback plan from a fictional warehouse system release: sixteen timed reverse steps with owners, verification, triggers
Stakeholder Map Example: A Filled-In Map from an HR System Replacement
A filled-in stakeholder map from a fictional HR and payroll replacement: influence, interest, current and target stance, owner and