Microsoft Project alternative for project charter
In Microsoft Project you plan time, cost and resources, while the business case for a project is recorded separately, usually in a Word or Excel file with a line for the sponsor’s signature. Such a document is current on the day of approval and drifts away from the schedule in the weeks that follow. In a Microsoft Project alternative for project charter work the charter is part of the system: it has a configurable template, data taken from the project, an approval path and a history of approved versions. To stay useful after the kick-off, a charter has to meet eight requirements: a configurable template, templates for project categories, data from the project, out-of-scope entries, success indicators, an approval path, versions, and data that shows up in reports. FlexiProject covers them in its project charters module.
Key takeaways:
- Microsoft Project has no charter with versions and approval. The document is created outside the system, most often in Word or in an app built on the Power Platform.
- A text file does not pull data from the project. Milestones and risks typed in by hand go stale after the first changes to the schedule.
- One template does not fit every project. Investments, IT rollouts and marketing campaigns need different fields and different decision makers.
- An approval path replaces signatures on a printout. Stages, named decision makers and recorded justifications leave a trail that a mailbox does not.
- Charter versions show how the assumptions changed. Every approved version stays saved in the project and can be reopened.
In Microsoft Project the project charter ends up in a separate file
In Microsoft Project you plan time, cost and resource allocation. The business case, the success criteria and the sponsor’s decision are recorded in a separate document. In the server edition you can configure a form on the project detail page and approve a project at each lifecycle stage in a workflow, but neither produces a versioned charter that is approved as a document.
A charter in Word or Excel sits next to the plan file
Teams using Microsoft Project usually keep the charter as a Word or Excel file next to the plan file. Template libraries suggest the same format and recommend keeping the charter to one or two pages with a line for the sponsor’s signature. That is enough for a single document. The charter is then static, however, and the problems show up later in delivery.
An app on the Power Platform needs its own implementation
Organisations that want to store charters in Microsoft 365 sometimes build their own app on SharePoint and the Power Platform. Such a solution has to be designed, built and maintained, so it needs an owner, developer time and ongoing maintenance costs.
During delivery the charter stops matching the plan
The charter is approved and the project starts. Over time milestones shift, the budget is refined and new risks appear in the register. Nobody updates a signed file, so it keeps the assumptions from initiation. Later versions travel by email, and after a while nobody knows which one the sponsor accepted.
The charter then stops being a reference point. When someone asks to extend the scope, there is no approved record of what was agreed to base the assessment on.
Create your Project Charter in FlexiProject. Get 30 days of full, free access to all features.

A charter stays useful after the kick-off when it meets eight requirements
Eight functional requirements decide whether a charter is still useful once the project has started.
| Why it matters | Effect on daily work | |
| A configurable template | Reflects the standard adopted in the organisation | The PMO arranges sections and fields in a builder, without a developer |
| Templates per project category | Match the document to the type of work | An investment charter and a marketing charter have different fields |
| Data from the project | Keeps the charter consistent with the plan | Milestones, risks and dates come from the schedule, the risk register and the budget |
| Out-of-scope entries | Define the boundary of the project | An approved exclusion answers a request to extend the scope |
| Success indicators | Make the goal measurable | A table with a starting and a target value; after the project you add the values achieved |
| An electronic approval path | Formalises the approval | Notifications, recorded decisions and written justifications |
| Charter versions | Record how the assumptions changed | Every approved version stays on the list of charters in the project |
| Charter data in lists and reports | Allow projects to be compared | Attributes such as category and sponsor, and the budget, can be filtered in the project list and in reports |
The schedule moves to FlexiProject in an .mpp file with its tasks, dependencies, assigned resources, effort, working days and baselines, so the differences concern the documents around the plan. The full feature comparison of the two systems is on the page Microsoft Project alternative.
The PMO builds the charter template in a builder, without a developer
In FlexiProject a charter is created from a template. Templates are in the main menu, under Project charters. The layout is assembled in the builder from ready elements: sections, two-column rows, text fields, lists, dates, numbers, tables and attachments, plus fields with project, schedule, budget, risk and product data.
Templates are looked after by the project management office, and preparing them needs no developer. In FlexiProject you recreate the existing charter template in the builder and keep it after the change of tool, instead of adapting to a ready-made layout.
A template can be cloned, renamed or deleted. Charters created from a deleted template stay in their projects with all their content.

