Dictate Email as Executive Assistant: Sound Like Your Manager

Writing mail for a manager's mailbox starts with delegation, and the craft is to dictate email as executive assistant in their own voice. The setup that matters is Send As permission, which lets the assistant send from the manager's address so the recipient sees a mail from the manager and not from the assistant's account. Without it, every mails sits under the assistant's identity and the delegation is only administrative; with it, the written voice can genuinely be the manager's. Grant it in the Exchange environment, usually in the same panel where folder permissions live, and have the manager confirm the level, because Send As and Send On Behalf differ in the header that the recipient sees. Verify the choice with a test mail to yourself.

The test also confirms the two practical behaviors that the workflow depends on. First, the reply goes from the manager's address and lands in the manager's sent items, so the archive and the audit trail stay where the manager expects them. Second, the draft you compose appears in the manager's drafts folder, which is where the approval loop lives if you use that mode. The folder mapping is the quiet backbone of the delegation: whichever account the draft travels through, both the assistant and the manager see the same story in the shared view. Set the reading pane and the drafts preference so that the assistant's default compose is the manager's mailbox, and the daily flow starts in the right place.

One caution belongs at the top of this section rather than the bottom: with Send As, the mail you send is the manager's mail, and the accountability is shared. Use the capability for the correspondence the manager approves in structure, keep the sensitive classes such as salary matters and legal commitments on the manager's own send path, and always let the manager see what went out in their name. A good delegation is a trust arrangement with a paper trail, and the paper trail is the sent items. The setup is five minutes of configuration and a week of calibration, and the calibration is exactly what the rest of this article describes.

The hardest part of assistant-written mail is not speed; it is sounding like the manager. The training material is sitting in the manager's sent items, and the method is to read a selection of the manager's own mails before drafting: their greeting style, their sentence length, whether they open with a thanks or with the point, their sign-off, and their policy on emojis and exclamation marks. Ten minutes of reading, twice a week, teaches the register faster than any style guide, because the register is in the rhythm rather than the rules. Then dictate with that rhythm: shorter sentences where the manager is short, plain verbs where the manager is plain, and the closing that the manager always uses.

The specific voice markers to collect are few and high-yield. The opening line pattern, such as thanks for the note or straight to the ask. The paragraph habit, one idea per paragraph versus dense blocks. The hedging vocabulary, whether the manager says could you or please confirm. The sign-off, and the spellings of the names they use. Keep a one-page voice card with these markers, updated weekly, and consult it while drafting. The card is not a mask; it is the manager's known handwriting, and the assistant's job is to reproduce it so the recipient cannot tell the authorship, which is precisely the standard the manager will judge the work by.

The dictation layer makes the reproduction natural rather than performative, because when you speak first and edit toward the model, the voice comes out in your own normal tone and the markers are applied as adjustments. The trap to avoid is the opposite order: writing in the assistant's voice and then sprinkling the manager's phrases on top, which reads as an imitation and usually as an awkward one. Speak the mail as yourself, then edit it toward the manager's rhythm, and the final text reads like the manager's own mails. The sent items are the reference, the voice card is the checklist, and the dictation is the instrument that makes the reproduction smooth enough to be invisible.

The sign-off loop is the guardrail that keeps the delegation honest, and its shape is simple: dictate the draft from the manager's mailbox, then send it to the manager for approval rather than to the recipient. The loop exists because the assistant's job is to reduce the manager's mail burden, not to become the manager's mail. The draft arrives in the manager's inbox as a proposal, the manager reads in thirty seconds, either approves the send or edits a line, and the mail goes out with the manager's knowledge and often with the manager's own touch. The loop is the calibration engine: every edit the manager makes is a lesson in the voice card, and after a month the edit rate collapses.

The mechanics that keep the loop fast are pre-determined. Use a consistent subject prefix, such as draft for approval, so the manager can triage the batches; batch the approvals into one or two daily windows rather than firing each draft individually, so the manager evaluates once and the assistant learns from the whole set; and set the default so the draft is visible in the manager's drafts folder as well, giving the manager a second route to read and edit before send. The dictate part is where the assistant's time goes, and the approval part is where the trust grows. A loop that runs daily at a fixed time becomes a rhythm neither side has to think about.

