How to Write a Capital Project Charter

A capital project charter authorizes a regulated project and defines its objectives, scope, high-level requirements, governance, and success criteria — including the quality and regulatory expectations that must be built in from the start. It is where GxP intent enters a capital project before design begins.

1. 1

   Define objectives, scope, and business case

   State what the project will deliver, where its boundaries fall, and the business and regulatory drivers behind it. Boundaries are the part people skip and later argue about: name what is explicitly out of scope, including the adjacent systems, utilities and areas the project will touch but not deliver. A charter whose scope is only positive will absorb work by default, and in a regulated project the absorbed work is usually the interfaces — which is where qualification effort concentrates.

2. 2

   Capture high-level requirements including GxP

   Capture the requirements that constrain the design before anyone begins designing: the product and process the facility must support, the classifications required, the regulatory jurisdictions the site will supply, and the data and record expectations the automation must meet. These are high-level by nature, but they must be specific enough to be wrong. "GMP compliant" constrains nothing; "supports aseptic filling to Grade A with continuous viable and non-viable monitoring" constrains a great deal.

3. 3

   Define governance and roles

   Name the decision-makers, not the participants. Say who authorises scope changes, who approves design, who accepts systems at handover, and who has the authority to stop the project on a quality question — and make sure the last of those exists. Governance written as a list of stakeholders records who attends meetings; governance written as a set of authorities records who decides, which is what the project needs when the schedule and the design disagree.

4. 4

   Define success criteria and constraints

   Define what success means in terms that can be tested at the end, and state the constraints that bound it — budget, schedule, regulatory milestones, and the operational date the business is committing to. Include the quality criteria explicitly: a project delivered on time into an unqualified state has met a schedule and failed. Constraints recorded here are also what later justifies a scope decision that would otherwise look arbitrary.

5. 5

   Approve to authorize the project

   Approval is the act that authorises spending and commits the organisation, so the signatories should include quality as well as the business sponsor. This is the cheapest point at which quality expectations enter the project; every subsequent entry point costs more, and the ones that arrive at qualification arrive as change orders. A charter approved without quality participation is a business document that a regulated project will have to reconcile later.