Intro Emails for Board and Advisory Contacts

A brevity-first method for board and advisor introductions

Voiskey Voiskey Team
Email IntroductionsIntro TemplatesIntro Emails Board

Respect the Reader's Limited Time

Intro Emails for Board members and advisory contacts follow a different etiquette from peer introductions. The reader is usually unpaid, time-constrained, and exposed to a steady stream of documents that all claim to be urgent. They are not looking for a relationship; they are looking for the decision, the risk, and the cost in time. A note that respects those three things gets read. A note that begins with background gets skimmed and deferred. The introduction should feel like a briefing from a competent colleague, not like an invitation to a longer conversation the reader did not ask for.

Assume the reader has five minutes and no context. Board members and advisors move between organizations, so they will not remember the details of your project unless you restate them. Give the minimum context needed to understand the decision, then move to the ask. Do not assume they recall last quarter's discussion, even if they were in the room. A short recap sentence is not an insult; it is a courtesy that saves them from searching. Restate it once and move on. The best board notes read as if they were written for a smart person who joined the conversation five minutes ago.

Get the formality right. Use the reader's preferred name and title, and check both before you send. If you are unsure how someone prefers to be addressed, ask the person who works with them. Check the spelling of that name. Copy the right people: usually the board liaison, the executive sponsor, and anyone who will need to act on the answer. Do not copy a large group to create visibility; it makes the note feel like an announcement and invites replies that fragment the thread. Formality here is not stiffness. It is the signal that you understand the reader's position and the norms around it.

Route the note through the right channel. Many boards and advisory groups have a liaison, a chief of staff, or an assistant who manages the calendar and filters requests. If that person exists, send the introduction to them first or copy them deliberately, and follow their preferred format. Trying to reach a board member directly when a channel exists creates work for everyone and can delay the request. If you are unsure who the right contact is, ask one question rather than guessing. The channel is part of the message, and using it correctly is a form of respect. Keep the channel stable for the whole request.

State the Decision at Stake

Say what judgment you want the reader to make. Board and advisory contacts are used to being asked for opinions, and an opinion request without a decision attached is easy to postpone. Name the decision in one sentence: whether to sponsor a pilot, whether to support an introduction, whether a proposal is worth pursuing, or whether a risk is acceptable. If the decision is not theirs to make, say whose it is and what role you want the reader to play. Clarity about the decision is the difference between a reply and an archive. One clear sentence is enough for this reader.

Separate context from request with a line break. Put the background in two or three sentences, then start a new paragraph with the ask. Readers scan for the ask, and a visual break helps them find it. Keep the context factual: what changed, what is being considered, and why now. Do not mix a recommendation into the background, because the reader will not know whether they are reading your view or the facts. The separation also makes it easier for the reader to disagree with the recommendation without disputing the facts. Keep the two paragraphs physically separate on the screen, with white space.

Quantify the cost in the reader's currency: time. Say how long the meeting would take, how many pages they would need to read, and what preparation, if any, is expected. A board member can decide quickly whether twenty minutes is available; they cannot decide about an unspecified commitment. If the answer requires a call, propose two windows and state the time zone. If it requires only a written reply, say that. Time is the constraint that governs everything else, so naming it early makes the rest of the note easier to evaluate. Specific numbers make the whole note more credible and easier to answer.

Say what happens if the answer is no. A clear alternative makes it easier for the reader to decline without feeling that the project collapses. Name the fallback: a smaller review, a later date, another sponsor, or a decision made elsewhere. This is not pessimism; it is planning that the reader can see. It also protects you, because a no with a fallback keeps the relationship intact and leaves the door open for the next request. A note that treats no as a catastrophe puts pressure on the reader, and pressure is the fastest way to silence. That honesty is what keeps the channel open.

Keep the Ask to One Page

Keep the note to one screen. A board or advisory reader should be able to understand the request without scrolling, and the whole note should fit in roughly two hundred and fifty words. That is enough for a context sentence, a decision sentence, a time estimate, and a fallback. If your draft is longer, the extra material belongs in an attachment or a later conversation. The one-screen rule is not about style; it is about the reader's attention, which is the scarcest resource in this exchange. The rest of the note exists only to support that one sentence, so write it first.

Cut the history. Most drafts begin with a chronological account of how the project arrived at this point, which is useful to the author and unnecessary to the reader. Replace it with one sentence that states the current situation and one that states what changed. If the reader needs more history, they will ask, and the answer can be longer. A note that begins with the current decision and works backward only as needed is easier to act on than one that tells the story from the beginning. The reader's question is what to do now. A short note wins on this point every time.

Attach at most one document, and say why it is there. A board note with three attachments asks the reader to choose what matters, which is work you should have done. If a document is essential, name it in the note and say which page or section matters. If it is supporting material, say it can be read later. When in doubt, leave it out and offer to send it on request. The note should stand alone; the attachment should deepen a point the reader already understands from the note itself. One attachment is a decision; three attachments are a deferral.

