Meeting Follow-Up Emails in Australian English: Phrases That Get Action

Meeting follow-up emails written by non-native speakers tend to fail in Australian workplaces for three overlapping reasons: the tone is too formal, ownership of action items is buried in passive voice, and the opening signals "template" rather than "person." Australians read through formality quickly and respond to directness. If your follow-up reads like a memo from 1994, the person at the other end will skim it and move on.

Subject Line Conventions

Australian subject lines are functional. They say what the email is about, not what it aspires to achieve.

A subject line like "Follow-Up Regarding Today's Discussion" says almost nothing. Which meeting? Which discussion? Australians receive many emails and will often triage by subject line alone. If yours is vague, it gets opened last — or not opened before the deadline passes.

Specific subject lines work better:

• "Sprint planning recap — actions for this week"
• "Follow-up: procurement review 14 May — your items due Friday"
• "Quick recap from this morning's check-in"

Note the lowercase formatting. Australian professionals rarely capitalise every word in a subject line. Title case reads as slightly formal or American. Sentence case is the norm in most workplaces. (This is covered in more detail in the article on Australian vs British English at work.)

Avoid subject lines that imply urgency you haven't earned. "URGENT: Action Required Following Today's Meeting" when it isn't urgent will irritate people. Save urgency markers for situations that genuinely warrant them.

Opening Line Norms: Australians Hate Overly Formal Openers

This is where a lot of non-native writers lose the room before the email even starts.

Openers like "I trust this email finds you well" or "I am writing to follow up on the matters discussed during our meeting held earlier today" are technically correct but they signal to an Australian reader that what follows will be bureaucratic and slow. The instinct to be formal out of respect is understandable — it comes from educational contexts and cultures where seniority and register matter. In Australian workplaces, that instinct works against you.

Australian email culture is egalitarian. Your manager, your CEO, and the graduate you're following up with are all on first names. The opener should sound like a person, not a form letter.

Good Australian openers for a follow-up email:

• "Thanks for a productive session this morning."
• "Good to get through everything today — here's a quick recap."
• "Cheers for everyone's time this afternoon."

If the meeting was difficult or inconclusive, you can still open warmly without being falsely cheerful: "Thanks for your time today — a few things to note from our discussion."

What you should not do: open with a long contextual sentence re-establishing the entire history of why you are writing. The recipient was in the meeting. They know. Get to the point.

Action Items: Own Your Items, Name Others Clearly

This is the most common structural failure in follow-up emails from non-native speakers, and it directly affects whether things get done.

Passive voice is natural in many languages and in formal English registers. But "It was agreed that the report would be submitted by Friday" does not tell anyone who is doing what. In a follow-up email, that ambiguity is expensive. People read their name and skip to the next sentence. If their name isn't there, they assume it belongs to someone else.

Australian workplace culture — particularly in engineering, project management, and consulting — expects action items to be owned explicitly.

The pattern is consistent: name the person, state the action, give the deadline. That structure is not rude. It is useful.

For your own items, use first person directly: "I'll send the updated scope to the team by Wednesday." This reads as confident and accountable. "I will endeavour to forward the documentation" reads as evasive, even if that wasn't the intention.

Follow-Up Timing and Tone

Send your follow-up within two to four hours of the meeting ending, or by end of day at the absolute latest. Same-day follow-ups communicate that the meeting mattered and that you are on top of your commitments. A follow-up sent the next morning is still fine, but same-day is the gold standard.

If the meeting ran at the end of the day — a 4:00 pm Friday call, for example — sending the recap Monday morning is completely acceptable. Sending it at 11:00 pm Friday is not. Australians generally respect work-life boundaries. A late-night email puts low-grade pressure on the recipient to respond, which is not the impression you want a follow-up to create.

For tone: keep it warm but brief. You are writing a functional document, not a thank-you letter. Three to five sentences of context, a clean list of action items, and a closing that makes it easy to respond. That's the format.

If there were unresolved items or decisions deferred to the next meeting, name them explicitly: "We didn't land on the deployment window — I'll put it on the agenda for Thursday." Flagging the gap is more useful than pretending the meeting was fully conclusive.

Directness Without Being Pushy: The Australian Balance

Australian directness is not bluntness. There's a meaningful difference between the two, and it matters in follow-up emails specifically.

Blunt: "The vendor report is overdue. Please submit immediately."

Direct: "The vendor report was due last Friday — can you get it to me today?"

The direct version states the fact and makes a specific, reasonable request. The blunt version sounds like a reprimand. Neither version hedges or softens with excessive qualifiers. The difference is in the closing — a question rather than an imperative — which keeps the register collegial without making the ask ambiguous.

Australians are also attuned to passive-aggressive politeness. Phrases like "As previously discussed" or "As per my last email" are understood by most Australians as mild escalations. Use them if escalation is genuinely warranted. Don't use them out of habit or because they feel more formal.

If you need to chase an action item someone has missed, be direct but not accusatory: "Hey Liam, just checking in on the supplier quote — do you have an update?" That's it. No lengthy re-establishment of context. No implied criticism. Just the question.

A Full Example Follow-Up Email

Subject: Sprint planning recap — actions for this week

Hi all,

