The project charter is the most skipped document in manufacturing project management. Teams launch projects with a verbal approval, a shared email thread, or an entry in a spreadsheet tracker and call that enough. It rarely is.
I have seen capital projects stall halfway through because the sponsor changed and the new one did not agree with what the original had informally approved. I have seen scope grow by 40% with no formal decision point because nobody had defined what was in and what was out at the start. I have seen project managers spending their own money on small costs because nobody had formally given them budget authority.
Every one of those problems traces back to the same root cause: the project was never formally authorised. A project charter fixes that. It takes about two hours to write. The problems it prevents can cost weeks.
What a Project Charter Actually Is
A project charter is the document that formally authorises a project to exist. It gives the project manager the authority to use resources and spend budget. It tells everyone in the organisation what this project is, why it exists, what is in scope, and who is responsible for it.
It is not a project plan. It does not contain the WBS, the Gantt chart, or a detailed risk register. Those come later. The charter comes first, and it should be short enough that the sponsor will read it and sign it in one sitting.
A project charter that nobody reads is a bureaucratic exercise. Keep it to two pages. Every section should earn its place. If it does not help the sponsor make a decision, take it out.
The Eight Sections That Matter
There are eight things a project charter needs to contain for a manufacturing or NPI project. Everything else is optional. These eight are not.
Project Purpose
One paragraph. What are we building, changing, or improving, and why? If you cannot explain the project in four sentences, the scope is not clear enough to start.
Business Case
Why is this project worth doing now? Revenue opportunity, regulatory requirement, cost reduction target, or capacity need. Be specific. "To improve operations" is not a business case.
Scope Statement
What is included and, critically, what is explicitly excluded. The exclusions are as important as the inclusions. If it is not listed, it will eventually be assumed.
Objectives and Success Criteria
Three to five measurable statements of what done looks like. Not "deliver the product" but "achieve validated production output of 500 units per shift by Q4 2026."
Budget Envelope
An approved spending limit, not a detailed cost breakdown. The project manager needs to know what they have authority to spend before they can plan anything.
High-Level Timeline
Key milestones and the target completion date. Not a full schedule. Four to six major waypoints that the sponsor can hold the project accountable to.
Key Risks and Assumptions
The three to five things most likely to derail this project. Not a full risk register, that comes in Phase 2. Just the risks that are real enough to affect the decision to proceed.
Sponsor and PM Sign-Off
The sponsor's signature. Without it, the charter is a draft. With it, the project has formal authority. This is the whole point of the document.
The Section Most Teams Leave Out
The exclusions list is the section that most project charters in manufacturing are missing. And it is often the most valuable part.
Every project has things adjacent to it that people will naturally assume are included. A new production line project will attract assumptions about the training programme, the quality validation, the ERP integration. If none of those are explicitly called out as out of scope, they will creep in, each one arriving with a reasonable rationale and a confident expectation that the project team will deal with it.
Write a short exclusions list. Even four or five items. It forces the conversation about scope boundaries at the start, when it is cheap to have it, rather than six months in when it is expensive.
What the Business Case Needs to Be Specific About
The business case in a project charter does not need to be a full investment appraisal. But it does need to be specific enough that a decision can be made against it.
"To improve our manufacturing capabilities" is not a business case. It is a direction. A business case needs to answer: what problem are we solving, what happens if we do not solve it, and what does success look like in measurable terms?
| Weak Business Case | Stronger Version |
|---|---|
| To improve production throughput | Current throughput is 320 units per shift. Customer contract requires 500 by Q3. Gap is 180 units per shift. |
| To comply with new regulations | ISO 13485:2016 clause 7.3 requires documented design controls. Current process has no formal design history file. Audit finding risk is high. |
| To reduce costs | Current manual inspection process costs €180k per year in labour. Automated solution is estimated at €95k capital with €40k running cost. Payback in 18 months. |
| To improve quality | Defect rate is 3.2% against a target of 0.8%. Customer returns in Q1 cost €62k. Root cause traced to inconsistent operator setup, this project addresses that. |
Who Writes the Charter and Who Signs It
The project manager writes the charter, usually in collaboration with the sponsor. The sponsor provides the business case and the budget envelope. The project manager translates that into a structured document.
The sponsor signs it. Only the sponsor. A charter signed by the project manager alone is not a charter. It is a statement of intent with no organisational authority behind it. The sponsor's signature means the organisation is committing to this project: the budget is allocated, the resources are authorised, and the project has a mandate to proceed.
If the sponsor will not sign the charter, that is the most important information you have. It usually means the project does not have genuine organisational commitment yet. Better to find that out now than after the team has spent three months on it.
How Long Should a Project Charter Be?
Two pages for a standard NPI or capital project. Three at the absolute maximum. A charter that runs to ten pages is a project plan pretending to be a charter. Nobody will read it, and more importantly, nobody will sign it quickly enough for it to be useful.
The purpose of the charter is to get a formal decision. That requires a document that is clear, direct, and readable in ten minutes. If it takes longer than that, trim it until it does not.
When to Write the Charter
The charter should be written before any significant work begins. That means before the team is assembled, before suppliers are engaged, and before any budget is spent beyond the initial scoping conversation.
In practice, many teams write the charter after a certain amount of informal work has already happened. That is not ideal, but it is still worth doing. Even a charter written two weeks into a project is better than no charter at all, because it forces the scope and authority questions into the open at a point where the answers can still shape how the project runs.
Frequently Asked Questions
What is a project charter in manufacturing?
A project charter is the formal document that authorises a project to start. It names the sponsor, defines the scope, sets out the business case, allocates a budget envelope, and gives the project manager the authority to use resources. Without a signed charter, a project has no formal mandate and no reference point when scope, budget, or direction is disputed later.
What should a project charter include?
A project charter should include: the project purpose and business case, scope definition with explicit exclusions, key objectives and success criteria, a budget envelope, a high-level timeline, the project sponsor and manager names, key risks and assumptions, and a sponsor signature block. Anything longer than two pages is too long for a manufacturing or NPI project.
Who signs a project charter?
The project sponsor signs the charter. This is non-negotiable. A charter signed only by the project manager has no organisational authority. The sponsor's signature confirms that the organisation is committing the budget and resources the project requires, and gives the project manager a formal mandate to proceed.
What is the difference between a project charter and a project plan?
A project charter authorises the project to exist. A project plan describes how the work will be done. The charter comes first and is usually one to two pages. The project plan is created after the charter is approved and is a much more detailed working document covering the WBS, schedule, resource plan, and risk register.
Book a Discovery Call
See how Arcturus Pro structures project initiation, phase gate governance, and programme tracking for regulated manufacturing and med-tech teams in Ireland and Europe. A 30-minute call, no obligation.
Book a 30-Minute Discovery Call