Each project category can have its own charter template
In a single form, R&D, investment, HR, marketing and IT projects share the same set of fields. Each category then fills in sections that do not apply to it and omits the matters that decide the case.
In FlexiProject you create any number of charter templates and assign them to workspaces. Here are example variants an organisation can save as a project charter template:
- Investments. Fields for CAPEX and OPEX, payback period, technical specification and a list of key suppliers.
- Marketing. Target audience, communication channels, campaign budget, and reach and conversion metrics.
- Renewable energy. Rated power, location, area, main investor and expected annual energy yield.
A production division and a sales division can keep their own charters, while a shared set of fields, such as project data and attributes, placed in every template keeps the charters comparable across the company.
The charter takes data from the schedule, risks and budget
Retyping data by hand takes time and leads to discrepancies. In FlexiProject the charter fields fill in from the project: lists of milestones, tasks, risks and products, costs and revenues, and dates, progress and planned values from the schedule, the budget and the risk register.
Company procedure often requires the most significant risks to be shown on the charter. Where the register and the charter are separate documents, the data has to be retyped and checked for consistency all the time. A field pulled from the register needs neither.
Fields taken from the schedule, budget, risks and products fill in from the system. While the charter is a draft they show the current project data, and once it is sent for approval they keep the data as at that moment. Fields with project data, such as the name, status, manager and attributes, are edited in the charter, and the change goes straight to the project.

Define project goals with a Project Charter in FlexiProject. Try it free for 30 days.

Out-of-scope entries are written in the charter and approved by the sponsor
The definition of scope tells the team what the project is to deliver. During delivery what the project explicitly does not cover turns out to matter just as much. Without a clear boundary new requirements appear gradually, and each of them looks justified on its own.
In the charter template you can add a text field called “Out of scope”. The entry becomes part of the charter, which the approval path approves, and an approved charter is read-only. When an extension is proposed later, you point to the entry in the approved charter. A change of scope is submitted as a plan change with a description, the alternatives considered and a justification, and it goes through the approval path.
Success indicators go into the charter and the results into the closure card
A goal without a specific numerical value does not allow an objective assessment. Optimising a logistics process with a 5% cost reduction and the same optimisation with a 20% reduction are two different projects, requiring a different approach and a different budget.
The charter template can include a table of success indicators with columns set by the administrator, for example the indicator, the starting value and the target value. An approved charter shows the data as at the moment it was sent for approval.
The settlement happens once the project ends. A closure card is built from a project document template and can contain the achieved values next to the planned ones, the deviations in schedule and budget, the risks and the lessons learned. An approved document stays in its project with the approval history.
An approval path replaces signatures on a printout
In many organisations approving a charter requires a printout and a round of signatures, or an exchange of emails in which the only trace of the decision is a mailbox.
Project approval software replaces such an exchange. In FlexiProject you fill in the charter, choose a path and submit the charter for approval, optionally together with the schedule and budget sections. The charter changes status from draft to “In approval”. The decision makers at the first stage receive a notification in the application and, if the setting is on, an email. Each of them records a decision: approve, send back for correction or reject, and can add a comment. You can also submit the charter without a path, by leaving that field empty. The charter is then approved at once.
A path can have any number of stages, which the charter passes through in order. A decision maker can be a specific person, a project role, the project manager or the line manager of the person submitting, and FlexiProject identifies the person holding the role at the moment of submission. For an approver you can also choose an opinion instead of a decision: a person giving an opinion does not close the stage.
Different decisions can follow different paths, because you choose the path when you submit a charter or a plan change. A single stage can name several decision makers, for example the sponsor (business), the CFO (financial), the compliance department (legal) and the technology director (technical), and you set whether all of them must decide or one is enough.

Start with a Project Charter in FlexiProject – 30 days free, with full access to all features!