The loop has a target metric that tells you when it is tuned: the edit rate, meaning the share of drafts the manager changes meaningfully. Early on, the rate runs high and that is the reason the loop exists. As the voice card and the pattern collection improve, the rate falls, and the assistant can safely route more classes of mail directly. Write the metric down monthly, and expand the categories of mail that pass through the loop as the rate drops. The loop never fully disappears for the sensitive classes, and that is correct: the manager always holds the final word on the mail that goes out under their name, which is exactly the trust the delegation is built on.

The reply classes that repeat are the ones that define an assistant's week, and each deserves a stored pattern. The standard four are: the scheduling response, such as the executive is available Tuesday at 2 or unavailable this week; the requested-introduction reply, where the manager is asked to connect two parties; the meeting-summary note, a two-line recap after a call; and the status update to a stakeholder who asks where things stand. Each of these has a fixed shape with one variable, and the shape belongs in a Quick Part while the variable belongs to dictation. Build the four patterns once, in the manager's voice, and the weekly cycle becomes a fill-in rather than a composition.

The pattern-write session is a half hour and it is the most valuable half hour in the assistant's week. Write each of the four patterns in its best form, mark the slots with placeholders, save each as a named Quick Part in the manager's profile, and then do a rehearsal: insert each one into a test mail and read it in the manager's voice, correcting the wording until the test mail reads like something the manager would actually send. The rehearsal is where the generic boilerplate becomes the manager's pattern. Each week the slots get filled by dictation, and the pattern text stays fixed, which is the definition of consistent output, and it is also what makes the manager's mail reliably sound like the manager.

The calibration continues after the build. When the manager corrects a pattern reply for the third time, the pattern itself is wrong, not the send, so update the Quick Part rather than the habit. Mark the patterns with the approval-loop classification, since some classes, such as the introduction request, may always need the manager's yes before the send. Once a month, review the pattern set and prune the shapes that drifted out of use. The result is an assistant workflow where the repeating 80 percent of the week is a set of four spoken sentences and two manager dozend-second checks, and the remaining 20 percent is the real assistant work: judgment, timing, and the judgment call that no pattern covers.

The triage order for a shared mailbox is where the assistant's day is actually won, and it has a rhythm that the dictation slots into. Morning pass: open the manager's inbox, sort by the arriving pattern, and classify each item into one of three buckets. The file bucket is the read-and-know, the reply bucket is yours to answer, and the manager bucket is the one that needs the manager's own judgment. Do the file bucket quickly, dictate the reply bucket in one session, and deliver the manager bucket as a short summary rather than forwarding twenty mails. The summary is the place where you dictate your own judgment: what needs the manager, what it waits on, and what you recommend.

The dictation session belongs after the triage, not before, because the microphone cannot triage for you and the ordering is where the leverage lives. Two blocks per day are enough: a morning session for the reply bucket that arrived overnight, and an afternoon session for the mails that landed across the day. Each session runs the same way: open the first reply-class mail, say the pattern, fill the slot, send or send for approval, next. The queue is a pipeline rather than an inbox, and the pipeline ends each day empty of the buckets it handles. The manager's inbox at 6 PM should show the manager bucket only, and that is the visible proof the assistant system is working.

Two habits finish the day and prevent the tomorrow mess. First, the closing pass: five minutes before the end of the day, scan the sent items and confirm every mail that carries the manager's address was intended, approved if the loop applies, and addressed correctly. Second, the note: write the one line of context about anything unusual, such as the mail the manager should expect tomorrow morning from the client, into the day's handwritten context or the next-day memo, because the dictation workflow runs better when the assistant's own context is scripted too. The shared mailbox then runs as a system: triaged, dictated, approved, archived, and ready for the next day, which is the quiet standard that makes an executive assistant indispensable.