Six steps, a reminder you can copy, a stage table and a pre-send checklist, so the fourth chase in March reads like the first one in January.
To keep audit reminder emails on brand, fix the reminder stages once (nudge, deadline, escalation), write one skeleton per stage, and draft every reminder from a skeleton rather than from a blank screen. Pidgy drafts the reminder in your firm's voice from the thread and the open items, and a person reads it and presses send. The timing then belongs to software rather than memory, which is what stops reminders turning terse in week three of busy season.
Reminders go off brand at the moment of writing, not at the moment of planning.
Week three of busy season, one client, three seniors. The first chases with two warm paragraphs and a smiley, the second sends a one-liner with "URGENT" in the subject, and the third forgets entirely. The client reads all three and concludes the firm does not talk to itself. None of them decided to go off brand; each wrote under pressure with no standard to fall back on. The fix is to take the writing decision out of the moment.
Decide the standard once, then let the drafting and the timing run from it.
Three stages cover almost every PBC chase. A nudge after three working days of silence, a deadline reminder two days before the date, and an escalation the day after the date passes. Write those gaps down; they are the brand as much as the wording is.
Each skeleton has the same bones. Thank the client for what has arrived, list what is still open with PBC item numbers, give one date, offer a way out if the date is impossible, and sign off. Only the register changes between stages, from friendly to plain to formal.
Seniors send nudges, managers send deadline reminders, and the partner is copied on escalations only. Escalate by changing the recipient and the signatory, never by sharpening the same email to the same bookkeeper.
This is where Pidgy earns its place. It drafts the reminder from the thread and the open items in your own voice, in one of four tones that map onto the three stages. The senior reads it, corrects an item number if needed, and presses send.
Pidgy tracks who owes you a reply and brings the thread back with a chase drafted when it stalls, so the day-three nudge does not depend on the senior's memory. For the formal request list, Alkmist's smart follow-up, a separate product, nudges the client on a set cadence through its portal.
Pull the sent chases for two clients and read them in order, looking for tone drift between seniors and reminders that got no reply. Tighten the skeleton, not the people.
The skeleton from step 2 with real items in it, drafted by Pidgy in the plain tone and sent by the manager.
FY25 audit, two items due Friday 13 March
Hi Priya,
Thanks for the payroll reconciliations yesterday, those are in. Two items are still outstanding ahead of Friday's fieldwork start, the year-end bank statements for the euro account (item 6) and the signed related-party schedule (item 15).
If both reach us by Friday we stay on plan. If the related-party schedule needs another week, let me know today and I will move that section to the second week.
Best regards,
Marta Ruiz, Audit Manager
It thanks before it asks, names the items by number, gives one date and one way out, and carries the manager's name because this is the deadline stage. No apology for chasing, no exclamation mark. The senior's nudge four days earlier used the same bones in a warmer register.
Keep this table next to the skeletons so nobody has to guess the register.
| Stage | When it goes | Register and signatory | Subject line shape |
|---|---|---|---|
| Nudge | Three working days after the last reply | Friendly, from the senior | "FY25 audit, quick check on three items" |
| Deadline reminder | Two working days before the agreed date | Plain, from the manager | "FY25 audit, two items due Friday 13 March" |
| Escalation | The working day after the date passes | Formal, from the manager, partner and finance lead on copy | "FY25 audit, overdue items and revised timetable" |
Four habits worth banning in the skeleton itself.
A new thread strips the client of context. Reply in the thread they have been answering, so the history and the item list travel with the reminder.
Without item numbers the client has to open the list and guess. Name each item and its number every time, even when there is only one.
"Sorry to chase" tells the client the request is optional. The firm has a timetable; say what is due and by when.
A sharper email to the same bookkeeper changes nothing except the relationship. Change the recipient and the signatory instead.
Pidgy is an inbox agent for Outlook and Gmail that drafts reminders in your voice, flags stalled threads and leaves the send button to you.
It reads both mailboxes as one and ranks what needs a reply, so the senior sees the client's answer before the noise. Mail is grouped into engagement projects, and one Inbox Health score tells the manager if client correspondence is under control. Everything is hosted in the EU, never used to train a model, and nothing is sent until a person clicks. Pidgy has a 7-day free trial with no credit card needed.
Thirty seconds, every time, whoever drafted it.
More on client email for audit and accounting teams.
Pidgy drafts each chase in your firm's voice, flags the threads that have gone quiet, and waits for your click. The free trial is open below.