To write a follow-up email without sounding pushy, name the outstanding action, keep the real deadline, and explain what depends on the reply. Remove comments about the person's silence. For an Ops team waiting on an approval, a courteous email still needs to make the next step clear: what needs signing off, who needs to approve it, and when.

Here is a worked example, a reusable rewrite prompt, and a way to apply it to email drafts on your Mac.

Start with the decision you actually need

Imagine you are preparing a vendor data import. Jordan needs to approve the tax-code column in the vendor file before you can run it. You have already asked, and the import is waiting on that approval.

This fictional draft has the right details but carries some frustration:

Draft: “Hi Jordan, following up again on the vendor file. You still haven't approved it, and you're holding everyone up. I need your sign-off on the tax-code column by noon Thursday so I can run the import. Please get this sorted.”

Before editing the tone, identify what must survive the rewrite: Jordan's sign-off, the vendor file, the tax-code column, noon Thursday, and the import that depends on approval. Those details define the task.

“Following up again” and “please get this sorted” add pressure without making the request more specific. “You're holding everyone up” assigns blame where a description of the dependency would be more useful. You can remove those phrases without weakening the deadline.

Make the request easy to answer

Suggested rewrite: “Hi Jordan, following up on the vendor file. Could you approve the tax-code column by noon Thursday? I need your sign-off before I can run the import. Thanks.”

The revised email asks for approval explicitly. It does not ask Jordan to “take a look,” which could produce feedback when you need a decision. It also explains the reason for the deadline without speculating about why Jordan has not replied.

If you want Jordan to flag a problem, add: “If anything is blocking approval, could you let me know?” That is a deliberate addition to the request. It is useful when a missing answer might mean an unresolved issue, but you should choose to add it yourself.

These are editorial examples, not recorded outputs from a RewriteCmd test. Use them as a pattern for your own draft, with the actual file link and deadline filled in.

Tip

Keep a real deadline explicit. “Whenever you get a chance” is a poor substitute for “by noon Thursday” when another task depends on the answer. Soften the judgment about the person, while preserving the action they need to take.

Use a rewrite prompt that preserves the ask

“Make this more professional” leaves room for an AI rewrite to become wordy or vague. For an operational follow-up, describe the tone you want and the facts it must preserve.

Reusable prompt: “Rewrite this follow-up email in natural English. Keep it direct, courteous, and concise. Remove blame and comments about the recipient's lack of response. Preserve every name, file reference, requested action, deadline, time zone, and dependency. Keep approval requests as approval requests. Do not add facts, apologies, agreements, deadlines, commitments, threats, or escalation. Return only the revised email.”

Use the full draft, including the greeting and the sentence explaining the dependency. If the original says only “the file,” add the file name or link before rewriting. A writing tool cannot know which version your colleague needs to approve.

If you want an optional question about blockers, include that instruction separately. Otherwise, compare the output against the original and remove any new question or offer you did not intend to make.

Check meaning before you check polish

A smoother email can still change the work. Compare the draft and rewrite for these specific errors:

Read the message once as the recipient. Can you identify the file and answer the request without hunting through the thread? Add missing context from your records rather than asking the rewrite to invent it.

Apply the prompt to drafts on your Mac

If you regularly rewrite follow-ups, you can reuse the same instruction instead of composing a new prompt each time. The official RewriteCmd site describes custom rewrite instructions with keyboard shortcuts that act on selected text and replace it in the application you are using.

Save the prompt as a custom instruction and assign a shortcut. Start with the fictional draft above in an unsent message. Select the email text, trigger your instruction, and compare the replacement with the original facts before sending anything.

Keep the subject line separate if your selection covers only the message body. An unchanged, specific subject such as “Vendor file: tax-code approval” can make more sense within an existing thread than a new subject that breaks the conversation's context.

This is a suggested workflow, not a compatibility test of your mail app. Check that the selection and replacement cover the intended text and preserve links and paragraph breaks. Keep a copy of the original draft until you have checked the result.

When the deadline has already passed

Once a deadline is missed, decide what you need next before rewriting. Do you need a revised approval time, confirmation of a blocker, or a different person to handle the request? Those are operational choices, not tone adjustments.

For example, if you now need a revised time, write: “Hi Jordan, the noon Thursday approval deadline has passed, and the vendor import is still waiting on sign-off. When can you approve the tax-code column?” Use that wording only when it matches the facts. Do not let a rewrite invent a new deadline or an escalation path.

Rewrite your next follow-up with RewriteCmd

If this is a recurring part of your Ops work, explore RewriteCmd to rewrite selected text on your Mac with a keyboard shortcut. Start with the prompt above, try it on a draft, and check that the action, owner, and deadline still say exactly what you mean.