Thanks for a good session this morning. Here's a quick recap of what we landed on.

**Actions this week:**
- Priya: finalise the scope document and share with the team by Wednesday
- Liam: confirm the deployment window with infrastructure — Thursday EOD
- Wei: review the API dependencies doc and flag any blockers before Thursday's standup
- All: review the updated sprint board before tomorrow morning

**Deferred:**
- Vendor contract review — I'll reach out to them today and update the team early next week

Any questions or corrections to the above, let me know.

Cheers,
Priya

A few things worth noting in this example: no formal greeting ("Dear team" is unnecessary), the opener is one line, the action items use names rather than roles, deadlines are specific, and the deferred item has an owner and a timeline. The sign-off is "Cheers" — standard in most Australian workplaces, even for internal professional correspondence.

In Practice: Priya's Sprint Planning Follow-Up

Priya is an Indian-born project manager at a mid-sized engineering consultancy in Perth. She's been in Australia for four years and is confident in spoken English, but still catches herself defaulting to formal written patterns from her previous work in Bangalore — where hierarchical register and careful hedging were important signals of professionalism.

After a sprint planning meeting with her five-person team, she drafts her follow-up. Her first draft opens with: "I am writing to summarise the key outcomes and action items arising from today's sprint planning session." She reads it back and knows something feels off, but isn't sure what.

The issue is the opener. It re-establishes context the recipient already has, it's in formal register, and it delays the useful content by a full sentence. In an Australian office, her team will read that sentence and mildly roll their eyes before getting to the actual content.

Her revised opener: "Good session this morning — quick recap below."

Seven words. Same information. The tone shift changes how the entire email reads.

She also catches herself writing "It would be appreciated if all team members could review the attached sprint board prior to Thursday's standup." The passive construction diffuses ownership and the register is stilted. She replaces it with: "Can everyone check the sprint board before Thursday?" — direct, clear, and easier to action.

The final email takes two minutes to write and lands in inboxes within an hour of the meeting ending. Two team members respond the same afternoon to confirm their actions. She gets the vendor update she needed by end of week.

The pattern Priya follows isn't complicated: functional subject line, short opener, named action items with deadlines, one deferred item with an owner. That structure transfers across any meeting type — client calls, internal reviews, stakeholder check-ins.

For a deeper look at how written register varies by context in Australian professional settings, the article on writing a tenancy dispute email in Australian English covers a different but equally context-specific register.

How to Self-Check Before You Send

1. Does the subject line name the meeting and the purpose? If someone sees it on a phone screen with no preview text, will they know what it's about?
2. Does the opener get to the point within the first sentence? If your first sentence contains the words "I am writing to," cut it and start with the second sentence.
3. Is every action item named to a person? Read through and check that no task is unassigned. If it's unassigned, it won't get done.
4. Does each action item have a deadline? "Soon" and "ASAP" are not deadlines. A day of the week or a specific date is.
5. Have you used first person for your own items? "I'll send the report by Wednesday" is better than "The report will be sent."
6. Does the closing make it easy to reply? A question ("Any questions, let me know?") or a simple "Cheers" is enough. You don't need a formal sign-off paragraph.

If you want a second opinion on your writing before you send, this is exactly the kind of check that Local Tone's review cycle can help with — getting feedback that goes beyond grammar into whether the tone actually works for your audience.

Frequently Asked Questions

Is "Cheers" too informal for a work follow-up email in Australia?

No. "Cheers" is standard sign-off in most Australian professional workplaces, including formal industries like engineering, law, and finance. It is not casual in the way it might read to a North American audience — in Australian English it simply means "thanks" or "goodbye," and using it signals that you understand the local register. If you are writing to a very senior external contact for the first time, "Thanks" or "Kind regards" is also fine. But within an established team, "Cheers" is completely appropriate and in fact more natural than "Best regards" or "Sincerely."

How long should a meeting follow-up email be?

As long as it needs to be, and no longer. For a standard internal meeting, the follow-up should fit on one screen — roughly five to fifteen lines including the action item list. If the meeting covered complex decisions or had many participants, a slightly longer recap is appropriate, but you should still lead with the action items rather than burying them after a narrative summary. Australians tend to read action items first, context second. Structure your email accordingly.

What if I need to follow up on something that wasn't resolved in the meeting?

Name it explicitly in a "Deferred" or "Outstanding" section, assign an owner to resolve it, and give a date for when it will be revisited. Do not omit unresolved items — leaving them out implies they were resolved. Something like: "Budget approval — awaiting sign-off from finance, expected by 20 May" is clear, honest, and forward-looking. If you are the one who needs to chase it, say so: "I'll follow up with finance and update the team by Monday."

How Local Tone Helps

Follow-up emails are short, but they carry a lot of professional weight — they are the documented record of what was agreed, and they shape how your colleagues read your reliability and communication style. Local Tone lets you paste a draft and get feedback on whether the tone, ownership language, and phrasing actually land for an Australian audience. It goes beyond grammar to flag the specific patterns — passive voice for action items, over-formal openers, hedged requests — that hold back non-native writers in Australian workplaces. If you write follow-ups regularly, it's worth running a few through to calibrate your defaults.