Project charter, warehouse management system rollout, Kestrel Distribution
Project charter template with the scope in and out on one page
A charter exists so that a project starts with a sponsor's signature on a page that says what it is and is not. This one fits a system rollout on three pages: a measurable objective, scope in and out as two lists side by side, the team with their authority, a $341,000 budget, five milestones on a timeline and the five risks worth naming on day one.
The document, page by page
Every page as it renders and as it prints, with nothing summarised. Read the wording before you reuse it.
Section by section
What each section is for, so you can keep the ones you need and drop the rest.
- Header block
- Project name, code WMS-01, sponsor, lead, date approved and version 1.0.
- Purpose and objective
- The problem in two sentences, then the objective as two numbers with a date.
- Scope
- Six things in and four things out, as two lists side by side.
- Deliverables
- Five deliverables, each with a measurable acceptance test.
- Team and authority
- Five roles with names and what each may decide, in dollars.
- Budget
- Six lines with 10 percent contingency, totalling $341,000.
- Milestones
- Five dates on a timeline, from approval to the benefits review.
- Risks
- Five day one risks with likelihood, impact, owner and response.
- Success criteria
- Three measures with targets and the date each is measured.
- Assumptions and constraints
- Four lines the approval depends on, including the spend cap.
- Approval
- Sponsor and project lead sign side by side, with dates.
Clauses in this document
Charter versus plan versus business case
Three documents get confused at the start of a project, and each has one job. The business case argues the project should exist: options, benefits, costs, judged by whoever owns the money. The charter, this document, authorises it: the objective, the scope boundary, the budget cap, the named authority, signed by the sponsor once. The plan schedules it: tasks, dependencies, dates, owned by the project lead and rewritten as often as reality demands. A plan without a charter is a schedule for work nobody has authorised. Write the case to win the money, the charter to fix the deal, the plan to run the weeks.
How to adapt this document
For an internal process improvement with no vendor, drop the vendor row from the team table, let the budget shrink to backfill and training, and keep the authority column, because internal projects suffer most from nobody knowing who decides. For a construction project, make the signed contract a deliverable with its own acceptance row, and move the milestones to practical completion stages. For a research project, put ethics approval on the timeline before any data collection, and write the success criteria as review gates. In every variant the skeleton holds: one measurable objective, scope in and out side by side, authority with a dollar figure, a sponsor signature.
What makes this document work
The objective is two numbers with a date
Pick error rate from 1.8 percent to under 0.5 percent, and dispatch time from 41 to 25 minutes, within three months of go live. Because the objective is written as numbers with a deadline, the benefits review on 30 June 2027 is a real meeting with a pass or fail, not a discussion about how everyone feels the rollout went.
Scope in and out sit side by side
The scope section is two lists on one page: six things in, four things out. The out column names exactly what people would otherwise assume is included, the third depot, returns, fleet telematics. This is the only part of a charter anyone re-reads mid project, and here it can be read in ten seconds without hunting through prose.
The authority column carries a dollar figure
The team table does not just name people, it says the sponsor approves changes over $10,000 and the project lead decides below that alone. That number is the change control rule, sitting on page two where every argument about who approves what gets settled by pointing at it.
Questions people ask
What is the difference between a project charter and a project plan?
The charter authorises; the plan schedules. A charter is signed once by the sponsor and says what the project is, what it may spend and who decides things. The plan is the working schedule of tasks and dates that changes weekly underneath it. This example stays at charter altitude: milestones, not tasks.
Who signs a project charter?
The sponsor, because the charter is the sponsor's authority to spend handed to the project, and the project lead, because they are accepting delivery on those terms. This example ends with both blocks side by side. Nobody else signs; everyone else appears in the team table with their authority instead.
How long should a project charter be?
Two to four pages. Shorter and it will not survive its first argument, because the scope and authority detail is missing; longer and it has become the project plan wearing the wrong name. This example lands on three pages of tables, lists and short paragraphs.
What goes in the out of scope list?
The things people will assume are in unless told otherwise. Here that is the third depot, finance integration beyond invoicing, returns and fleet telematics. Writing them down at approval is far cheaper than debating them once the budget is half spent.
Should the budget be in the charter?
Yes, at summary level with contingency shown, because the sponsor is authorising the spend and the number needs to sit on the signed page. This example carries six lines totalling $341,000 with 10 percent contingency. The cost breakdown by month belongs in the plan, not here.
When is a project charter updated?
Only through change control, and as a new version rather than an edit, which is why this one carries version 1.0 in its running header. If scope or budget moves beyond the authority in the team table, the sponsor approves a version 1.1, so there is always exactly one signed truth.
Build your own in about a minute
The button below opens the generator with this use case already described. Change the wording to match your own, generate, then edit anything you like.
Make my project charter template with the scope in and out on one pageOther document examples
Project status report template with a RAG status
Month four of the Kingsway Street office fit out. The report opens Amber, nine days behind and 61 per cent complete, with a forecast cost of $2.41M against a $2.35M budget, and the first sentence names the cause: asbestos sheeting found behind walls during demolition. Five pages carry progress by work package, a budget table, a spend chart, five risks and three decisions the sponsor has to make.
Capability statement template with past performance in numbers
A capability statement is read by a procurement officer with forty of them, in about ninety seconds, looking for the numbers that let them shortlist. This one is four pages for a cleaning company chasing council work: the six number snapshot up front, three past contracts with values and outcomes, and the certifications and insurances in a table they can check.
Risk register template that works as a monthly meeting document
A risk register is a spreadsheet until someone has to read it out at a meeting, and then it needs a scale, a matrix, owners and a summary of what changed. This one defines its five point scales on page one, rates twelve risks in a table, charts the top five and lists the three that moved since last month.
Want the steps in the builder? Read Create a document with AI, then Document builder components. For everything this generator can do, see the document maker.
Written and checked by the OneCraft team. Last checked .