Follow-ups are not nagging when they are structured, factual, and tied to agreed milestones.
11 min readWhen to follow up
| Situation | Wait time | Then |
|---|---|---|
| Proposal sent | 3 business days | Gentle bump |
| Feedback needed | 2 business days past due | Blocker note |
| Invoice due | Day after due date | Payment reminder |
| Invoice overdue | 7 days | Firmer reminder + pause rule |
Set calendar reminders so you do not forget or panic-send at midnight.
SHIELD email frame
- State the fact (invoice #, deliverable name)
- Highlight the agreed date
- Include one clear ask ("approve by Friday")
- Explain impact ("I pause next phase until payment")
- Link to original thread
- Document (save every send)
Templates
Approval nudge
Hi [name], checking in on [deliverable] sent [date]. Need your feedback by [date] to hit [milestone]. Reply here or I can send a Loom walkthrough.
Invoice reminder (day 1 overdue)
Hi [name], invoice [#] for [amount] was due [date]. Could you confirm payment status or expected date? Happy to resend the PDF.
Invoice reminder (day 7+)
Hi [name], invoice [#] is now [X] days overdue per our terms. I will pause new work on [date] until settled. Let me know if there is a blocker I can help with.
See chasing overdue invoices for full ladder.
Proposal follow-up
Hi [name], following up on the proposal sent [date]. Valid until [date]. Should I hold the start slot or adjust scope?
Tone rules for Filipino VAs
- No "sorry sorry" loops. One "thanks" is enough.
- No passive aggression. Facts only.
- Same timezone note if they are US/EU: "your Tuesday morning"
- Phone-first read: short paragraphs, bold dates if your client reads on mobile
Common mistakes
| Mistake | Fix |
|---|---|
| New thread every bump | Client loses context |
| Emotional walls of text | Use three sentences max |
| No agreed deadline originally | Add response windows to scope |
| Following up once then giving up | Use a ladder, document tries |
How Salag helps
- Agreement Builder: put response windows in scope.
- Freelance Readiness Checker: payment terms before you chase.
- Scope Creep Detector: when follow-ups are really new scope.
Move safer. Not faster.
In short
A follow-up is not nagging when it is factual: what you need, when you asked, what date you agreed, what happens next.
Keep it short. Same email thread. No guilt paragraphs.
Common questions
A follow-up is not nagging when it is factual: what you need, when you asked, what date you agreed, what happens next. Keep it short. Same email thread. No guilt paragraphs.
Restate what you need, the date you sent it, and the agreed deadline. Stay factual, not emotional.
Short English, same thread as original ask, polite tone. Global clients respect clarity over long apologies.
Put response windows in scope when possible (e.g. feedback within 3 business days). Makes follow-ups fair.
If they call you pushy, point to the milestone date you both agreed. Offer a call if text is unclear.
State facts, Highlight deadline, Include next step, Explain pause if needed, Link to original, Document every send.
After two polite follow-ups on payment or approval. Escalate means firmer language and pause rules, not rage.
Yes. Follow-ups are documentation. They show you asked professionally.
Templates and late fee tools support payment follow-ups without awkward guessing.
Email templates, calendar reminders, invoice tracker, late fee calculator.
Two minutes per follow-up if you use a template.
Retainers: weekly recap nudges. Projects: milestone and invoice follow-ups.
If they will not confirm scope or payment, pause work per your agreement. Follow-up documents that pause.