Project Charters, Milestones and Work Breakdown Structures: How Agencies Plan Client Work That Stays Profitable

A project charter is a short, agreed document that states why a project exists, what is inside and outside its scope, who approves the work, and on what basis it is billed. On agency client work it does a job the textbook version never had to do: the sponsor is a paying client who did not ask for a charter, the budget is a fixed fee or a retainer, and every milestone has to survive being disputed on an invoice. This page rewrites the three planning artefacts — charter, milestones and work breakdown structure — for that situation, and runs one illustrative brand-launch project through all three so you can see how they connect.

By Ed Kamel, founder of Zerak and Wieldy. Published September 2026. Reviewed by the Wieldy team.

Why do agency projects need charters more than internal projects do?

Because a vague charter on client work costs margin immediately, not just time. Here is the failure mode, and every agency owner reading this has lived some version of it. The proposal is signed. Work starts the following Monday. Nobody wrote down who on the client side is allowed to approve a route, what counts as one round of revisions, or what happens when the client's new marketing director arrives in week six and asks for a different direction. By week nine you are three unbilled rounds deep, the launch date has moved twice, and the conversation about who caused it is happening over email with no document to point at.

In a corporate project the sponsor sits down the corridor and the budget comes out of the same company's pocket. A loose charter there causes delay and irritation. In an agency project the sponsor is external, the fee was fixed before anyone understood the work, and every hour you spend absorbing an unlogged change is an hour of gross margin you have given away. The scope creep is not a formal change request. It is a WhatsApp message on a Friday afternoon.

A charter does not replace your contract or your proposal. The contract is the legal instrument. The proposal sold the work. The charter is the working document that translates a signed proposal into something the delivery team can act on — and, critically, that the client has seen and agreed to. It is written after the signature and before the kickoff meeting.

The three artefacts nest:

The PMI/PMBOK tradition gave us all three, and the thinking holds up. What it did not give us is a version written for someone outside your company who may dispute a milestone on an invoice. That is what the rest of this page is.

What is a project charter and what should it include?

A project charter for client work is a one-page agreement, attached to the signed proposal, that states the client's business outcome, exactly what is in and out of scope, the deliverables with formats and quantities, the single named person on each side who can approve work, the revision rules, what the client owes you and by when, and the billing basis. It is signed by both sides. It exists so that disagreements later are settled by reading rather than arguing.

Agile teams sometimes use a lighter version — an agile charter covering vision, success measures and working agreements — and that is fine for discovery or ongoing retainer work where the deliverable list is genuinely open. For fixed-fee project work, write the full thing.

The eight things an agency charter must contain

1. Project purpose and the client's business outcome. Weak version: "refresh the brand". Strong version names the outcome the client is buying — a market the brand has to speak to, a launch it has to support, a metric it has to move.
2. Scope in. Weak version: a category list ("creative, digital, launch"). Strong version is countable: what exists at the end that did not exist at the start.
3. Scope out. Weak version: omitted entirely. This is the single most expensive omission in agency project planning.
4. Deliverables with format and quantity. Weak version: "social assets". Strong version: "12 static assets, 4:5 and 1:1, supplied as layered source files plus export-ready PNG".
5. Named client-side approver and named agency lead. Weak version: "the client team". You cannot send a round to a team.
6. Approval and revision rules. Weak version: "revisions as required". Strong version defines a round, a turnaround window, and what happens after the included rounds are used.
7. Assumptions and dependencies the client owns. Brand assets, ad account access, product copy, legal sign-off, stakeholder availability — each with a date.
8. Budget and billing basis. Fixed fee, retainer draw-down or time and materials; what each milestone releases; what out-of-scope work is billed at.

If you want a RACI grid as well, use it — but a RACI with five "A"s in a column is worse than one named approver. The purpose of the exercise is a name, not a matrix.

The three lines that save you the most money

One named approver, with a named deputy. Approval by committee is how a two-round project becomes a six-round project. Write a name and an email address, and write a deputy for when that person is on holiday. Then add the sentence that does the work: feedback from anyone else is routed through the named approver and returned as one consolidated set. You are not restricting who has opinions. You are restricting who hands you work.

