Published 31 July 2026
The Delivery Lifecycle Model is already yours, free the moment you subscribe: four stages, Brief, Plan, Deliver, Close, built from 25+ years running agency delivery, not adapted from a textbook. That's the map, and it isn't going behind a paywall. What we're building now are the tools that make each stage easier to actually run. That's the Template Library.
Two types of thing live in it. Operational models are the bigger systems, how you run capacity, governance or leadership meetings across a whole delivery function. Templates are the individual documents you fill in and use on a specific project. You've already seen a taster of both on the homepage. This is the fuller picture, and the order it's shipping in.
You won't need every one on every project. A three-week internal piece of work doesn't need the same paperwork as a six-month client delivery. Mapping everything to a stage means you can see exactly what's available for the problem in front of you, and skip the rest.
Confirm scope, budget, timeline and stakeholders before anything starts.
In this stage: Project Discovery Brief, Stakeholder Map, Project Kickoff Deck, Scope Statement.
Where capacity, ownership and risk get made explicit.
In this stage: RAID Log, Capacity Planning System, Resource & Capacity Tracker, Governance & Role Clarity, RACI Matrix, Communication Plan, Meeting Cadence Planner, Risk Register.
Staying on track without the status updates turning into noise.
In this stage: Leadership Meeting Model, Status Report Template, Escalation Framework.
The stage most teams skip.
In this stage: Delivery Checklist, Sign-off template, Project Closure Report, Lessons Learned template.
Not tied to one stage: the Delivery Lifecycle Model itself, and a PM Onboarding Checklist for getting a new PM productive on a project that's already live.
Two pairs look similar but aren't duplicates: Capacity Planning System is the operational model for how your team plans capacity generally, the Resource & Capacity Tracker is the per-project document you fill in. Same pattern with Leadership Meeting Model and the Meeting Cadence Planner.
Most template libraries are a folder of fifty documents nobody opens twice. Ours is smaller on purpose. Every template exists because it maps to a specific point where projects actually go wrong, not because it pads out a package.
If there's a template you keep having to build from scratch on your own projects, tell us. That's exactly the kind of gap this library is for.
Want the frameworks that make delivery less chaotic, as they ship?
Join PM Hub