Pending approval can stall a project, delay a purchase, or hold up a decision that affects your workday. The best follow-up is calm, specific, and easy to act on.
Good follow-up is not about pressure. It is about making it simple for the reviewer to respond, approve, or tell you what is missing.
Understand what is actually pending
Before you send a message, identify the exact approval stage. A request may be waiting on a direct manager, a finance reviewer, a legal check, or a system queue.
That distinction matters because each reviewer needs different information. A manager may want business context, while finance may need a cost breakdown or a budget code.
Check the original submission for missing fields, attachments, or required sign-offs. Many delays happen because the request is not truly pending approval; it is incomplete.
Confirm the approval owner
Find the person or team responsible for the next action. If the request moved through a workflow, confirm whether the current owner is the final decision-maker or just one step in the chain.
Use the system record, not assumptions. In many organizations, approvals reroute when someone is out of office, and the visible status can be misleading.
Check the status before you reach out
Review the platform, ticketing tool, or email thread for any status notes. A brief internal comment may already explain the delay.
If the request shows “in review,” “awaiting documents,” or “returned for revision,” your follow-up should address that specific state. This keeps the message focused and avoids asking for information they already gave you.
Choose the right timing
Timing changes how your follow-up is received. A message sent too early can feel impatient, while one sent too late can let the request drift.
Match your follow-up to the urgency of the request and the normal pace of the process. A routine expense approval may need a few business days, while a time-sensitive contract may need a same-day check-in.
When possible, follow the cadence the organization already uses. If approvals usually take three days, a reminder on day four is reasonable.
Use milestones, not emotion
Base your follow-up on a concrete milestone. For example, send a reminder after the reviewer returns from travel, after a meeting where the request was discussed, or after a deadline passes.
This makes your timing easier to justify. It also keeps the message grounded in process rather than frustration.
Avoid over-messaging
Repeated pings can slow the response you want. If someone has not answered, give them a practical reason to reply instead of sending the same reminder again.
Space follow-ups out unless the approval is blocking a critical deadline. A well-timed message with complete details usually works better than a stream of short nudges.
Make the message easy to act on
The best follow-up messages remove friction. The reviewer should be able to understand the request, see what is needed, and respond quickly.
Keep the subject line clear. Use a label that matches the request, such as “Approval needed for Q3 training budget” or “Pending sign-off: vendor contract revision.”
In the body, state the request, the current status, and the needed action in the first two lines. Do not bury the point under background details.
Include the essentials only
List the item awaiting approval, the date it was submitted, and the deadline if one exists. Add the amount, project name, or document version when those details matter.
Attach or link the relevant file again if the reviewer may need it. A direct path to the document saves time and reduces back-and-forth.
Use one clear call to action
Ask for one specific next step. For example, ask them to approve, reject, or confirm whether they need more information.
Multiple requests in one note can create hesitation. A simple action prompt is easier to answer and less likely to be ignored.
Adjust your tone to the context
Tone can influence whether your follow-up feels professional or pushy. The goal is to sound respectful, steady, and solution-oriented.
Use neutral language when the approval is routine. When the item is urgent, be direct without sounding accusatory.
A phrase like “I wanted to check whether you need anything else from me to move this forward” often works better than “Why is this still pending?”
Stay courteous under pressure
If the delay is affecting your timeline, acknowledge that clearly without blame. You can note that a deadline is approaching while still assuming good intent.
This approach keeps the relationship intact. It also makes it more likely that the reviewer will tell you the real reason for the hold-up.
Match the formality of the channel
Email should usually be more formal than chat. A Slack message can be shorter, but it still needs a complete request.
If the reviewer prefers phone calls, use that channel for urgent approvals. Some approvals move faster when the conversation is live and the decision can be made on the spot.
Use context to strengthen the reminder
Context helps the reviewer prioritize your request. A follow-up that explains why the approval matters is more effective than a generic “just checking in.”
Show the practical impact without exaggeration. Explain whether the pending approval is blocking a shipment, delaying onboarding, or affecting a client commitment.
If the item is not urgent, say so. That signals maturity and helps the reviewer decide where it fits in their queue.
Connect the approval to a business outcome
Reviewers respond faster when they understand the consequence of delay. For example, an approved purchase order may be needed to lock in a vendor price before it changes.
That kind of detail can justify priority without sounding dramatic. It also helps the reviewer defend the approval internally if needed.
Reference prior discussion when relevant
If the approval was already discussed in a meeting, mention the date and the agreed next step. This gives the reviewer a quick memory cue.
Use the reference sparingly. The goal is to support the decision, not to reopen a debate that has already been settled.
Follow up through the right channel
Channel choice affects response speed. Some approvals move fastest by email because there is a record, while others move faster in chat because the reviewer sees it immediately.
Use the channel that fits the workflow. If the approval system sends automatic notifications, your follow-up should complement that system rather than duplicate it blindly.
For high-priority items, combine channels thoughtfully. A brief chat message can alert the reviewer, while an email preserves the details.
Email works best for traceable requests
Email is useful when the approval needs documentation. It creates a record of the request, the date, and any response.
Keep the email short and structured. A reviewer should be able to scan it in seconds and understand what action is needed.
Chat works best for quick nudges
Chat is effective when the reviewer is already active in that tool. It works well for a short reminder or a request to confirm whether they saw the email.
Do not overload chat with attachments or long explanations. Use it to prompt action, then move detailed information into the original thread if needed.
Phone calls are useful for urgent blockers
Call when the delay has real operational consequences. A live conversation can clear confusion faster than a chain of messages.
Prepare before you call. Know the request, the deadline, and the exact decision you need so the call stays efficient.
Escalate only when the process justifies it
Escalation should be a process tool, not a threat. It is appropriate when the approval is stuck, the deadline is real, and the normal follow-up path has failed.
Before escalating, verify that the request is complete and that the reviewer had a fair chance to respond. Escalating an incomplete request often creates more delay.
When escalation is appropriate, keep it factual. State the date submitted, the reminders already sent, and the impact of the delay.
Escalate with evidence, not frustration
Use a concise timeline. This helps the next person understand the situation without reading the full thread.
Focus on the process failure, not the person. That keeps the escalation professional and reduces defensiveness.
Know when to involve a backup approver
Some workflows allow a delegate or secondary approver. If the main reviewer is unavailable, a backup can prevent the request from stalling.
Confirm that the backup has authority before routing the request. A workaround only helps if it is valid within the process.
Handle silence with a practical sequence
Silence does not always mean rejection. The reviewer may be busy, traveling, or waiting for another input.
Create a simple follow-up sequence so you do not improvise each time. A first reminder can be light, a second can add context, and a third can ask for a direct yes, no, or timing update.
Each message should add new information. Repeating the same note word for word makes the request easier to ignore.
First follow-up: polite reminder
The first reminder should assume the reviewer simply missed the request. Keep it short and helpful.
Include the original submission date and the item name. That gives enough context without making the message feel heavy.
Second follow-up: clarify the blocker
If there is still no answer, ask whether anything is missing. This invites a response even if the reviewer is not ready to approve.
You may discover that the delay is caused by a missing attachment, an unclear cost center, or a question that was never answered.
Third follow-up: request a decision or timeline
At this stage, ask for a clear next step. A simple request for either approval or a date by which they can respond is reasonable.
This is especially useful when the approval affects a launch date, invoice payment, or customer delivery. The reviewer may not be able to decide immediately, but they can usually give a timeline.
Tailor the follow-up to the approval type
Different approvals need different framing. A hiring approval, a budget approval, and a legal approval each have their own concerns.
When you tailor the message, you show that you understand what matters to the reviewer. That increases the chance of a quick response.
Budget and expense approvals
For financial approvals, include the amount, purpose, and budget source. If the request fits within an approved plan, say so clearly.
Finance reviewers often care about policy compliance and documentation. Make it easy for them to verify both.
Contract and legal approvals
For contracts, identify the version, redlines, and any outstanding clause. Legal reviewers need to know what changed since the last draft.
Point out any deadline tied to the agreement, such as a renewal date or vendor start date. That helps them assess urgency without reading the entire file first.
HR and hiring approvals
For hiring or headcount approvals, explain the role, the business need, and the timing. If the position supports revenue, service levels, or compliance, say that plainly.
Hiring approvals often compete with other priorities, so specificity matters. A clear business case can move the request ahead of generic staffing asks.
Use documentation to reduce back-and-forth
Documentation speeds up approval because it removes uncertainty. When the reviewer has everything in one place, they are less likely to pause the request for clarification.
Keep a clean record of what was submitted, when it was sent, and what responses were received. This record helps if the approval later needs to be audited or revisited.
If you revise the request, label the new version clearly. Confusion over file versions is a common reason approvals stall.
Create a simple approval trail
Save the original request, follow-up dates, and any comments from the reviewer. A short timeline can be enough for internal tracking.
This is useful when multiple people touch the same request. It prevents duplicate follow-ups and keeps everyone aligned on the current state.
Clarify changes after resubmission
If the reviewer asked for edits, highlight what changed. Do not make them compare every line to find the difference.
A short note like “Updated the budget amount and added the missing vendor quote” can save time and reduce friction.
Protect the relationship while pushing for action
Approval follow-up is part persistence and part relationship management. People are more responsive when they feel respected and not cornered.
Show that you value their time. A concise message, a clean file, and a reasonable cadence communicate professionalism.
If the reviewer is consistently slow, look for a process fix instead of treating every delay as a personal issue. A better workflow often solves the problem more effectively than repeated reminders.
Offer help, not pressure
Sometimes the fastest way forward is to remove a small obstacle. Offer to resend the document, provide a summary, or walk through the request in five minutes.
This makes the reviewer’s job easier. It also keeps the tone collaborative.
Recognize the reviewer’s constraints
Approvers often juggle many decisions at once. Acknowledging that reality can make your message more effective.
You do not need to over-explain their workload. A simple, respectful note is enough to show awareness.
Build a reusable follow-up system
A strong follow-up process saves time across every approval request. Instead of writing each reminder from scratch, use a structure that you can adapt quickly.
Create templates for routine approvals, urgent approvals, and escalation notes. Templates keep your messaging consistent and reduce the chance of forgetting key details.
Track which wording gets responses in your organization. Small adjustments in phrasing, timing, or channel can improve results over time.
Standardize the information you send
Always include the same core items where relevant: request name, date submitted, current status, deadline, and needed action. That consistency makes your messages easier to scan.
If your team uses a shared approval process, align the template with that workflow. The less the reviewer has to interpret, the faster they can respond.
Review what slows approvals down
Look for recurring causes of delay. Missing attachments, unclear ownership, and vague subject lines are common culprits.
Once you know the pattern, you can prevent the delay before the follow-up is needed. That is often more effective than any reminder message.
Write follow-ups that get a response
Effective follow-up on pending approval is specific, timely, and easy to process. It respects the reviewer’s time while making the next step obvious.
The strongest messages do not try to persuade with pressure. They make approval simple by removing confusion and reducing effort.
When you combine clear context, the right channel, and a steady cadence, pending approval stops becoming a bottleneck. It becomes a manageable part of the workflow.