The number of revision rounds, and the definition of a round. "Two rounds of revisions" means nothing until you define a round. A round is one consolidated set of comments, returned within an agreed window, acted on once. Without "consolidated", three stakeholders emailing separately over four days is three rounds of work that you contracted as one.

An explicit out-of-scope list, written as sentences. Not "additional creative" but "additional ad sizes beyond the twelve listed", "a second brand route after the chosen route is approved", "localisation into languages other than English", "amends to assets after final approval and handover". Write the things this specific client is likely to ask for. A category list protects nobody; a client recognises a sentence that describes the thing they just requested.

On rate: state in the charter that out-of-scope work is quoted in advance and billed at your standard hourly rate of \_\_\_\_. Set that number yourself — it depends on your market, your mix of seniority and the relationship. The trade-off is real. A rate set high enough to be a deterrent keeps scope tight but makes every extra request a negotiation. A rate set at or near your normal blended rate keeps the relationship easy and the work flowing, but removes the friction that stops creep. Pick deliberately, write it down, and apply it consistently. Wieldy does not publish a recommended figure, because the right one depends on your country, your contract and your market.

Charter vs proposal vs statement of work vs creative brief

These four documents get used interchangeably, and that is where a lot of confusion starts.

In a small agency, the proposal and the charter are often the same document, and that is a reasonable choice — put the charter sections into the back of the proposal and have the client sign once. Separate them when any of these are true: the project runs longer than a quarter, more than one client stakeholder has an opinion, the fee is large enough that a dispute would hurt, or the proposal was written before discovery and the scope has since changed. A charter written after discovery is far more accurate than one written to win the pitch.

Who signs a project charter on a client project?

At minimum, the named agency lead and the named client-side approver. On larger engagements, add whoever controls the client's budget, because the person who approves creative and the person who approves an invoice are often not the same human — and that gap is exactly where milestone disputes live. Use an e-signature rather than an email reply. The charter is the document people dispute, so it should be the document with the clearest record of who agreed to it and when.

Writing the charter: a worked example

The example below is illustrative — invented for this article to show the method, not data from any Wieldy customer. One mid-size client, one brand refresh plus launch campaign, an illustrative fixed fee of $60,000.

Three lines in that charter are carrying most of the weight.

"A round is one consolidated set of written comments returned within five working days." The word consolidated prevents three stakeholders from each spending a round. The five-day window is not there to punish anyone; it is there so the sentence after it has a basis.

"Comments returned after that window move all downstream dates by the same number of days." This converts a future argument into arithmetic. You are not blaming anyone. You are stating a rule both sides agreed to before the project started.

"Media spend is paid by the client directly to the platforms." Whoever's card is on the ad account is carrying the cash-flow risk. Decide that in the charter, not in the first week of the campaign. If you do front media spend, say so explicitly and say how it is reconciled and recovered — and set your own threshold for how much un-recovered spend you will carry.

"One visual identity route developed to completion" plus the out-of-scope line about a second route. Two concepts, one developed. That is a different project from two concepts, both developed, and the fee only covers one of them.

Start from the free agency proposal template — no sign-up, no email gate — and put these charter sections at the back of it.

Milestones: define them as billing and approval events

What a milestone actually is

A milestone is a zero-duration point in a project that marks something being finished, decided or approved. It consumes no time and no budget itself; it is a marker, not a piece of work.

That is the textbook definition, and it is correct but useless on its own for client work. Here is the agency test. For every milestone on your list, answer this question: what invoice, approval or decision does this milestone trigger? If there is no answer, it is a task with ambitions. Delete it or demote it. A milestone list that is really a task list is how clients end up with visibility into work they should not be managing, and how invoices end up detached from progress.

Milestones vs deliverables vs phases vs tasks

The distinction that matters commercially is deliverable versus milestone. A deliverable is a noun. A milestone is an event. You do not invoice for sending a file; you invoice for the file being accepted. Writing milestones as acceptance events rather than delivery events removes the most common invoice dispute in agency work — "we received it, but we hadn't signed it off".

