Faculty email you stop dreading

What you’re making

A reusable set of faculty emails in your own voice. The invitation, the confirmation with a materials request, the disclosure chase, the first reminder, the awkward third follow-up, and the one where you have to tell someone their slides need to change.

Nobody puts this on a professional development plan, and it’s where a genuinely large chunk of a coordinator’s week goes. Forty emails a week at four minutes each, and by the tenth reminder your patience is gone and the tone slips.

What to have open

Five emails you have actually sent. That’s the whole trick. There’s a worksheet for this if you’d rather fill in a form than start from nothing.

Generic AI email is easy to spot. The relentless enthusiasm, the “I hope this finds you well”, the thanking people twice. Faculty who get it will think less of you. Your own sent folder is the fix, and it takes thirty seconds to gather.

The prompt

Below are five emails I have actually sent to faculty. Read them and describe my writing voice back to me: how I open and sign off, sentence length, how direct I am, how I handle deadlines, how formal I am, and what I never do.

Then turn that description into a short set of instructions you could follow to write in my voice, and give it to me so I can save it and reuse it.

[paste 5 real sent emails]

Save what it gives you. That’s your voice profile, and you’ll paste it at the top of every request from now on. Better still, keep it in a project so you never paste it again.

Write in my voice, using this profile:
[paste your saved voice profile]

Write [an invitation / a disclosure reminder / a second follow-up / a materials deadline chase] to [name and role].

Facts to include:
- [activity name, date, format]
- [what I'm asking them to do, exactly]
- [the deadline, and what happens if it's missed]
- [anything they need from me first]
- [history: is this the first ask or the third?]

Constraints:
- Under [120] words.
- Ask for exactly one thing. Put it in its own sentence.
- No pleasantries beyond one line.
- If this is a repeat follow-up, be warmer but more specific. Name the date I last wrote, and make the ask smaller if there's a smaller version of it.
- Do not invent any detail I haven't given you. No dates, no times, no links, no attachment names, no titles you haven't seen me use.

Give me two versions: one direct, one softer.

Asking for two versions is a habit worth keeping generally. Picking between two drafts is faster than critiquing one, and you end up with something better.

The one that’s actually hard

Telling a senior faculty member their slides need to change is the email coordinators dread most. Unmitigated commercial content, an off-label recommendation that isn’t labelled, a logo that shouldn’t be there. This is where tone matters most.

In my voice, using this profile: [paste voice profile]

I need to tell [role, for example "a senior faculty member I'll work with for years"] that their submitted slides need to change before the activity. I'm the coordinator. I'm not their clinical peer, and I need this not to turn into a conversation about status.

The problem: [describe it plainly]
What has to happen: [the specific change required]
Why it's required: [the standard or policy that applies. Quote it if you have it.]
Deadline: [date]

Write it so that:
- The requirement is clearly not negotiable, but the framing is about process rather than about them. This is a rule that applies to everyone, not a judgment of their work.
- I don't apologize for enforcing it. One line acknowledging it's a nuisance is fine. Apologizing is not.
- The specific change is impossible to miss. Put it on its own line.
- I offer one concrete piece of help.
- Under 150 words.

Then tell me what a reasonable person might push back with, and give me a two-sentence reply to that.

That last instruction is the useful one. Thinking through the pushback before it arrives is most of what makes these conversations go well, and it’s the thing you can’t do at 4:45 on a Friday.

How to check it

Read it out loud. That catches most of the problems, and it catches them faster than reading silently.

Then three quick checks. Is the main ask unmistakable? Multiple requests may need bullets or separate messages. Is every fact one you supplied? Verify dates, times, links and attachment names. Would you be comfortable if this got forwarded to their department chair? If not, give it another pass.

Where it goes wrong

It’s far too enthusiastic. The default is warmer and more effusive than professional email should be. It’ll thank people twice, call things exciting, and add a closing line about looking forward to it. Your voice profile is what fixes that. Without one, every email sounds like a conference brochure.

It invents the specifics. Times, room numbers, portal links, attachment names. It fills gaps to be helpful. Check every concrete detail against reality.

It apologizes for the rules. In the difficult email, the default is to soften a firm requirement until it reads as a suggestion. Then you have to send a second email, which is worse for everyone.

It runs long. Ask for 120 words and you’ll get 180. Cut it yourself. Faster than another round.