IT Project/Program Management
IT Project Manager Toolkit
An IT project manager toolkit: project charter, RAID log, decision log, status report, stakeholder map, cutover checklist, and hypercare plan.
Overview
A toolkit should reduce cognitive load, not add ceremony. Each item here exists because it answers a question a programme leader will be asked more than once.
Downloadable versions are being prepared. The descriptions below explain what each template contains and when to use it.
Practice 01
Start with a charter that settles the basics
The charter records the problem, the intended outcome, the scope boundary, the sponsor, and the constraints. It is short enough to be read and specific enough to resolve early disagreements.
We revisit it at phase gates. Scope that has changed without a recorded decision is a risk, not a detail.
Practice 02
Keep RAID and decisions close together
Risks, assumptions, issues, and dependencies belong in one active log with owners and next actions. Decisions are recorded separately, with the options considered and the rationale.
Both are reviewed in the same governance rhythm, which prevents decisions from being reopened without context.
Practice 03
Report status in a form leaders can use
A good status report is one page: outcomes since the last period, decisions required, risks that changed, and the next milestone. Red/amber/green is used only where the definition is agreed.
The report should be stable enough that readers notice when something is different.
Practice 04
Prepare for the moments that matter
Cutover checklists, readiness assessments, and hypercare plans are prepared before they are needed. Building them under pressure is how steps get missed.
Each checklist has an owner and a sign-off point, so completion means evidence rather than optimism.
From the field
Illustrative use
A newly appointed programme lead starts with the charter, the RAID log, and a one-page status format. Before the first steering meeting, the sponsor and lead agree what “amber” means and which decisions sit below the steering committee. The meeting is shorter, but more of it is spent on the choices that actually need senior attention.
Reference material
Documents and templates
Final documents will be published here when approved. Each placeholder describes the intended content so programme leaders can judge whether it will be useful.
Project Charter Template
A concise charter covering outcomes, scope, governance, and constraints. Document to be supplied.
Document to be supplied
RAID & Decision Log
A combined register with owners, triggers, and decision history. Workbook to be supplied.
Document to be supplied
One-Page Status Report
A leadership-ready status format built around decisions and outcomes. Document to be supplied.
Document to be supplied
Cutover Readiness Checklist
Evidence-based checks across data, testing, people, support, and rollback. Document to be supplied.
Document to be supplied
Downloadable files are being prepared for release. No links are published until final documents have been reviewed and approved.
Continue exploring
Related capabilities
03 Sample Project Plans
Reference plan structures for ERP assessments, implementation rollouts, and support transitions — ready to adapt.
Explore service
02 Best Practices
A practical set of delivery habits for governance, planning, risk, stakeholder alignment, and stabilisation.
Explore service
01 Lessons Learned from Various Local & Global Rollouts
Patterns that repeat across local and global rollouts — and the early decisions that change the outcome.
Explore service