How to write a project charter (with an example)

A project charter is essential to determine whether the project gets started. It authorizes the project to become active and the project manager will need it before they can access the resources. This is everything you need to know in order to create the perfect project charter.

Project charter definition
The scope, objectives, as well as the people involved in the project are all laid out in a project charter. This formal document contains all the information necessary to authorize the project. The charter allows the project manager to use organizational and other resources to complete the project.
Can a project charter ever be changed?
The charter can be modified and updated just like any other project document. Sometimes, the charter is even required to meet the project objectives and Statement of Work.
Changes must be approved by the project initiator, sponsor or Change Control Board. Before a project manager proposes changes, they must consider their effect on the charter.
Time
Scope
Cost
Quality
Risques
Resources

How to create a project charter
These headers will help you build your charter to cover all the essential elements.
Introduction – This section explains the purpose of the project. This section includes the project name, brief description, and formal authorization.
Project business case, goals, and scope – This defines the scope of the project as well as any unique characteristics.
Success criteria are the key factors that will determine the success of a project. This is a list listing the deliverables that are expected upon project completion.
Deliverables – More detailed requirements for the primary project or key deliverables.
Budget – The cost estimate for the project. It also includes information about who can approve expenses. Any additional expenditures that the project may require.
Schedule/milestones: A comprehensive schedule that includes milestones or stages for measuring the project’s progress and success.
Constraints & assumptions – These are the known and unknown parameters of a project.
Summary of risks – a summary of any real or potential major threats to the project’s success.
Team and organization – List the stakeholders and people who will be working on the project (the team). Describe their roles and identify who is the project manager. A project team structure can be shown using an organization chart.
Approvals – Finally, a section is set aside for the project’s client/sponsor and stakeholders to record their approval or disapproval of the project charter document.
How to present a project chart
To ensure project approval, it is important to properly present the project charter. It is not enough to attach a slideshow or PDF to an email. However, you can do this after a formal presentation.
Make a slideshow and show your project charter to the client, sponsor, or other stakeholders during a meeting. Allow them to ask questions. It is a good idea for team leaders and other team members to be included in the presentation. Here are some presentation tips.
Prepare to adapt your presentation style to suit your audience.
Print out summary pages of the presentation on a single page.
Analyse your audience. Who are the technical and primary decision makers? What are their preferences? What do they think about the project?
Expect people to ask questions during the presentation and to talk. Be prepared to answer any questions before the end.
Maintain eye contact with your audience by using an open body language style. However, avoid excessive body and hand movements.
Do not read your presentation from notes in your hands.

Project charter example
Opportunity
The website is not optimized for mobile at the moment.
Goal
Redesign the website to make it more responsive and easier to place orders from mobile devices.
Objectives
Customer satisfaction can be increased
Mobile devices increase purchase completions
Improve user experience

Scope
Business Case
Make your website mobile-responsive
Mobile devices can increase business
Constraints
Assumptions
Attitudinality of users