The columns of an approval matrix
An approval matrix is a table that says, for each deliverable or decision on a client project, whose yes moves it forward: for example, the bakery owner approves the home page design on the review link within 3 business days, the manager approves it if she is away, and any extra work over the agreed spend limit needs the owner’s email.
Projects rarely stall because the work is hard. They stall because nobody is sure who can say yes, or the one person who can is on holiday. An approval matrix answers that once, at kickoff, for every deliverable. Pick a preset, rename the people and items, and print it or attach it to your proposal.
- Deliverable or decision
- One thing that needs a yes before work moves on: the brief, a set of page designs, the final logo files, a spend over a limit, the launch go-ahead. Write it the way it will appear in your emails, so there is no doubt which row applies.
- Approver
- The one person whose yes counts for that row. Name a person, not a team or “the client”. If several people need to agree, one of them still owns the final call and the others give input before it.
- Backup approver
- The person who decides when the approver is away or silent past the response time. Without one, a two-week holiday on the client side becomes a two-week gap in your schedule.
- How approval is recorded
- What counts as a yes: approving on the review link, an email reply that says “approved”, a signed sign-off form, or a call followed by your written summary. Bigger, harder-to-undo decisions deserve the more formal methods.
- Response time
- How many business days the approver has to reply. It makes the schedule honest: a launch date only holds if each approval along the way arrives on time.
- Condition
- Anything that changes who approves or when, such as a spend limit for extra work, a round limit, or “before files go to the printer”. Conditions are where approval disputes usually start, so write them down.
An approval matrix for a website project
This is the website preset from the tool above, a made-up bakery project with an owner and a manager. Notice that the two people share the work, each backs up the other, and the owner alone approves extra spend. The checker in the tool flags the row with no backup, so you can decide whether that is deliberate.
| Deliverable or decision | Approver | Backup | How it is recorded | Response time |
|---|---|---|---|---|
| Brief and scope | Maria Lopez (owner) | Tom Reyes (manager) | Signed sign-off form | 3 business days |
| Sitemap and page list | Tom Reyes (manager) | Maria Lopez (owner) | Email reply “approved” | 2 business days |
| Home page design | Maria Lopez (owner) | Tom Reyes (manager) | Approve on the review link | 3 business days |
| Inner page designs | Tom Reyes (manager) | Maria Lopez (owner) | Approve on the review link | 3 business days |
| Page copy and prices | Tom Reyes (manager) | Maria Lopez (owner) | Approve on the review link | 2 business days |
| Extra work outside scope | Maria Lopez (owner) | None (owner only) | Email reply “approved” | 2 business days |
| Launch go-ahead | Maria Lopez (owner) | Tom Reyes (manager) | Signed sign-off form | 1 business day |
Before the client agrees to the approval matrix
An approval matrix is not a RACI chart
A RACI chart lists who does, approves, is consulted on and is told about each task. An approval matrix only answers the approval question, in more detail: backup, method, response time and conditions. Many projects use both; use the RACI chart generator if you also need the full roles.
Get the client to agree to the approval matrix in writing
A matrix you wrote but the client never saw does not help when the approver goes quiet. Send it with the proposal or at kickoff and ask for a reply or a signature on the printed version.
Silence is not approval
The matrix says the backup decides when the approver misses the response time. It does not say that no reply means yes. Treating silence as approval is the kind of shortcut that turns into a dispute at invoice time.
Keep the approval matrix short
Six to ten rows cover most projects. If every small task has its own row, nobody reads it. Group small items under the deliverable they belong to.
Questions about approval matrix templates
What is the difference between an approval matrix and a RACI chart?
A RACI chart covers four roles for every task: responsible, approver, consulted and informed. An approval matrix goes deeper on one of them. It adds a backup approver, how the yes is recorded, how long the approver has and any condition, such as a spend limit.
Who should be the approver in an approval matrix for a small client?
Usually the person who signs your invoices or the contract, often the owner. For day-to-day items such as social posts, a manager can approve, with the owner as backup. The rule is one named person per row.
Can an approval matrix have two approvers for one item?
It can, but it tends to stall. When two people must both say yes, any disagreement stops the work. Name one approver and list the other as someone who gives input before the deadline. The tool warns when a row names two people.
What response time should an approval matrix give the client?
Use the feedback window you agreed in the contract or proposal. Shorter for small, frequent items such as posts; longer for large ones such as a full set of page designs. Whatever you choose, make the project schedule match it.
How do I share the approval matrix with my client?
Use Print or save as PDF for a one-page sheet with a signature line, Copy text to paste into an email or proposal, or Download CSV to keep it with your project files. Nothing leaves your browser until you send it.
Should the approval matrix change during the project?
Only when people change. If the client hires a new manager or the owner hands over the project, update the matrix and send it again, so everyone knows whose yes counts from that date on.