How to Write a Polite Approval Reminder Email

A proposal has been sent. The work is ready to begin. Your team has held capacity, the client has said they are interested, and then the decision disappears into their inbox. This is the moment to write a polite approval reminder - not because you want to chase someone, but because an unanswered decision creates...

Dariusz Mazur · Nov 7, 2026

A proposal has been sent. The work is ready to begin. Your team has held capacity, the client has said they are interested, and then the decision disappears into their inbox. This is the moment to write a polite approval reminder - not because you want to chase someone, but because an unanswered decision creates real uncertainty for both sides.

For a small agency, unclear approvals cause more than minor admin friction. They affect scheduling, staffing, supplier commitments, launch dates, and cash flow. The client may simply be busy, waiting on an internal stakeholder, or unsure what you need from them. A good reminder makes the next step easy to understand and easy to take.

Why approval reminders often get ignored

Most reminders fail for a simple reason: they ask the client to do too much thinking. “Just following up” tells them very little. Following up on what? What decision is needed? What happens after they reply? Is there a deadline that matters, or is it merely an agency preference?

The opposite problem is pressure. A message that implies the client is holding you up can damage a relationship, particularly when the delay is caused by their procurement process, their leadership team, or a competing priority they have not explained. You need to be clear without making them defensive.

The strongest approval reminders do three things. They name the item awaiting approval, state the specific decision or response required, and explain the practical impact of timing. That is enough. You do not need an elaborate email sequence or a dramatic deadline.

Write a polite approval reminder with one clear ask

Before drafting the email, define what “approval” means in this situation. A client might need to approve a project proposal, a revised scope, a homepage design, a budget increase, a content plan, or a change to a delivery date. Those are different decisions and should not be bundled into one vague request.

If you are waiting on several things, separate them. A client can usually answer “yes, proceed with the revised estimate” quickly. They may delay if the same email also asks them to choose between three design routes, confirm copy, and schedule a kickoff meeting.

Your message should answer four questions in a few lines:

• What document, deliverable, or change are you referring to?
• What exact approval or decision do you need?
• What should the client do to provide it?
• What timing consideration should they know about?

The timing point should be truthful and proportionate. “If we can confirm by Thursday, we can keep the planned Monday kickoff” is useful. “Please approve urgently” is not. If there is no meaningful deadline, do not invent one. Ask for a status update instead.

Start with context, not an apology

Avoid opening with “Sorry to bother you.” You are not interrupting at random. You are managing an active commercial conversation and trying to keep agreed work moving.

A better opening reconnects the client to the decision: “I’m following up on the revised website proposal we sent on Tuesday.” If you discussed it in a call, mention that: “Following our conversation last week, I wanted to check whether you have approval to proceed with the updated scope.”

This is especially helpful when the recipient has a crowded inbox or was not the original signer on the proposal. Context lets them forward the email internally without having to explain it from scratch.

Make the reply easy

Do not make a busy client search for an attachment, reread a long proposal, and compose a formal response if a simple confirmation will do. Tell them exactly what you need.

For example: “If you are happy to proceed, please reply ‘approved’ and we will schedule the next steps.” If approval requires a signed document or a purchase order, say so plainly. If they are still reviewing, give them a lower-friction option: “If the decision is still with your team, a rough timing update would help us plan our schedule.”

That second route matters. Silence is not always a no. It is often an unresolved internal process. A polite reminder gives the client a way to be honest without feeling cornered.

Approval reminder email templates

Use templates as a starting point, then add the details that prove you know the account. The client should feel that this message belongs to the work in front of them, not to an automated campaign.

When a proposal is awaiting approval

Subject: Approval needed to schedule the [project name] kickoff

Hi [Name],

I’m following up on the [project name] proposal sent on [date]. To reserve the planned kickoff date of [date], we need confirmation that you are happy to proceed with the scope and fee outlined.

If you are ready, please reply to confirm approval. If it is still under internal review, could you let me know when you expect a decision? That will help us plan the team’s availability accurately.

Thanks, [Name]

This works because it connects approval to a real operational consequence without claiming that the client must decide immediately.

When a design or deliverable needs sign-off

Subject: Feedback or approval on [deliverable]

Hi [Name],

Could you please confirm whether the [deliverable] is approved to move into [next stage]? We shared the latest version on [date], including the changes discussed around [specific item].

A reply with “approved” is enough for us to proceed. If there are remaining changes, please send them by [date] so we can review their effect on the schedule.

Best, [Name]

The phrase “review their effect on the schedule” is deliberate. It makes scope and timing visible without turning the email into a warning.

When a scope change is holding up work

Subject: Decision needed on the revised scope

Hi [Name],

I’m checking in on the revised scope and estimate for [project]. We need your decision on the [specific change] before we continue with [affected work].

Please let us know whether you would like to approve the revision, keep the original scope, or discuss an alternative. Once we have your direction, we can confirm the appropriate next step and timing.

Thanks, [Name]

Giving clear options is useful when the client may not be comfortable approving a cost increase but has not yet said so. It opens a business conversation rather than forcing a binary response.

Choose the right follow-up timing

There is no universal waiting period. For a simple design approval tied to work already in progress, two or three business days may be reasonable. For a six-figure proposal involving finance or legal review, a week or more may be appropriate. Consider the value and complexity of the decision, the client’s stated process, and the consequence of delay.

If you have already sent one reminder, change the message rather than resending the same wording. Offer a short call, ask whether the decision has moved, or confirm whether the project should be paused. Three identical “checking in” emails rarely create clarity.

A practical escalation might look like this: first, send a direct reminder with the required decision. Next, ask for a timing update and mention the scheduling implication. Finally, if there is still no response, state that you will release tentative capacity or pause the affected work unless you hear otherwise. Only say that if you will actually do it.

Keep the decision visible inside your agency

The client-facing email is only half the process. The deal did not die because the first message was imperfect. It may die because nobody remembers to send the second one, or because the team cannot tell whether the client approved a previous revision.

A spreadsheet or calendar can be enough when you have a small number of live opportunities and one person owns every follow-up. Notion can work if your team reliably updates a shared client page after calls and emails. An existing CRM may be the right place if it already gives your team a dependable view of pending decisions and next actions.

The problem appears when important approvals are scattered across inboxes, meeting notes, and people’s memories. At that point, a dedicated follow-up workflow can help. In AwiFin, for example, you can record what happened, identify what is waiting, set a next action and due date, prepare a message for review, and record the outcome. It is not a replacement for project delivery tools or a full CRM. Its value is making sure a client decision does not become morning inbox guesswork.

Know when to stop chasing

A polite reminder should preserve the relationship, not turn into an endless pursuit. If a client repeatedly misses agreed decision dates, acknowledge the reality: “As we have not received approval, we will pause this item and revisit it when your team is ready.” That gives you a clean record and protects your team from planning around a decision that does not exist.

The goal is not to force every client to say yes. It is to replace ambiguity with an answer, a realistic date, or a conscious pause. That is what lets an owner-led agency protect its capacity while remaining professional and easy to work with.