Client Decision Log for Agencies: Template, Workflow and Examples

Client decisions often disappear into the busiest parts of agency work. A client says “option B is fine” in a voice note. A stakeholder approves a layout in a comment thread. Someone changes the launch order during a call. Two weeks later, the team is asking who approved what, why the scope changed and which action items were supposed to follow.

For agencies, consultants, creative studios and freelancers, the problem is not only documentation. The real problem is that client decisions affect delivery, scope, budget, feedback, approvals and trust. If decisions are scattered across calls, email, chat and design comments, the team loses the context it needs to move confidently.

This guide gives you a practical client decision log for agencies. It includes a copyable template, decision tables, a raw voice-note-to-decision-record example, a workflow for agencies and a FAQ you can use to keep approvals and action items searchable.

Quick Answer

A client decision log for agencies is a shared record of important client choices, approvals, scope decisions, tradeoffs and follow-up actions during a project. It captures what was decided, who approved it, why it was decided, what it affects and what happens next.

The best decision log is short enough to use every week, but specific enough to protect the project later. It should separate feedback from approval, approval from scope change and scope change from ordinary tasks.

Use this quick structure:

A client decision log gives the agency one source of truth after messy feedback, async voice notes and live calls. VocalJet fits when the decision was spoken: the client records context, then the team turns that voice note into a transcript, decision summary, scope label, action items and follow-up email.

Why Agencies Need A Client Decision Log

Agency projects fail quietly when decisions are remembered differently by different people.

A designer may remember that the client approved the homepage direction. The account lead may remember that approval was conditional. The client may remember that they asked for another stakeholder to review it first. None of those people are acting in bad faith. They are working from different fragments of the same conversation.

Atlassian’s DACI decision-making framework is useful because it separates roles: driver, approver, contributors and informed people. Agencies need a lighter client-facing version of that logic. Every meaningful project decision should have a clear owner, a final approver and a written outcome.

Asana’s action log template also points to an important habit: decisions and follow-ups need owners and due dates in one place. A decision without a next action is just a note. An action item without the decision behind it is hard to defend later.

A client decision log is the operating record that connects client choices to approvals, scope, owners and next steps.

What A Client Decision Log Should Include

A useful client decision log should capture the decision without turning every update into a legal document.

Use these fields:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21

Decision ID:
Client:
Project:
Date decided:
Decision title:
Original client words:
Decision summary:
Decision type:
Decision owner:
Final approver:
Contributors:
Affected deliverable:
Scope impact:
Budget impact:
Timeline impact:
Options considered:
Reason:
Action items:
Follow-up sent:
Links:
Status:

The most important field is Decision type. It tells the team how seriously to treat the record.

Use client intake software for agencies or an AI client brief generator when the decision exposes missing context from the original brief. Use scope creep client intake when the decision changes the agreement.

Decision Log vs Action Log vs Approval Record

Teams often mix these records together. That is why project history becomes hard to search.

Atlassian’s scope creep guide frames scope creep as work expanding beyond the original plan without matching approval, time, budget or resources. A decision log helps agencies catch the moment a casual preference becomes a real scope decision.

For feedback-heavy projects, pair the log with async client feedback, voice feedback for agencies and client feedback to action items. Feedback explains what the client wants. The decision log records what the project will actually do.

Client Decision Log Template For Agencies

Copy this into your project management system, client workspace, shared doc or internal operating system.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48

Client decision log

Decision ID:
Client:
Project:
Date:
Recorded by:

Original client words:

Decision summary:

Decision type:
- Direction
- Approval
- Scope
- Dependency
- Deferral
- Authority

Decision owner:
Final approver:
Contributors:
People to inform:

Affected deliverable:
Current status:
Options considered:
Reason for decision:

Scope impact:
- No scope impact
- Included in current scope
- Needs clarification
- Change request required
- Deferred to later phase

Budget impact:
Timeline impact:
Risk if not documented:

Action items:
- Agency:
- Client:

Follow-up message sent:
Links:
Status:

This template works because it keeps the client decision close to the work it changes. It does not ask the team to write a long report. It asks for enough context to prevent confusion later.

Best Workflow For Agencies, Consultants And Freelancers

For client-facing service teams, the best workflow is to log decisions at the moment they affect delivery, not at the end of the project.

1. Decide What Counts As A Decision

Do not log every sentence.

Log a client message when it affects:

• direction;
• approval;
• scope;
• budget;
• timeline;
• stakeholder authority;
• client-owned dependencies;
• delivery risk.

If a message only says “thanks” or “looks good” without a version, decision owner or next step, treat it as feedback until confirmed.

