Project charter template for Word (free download)

Project charter template for Word (free download)

A project that starts without a written document almost always ends the same way: everyone remembers a different scope, the budget stretches with no record of who authorised it, and a few weeks in nobody can say clearly who decided what. A project charter template for Word closes that gap in a single meeting: it puts in writing what will be done, why, with which resources, with which team and where the work stops.

The project charter is the document that formally authorises the start of the work. It is not a detailed plan and it is not a task schedule: it is the high-level agreement signed by the person sponsoring the project and the person who will lead it. With that signature, the leader can commit resources, request staff and talk to suppliers without renegotiating the limits of the work every week.

This template is built for small and medium businesses, workshops, distributors, operations areas and small teams that have no dedicated project office. It is a Word file with no macros and no complicated fields: you download it, open it and fill it in by typing over the marked spaces. The charter fits in a few pages and follows an order that anyone on the team understands without previous training.

If projects in your company are approved by word of mouth in a meeting and each area then moves forward on its own, this form is the cheapest starting point available. It does not solve execution, but it removes the most expensive discussion of all: the one that shows up when the project is already halfway through and somebody asks what it was for.

What a project charter is

The project charter is the entry door of any organised project. It is written before the first supply is purchased, before the first contract is signed and before the first person is assigned. Its purpose is not to describe how the work will be carried out, but to make clear what was authorised, under which conditions and with which owners. It is a short document: usually two or three pages, with eight sections and two signatures at the end.

Unlike the project plan, which is long and changes every week, the charter is written once and edited rarely. When something changes substantially (the scope grows, the budget is trimmed, the leader is replaced), the charter is not rewritten from memory: an amendment is issued, signed and attached to the original. That way the document keeps its value as a reference, and anyone joining the project later can read it and understand where everything came from.

Inside the company the charter plays an organising role and a record-keeping role. Organising, because it distributes responsibilities and removes the grey area where two areas each believe the other is doing the task. Record-keeping, because if somebody later asks why that money was spent or why that decision was taken, the answer sits on a signed and dated page. In internal disagreements, the charter is often the only document that settles an argument of memory against memory.

What it is useful for in practice

• Formally authorising the start of the work, so the team does not depend on a verbal agreement that nobody remembers afterwards.
• Fixing the scope in writing, with an explicit list of what is included and another of what is left out.
• Recording the approved budget, its currency and who authorised it.
• Naming the sponsor and the project leader, with their responsibilities and their level of decision-making.
• Aligning the team and the neighbouring areas before disputes over shared resources begin.
• Providing a baseline for comparing progress, cost and dates once the project is under way.
• Making the handover of the project easier if the leader changes midway.

What the template includes

The file contains the eight standard sections of a project charter, plus the document control table at the top and a closing note. Every section comes with its fields already named, so all you have to do is fill in the spaces with the information of your project.

The control table is the part almost everyone fills in badly. Each charter should carry its own code inside the company series, for example PR-014, together with its version number. If the project receives an amendment, that amendment also carries a code and a version, and it is attached to the original. Without that numbering, two versions of the same charter circulate by email and nobody knows which one is current.

An example of how to close the scope

The scope section is the one that prevents the most arguments and also the one that is hardest to write. The practical rule is simple: if it does not fit in one short sentence, it is not defined yet. These are examples of the level of detail that actually works:

Writing the right-hand column costs more than the left-hand one, because it forces you to say out loud what other areas expect to receive and what was never included. The effort pays off: every line written there is a claim that will not arrive later.

How to use the template step by step

1. Open the file in Word and save a copy named after the project and the date, without changing the original download.
2. Replace the company details in the footer: legal or trading name, responsible area and the contact details you want to leave visible.
3. Fill in the document control table: write the code inside your company series in the [PR-___] field, keep the first version and note the date and the owner.
4. Complete the project identification. If the budget is not approved yet, do not leave the field empty: write under review and note who must approve it and by when.
5. Write the overall objective in a single sentence that starts with a verb, then the three specific objectives that land it.
6. Build the scope in two columns and read it with somebody from another area before signing. The uncomfortable questions appear there, not later.
7. Put together the deliverables, milestones, team and risk tables. Three or four real risks are enough; an inflated list protects nobody.
8. Print the charter, sign it with the sponsor and the leader, and store the signed file in the project folder. Give a copy to every area mentioned.

Common mistakes to check before signing

• Objectives written as tasks. Completing a task is noticed; completing an objective can be verified.
• A scope without the column of what is excluded, which is precisely the one that prevents claims.
• A budget written without a currency, or with an approximate figure that nobody can justify later.
• Dates committed out of enthusiasm rather than calculation: a date that is already impossible contaminates the whole project.
• Names without a role or a main responsibility, which leaves the team unsure of whom to answer to.
• Risks copied from another project. A charter with generic risks is a sign that nobody thought about the real ones.
• Scope changes agreed in conversation and never attached to the signed document.

When it makes sense to move to a system

The project charter does not need software: it is a document that is signed once and read a few times. The problem appears later, when the project starts and tracking becomes a daily task. That is where Word tables stop working, because nobody updates the file by hand and the real progress ends up living in the leader's head.

If your company runs one or two projects a year, the Word template is more than enough and there is no point in complicating things. But when projects overlap, share staff and consume inventory or materials, control stops being a formatting problem and becomes an information problem. That is the honest moment to evaluate Kardex Tauro: not for writing the charter, but so that the receipts, issues and consumption each project generates are recorded in one place instead of being spread across three different sheets. If you prefer to keep your own forms, Kardex Tauro also works as a reference for what an ordered control looks like before you make the change.

This form is a general guide for internal use: review it with your adviser before adopting it as company policy.