Charter versions keep the history of approvals
Approving the charter does not end the management of assumptions. Scope grows, budgets are corrected and dates shift. A static file cannot reflect those changes, so it quickly goes out of date.
FlexiProject lets you create and approve many charter versions. A new version is a draft with the values copied from the previous one, while the approved version stays read-only. A change to an approved plan is submitted as a plan change that covers the schedule, the budget and, if needed, the charter. It can go through the same approval path as the first plan, and the sponsor sees the planned and requested end date and the budget with the difference before deciding.
The approval history shows who made the decision, when and with what comment. You export the charter to PDF in two variants: the content alone, or the content with the approval history, when you need a formal copy outside the system.
The charter is linked to the plan, the roles and the reports of the project
A charter filled in only to satisfy a procedure quickly loses its substantive value.
When the charter is linked to the schedule, the risk register and the budget, it plays a different role. Milestones, risks and budget come into it from those modules, and you choose the approval path when you submit it. The project roles named in the charter, such as the sponsor, can act as approvers in the path. A carefully completed charter gives the project the right assumptions from the start.
Idea cards, project charters and closure cards are kept in one place in the project. Project attributes such as category and sponsor, and the budget, can be filtered in the project list and in reports, so finding every project in a given category, sponsored by a specific person or above a budget threshold takes a moment. Organisations that collect ideas before a full charter can use an initiative card with scoring, a shorter form for early assessment.
Test a Microsoft Project alternative for project charter on your own project in two weeks
A feature comparison does not replace checking in practice. Do it on one live project, preferably one whose schedule has already shifted.
- Reproduce the template. Move the charter form your organisation uses today into the template builder. Reproducing the sections and fields shows whether the standard survives the change of tool.
- Create the charter. Start a charter for the project and let the milestones and risks fill in from the plan. Enter the business case and the out-of-scope entries in the charter’s text fields, and fill in the starting and target values in the success indicators table.
- Run the approval. Submit the charter to an approval path with the real decision makers, and export the approved charter to PDF.
After two weeks you know three things: whether the sponsor read a document consistent with the current plan, how long the approval took compared with the traditional round of signatures, and whether the team still needed the Word file.
Frequently asked questions
Does Microsoft Project have a project charter?
Not as a document with versions and approval. The plan file does not contain a charter, so teams prepare it in Word or Excel next to the plan or build their own app on the Power Platform. In the server edition you can configure a form on the project detail page, but without versions and approval.
What should a project charter contain?
The purpose and the business case, the scope together with its exclusions, measurable success indicators, milestones and time frames, the budget, the most significant risks, project roles including the sponsor, and a record of approval. A charter usually fits on one or two pages, which is enough when the detailed data sits in the system.
Who approves a project charter?
The sponsor approves it on behalf of the organisation funding the project. Depending on the structure of the organisation, additional approvals from finance, legal or technology are often needed. An approval path lets you name all the decision makers in one or several consecutive stages and records each decision together with its comment.
Can a Word template be reproduced in a PPM system?
Yes. The template builder lets you reproduce the structure of fields and sections used in the organisation, so the corporate standard is preserved. In a running project, a new charter version takes over the field values according to the current template.
How do you make changes to an approved charter?
You create a new charter version that takes over the data from the approved one. The change is submitted as a plan change, which can go through the same approval path. The sponsor sees the description and justification of the change together with the planned and requested end date and the budget. The previous version stays saved in the project, so the original assumptions can still be checked.
The project charter contains the justification for delivering an undertaking. The Microsoft Project plan file does not contain it, so teams keep it in text files and spreadsheets. That works until the first changes occur in the project. Milestones in the file then stop matching the schedule, risks stop matching the register, and identifying the version accepted by the sponsor becomes impossible. The charter becomes a formality and is filled in superficially.
In a Microsoft Project alternative for project charter work the charter is kept in the system. The PMO builds the template from the document already agreed in the organisation, in as many variants as there are categories of project. Milestones and risks are taken from the plan. Out-of-scope entries and success indicators are approved together with the rest of the assumptions. An approval path takes the place of the round of signatures, and every version stores a record of who accepted what and with what justification. None of that requires giving up the schedule you already have, because the plan moves in an .mpp file together with its tasks, dependencies, assigned resources, effort, working days and baselines.