2. Capture The Client’s Original Words

Preserve the raw input before summarizing it.

Client decisions can arrive through email, voice notes, calls, comments, forms or project tools. The exact wording matters because small phrases often signal assumptions: “quick”, “just”, “if possible”, “before launch”, “our CEO asked” or “legal might need to see it.”

Use client voice notes to action items when the decision was spoken and needs to become a transcript, summary, tasks, owners and follow-up-ready text.

3. Separate Decision, Reason And Action Items

A clean record has three layers:

This prevents the action items from floating without context.

4. Identify The Real Approver

Client-facing teams need a named approver, not a vague group.

Atlassian’s DACI model makes a sharp distinction between people who contribute input and the one person who approves the decision. In agency work, that distinction protects delivery. Stakeholders can comment, but the project still needs one final decision owner.

When approval is unclear, connect the issue to a client approval workflow for agencies before production continues.

5. Send The Follow-Up While Context Is Fresh

Every decision log entry should produce a short written recap.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20

Subject: Confirming decision: [Project] - [Decision]

Hi [Name],

Confirming the decision from [call / voice note / review thread].

Decision:
[One-sentence decision]

Reason:
[Why this direction was chosen]

Scope status:
[Included / needs estimate / deferred / no scope impact]

Next steps:
- Agency: [action]
- Client: [action]

Please reply by [date] if this does not match your understanding.

GitLab’s communication handbook is a strong reference for this habit because it treats async communication as documentation, not just messaging. For agencies, the follow-up is what turns a spoken decision into a durable project record.

Raw Client Voice Note To Decision Log Example

Here is how one messy client update becomes a useful decision record.

Raw Client Voice Note

1

I talked to sales this morning. Let's go with option B for the homepage hero because it explains the offer more clearly. We can skip the testimonial section for launch if that keeps us on schedule. Legal still needs to approve the ROI line, so don't publish that part yet. Also, our founder wants to see the final page before it goes live, but she is traveling until Wednesday.

Structured Decision Log

Action Items

This is the difference between “the client sent a voice note” and “the team has a decision, risk and next step.”

When A Decision Needs A Change Request

Not every client decision changes scope. Some decisions simply choose between options already included in the project.

Use this table before turning a decision into production work:

PMI’s scope management guidance emphasizes that changes to an approved baseline should be identified, communicated, coordinated and approved before work starts. Agencies do not need heavyweight governance for every client project, but they do need the same discipline when a decision changes scope.

How VocalJet Fits This Workflow

Client decisions often happen in the channel that is easiest for the client, not the channel that is easiest for the agency to search later.

VocalJet gives agencies a product path for those moments:

• the client records a nuanced decision by voice;
• the agency gets the transcript and summary;
• the team extracts the decision, approver, scope impact and open questions;
• the spoken context becomes action items and a follow-up email;
• the decision record can be searched and shared later.

Async voice feedback helps agencies capture the context behind a decision without forcing another meeting. A client decision log makes that context operational.

Use the decision log with voice feedback for agencies, client feedback to action items and client voice notes to action items when a decision starts as spoken feedback.

FAQ

What is a client decision log for agencies?

A client decision log for agencies is a shared record of important client choices, approvals, scope decisions and follow-up actions during a project.

What should a client decision log include?

A client decision log should include the original client words, decision summary, decision type, final approver, affected deliverable, reason, scope impact, timeline impact, budget impact and action items.

Is a decision log the same as an action log?

No. A decision log records what was decided and why. An action log records who will do what by when. Agencies usually need both because client decisions create action items.

When should an agency log a client decision?

An agency should log a client decision when it affects direction, approval, scope, budget, timeline, stakeholder authority, dependencies or delivery risk.

How does a decision log prevent scope creep?

A decision log helps prevent scope creep by showing when a client choice changes deliverables, review rounds, budget, resources or timeline before the team starts extra work.

How can VocalJet help with client decision logs?

VocalJet helps when decisions are explained by voice. The recording can become a transcript, summary, action-item list, scope label and follow-up message that the agency adds to the decision log.

Final Recommendation

Start with a simple rule: log every client decision that affects direction, approval, scope, timeline, budget or ownership.

For agencies, the decision log should be lighter than a contract and stricter than a meeting note. Preserve the client’s original words, name the final approver, connect the decision to action items and send a written recap while the context is fresh.

When the decision is easier for the client to explain by voice, use VocalJet to capture the recording, structure the decision and turn it into follow-up-ready work.

Sources

• Atlassian DACI decision-making framework
• Asana action log template
• Atlassian scope creep guide
• PMI scope management guidance
• GitLab communication handbook