Write in plain language and define any term the reader may not share. Boards include people from different functions, and an internal acronym can stop a reader cold. Spell out the term once, then use the short form. Avoid nominalizations and stacked nouns, which make simple requests sound like policy documents. Read the draft aloud; if you run out of breath, the sentences are too long. A short note in plain language signals confidence, while a long note in dense language signals that the author has not decided what matters. Plain language is a professional courtesy in this setting, not a simplification.

Dictating Board Intros with Voiskey

Download Voiskey and dictate the note in the message window you already use. Put the cursor in the body, press the shortcut, and speak at a normal pace; the text appears at the insertion point with no separate recorder and no copy-paste step. Voiskey removes filler words, stutters, false starts, and self-corrections, so the draft keeps the brief structure you planned. Speak the decision first, then the context, then the time cost and the fallback. That order matches how a board reader scans, and it keeps the note from drifting into history. Keep the finished note under one screen.

Set the register before you speak. Say 'write this as a brief, formal note to a board member' and the app adapts punctuation, formatting, tone, and word choice to that instruction. Ask for short paragraphs and no promotional language. If the same content also goes to an internal sponsor, dictate a second version from the same facts and compare; the board version should be shorter and more decision-focused. Read both aloud and keep the one that sounds like a competent briefing rather than a request for attention. Then dictate it and compare the two. That comparison is a habit worth keeping.

Let the app learn the names and titles that carry weight here. Board members' names, committee names, institution names, and program titles are exactly the details that must be right, and Voiskey learns names, jargon, acronyms, and spelling preferences. Say each one once, check the draft, and correct it by voice. If several people prepare board notes, the team plan offers shared vocabulary and workflows, so titles and program names stay consistent across the group. A misspelled title in a board note is a small error with a long shadow. That comparison is the whole method here, and it takes only two minutes.

Edit in three passes with the one-screen rule in mind. First, confirm the decision sentence is explicit and appears early. Second, cut any context the reader does not need to make the decision. Third, check the time estimate and the fallback. The Speak-Polish-Type-Edit workflow is fastest when you dictate the whole note once and then remove material rather than adding it. Board notes improve by subtraction. Read the final version on a phone screen, because that is how many readers will see it first. A short budget note is a courtesy to a reader with a full calendar.

Reviewing Before It Reaches the Board

Review the note as the reader, with a five-minute limit. Read it once without stopping, then close it and ask what you were being asked to decide. If you cannot answer in one sentence, the note is not ready. This test catches the most common board-note failure: a well-written message that never quite states its request. Do the test before you polish the language, because polishing a note with an unclear ask only makes the confusion more elegant. Clarity of request comes first; tone comes second. Do it once, before you call the note finished and send it on.

Check every name, title, and affiliation against a current source. Board roles change, organizations rename, and an outdated title is a visible error to the person who holds it. Ask the liaison to confirm the list of recipients and the preferred form of address. Check that the right people are copied and that no one who should be informed is missing. This mechanical pass takes ten minutes and prevents the kind of mistake that is remembered long after the decision itself is forgotten. That mechanical pass is worth every one of those ten minutes, every time. Small errors are expensive here.

Test the decision and the fallback together. Ask a colleague to read only the decision sentence and the last paragraph, then say what they think the reader is being asked and what happens if the answer is no. If their summary differs from yours, rewrite those two parts. The rest of the note can be beautiful, but these two elements determine whether the reader can act. A board note that is clear about the decision and honest about the fallback is doing its job, even if the prose is plain. Two readers, two tests, and one clear decision at the end of the note.

Record the request and follow up once. Note the date, the recipient, the decision requested, and the answer. If no answer arrives within the stated window, send one short reminder in the same thread, restating the decision and the time cost in a single sentence. Do not forward the entire note again. When the answer arrives, confirm it in writing and close the loop with anyone who was copied. A short record of board requests shows patterns over time and makes the next note easier to write. Write the date, the request, and the answer on a single line of notes.

FAQ s

Speak the decision first, then the context and the time cost, and Voiskey removes filler and self-corrections so the note reads as a brief briefing rather than a pitch. Ask for a formal tone before you dictate, keep the note to one screen, and check every name and title before sending.

Yes. Say that you want a brief, formal note before you dictate, and Voiskey adapts tone, formatting, and structure to that instruction. Ask for short paragraphs and one clear decision sentence. Then cut the history and the extra attachments. Board notes improve by subtraction, so dictate the whole draft once and remove whatever the reader does not need.

Voiskey learns names, jargon, acronyms, and spelling preferences. Say each board member's name, committee name, and institution once, then check the draft and correct any misspelling by voice. Titles change often, so confirm them with the liaison as well. A correct title is a small signal that the note was prepared with care for the reader's position.

Read it once with a five-minute limit and ask what decision it requests. Check every name, title, and recipient against a current source. Confirm the time estimate and the fallback, then read the note on a phone screen. If the decision is not clear in one sentence, dictate the note again with Voiskey and cut until it is.

Say less. Get more
Say less. Get more
Say less. Get more
Say less. Get more
VoiskeyVoiskey

Your voice, amplified.

Download Voiskey for Mac and Windows and dictate a concise board introduction.

Use it across macOS, Windows, iOS, and Android

Use it across