Client Approval Tracker Template: Deliverables, Review Rounds, and Sign-Off

A client approval tracker records what you submitted, which version needs review, who can approve it, and what decision is still outstanding. Use one row per deliverable, with a clear approval status and next action.

For work with several revision rounds, keep a separate review history. That prevents an approval for an earlier draft from being mistaken for approval of the final version.

This template works for website pages, design files, reports, proposals, content, and other client deliverables.

Free client approval tracker template

Copy this table into a spreadsheet or document.

Client: [Name]
Project: [Name]
Approval coordinator: [Name]
Agreed review process: [Who reviews, how feedback arrives, and who gives final approval]

For each deliverable, also record:

• Approval scope: What the client is being asked to approve.
• Acceptance criteria: What must be true for the deliverable to be accepted.
• Decision evidence: The message, comment, or document containing the decision.
• Approved by and when: The person and date.
• Outstanding conditions: Anything still required before the next step.

Keep the reference precise. “Homepage” is a deliverable name. “Homepage preview v3, submitted October 16” identifies what the client actually reviewed.

Review-round history template

Use this when a deliverable goes through more than one submission.

The first table shows the current position. The second preserves how you got there.

Filled example: a website project

This fictional example follows a freelancer delivering a website for North Studio.

Maya is the client’s final approver. Other stakeholders can provide feedback, but Maya confirms the consolidated decision.

The contact form specification is approved. That does not mean the form has been implemented or tested.

Likewise, approving individual page designs does not automatically approve the completed website for launch.

Approval belongs to a defined output, version, and decision.

Example approval record

Deliverable: Contact form specification
Version: v1, submitted October 15
Approval scope: Fields, required inputs, and submission recipient
Decision: Approved
Approver: Maya
Approval date: October 16
Evidence: Client email confirming the specification
Next action: Implement and test the agreed form
Exclusions: Final website launch approval remains separate

This gives you a useful record without turning a small project into an administrative exercise.

Choose statuses that describe the decision

Use a short, consistent set.

Keep approval status separate from implementation progress.

For example:

• Approval status: Approved
• Implementation status: In progress

Combining both into “Done” makes it difficult to see what actually happened.

Define what you are asking the client to approve

A vague review request often produces vague feedback.

“Please review the website” leaves several questions open:

• Are you asking about layout?
• Should the client check every paragraph?
• Is functionality ready for testing?
• Does a positive reply authorize publication?

Make the decision explicit.

For example:

Please review homepage design v3 for layout, imagery, and section order. The copy remains a draft. This review does not authorize publication.

Later, the launch request can ask for a different decision:

Please confirm whether the final staging version is approved for publication, including the agreed copy, links, and functionality.

The tracker should reflect those separate approval scopes.

Identify the person who can approve

The person giving feedback is not always the person authorized to make the final decision.

At the start of the project, establish:

• Who gathers stakeholder feedback.
• Who resolves conflicting requests.
• Who gives final approval.
• Whether different deliverables need different approvers.

If several people must approve, record each required decision separately.

Do not mark the deliverable approved because one person responded positively while another required reviewer remains outstanding.

A useful coordination rule is to request one consolidated feedback set per round. Agree that process with the client rather than assuming it.

Keep revision requests specific

“Make it more modern” is not yet a clear implementation task.

Before revising, translate feedback into observable changes.

Separate corrections within the agreed deliverable from new requests.

An approval tracker records decisions. It does not automatically authorize additional work.

Copy-paste approval request

Hi [Name],

[Deliverable] version [number] is ready for review: [location].

Please review [specific scope] against [agreed criteria].

In particular, I need confirmation on:

- [Decision 1]
- [Decision 2]

Please send consolidated feedback or explicit approval by [agreed review date].

If that timing no longer works, let me know so I can review the next project steps.

If no review date has been agreed, propose one and ask whether it works.

Copy-paste approval confirmation

Hi [Name],

Thanks for confirming approval of [deliverable], version [number], covering [scope].

I have recorded the decision and will proceed with [next step].

[Outstanding item] remains separate and still needs confirmation.

Use this to reflect an actual client decision. If the reply is ambiguous, ask for clarification first.

“Looks promising” may mean the direction is right. It does not necessarily mean the deliverable is approved.

Handle conditional approval carefully

A client may say:

Approved, provided the headline is changed and the new photograph is used.

Record the exact conditions.

Then decide whether another review is needed under the agreed process.

If the conditions are unclear or require judgment, keep the status at Clarification needed or Changes requested until the next decision is explicit.

For straightforward conditions, you can record the completed changes and request confirmation where appropriate.

Avoid using “Approved” as a shortcut that hides unfinished requirements.

Use the tracker alongside client work in SelfManager

SelfManager can keep tasks, notes, comments, and supporting files together in dated tables.

For an approval workflow, you might:

1. Keep the deliverable and review instructions with the relevant table.
2. Add a dated task to request approval.
3. Record feedback in notes or comments.
4. Turn requested changes into working tasks.
5. Keep the final decision beside the deliverable reference.

For client access, SelfManager provides Owner, Admin, Member, and Viewer roles. Viewers can read the table but cannot contribute feedback through edits or comments. Choose access based on what the client needs to do.

The fields in this article are a template you can maintain in notes or a separate tracker. They are not a claim that SelfManager has a dedicated approval engine or electronic-signature workflow.

If you need formal document execution or an auditable approval process with specific compliance requirements, use a tool designed for that purpose.

Try SelfManager with one client deliverable: keep the review reference, requested changes, and next action beside the work.

Use files as review context

A PDF brief or document can help explain what the deliverable needs to satisfy. Screenshots can show a visual issue, while a recording can demonstrate behavior.

SelfManager supports documents and video alongside tasks. Its AI can use selected documents, images, and audio transcripts as context. Videos are available for playback but are not sent to the AI.

An AI-assisted review prompt might be:

Review these tasks, included comments, and documents.

List the recorded approval decisions, unresolved feedback, and next actions.

Distinguish explicit approval from positive feedback.

Do not infer approval from completed tasks or missing objections. Flag unclear versions and missing decision evidence.

Check the result against the client’s actual messages. AI should help organize the record, not decide whether the client approved something.

Close the approval loop

Before closing a deliverable’s approval record, check:

• The approved version is identifiable.
• The decision came from the required approver.
• The approval scope is clear.
• Conditions have been resolved or remain visible.
• The evidence is easy to find.
• The next implementation or delivery step is scheduled.

If a later change replaces the approved version, record what changed and whether fresh approval is required.

Keep the earlier decision in the history.

Use SelfManager to connect those decisions with the tasks that follow, so approval becomes a clear next step rather than another message to remember.

Frequently asked questions

What is a client approval tracker?

It is a record of deliverables awaiting client decisions. It identifies the version submitted, approver, review date, feedback, decision evidence, and next action.

How is it different from a follow-up tracker?

A follow-up tracker manages open requests and correspondence. An approval tracker focuses on whether a specific deliverable and version has been accepted, rejected, or returned for changes.

Does positive feedback count as approval?

Not necessarily. If the response does not clearly confirm the decision you requested, ask the authorized approver to clarify. Record what was actually said.

Should each revision have its own record?

Keep a review-history entry for each submitted version when revisions affect the decision. Maintain one current overview row per deliverable so the latest position remains easy to scan.

Can SelfManager manage client approvals?

You can use SelfManager to organize approval tasks, files, discussions, and decision records. It is a practical tracking workflow rather than a dedicated electronic-signature or formal approval system.