Read: ~8 min · Try it: 25–35 min
Students who have been in your class for a few months can usually recognize your feedback before they see your name on it.
That recognition is not just about handwriting or a familiar font. It is about voice — the particular way you open a comment, the phrases you reach for when something needs work, the language you use to encourage. Those patterns are real. They are also part of what makes feedback feel trustworthy, not just accurate.
This article is about identifying those patterns. The work it asks for is reflective rather than technical: looking at your own recent feedback and noticing what you already do. Once those patterns are visible, they can be brought into TA39's Template Builder so that AI-assisted feedback continues to sound like you, not like a competent stranger.
What voice actually means in feedback
Voice is not decoration on top of "real" feedback. It is part of what makes feedback land.
A student who reads "This needs more development" hears something different from a student who reads "Let's look at where this argument loses some of its momentum." The information may be the same. The relationship being signaled — what the teacher expects, how much warmth is present, what kind of effort the comment respects — is not.
In practice, voice shows up in six recurring moments inside almost every piece of written feedback:
- Openings — how the comment begins
- Transitions — how the comment moves from praise to critique, or from one issue to another
- Encouragement — how progress and effort are acknowledged
- Constructive framing — how issues are named
- Guidance — how the next step is described
- Closings — how the comment ends
These are the structural beats. Teachers vary widely on each, and the variation is not random — it reflects how each teacher actually relates to students, and how they expect to be received in return.
Why voice gets lost in AI feedback
Most AI tools, including TA39, will generate competent-sounding feedback out of the box. The structure is reasonable. The rubric language is present. The next steps are named.
But the feedback often does not sound like any specific teacher, because the system has nothing to draw from. It has the rubric, the assignment, the student's writing — and a default register. The default register is reasonable. It is also generic.
That gap matters because students notice. A student who reads feedback that does not sound like their teacher will often read it more skeptically, even if the content is correct. The trust signal is missing.
Closing that gap is not about teaching the system a new voice. It is about making your own voice visible enough that the system can echo it. Most teachers already have characteristic phrases and patterns. The voice is there; it just isn't on paper.
A Voice Profile, in seven elements
A Voice Profile is a short, written description of the patterns that already shape your feedback. It is the artifact you will bring into the Template Builder later.
Seven elements together form the profile:
- Tone — the three or four words that best describe how your feedback usually sounds (e.g., direct but warm; rigorous and curious; brisk and supportive).
- Characteristic phrases for each of the six moments above (openings, transitions, encouragement, constructive framing, guidance, closings).
- Preferred vocabulary — the praise words, growth words, and action verbs you reach for most often.
- Words you avoid — phrases that don't sound right in your mouth ("good job," "nice work," anything else that feels too generic for you).
- Formality level — formal, conversational, or somewhere in between.
- Adaptations for different students — how, if at all, you adjust voice for struggling students, high-achievers, ELL students, or anxious students.
- Structure preferences — paragraphs, bullets, or a mix; length; visual emphasis.
None of these are right or wrong. They are descriptive — capturing how feedback already gets written when no one is asking.
Where TA39 fits
The Template Builder has a Custom Instructions field. That is where the Voice Profile gets translated into something the system can use.
You don't need to phrase it technically. The patterns you identify here become short instructions in the builder — "Always open with one of these phrases," "When framing growth areas, use phrases like…," "End with…" — and the generated feedback begins to reflect them.
A short worked example is enough to make the translation concrete:
Voice Profile (excerpt) Tone: direct but warm; rigorous and curious Opening: "I noticed…" / "[Student name], you're tackling this well…" Growth framing: "To take this further…" / "Here's where I got lost…" Closing: "Looking forward to your revision."
Custom Instructions in the Template Builder Tone: direct but warm; rigorous and curious. Always open feedback with one of these phrases: "I noticed…" or "[Student name], you're tackling this well…" When framing growth areas, use phrases like "To take this further…" or "Here's where I got lost…" Always close with: "Looking forward to your revision."
The translation is mostly mechanical: each line of the profile becomes a short instruction in the builder. Tone goes in once. Phrase banks become "use one of these" prompts. The closing line becomes the closing line. The mechanical part is the easy part; the work is the reflection that produced the profile in the first place.
The product video Building Your Template from Your Voice Profile walks through this translation step inside the builder, with a real profile entered alongside. If the Voice Profile is in hand, the product step takes about five minutes. If it isn't, the product step has to invent the patterns on the fly — which usually produces a thinner result.
Try it: Build Your Voice Profile
About 25–35 minutes. Three or four pieces of feedback you have written recently — printed or open on screen — and a pen.
This exercise produces a one-page Voice Profile you will use in the next product video. The profile only needs to be honest, not exhaustive. Aim for the patterns that actually appear in your recent feedback, not the ones you wish you used.
Step 1 — Read your own feedback aloud (about 5 minutes)
Pull three or four recent pieces of feedback you have written. Read each one aloud, slowly. Listen for the patterns — what each comment does at the start, in the middle, and at the close.
Write three or four words at the top of the page that describe the tone you hear. Direct? Warm? Rigorous? Encouraging? Calm? Curious? These three or four words are your tone summary.
Step 2 — Capture your characteristic phrases (about 10 minutes)
For each of the six moments, write down the one or two phrases you actually used most often in the samples. If a moment is missing from your default mode (for example, you rarely open with praise), note that too.
- Opening. How does feedback begin? "I noticed…" / "You're tackling this well…" / "[Student name], this is a solid start…"
- Transition. How does the comment move from one thing to the next? "Now, let's look at…" / "Here's where we can strengthen this…" / "One area that needs attention…"
- Encouragement. How is effort or growth named? "You're really getting this." / "This shows clear improvement from your last draft."
- Constructive framing. How is an issue introduced? "This is where I got lost." / "To take this further…" / "Not quite yet — here's what's missing."
- Guidance. How is the next step described? "Try this: …" / "Go back and…" / "Review the example from class where…"
- Closing. How does feedback end? "Looking forward to your revision." / "Come find me if you want to talk this through."
The examples above are not yours. Yours go on the page in your own words.
Step 3 — Vocabulary and avoidance (about 5 minutes)
Write three short lists.
- Praise words. Five or six you reach for most often. (e.g., thoughtful, clear, sophisticated, strong, careful.)
- Growth words. Five or six you use when something needs work. (e.g., underdeveloped, unclear, surface-level, missing the connection.)
- Words you avoid. Anything that sounds generic in your mouth — good job, nice work, interesting, anything that doesn't pass your own ear test.
Step 4 — Adaptations (about 5 minutes)
Do you change voice for different students? Note any genuine adjustments:
- For struggling or discouraged students — softer constructive framing, more visible encouragement, shorter sentences?
- For high-achieving students — more direct critique, higher expectations, less reassurance?
- For ELL students — simpler sentence structure, more direct language?
- For anxious students — extra reassurance, strengths emphasized first?
If your voice is consistent across all students, note that too. Both are valid; making the choice visible is what matters.
Step 5 — Synthesize into one page (about 5 minutes)
On one sheet of paper, write:
- Tone — three or four words
- Six characteristic phrases — one per moment
- Three short vocabulary lists — praise, growth, avoid
- Adaptations — one or two lines, or "consistent across students"
- Formality level — formal, conversational, or in between
- Structure preferences — paragraphs, bullets, mix; length; emphasis
That sheet is your Voice Profile. It is the artifact you will bring into Building Your Template from Your Voice Profile and, eventually, into the Template Builder's Custom Instructions field.
What to read or watch next
Continue Module B with Why Good Feedback Still Doesn't Improve Student Work — and 5 Structures That Help Fix It. That article introduces the five feedback structures and helps you choose the one that fits your next assignment.
The third Module B reading, Why Feedback Templates Matter, shows how voice and structure converge into a template the system can apply consistently.
Once all three Module B readings are complete, watch Building Your Template from Your Voice Profile. The Voice Profile you just produced is one of the three inputs the video uses.
A note on adaptation over time
Voice evolves. The patterns you identify today are not a fixed identity — they are a snapshot of how feedback currently sounds when you write it.
Most teachers find that the profile changes over a term or a year. New phrases enter. Old phrases drop out. Adaptations sharpen. That evolution is healthy. Revisit the profile when feedback starts to feel formulaic, when a new curriculum demands different language, or when the templates start producing feedback that doesn't quite sound like you anymore.
The goal is not to lock voice in. It is to make voice visible enough that the system can echo it — and to keep that echo accurate as your practice changes.