Evidence-backed project mobilisation
Turn agreed project evidence into a charter ready for approval
Reqify generates a clean charter from the approved business case and discovery files: vision, objectives, scope, stakeholders, RACI, milestones, governance, and a high-level risk summary.
- PMBOK-aligned
- Stakeholder register included
- High-level milestones
- Charter + RACI
A weak charter is a slow approval
The project charter is the artefact that converts an approved investment into an authorised project. Done well, it gets signed at the kickoff steering meeting. Done poorly, it triggers a fortnight of back-and-forth on scope, sponsor, and authority — by which point momentum is lost and someone is already escalating about the wrong constraint.
Most charter templates are exhaustive enough to be boring and short enough to be useless. The hard part is calibrating depth: enough governance and constraint to be authoritative, short enough for an executive to read in ten minutes.
Generic AI document tools either pad the charter into a 30-page brick or strip it to bullet points. Neither passes a steering review.
How Reqify produces a kickoff-ready charter
Reqify reads the approved business case (or discovery files if no business case exists) and emits a PMBOK-aligned project charter: project vision, SMART objectives, scope and explicit out-of-scope items, success criteria with measurement, high-level milestones, project sponsor and steering committee, RACI for the core team, high-level risk summary (drawn from the RAID log when present), assumptions, constraints, and budget envelope.
The depth is calibrated for executive review: long enough to be authoritative, short enough to be read end-to-end. When a number cannot be derived — budget envelope without finance sign-off, target go-live without sponsor approval — Reqify flags it as awaiting decision rather than guessing.
The charter cross-references other Reqify artefacts directly: the business case, the RAID log, the stakeholder register. One source of truth across the kickoff pack.
What ships in the charter
Vision + SMART objectives
Concise project vision plus measurable objectives, each tied back to the business case driver.
Scope and out-of-scope
Explicit in-scope and explicit out-of-scope items — the latter is what stops scope creep at week three.
Sponsor + RACI
Named project sponsor, steering committee composition, and a RACI for the core team.
High-level milestones
Phase-level milestones with target dates. Not a Gantt chart — the right level for charter approval.
High-level risk summary
Top risks from the RAID log surfaced in the charter with mitigation references — no duplication.
Assumptions and constraints
Explicit assumptions and constraints (budget, time, regulatory) called out so the authorising authority sees them.
Project charter FAQ
Is this PMBOK-aligned?+
Yes. The structure matches PMBOK 7 guidance for project charters: project purpose, measurable objectives, high-level requirements, assumptions, constraints, scope description, milestones, budget summary, key stakeholders, sponsor, and approval criteria. PRINCE2 vocabulary is supported as an alternative.
Does the charter cross-reference the business case?+
Yes — each objective cites the driver from the approved business case. Top risks reference the RAID log entries. The stakeholder register is one source. No duplication across documents.
How long is the output?+
Calibrated for executive review: typically 6–12 pages including the RACI and milestone view. Not a 30-page brick.
Can I generate the charter before the business case?+
Yes, but the quality is better with an approved business case as input. Without one, Reqify generates a draft charter and flags the sections that should be confirmed against a formal investment decision.
Can I export to Word?+
Yes — one-click .docx with formatting and a table of contents. PDF export too.
Sign the charter at kickoff, not three meetings later
A charter calibrated for executive review, with the right level of detail and no fabricated content.