Project charter

It is free to fill in online, needs no account, and downloads as a Word document or a PDF. See all IT and projects templates

• Project name

  For example: New customer portal

• Organisation

  For example: Brightwater Analytics

• Sponsor (who pays and decides)

  For example: Eleni Papadakis, Chief Executive

• Project manager

  For example: Priya Nair

• Date of the charter

  For example: 11 January 2027

• Why this project (the problem or chance)

  For example: Clients ask for the same reports every week by email, and our support team spends about 60 hours a month sending them. A self-service portal would save that time and give clients answers at any hour.

• Objectives and how success is measured

  One per line, each with a number or a date.

  For example: Launch the portal for all clients by 30 June 2027. Move 80 percent of report requests to self-service within three months of launch. Keep the client satisfaction score at 4.5 out of 5 or above.

• In scope

  For example: Sign-in for clients, a report library, a download button, a help page and the connection to our reporting system.

• Out of scope

  What the project will not do. This prevents arguments later.

  For example: A mobile app, changes to how reports are made, and the migration of data older than 2024.

• Main deliverables

  For example: A working portal, user guide, training for the support team and a launch plan.

• Milestones

  One line for each milestone, in order.

• Budget

  For example: EUR 85,000, including a 10 percent contingency

• Team and roles

  For example: Priya Nair, project manager Carlos Mendes, lead developer Aisha Khan, designer Daniel Costa, support lead (client voice)

• Main risks and assumptions

  For example: Risk: the reporting system's connection takes longer than planned. We will test it in the first month. Assumption: clients agree to sign in with their email.

• Other people to keep informed (optional)optional

  For example: Head of Sales, Data Protection Officer, the client advisory group

1. 11. Why this project
2. 22. Objectives and measures of success
3. 33. Scope
4. 44. Deliverables
5. 55. Milestones
6. 66. Budget
7. 77. Team and roles
8. 88. Risks and assumptions
9. 99. Authority and changes
10. 1010. Approval

1. 01

   Fill in

   Type your details in the form. The document fills itself in as you type; click any gap to jump to its field.

2. 02

   Check

   Read it through. Gaps you have not filled stay marked, so nothing goes out half done.

3. 03

   Download

   Save it as a Word document to edit further, or as a PDF to send or print.

What details does this template ask for?

The form asks for 15 details, starting with Project name, Organisation, Sponsor, Project manager, Date of the charter. 1 more are optional.

Can I download this template as Word or PDF?

Yes. When you have filled in the form, save it as a Word document to keep editing, or as a PDF to send or print. It is free and needs no account.

Is what I type sent anywhere?

No. What you type stays in your browser while you fill in the document. It only goes to nerix if you choose to open the template in the chat.

What should I check before I use this template?

A charter is an agreement, not a plan of every task. Keep it short, write the goal and the limits in words that everyone reads the same way, and get the sponsor's sign-off before work or spending begins. Change it in writing when the project changes.

Are these IT and project templates free?

Most are. Fill in and download them for free as Word or PDF, with no account. A few longer documents are premium: free to fill in, paid once to download, and marked with their price.

Does a security policy make us secure?

No document does that alone. A policy helps when it matches what people really do, so keep it short, explain it to your team and review it every year.

Is a project charter only for large projects?

No. A small project benefits too, because one page that names the goal, the limits and the decision maker prevents most arguments later.

• API integration specificationSpecify how two systems connect: what data moves, how it is secured, how errors are handled and who owns it.IT and projects
• Architecture decision recordRecord a technical decision with its context, options, reasons and consequences, for the team to find later.IT and projects
• Bring your own device policySet the rules for using personal phones and laptops for work: security, privacy, support and leaving.IT and projects
• Bug reportReport a software problem so a developer can repeat it, judge its impact and fix it.IT and projects
• Change management planPlan how people will be told, trained and supported through a big change, and how you will know it worked.IT and projects
• Change requestAsk for a change to a project or system, show its impact and record whether it is approved.IT and projects

See all IT and projects templates