Free PRINCE2-style project templates
The core governance documents every structured project needs — written in plain English, ready to fill in. No email wall, no watermark, edit and reuse freely.
Each template includes guidance notes and, where useful, worked examples and built-in scoring formulas.
Project Brief
Enough definition to decide whether a project is worth starting: background, objectives, scope, outline business case, roles and known risks.
- 10 guided sections
- Scope in/out and constraints tables
- Tolerance table with escalation routes
Project Initiation Document (PID)
The contract between the project board and the project manager: what will be delivered, by whom, how it's controlled, and within what limits.
- Stage plan and organisation tables
- Quality, risk and communication approaches
- Controls, tolerances and tailoring
Business Case
The justification the board returns to at every stage boundary: options, measurable benefits, costs and the risks that could invalidate the case.
- Options table incl. "do nothing"
- Benefits with baselines and owners
- Costs and investment appraisal
Risk Register
Cause → event → effect risk descriptions with automatic probability × impact scoring, severity banding and colour-coding — the same 5×5 methodology Guddle uses.
- Score + severity formulas built in
- Response type and status dropdowns
- Worked example and how-to sheet
Lessons Log
Capture what went well and what didn't while everyone still remembers — and turn each lesson into a recommendation someone can act on next time.
- Went well / went badly / near miss
- Recommendation-first structure
- Worked example and how-to sheet
Have Guddle build it for you
Paste a plain-English brief and Guddle drafts the whole project — stages with dates and budgets, a scored risk register, starter tasks, the organisation and the business case — for you to review, edit and approve before anything is created.
Start free — first project on usA template is a snapshot. A project moves.
Documents drift out of date the day after you write them. In Guddle the PID, risk register and business case are living views of the project — always current, exportable to PDF whenever someone asks for "the document", and watched overnight by an analyst that flags the risks nobody has raised.
See how Guddle worksUsing these templates
What's the difference between the brief and the PID? The brief is written before the project is approved — just enough to decide whether to initiate. The PID is written once you're committed: fuller, and the baseline the board controls the project against.
How does the risk scoring work? Probability × impact, each on a 1–5 scale, giving a score out of 25. Scores of 15+ are treated as High and should be escalated; 8–14 are managed actively; below 8 are monitored. If your organisation has its own matrix, map each axis onto 1–5 and keep your descriptors in the risk description.
Do I need all five documents for a small project? No — that's what tailoring means. A small project might merge the business case into the brief and keep just the register and log as living documents. Keep the thinking, shrink the paperwork.