The most common cause of project delays isn’t bad execution. It’s waiting. Waiting for someone to approve the brief. Waiting for the client’s boss to sign off on the direction. Waiting for legal to review the copy. Waiting and wondering if you should follow up or if following up will seem pushy.
These delays are not accidental. They happen because nobody agreed on who decides what and how fast. The project launched with a vague approval process that sounded fine in the kickoff because nothing needed approval yet. Then Week 2 arrived and suddenly three people had opinions and nobody knew whose opinion was final.
The decision authority matrix kills this problem at the source. You build it at kickoff, before the first approval is needed. Once it exists, you never have to negotiate the process mid-project again.
Why Approval Delays Are a Structural Problem, Not a People Problem
When a project stalls at approval, the instinct is to blame the client for being slow. But slow approvals usually have structural causes: unclear who the decision-maker is, no agreed timeline, an internal review process that nobody mapped for you.
The client’s boss gets pulled into a decision she didn’t know she was supposed to make. She hasn’t read the brief. She asks three questions. The client has to relay the answers back to you. You make revisions. The cycle repeats.
None of this is the client being difficult. It’s the natural result of launching a project without an approval map. You can’t speed up a process that was never defined.
The decision authority matrix gives you the map before you need it. And the act of building the map, sitting with the client and asking “who actually approves this?”, often surfaces organizational confusion the client didn’t realize existed.
The 5-Column Matrix
Set up your table with these exact columns:
Decision Type | Who Approves | Fallback (If Unavailable) | Target Turnaround | Escalation Path
Build one row for each of these five decision types. Add more if the project warrants it, but these five cover 90% of what causes delays.
Row 1: Creative Direction Who approves the overall direction, tone, and visual approach?
Example row: | Creative Direction | Sarah M. (Marketing Director) | Tom K. (CEO) | 24 hours | Sarah → Tom → you flag delay |
This one matters most at the start of the project, when you’re establishing creative direction and need a single voice to sign off. If “the whole team” is the approver, you have no approver.
Row 2: Copy and Content Changes Who approves text changes, messaging shifts, or content edits above minor proofreading?
Example row: | Copy/Content | Sarah M. | Legal review (5 days) if regulated | 48 hours | Sarah → legal if needed |
The “legal review” flag is important. Some industries (finance, healthcare, legal) require compliance review. If you don’t build this into the matrix, a copy change at Week 3 can trigger a 2-week legal hold nobody anticipated.
Row 3: Budget Changes Who approves any spending changes, including unexpected software costs, additional hours billed, or scope additions with cost impact?
Example row: | Budget Changes | James R. (CFO) | Board approval if >$10K | 5 business days | James → CEO → flag at Day +3 |
Freelancers skip this one and then have uncomfortable conversations when they bill for work the wrong person approved. Get the budget authority name upfront. This also signals to the client that you intend to communicate budget impacts before acting on them, which builds trust.
Row 4: Scope Changes Who approves adding or removing deliverables from the project scope?
Example row: | Scope Changes | Sarah M. + you (joint) | N/A | 48 hours | Written CR form required |
This is the most important row for protecting your revenue. A verbal “can you also add X?” from anyone other than the named approver is not a scope change, it’s a suggestion. Scope changes require approval from the named person plus your written change request form.
A scope change approved by the wrong person is not a scope change. It’s a favor you did for a junior contact that you’ll now struggle to bill for. The matrix defines whose voice counts.
Row 5: Launch / Final Approval Who has final sign-off before the deliverable goes live, is submitted, or is considered complete?
Example row: | Launch Approval | Sarah M. + CEO (dual sign-off) | N/A | 72 hours | Both required; no exceptions |
Some projects need dual sign-off at launch. Others don’t. Find out now. A project where you thought one person had final authority, but actually the CEO needs to see it before launch, will surprise you at the worst possible moment.
How to Present the Matrix at Kickoff
Don’t show up to the kickoff with a blank matrix and try to fill it in live, that’s inefficient and signals that you haven’t prepared. Instead:
Before the kickoff, fill in your best guess for each row based on what you know about the organization. Put question marks next to names you’re unsure about.
At the kickoff, say: “I’ve drafted the decision authority matrix so we can confirm the right people for each decision type. I’ll pull it up, can you tell me if any of these names are wrong or should be different?”
This framing makes it efficient. You’re not starting from zero. You’re confirming. Most clients will correct 1-2 names and approve the rest. The whole exercise takes 8-10 minutes.
Once confirmed, email it to the client with: “Attached is the confirmed decision authority matrix from today’s kickoff. This will be our reference for approvals throughout the project. Please forward to anyone on the list so they know what we’ve agreed to.”
That last sentence is important. If Sarah is listed as the copy approver, she should know she’s the copy approver.
Handling a Client Who Won’t Commit
Some clients resist naming specific approvers. They say “the whole team reviews things” or “it depends on the decision.” This is a flag, but it’s not a dead end.
Try this: “I completely understand, different decisions involve different people. For our purposes, I just need to know who has final say when there’s a disagreement. If you and Tom both reviewed a piece of copy and had different opinions, whose call would it be?”
Everyone has an answer to that question. The political reality of their organization has a hierarchy, even if it’s informal. You’re not asking them to change how they work, you’re asking them to tell you how they already work.
If they genuinely can’t name anyone, if truly everything requires committee consensus with no tie-breaker, then add 2 weeks to your project timeline. That’s the cost of a decisionless approval process. Name it explicitly: “Without a named decision-maker, I’d plan for 5-7 business day approval windows on major decisions. Does that work with your timeline?”
That question usually produces a name.
The Fallback Column: Why It Matters
The fallback column is the one freelancers skip, then desperately wish they had when the primary approver goes on vacation in Week 3 and the project grinds to a halt.
Every primary approver needs a fallback. The fallback doesn’t need to be at the same seniority level, they just need to have authority to make a call in an emergency.
At kickoff, ask: “If Sarah is unavailable for 3+ days and we need a copy decision, who would you want us to escalate to?” Most clients find this reasonable. They know people go on vacation. Having a fallback is professional.
What the Matrix Produces
By the end of the kickoff call, the confirmed decision authority matrix gives you:
- A named approver for every decision type (no more “I’ll check with the team”)
- A documented turnaround expectation (grounds for a follow-up after the agreed time)
- A fallback for every approver (continuity when people are unavailable)
- An escalation path when standard timelines aren’t met
- A reference document that removes the need to renegotiate process mid-project
Projects with a signed authority matrix move faster for a simple reason: both sides know who decides, so decisions get made rather than deferred. The fog lifts. The path is clear.
The matrix isn’t about accountability, it’s about clarity. Clients don’t drag approvals on purpose. They drag because nobody defined the path. Give them the path and they’ll walk it.
Build the matrix before your next kickoff call. It takes 15 minutes and it will save you days on every project it touches.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