The three milestone types agencies actually use

Payment milestones. Each releases a stated share of the fee. Write the trigger, not just the name.

Approval gates. A point where work cannot proceed until the named approver signs off, because everything downstream depends on the choice. Route selection is the classic one: you cannot do packaging for a route that has not been chosen.

Client-dependency milestones. The point at which the client owes you something — assets, account access, approved copy, legal sign-off. This is the type almost nobody writes about, and the one that protects your margin most. It does two things. It tells the client, before kickoff, that their own team has dated obligations. And when a date slips, it gives you a dated record showing why, which turns an awkward conversation into a factual one. Put them on the same list as your payment milestones and give each one a date and an owner's name.

How many milestones should a client project have?

Set the number from your billing rhythm, not from a rule in a book. Two tests:

• Exposure test. No single milestone should represent more than a share of the fee you would be comfortable chasing if the relationship went wrong. You decide that share.
• Cash-flow test. The gap between milestone invoices should not be longer than your business can comfortably fund. If payroll runs monthly, monthly billing events is a sensible floor.

For a three-month fixed-fee project, four to six milestones usually satisfies both. For a retainer, the billing rhythm is already monthly, so use approval gates and client-dependency milestones instead of payment ones. If getting paid on time is the live problem, the mechanics are covered in getting clients to pay on time.

The five milestones for the worked example

Illustrative, on the $60,000 illustrative fee:

Alongside those, three client-dependency milestones with dates: brand assets received (4 Mar), ad account access granted (18 Mar), legal claims sign-off (8 Apr). They release no money. They exist so the schedule has a defensible cause when it moves.

What is the difference between a roadmap and a project schedule?

A roadmap is the communication layer: a time-ordered view of milestones that the client sees. A schedule is the working plan the team runs on: tasks, assignments, dependencies, dates, hours. Same project, two different documents, two different audiences.

The agency rule is simple. The client-facing roadmap shows milestones and dependencies, not internal tasks. Showing tasks invites task-level opinions from people who are not doing the work, and it makes every internal re-sequencing look like a change to the plan. Keep the detail in the schedule.

Dates or sequence only? Show dates when your client-dependency milestones are on the same roadmap — dates create accountability in both directions, and a roadmap that dates your obligations but not theirs is a rod for your own back. Use sequence only for genuine early-stage discovery, where estimating is guessing, and switch to dates the moment scope firms up.

One more thing, and it is the real reason agency roadmaps stop being believed: keep one source of truth. A roadmap pasted into a kickoff slide deck is stale by the following week, and once a client has caught two stale dates they stop reading it. The roadmap should be a view of the live plan, not a snapshot of it.

What is a work breakdown structure and how do you create one?

A work breakdown structure is a hierarchical decomposition of the total scope of a project into progressively smaller pieces, where the lowest level is a work package that one person can own, estimate in hours and complete. You build it by starting from the deliverables in the charter, breaking each into the activities required to produce it, and stopping when each leaf passes the ownership test below. It is an internal document. The client does not need to see it.

The 100% rule and why agencies break it

The 100% rule says the children of any node must add up to exactly the parent — no more, no less. If "2.0 Identity" has four children, those four children are the whole of the identity work. Nothing extra, nothing missing.

Agencies break it in two predictable places.

The non-production work goes missing. Account management, client calls, internal reviews, the revision rounds you already promised, project management time, the hour after every presentation spent writing up actions. None of it looks like a deliverable, so none of it gets a node — and then it gets done anyway, by people whose time costs money. The hours that disappear from agency WBSs are nearly always the ones that look unbillable. That is exactly why projects run over budget while every single task looks on track.

Client-dependency waiting time goes missing. The week you spend waiting for legal sign-off is not free. Someone is chasing it, the team has been re-planned around it, and the slot you kept open is a slot you did not sell.

Give both a branch. If you cannot bill them separately, they still have to be costed, because they are consuming the fee.

How far should you break down a work breakdown structure?

Stop decomposing when a work package meets three conditions: one person can own it, you can estimate it in hours with reasonable confidence, and you can tell unambiguously when it is done. If any of the three fails, break it down further.

