"Make it inspiring but not salesy" is a note a speech engine has no way to use. Type it above a product update and the voice comes back brighter than last week's episode while still saying "synergy" with a straight face, because "synergy" was in the script and "inspiring" was not an instruction it can apply. A brief only works once it becomes text, tags, or a choice of voice.
You are not sitting in a booth. There is no one to tap on the glass and say "drier." In VoxAnvil you prepare the manuscript, choose a voice, and send the prepared text to a third-party voice provider for synthesis. There is no separate performance-prompt field waiting for a paragraph of vibes. If you want direction, you put it where the pipeline actually looks: the words, the punctuation, a rare tag, and the voice you already auditioned.
Write the brief on one page
Keep it short enough to reread before every generation. Six lines are enough.
- Listener. One person, in one place. "A nurse on a break" is usable. "Everyone who cares about leadership" is not.
- Job of the piece. Explain, confess, instruct, or tell the story. Pick one. A piece that tries to do all four will sound like a montage.
- Pace. "Sentences a person can say in one breath" is a pace. "Punchy" is not. If you want punch, write short sentences.
- Pronunciation. Point at the list, not at a feeling. "Use the stored forms. Do not invent nicknames."
- Off limits. "No excitement tag on the open. No all caps. No second voice." Constraints are the part people skip, and they are the part that keeps episode ten in the same family as episode one.
- The line that matters. Quote the one sentence that must not be ironic, rushed, or soft. Generate that line first when you test a change.
This page lives in your notes or at the top of a scratch file you delete before generating. Do not leave "BRIEF: drier" inside the chapter. The voice will say it. The clean script pass is how those leftovers get caught.
Turn the brief into script moves
Go down the brief and convert each line into something audible.
If the listener is tired, the sentences get shorter and the jokes get fewer. You do not tag the chapter [soft] and hope. Soft on every line is a whisper podcast. Soft on one aside is a choice. The tag list and its limits are in the direction guide.
If the job is instruction, the brief's pace line becomes a pattern: step, pause, step. Write "Wait ten seconds" as its own sentence. Do not hide it in a clause. The voice can hit a period. It cannot hit your intention.
If the line that matters contains a "not," bold it in your brief and then listen for it. Do not bold it in the manuscript as a font trick. Fonts are not speech. The words around the negation should be simple. "This does not replace a backup" is a line you can hear. "While this shouldn't be seen as a replacement for a comprehensive backup strategy" is a line the voice will skate over. Rewrite to the brief, then generate.
A human narrator, you could argue, would understand "inspiring but not salesy" from a conversation. Some would, and they would still ask you to point at a sentence. You are the director. The model is the take. Point at the sentence.
What not to put in the brief
Do not write a biography of the brand. The listener will not hear it, and it will tempt you to paste it into the open. Do not write "sound like a famous actor." That is how people end up cloning a voice they do not own. Choose a stock voice you can describe in plain words: slower, clearer consonants, no trailer lift. Audition it with the nonfiction sentences or the general matching paragraph, depending on the book.
Do not add a new adjective every episode. A brief that grows to two pages is a brief you will not read. If you learned something from the last listening pass, replace a line. Do not append it. "We also like warmth now" plus last month's "keep it dry" is how a series drifts. One pace. One listener. One off-limits list.
Do not include retailer specs in the creative brief. Loudness and room tone are an export problem, handled after the read, and described in the silence piece. Mixing compliance into the brief encourages pause tags as a fake master.
Use the brief as a gate
Before you generate a full chapter, read the brief and the first paragraph side by side. If the paragraph violates the brief, fix the paragraph. Generate the line that matters. Listen once. If it matches the brief, generate the chapter. If it does not, change the text or the voice. Do not add three tags and hope the brief sneaks in.
A brief for a release-note narration might read like this. Listener: an admin who did not read the changelog. Job: instruct. Pace: one action per sentence. Off limits: no hype tag, no version number said as a string of digits unless it is on the pronunciation list. The line that matters: "This update does not delete existing projects." The writer hears a take that rushes "does not" and splits the sentence. The second take is the one that ships. Nothing inspiring was requested, and nothing inspiring was needed.
When a colleague asks for the audio to "feel bigger," hand them the brief and ask which line they want changed. Bigger is not a line. A slower open, or a stock voice with more weight, is a line you can test. One change at a time, or you will not know which edit moved the read.
Frequently Asked Questions
Q: Can I paste the brief into an expression tag? A: No. Tags are a small set of words such as emphasis, whispering, and pause. A sentence of direction inside brackets is either ignored, flagged as an unrecognized tag, or read aloud. Keep the brief outside the script.
Q: Who is the brief for, if the model never sees it? A: It is for you, and for anyone else who generates a chapter on the project. It stops each session from inventing a new style. The model sees the script you wrote after you obeyed the brief.
Q: How often should I rewrite it? A: When the listener or the job changes. Not when you are bored. A series brief should survive a month. Update the pronunciation pointer when names change. Leave the pace alone.
Q: Does VoxAnvil store this brief for me? A: There is no dedicated brief field. Store the note in your own files, or in project text that you do not send to speech. The things the studio does store are the manuscript, the voice, the pronunciation rules on paid plans that include them, and the audio you generate.
Read the brief against the script one last time, and rewrite any line that breaks it before the script gets anywhere near a voice.