Audience design concerns how people shape the language they use in relation to their listeners or readers. A child may need a clear example of what evaporation means, while a science teacher discussing the same phenomenon may need precise measurement language. The underlying event does not have to change; the explanation changes because the addressee’s knowledge, task and need for detail are different.
This is a powerful technology of vocabulary. It helps students decide when to define a term, which assumptions can be left implicit, how much detail a practical instruction requires and why a message that works for one person may confuse another. The goal is not to flatter an audience or reduce their ability to a stereotype. It is to make meaning sufficiently precise and usable for the actual communication task.
This guide explains audience design as a sociolinguistic idea associated with Allan Bell, then develops tools for school writing, spoken explanations, multilingual communication, accessible instructions and digital publishing. It distinguishes the intended addressee from overhearers and later readers, and it shows how style, register, shared knowledge and responsibility interact. Every educational case is fictional and intended to be checked against the real audience rather than copied mechanically.
Editorial note: All school, community and family scenarios are original hypothetical teaching cases. Audience-design research supports general principles and does not certify any example as an observed result.
Contents: design language for the actual reader
Open all 52 chapters and worked cases
- A clear explanation depends on its reader
- The sociolinguistic idea of audience design
- An addressee is not every person who might hear
- Auditors and overhearers
- Future readers are another kind of audience
- Changing style is not changing facts
- Audience design is not merely politeness
- Register and audience expectations
- Technical terms need access routes
- Avoid assuming everyone starts with the same knowledge
- The curse of knowledge can affect explanations
- Common ground is not guaranteed by one shared document
- Different audiences need different answers to why
- Short does not always mean understandable
- Long does not always mean thorough
- A layered explanation can serve different readers
- Word choices can wrongly assign authority
- Do not substitute stereotypes for audience research
- Audience preferences may be individually expressed
- Accessibility is part of being understood
- Multilingual audiences need meaning, not word swapping
- Different audiences require different evidence detail
- The writer must know the communication goal
- An invitation and a report need different phrasing
- Reference words can fail outside their original context
- Labels can reduce translation and memory burden
- Writing for one reader versus a mixed audience
- Search readers often arrive without earlier chapters
- A title is a promise about content
- An instruction must survive a handover
- Spoken explanation and written record serve different tasks
- Numbers and units should not disappear in simplification
- The same achievement can be described at different levels
- Feedback needs an actionable level of detail
- Two-layer parent and student feedback
- Examination guidance needs exact terms
- Professional communication: register is not jargon density
- Audience design in Science reporting
- Audience design in public information
- Different audience roles can affect a conversation
- An audience can change during the task
- Feedback from actual readers is more useful than stereotypes
- An audience map with four questions
- Worked case: a vocabulary explanation for a younger pupil
- Worked case: the same explanation for a mathematics teacher
- Worked case: writing two versions of a school message
- Worked case: a technical diagram for the public
- A six-step audience-aware writing check
- Diagnostic: what kind of audience problem is this?
- Twelve quick questions with answers
- Frequently asked questions
- Primary sources and your next action
1. A clear explanation depends on its reader
Imagine a student explaining a simple water-cycle diagram. To a younger child, the student says, ‘Water can change into invisible water vapour and move into the air.’ To someone studying more advanced science, the explanation may need the molecular process, energy transfer and relevant conditions.
The two versions can be suitable for different learning goals. Neither is automatically more honest or valuable because it is shorter or longer.
Ask the writer to specify what the intended reader needs to understand or do after reading. Appropriate detail follows that purpose.
2. The sociolinguistic idea of audience design
Allan Bell’s Language Style as Audience Design (1984) argues that language style often responds to the audience, with addressees exerting a strong influence and other audience roles also mattering.
The ERIC bibliographic record summarises Bell’s sociolinguistic model, including style shifts influenced by topic, setting and reference groups.
Audience design is a broader theory of language variation. The writing checklists in this guide are practical applications and should not be mistaken for a complete reproduction of the original research.
3. An addressee is not every person who might hear
The addressee is the person or group a speaker primarily addresses. An audience can also contain people who are present but not directly addressed, and in public communication there may be later readers.
An organiser writing to the event participants may also know that parents or volunteers will see the message. The key dates and location need to remain clear to the intended participants; other readers may need additional context.
Ask whom the message directly requests action from and who else must avoid a misleading interpretation. This prevents the writing from assuming one undifferentiated listener.
4. Auditors and overhearers
Bell’s model distinguishes listeners with different participation roles, including auditors and overhearers, though the exact interpretation depends on the theoretical setting.
A school presentation may address an examining teacher while classmates listen. The speaker should explain the task clearly enough that the intended audience can follow without treating classmates’ incidental presence as identical authority.
Use the concept to notice multiple audiences, not to claim that you know what any individual overhearer thinks.
5. Future readers are another kind of audience
A note written for today’s class may be viewed next month by someone who did not attend the explanation. Words such as ‘this’, ‘the usual folder’ and ‘last Friday’ may then become unclear.
A durable page should supply identifying names, dates, versions and enough context to remain interpretable. A private reminder for one person may legitimately be shorter.
Ask whether the text needs to work after the shared conversation has disappeared.
6. Changing style is not changing facts
A parent-facing explanation might say, ‘The child is practising how to support an answer with details from the passage.’ A specialist note might say, ‘The learner is identifying textual evidence and relating it to an inference.’
The central task can remain the same, while the terminology and presentation change. The writer should not invent a stronger achievement merely to sound professional or simplify a qualification out of existence.
Compare the two versions by asking what claim each makes. They should preserve the relevant truth even when they use different words.
7. Audience design is not merely politeness
Politeness affects wording, but audience design also concerns knowledge, accessibility, purpose, genre, status and conversational context.
‘Please complete the task’ is polite yet vague if the reader does not know which task is intended. ‘Please complete Question 4 on the current worksheet’ is more actionable.
Start with what the reader must identify; adjust tone after the practical meaning is clear.
8. Register and audience expectations
Register concerns patterns of language associated with contexts and purposes. A school report, a casual message and a scientific explanation may require different levels of formality and terminology.
Formal wording is not automatically superior. ‘Peruse the attached documentation’ may be less helpful than ‘Read the attached instructions’ when direct action is the goal.
Choose a register that is appropriate to the medium while preserving exact requirements and respect for the reader.
9. Technical terms need access routes
An advanced term can be useful when it compresses a concept for someone who already knows it. For a newcomer, the same term may require a definition, an example or a diagram.
Audience design asks whether the reader has a route to the meaning. Do not remove essential technical distinctions just because they are difficult to spell.
A good introduction can name the exact term, explain it in accessible language and then use it consistently.
10. Avoid assuming everyone starts with the same knowledge
One classmate has studied algebra; another is encountering unknowns for the first time. A single unexplained instruction ‘solve for x’ may be easy for the first and opaque to the second.
Support can be differentiated through short definitions, examples or optional deeper explanations without labelling either learner’s potential.
Ask what prerequisite understanding the current task genuinely requires, then provide a reasonable way to access it. The Prerequisite guide explores this distinction.
11. The curse of knowledge can affect explanations
Someone who understands a task well may forget which steps were once confusing. They refer to ‘the obvious next step’ even when the audience cannot see it.
Ask a new reader to explain what they think the instruction requires. A failed interpretation can reveal a missing referent or assumption.
The test should address the task, not make a judgement about the reader’s intelligence.
12. Common ground is not guaranteed by one shared document
Two students may open the same chart but interpret a symbol differently. Shared access establishes a common reference, not necessarily a common understanding.
An audience-aware explanation names the relevant symbol or supplies a legend. It should not assume the reader has the author’s training.
See Common Ground for a deeper account of shared assumptions and conversational coordination.
13. Different audiences need different answers to why
A pupil asks why a grammar correction matters; the tutor can show how the error changes the sentence’s meaning. A school leader may ask why a particular practice method fits the curriculum; the explanation might focus on tasks, evidence and learning goals.
The same action can be discussed at different levels. A useful explanation identifies the question its audience is actually asking.
Answer that question before supplying extra background. A detailed answer to the wrong question is still unhelpful.
14. Short does not always mean understandable
‘Fix it’ is short but fails to identify the problem. ‘Change the unit from cm to cm² because the calculation gives area’ is longer and more actionable.
A small number of precise words may reduce confusion better than a vague one-line instruction.
Measure clarity by what the reader can accurately do or explain, not simply by word count.
15. Long does not always mean thorough
A document can contain hundreds of lines while avoiding the central question. Readers may need a summary, contents and a clear path to the relevant detail.
Good long-form audience design combines immediate definitions with deeper chapters and navigable sections. Readers can choose the level that fits their purpose.
The length should be justified by distinct useful material and worked cases, not repetitive boilerplate.
16. A layered explanation can serve different readers
Begin with a short answer, then explain why the idea matters and how to apply it. Follow with examples, limits and deeper reference notes.
This allows a newcomer to gain orientation and a more experienced reader to inspect the finer distinctions without forcing both through identical learning sequences.
Keep the terminology consistent across layers. A simple introduction should not contradict the later technical account.
17. Word choices can wrongly assign authority
A school notice says ‘The student may request a change’, but a casual summary says ‘The student can change the deadline’. The wording may imply authority the student does not have.
Audience design should not remove approval conditions when simplifying instructions. The reader’s relevant next action must remain accurately represented.
Test whether the simplified version would lead the recipient to do something the actual policy does not permit.
18. Do not substitute stereotypes for audience research
It is unreliable to assume that every person of a particular age, nationality or background has the same knowledge, preferences or reading level.
Ask about the actual task, learning stage, accessible format and evidence of understanding where appropriate. Offer more than one route if the audience is diverse.
Audience design should be based on usable information about the audience’s communicative needs, not unsupported demographic guesses.
19. Audience preferences may be individually expressed
A learner may prefer a visual worked example, a spoken explanation or short written steps. These can be offered as supports when the intended meaning remains clear.
Preference does not automatically predict effectiveness for every concept. The important check is whether the learner can actually use the explanation.
Record which support was used and what performance was demonstrated, without declaring one modality a fixed personal identity.
20. Accessibility is part of being understood
A diagram relying solely on red and green distinctions may be difficult for some readers to interpret. The information could also be labelled in text or differentiated by pattern.
An audience-aware resource asks whether the intended action is available through supported input and presentation methods. The W3C Web Content Accessibility Guidelines provide detailed standards relevant to digital content.
A teaching example is not a certified accessibility audit. Test the actual format and task with relevant users and applicable guidance.
21. Multilingual audiences need meaning, not word swapping
An English term may not have an equally concise counterpart in a reader’s strongest language. A plain definition or descriptive phrase may communicate its function more accurately.
Do not assume bilingual readers share the same interpretation merely because a translation is present. Context, register and terminology matter.
The Lexical Gap guide explores why meaning transfer sometimes needs more than one word.
22. Different audiences require different evidence detail
A younger student may need a concrete demonstration to understand what evidence is. An experienced researcher may need the actual method, data range and limitations before accepting the claim.
Neither group should be given invented certainty. The explanation can vary in depth while preserving what the evidence truly supports.
Ask what the intended reader needs in order to judge or act responsibly. The answer should guide the level of detail.
23. The writer must know the communication goal
Are you explaining a concept, requesting an action, reporting a result, asking a question or persuading an audience? Each goal makes different details relevant.
A notice telling families when to attend a meeting should foreground the date, time, place and required action. A report evaluating the meeting may need methods, attendance and findings.
Use Speech Acts to identify what your message is trying to do.
24. An invitation and a report need different phrasing
‘The reading club meets on Friday’ reports a schedule. ‘Would you like to join the reading club on Friday?’ invites a response.
An audience-aware invitation should make clear how to reply and which details matter for participation. A report need not create an RSVP process.
Identify the act before choosing its form. A perfect description of an event may still fail as an invitation if the reader cannot tell that they are being asked to respond.
25. Reference words can fail outside their original context
‘This is the one you need’ may work when two people point at a shared screen. In an emailed instruction sent later, the referent may disappear.
Repeat the identifier: ‘Use Worksheet B, page 3’ or another grounded description. This makes the message more durable across time and medium.
The Reference Chain guide shows how nouns and pronouns track intended objects and ideas.
26. Labels can reduce translation and memory burden
A folder called ‘Approved Script — Version 3’ carries more operational information than a file named ‘Final New Latest’. The label helps a reader find the intended item.
But even a clear filename must correspond to an accurate workflow record. Words do not establish that someone reviewed the content.
Audience design makes the label interpretable while verification protects its factual status.
27. Writing for one reader versus a mixed audience
A private note can refer to shared conversation without repeating the entire context. A public webpage serves readers who arrive through different searches, with differing background knowledge.
A mixed-audience page often benefits from direct definitions, contents links, accessible headings and deeper explanations that can be skipped or opened as needed.
Do not force every paragraph to target everyone equally. Use a coherent structure that helps readers find the level relevant to their questions.
28. Search readers often arrive without earlier chapters
A user searching ‘what is a discourse marker’ may land directly on a focused article, not on the site’s vocabulary hub. The first paragraphs should answer that question without requiring the reader to find a separate foundation first.
Related links can then support further learning. A first-time reader should not be left with an unexplained abbreviation or a private reference to something discussed on another page.
This is audience design for navigation as well as prose.
29. A title is a promise about content
‘What Is a Semantic Frame?’ tells the reader to expect an explanation of the concept. If the page instead contains mostly unrelated promotional material, the title has misled the audience about its purpose.
Good editorial design begins with the promised answer, continues with what matters and provides enough supporting examples. Relevant further reading comes after the essential explanation.
Do not fill every page with keywords while withholding the information the title offers.
30. An instruction must survive a handover
A teacher gives a task verbally, and a student relays it to a parent. If the message depends on a gesture or unspecified ‘that worksheet’, the handover can fail.
A written version with the exact task, resource and deadline can preserve the action the parent needs to understand, subject to the current authoritative instructions.
Audience design asks whether the message works for the recipient who did not witness the original classroom moment.
31. Spoken explanation and written record serve different tasks
Speech can use tone, pointing and immediate clarifications. A written note should contain enough context to remain usable when the original speaker is absent.
Neither format is automatically better. The appropriate choice depends on what information must endure and what interaction is available.
An audience-aware tutor may demonstrate an operation aloud, then provide concise labelled working the learner can revisit independently.
32. Numbers and units should not disappear in simplification
An explanation says a model is ‘fairly wide’. A student choosing a storage box may need the actual width and unit. Another reader learning the concept might benefit first from a visual comparison.
Simplification should not remove quantities necessary for a real decision. Where measurement matters, include the numerical condition and the context that gives it meaning.
Test the simplified statement by asking whether the intended reader could still choose or verify correctly.
33. The same achievement can be described at different levels
A pupil completed a difficult paragraph with one example visible. A parent-facing update might say, ‘The student can now build the paragraph when guided by a worked example.’ A tutor record might specify which elements were supplied and which were produced independently.
Both should preserve the support condition. Reporting ‘fully independent mastery’ to sound positive would misrepresent the observation.
Audience adaptation is honest when it changes accessibility, not the facts of the work.
34. Feedback needs an actionable level of detail
‘Improve the structure’ may be meaningful to a trained editor but unhelpful to a beginner. A learner might need ‘Put your main claim before the example and explain how the example supports it’.
Once the learner can identify those parts independently, feedback can become briefer. The appropriate level changes with demonstrated experience.
A good message makes the next feasible action identifiable rather than simply sounding encouraging.
35. Two-layer parent and student feedback
For an invented mathematics task, a concise family update might state that the learner understands the equation setup but still needs support with negative signs.
The learner-facing note might show one precise sign error and a short worked correction. The broader family note and the detailed practice example serve different purposes without contradicting each other.
Separate the actual observation from the proposed next action. A parent should not have to infer which part of the mathematics needs attention.
36. Examination guidance needs exact terms
A simplified explanation of at least should still say that the boundary value is included. Replacing it with ‘more than’ changes the Mathematics.
Similarly, a description of a current curriculum or assessment must use the correct official terminology and scope. Audience-friendly prose should not invent a new rule or qualification.
Where the requirement affects a student’s decision, refer to the appropriate current primary source rather than relying on a remembered paraphrase.
37. Professional communication: register is not jargon density
A professional message can be concise and direct: ‘Please review the source for paragraph three by Friday.’ Elaborate phrasing adds little if it hides the actual request.
The right register conveys courtesy and precision without substituting vocabulary complexity for substance.
Ask whether the recipient can identify the task, scope, deadline and expected response. If not, revise the meaning before decorating the style.
38. Audience design in Science reporting
A pupil’s lab summary can explain the measured outcome in plain language. A technical report may include equipment, units, data treatment and uncertainty.
Both should distinguish observation from inference. The accessible version can omit some methodological detail when the purpose permits it but must not transform a tentative association into a proven cause.
See Evidential Markers for the language of reported, observed and inferred information.
39. Audience design in public information
A community notice may be read by residents, visitors, staff and people using assistive technologies. Its critical instructions should be findable and unambiguous across those situations.
Put action and date information where the intended reader can see it. Supply accurate directions and an appropriate source for updates when the information may change.
Do not report a proposed event as confirmed merely to create a cleaner headline. The difference between planned, tentative and approved remains relevant to every audience.
40. Different audience roles can affect a conversation
A learner speaks to the tutor while classmates are listening. The learner may choose a shorter answer because the tutor already knows the diagram, or explain more for classmates.
Bell’s model recognises different audience roles. The relevant style may respond to an addressee and to other participants, but it is inappropriate to claim the student’s exact motive solely from one short utterance.
Use an observational question: ‘Which listeners needed the additional explanation, and what changed when the speaker provided it?’
41. An audience can change during the task
A group begins by discussing a project internally. Later it prepares a public exhibition caption. The participants, background assumptions and expected reading conditions have changed.
The draft should be reviewed for unexplained names, private shorthand and claims whose evidence is unavailable to public readers. Changes in audience can reveal previously hidden context dependencies.
Audience design is an ongoing check, not a single demographic label written before drafting.
42. Feedback from actual readers is more useful than stereotypes
Give an invented instruction to a second reader without the original explanation. Ask what action they would take and which word, number or referent remains unclear.
Do not simply ask whether they liked the wording. A pleasant impression is not the same as accurate understanding or task success.
Use the observed misunderstanding to revise one specific part. Then retest the revised instruction under an appropriate condition.
43. An audience map with four questions
Write four headings: Intended reader; Relevant knowledge; Required action or understanding; Misunderstandings to prevent. Add a fifth optional line for how the reader will access the message.
For a school project notice, the reader may need a clear deadline, precise task and a way to find the current file. The writer need not add several pages of background unrelated to that action.
This map is a practical design aid, not a scientific measurement of what every member of the audience knows.
44. Worked case: a vocabulary explanation for a younger pupil
A Secondary student is asked to explain invariant to a younger learner. They begin, ‘An invariant is a property preserved under a specified transformation.’ The definition is accurate but may be too abstract to serve as the only explanation.
They add, ‘If we move five counters into a different row without adding or removing any, we still have five counters.’ Then they return to the technical word: the count was invariant under the rearrangement.
The adaptation preserved the core idea and supplied a concrete example, without pretending that every mathematical invariant is just a counter count.
45. Worked case: the same explanation for a mathematics teacher
The learner then explains that parity is invariant under adding an even integer to another integer. They show a short algebraic argument with even and odd forms.
The more technical account is appropriate when the audience needs a general justification. It does not replace the younger learner’s example; it performs a different explanatory task.
Ask whether the two versions conflict. They need not: one illustrates a narrow case, and the other establishes a broader statement under explicit assumptions.
46. Worked case: writing two versions of a school message
Version A says, ‘The worksheet is due tomorrow.’ It may be adequate in a same-day classroom chat. Version B says, ‘Submit Worksheet C, Questions 1–4, by the date and time listed on the current class notice.’
The second is more durable when readers arrive later, but should name the actual date if it is known and needed for action. It must not invent a deadline or platform not provided by the teacher.
Audience design changes the supporting detail to protect the same intended action across time and readers.
47. Worked case: a technical diagram for the public
An engineer or teacher uses a diagram with abbreviations understood by their colleagues. A public-facing version may need a legend, descriptive labels and a short explanation of what the reader should notice.
The underlying measurement and physical relationships should remain the same. A friendly diagram that changes units or omits a critical limitation is not an accurate adaptation.
Ask a reader to explain what each symbol means and which conclusion the diagram supports. Revise the missing explanatory layer rather than changing the evidence.
48. A six-step audience-aware writing check
First state the intended reader. Second name the communication act: explain, request, report or persuade. Third identify essential facts and terms. Fourth supply necessary context. Fifth inspect accessibility and ambiguity. Sixth test whether a reader can perform the intended interpretation.
The sequence can be shortened for a casual low-stakes message. More consequential communication may require authorised reviews, source checks and an accessibility process beyond the checklist.
The steps are not a claim of scientifically optimal writing. Their value lies in making ordinary editorial assumptions visible and checkable.
49. Diagnostic: what kind of audience problem is this?
Case A: a note refers to ‘that one’ with no available object. Missing reference. Case B: a message says ‘approved’ when only receipt was confirmed. Misreported status. Case C: a science explanation skips a prerequisite concept. Missing accessible background.
Case D: a public notice contains unexplained private abbreviations. Missing context. Case E: a simplified claim drops the uncertainty in the original source. Meaning distortion.
Each issue needs a different repair. The word audience does not tell us which one until we inspect the reader’s task and the text.
50. Twelve quick questions with answers
1. Does audience design mean lying differently to different people? No. 2. Can the same facts require different explanation depth? Yes. 3. Is formality equal to clarity? No. 4. Can a future reader lack today’s common ground? Yes.
5. Is the addressee identical to every overhearer? No. 6. Should jargon always be deleted? No. 7. Can a glossary help a newcomer? Yes. 8. Does a short message always save effort? No.
9. Can a reader test improve the draft? Yes, for the tested task. 10. Should stereotypes replace evidence about readers? No. 11. Must requirements survive paraphrase? Yes. 12. What is the aim? Accurate, accessible communication that helps the intended reader understand or act.
51. Frequently asked questions
Is audience design only for public speaking? No. It applies to writing, messages, explanations and other language choices. Do children need a separate vocabulary? They may benefit from familiar words and concrete examples while also being introduced to precise new terms.
Can experts read plain language? Yes; plain language can help many readers when it preserves necessary detail. How do I handle a mixed audience? Use clear foundations and optional depth, with accessible navigation.
What is the risk of simplifying? Omitting a scope condition, requirement or evidential limitation. Check that the simplified version still supports the correct decisions.
52. Primary sources and your next action
Allan Bell, Language Style as Audience Design (1984), introduces a sociolinguistic model of style variation relative to addressees and other audience roles. The ERIC record summarises its claims. For accessible digital content, the W3C WCAG overview provides relevant accessibility standards.
The invented student, parent, tutor and public-notice cases above are educational illustrations, not findings that Bell’s research experimentally validated this particular writing checklist.
Choose a paragraph you wrote today. Identify who will read it, what that reader already has good reason to know, what action or understanding you need, and which important distinction could be lost in simplification. Rewrite the paragraph for that audience, then ask a real reader to explain what they understood. The vocabulary has become a practical design instrument.