The practical ceiling: if a work package is bigger than one person can finish inside one sprint or one billing period, split it. Packages that straddle a billing period cannot be reported on honestly — you end up saying "about 60% done", which is the phrase that precedes every budget overrun.

The WBS for the worked example

Three levels, illustrative:

``` 1.0 Discovery and strategy 1.1 Stakeholder interviews 1.1.1 Schedule and run 5 interviews 1.1.2 Synthesis and themes 1.2 Market and competitor review 1.3 Positioning development 1.4 Strategy deck build and presentation 2.0 Identity 2.1 Concept development (2 routes) 2.2 Route presentation 2.3 Development of selected route 2.3.1 Logo system 2.3.2 Colour and type system 2.3.3 Application examples 2.4 Brand guidelines document 3.0 Packaging 3.1 Template build 3.2 Adaptation, 6 SKUs 3.3 Pre-press checks and print-ready release 4.0 Launch campaign 4.1 Campaign concept 4.2 Static assets (12) 4.3 Video cutdowns (2) 4.4 Media plan 4.5 Campaign setup and 6 weeks management 4.6 Weekly reporting (6) 5.0 Account management 5.1 Weekly client calls (12) 5.2 Status reporting and comms 6.0 Revision rounds (contracted) 6.1 Strategy, 2 rounds 6.2 Identity, 2 rounds 6.3 Packaging, 2 rounds 6.4 Campaign assets, 2 rounds 7.0 Project management 7.1 Planning and scheduling 7.2 Internal reviews and QC 7.3 Dependency chasing ```

Branches 5.0, 6.0 and 7.0 are the ones that get left off. They are the reason the project costs what it costs.

How do you turn a WBS into a project budget?

Add three columns to every leaf: owner, estimated hours, and rate (internal cost if you are costing margin, billable rate if you are pricing). Then total it. Illustrative, using an illustrative blended cost of $85/hour:

Against the illustrative $60,000 fee, that is a gross margin of $8,745, or about 14.6%. All of those numbers are invented for the example. The point is the shape of the answer: branches 5.0 to 7.0 account for $13,005 of cost — more than the entire packaging workstream — and they are invisible in most agency plans. Leave them out and the same project appears to return a 36% margin, right up until the invoices are paid and the year-end numbers say otherwise.

Model your own version with the agency profit calculator, and if the work is a retainer rather than a project, the retainer pricing calculator and how to price your agency retainers cover the same arithmetic on a monthly basis.

What do you do when the WBS costs more than the fee you quoted?

You have four honest options, and discovering this before kickoff instead of in month three is the entire reason to do the WBS.

1. Reduce scope in the charter. Six SKUs becomes four. Twelve static assets becomes eight. Do it before the charter is signed and it is a conversation; do it after and it is a renegotiation.
2. Reduce rounds. Two rounds becomes one on the lower-risk deliverables.
3. Change the seniority mix. Move hours from the creative director to a mid-weight with a review checkpoint. This has a quality cost; take it consciously.
4. Accept a thinner margin, knowingly. Sometimes the logo on the website is worth it. The word doing the work is knowingly.

What you must not do is nothing. An unresolved gap between the WBS total and the fee does not stay a planning problem. It becomes an overtime problem, then a quality problem, then a renewal problem.

How do you keep the plan honest after kickoff?

By checking it against reality every week. A charter, a milestone list and a WBS that nobody revisits are three documents that made you feel organised in February.

The weekly check. Hours logged against each work package versus hours estimated for it. Then the earned-value question: how much of the budget have we consumed, against how much of the work is actually complete? Those two numbers diverging is the earliest reliable warning you get. Run the arithmetic with the budget at completion calculator, which projects where the project lands if the current burn rate holds. The broader set of numbers to watch across the agency is in the five numbers every agency owner should watch.

Change control, in agency terms. A change request is any request that touches the out-of-scope list or adds a revision round. That is the whole definition — you already wrote the list, so the test is mechanical. Every change gets a three-line change note:

• What changed: a fourth round on the packaging artwork, to accommodate the revised claims.
• What it costs: 9 hours at our standard hourly rate of \_\_\_\_, quoted at $\_\_\_\_.
• What it does to the dates: print-ready release moves from 22 Apr to 28 Apr.

Approved in writing by the named approver before the work starts. Not after. A change order approved retrospectively is a favour you are asking for, not a change order.

The Friday-afternoon WhatsApp request. This is the actual mechanism of scope creep in agencies, and refusing to use WhatsApp is not the answer — your clients like it, and responsiveness is part of what they are paying for. Keep the channel, remove the ambiguity. Log the request the same day. Check it against the out-of-scope list. If it is in scope, it goes into the schedule. If it is out, reply with the three-line change note before anyone opens a file. The discipline is not about the channel. It is that nothing becomes work until it has been priced.

Client-dependency milestones do the defending. When the launch slips because legal sign-off arrived eleven days late, you do not need to make an argument. You point at a dated milestone the client agreed to in the charter, and at the clause that says downstream dates move by the same number of days. Nobody has to be blamed, because it was all decided in advance.

Free templates and calculators

All of these are free, with no sign-up and no email gate:

The charter structure and the WBS outline above are written to be copied straight out of this page into your own document — that is why they are laid out in full rather than offered as a download.

Every calculator can be embedded on your own site: add `?embed=1` to the tool URL and put it in an iframe. Each one explains its formula with a worked example, so consultants and trainers can use them in client-facing material without sending people off-site.

Running charters, milestones and WBS in one place

Method first, software second — but once the method is working, having it in three documents and a spreadsheet becomes the bottleneck. In Wieldy, the agency management software built by Zerak, the project sits against the client and the retainer rather than in a separate tool. Tasks carry owners and estimates, so the WBS and the budget are the same object. E-signatures sign the charter. Milestones can trigger the invoice, and invoices take card payment through Stripe, so the milestone and its payment are one record instead of two systems that have to be reconciled. The built-in AI assistant answers questions about your own live data — for example, which projects are over their estimated hours this month.

Open the live demo workspace with sample agency data from wieldyapp.com (email only, no account), or start the 7-day free trial with no credit card. Pricing is flat per workspace — no per-user and no per-client fees — with Growth at $59/month at launch pricing, which ends 18 October 2026. If you are moving existing project data across, talk to the Wieldy team.

Frequently asked questions

Do small agencies really need a project charter?

Yes, but not a long one. A five-person agency running a $12,000 fixed-fee project needs the same five lines as a fifty-person one: named approver, revision rounds defined, out-of-scope list, client dependencies with dates, billing basis. Put them at the back of the proposal and sign once. The cost of writing it is twenty minutes; the cost of not having it is the third unbilled round.

What is the difference between a project charter and a statement of work?

The statement of work (SOW) is the legal instrument — obligations, payment terms, liability, IP, termination — and it is written to be enforceable. The project charter is the operating agreement the delivery team actually works from: who approves, how many rounds, what is out of scope, what the client owes you and when. The SOW protects you in a dispute; the charter is what stops the dispute happening.

What is the difference between a milestone and a deliverable?

A deliverable is a thing you hand over, such as a brand guidelines PDF. A milestone is the moment that thing is accepted or a decision is made, such as "brand guidelines approved". For agency billing the distinction is commercial, not semantic: you invoice against acceptance, not against sending a file, which removes the most common argument on milestone invoices.

What is the 100% rule in a work breakdown structure?

The 100% rule states that the child nodes of any element in a WBS must add up to exactly that element — nothing extra and nothing missing. Agencies break it most often by leaving out account management, contracted revision rounds and project management time, because those branches do not look like deliverables. Leave them out and the WBS no longer represents the real cost of the project.

How do you stop scope creep on an agency project?

Write an explicit out-of-scope list in the charter as sentences the client will recognise, define a revision round as one consolidated set of comments, and name a single approver. Then enforce one rule after kickoff: anything touching that out-of-scope list gets a three-line change note — what changed, what it costs, what it does to the dates — approved in writing before work starts. Keep the WhatsApp channel; price what comes through it.