analyzing-audience-brief-and-skopos

name	analyzing-audience-brief-and-skopos
description	Establish who will read the target text, how they will use and receive it, and the purpose (Skopos) the commission sets, from a translation brief and a document profile — before any wording decision.
kind	skill
status	ready
provenance	{"principles":["P002","P007","P020","P024","P056","P061","P069","P090","P099","P108","P109","P121","P129"],"claims":["C00035","C00040","C00047","C00058","C00095","C00110","C00125","C00576","C00583","C00618","C00631","C00749"],"evidence":["E00028","E00033","E00040","E00050","E00084","E00097","E00111","E00534"],"source_anchors":[]}

Analyzing Audience, Translation Brief and Skopos

Purpose

This skill guides the translator to establish who will read the target text, how they will use and receive it, and the purpose (Skopos) the commission sets, from a translation brief and a document profile — before any wording decision. It advises on the decision; it does not produce the final translation, override the client's brief, or sign off safety-critical or legally-mandated content — those are handed back to the translator and the commissioner.

When to use

• Starting a technical-translation or localization project.
• starting any translation project.
• Target users need a usable technical document rather than a surface replica.
• Creating or translating user-facing technical documentation.
• The final text type, medium, use, or audience is unclear or strategically important.
• the client supplies no usable brief.
• establishing a translation brief.
• no explicit style guidance is provided.
• Target function requires adaptation but stakeholders still have legitimate expectations.

Procedure

1. Base translation decisions on who will read the text, how they will use it, and how it will be distributed, and establish these via a translation brief specifying at minimum the target audience, the intended purpose (information vs publication), and any stylistic or terminological requirements. (P002)
2. Let target-user needs govern additions, omissions, condensation, restructuring, and explicitness. (P007)
3. Plan documentation around specific readers, their tasks, prior knowledge, problems, and objectives. (P020)
4. Define target-text function pragmatically from purpose, audience, initiator, translator, and situation; do not infer it from the source text alone. (P024)
5. Accept that the translation brief has no settled form and often forces educated guesses, so ask the client a short standard set of questions — kept small so as not to seem unprofessional, since the translator is usually the expert — covering at minimum the target language variety, the purpose (information vs publication), the deadline, and any required terminology. (P056)
6. Apply function plus loyalty: meet target-reader expectations while respecting source-side intentions and stakeholder relationships. (P061)
7. Make the audience the primary driver of translation: nearly every decision (term choice, rewording for clarity or tone, resequencing) depends on understanding it, and in translation the audience factors double because two languages and cultures are involved — so identify the source-text and target-text audiences, reconcile any incompatibility, and, when no brief is given, deduce the likely audience from context and text type. (P069)
8. Determine first what type of translation the client wants, because it drives what is translated, how, and how long it takes: a selective translation renders only certain sections; a gist translation is a rough summary needing less care over style; an information-purposes translation must convey all the information but tolerates rough style for internal use; and a publication-purposes translation demands the best content and flawless language, often with a second reviewer. (P090)
9. Understand why a text is structured as it is — function, circumstances of use, logical progression, and cultural norms — and distinguish linked, cohesive texts from discrete-section texts; in discrete-section texts read in unpredictable order, avoid anaphoric and cataphoric cross-references, instead making a reference specific (naming the chapter) or repeating the necessary information. (P099)
10. Categorize readers by role (Horton's novice, occasional, transfer, expert, rote; Markel's experts, technicians, managers, general) to reveal how they use a text — experts skim, novices read in sequence, rote users jump to steps — which for the translator means consistent headings for navigation and short, simple sentences for instructions; treat these categories as useful but oversimplified. (P108)
11. Analyze the target culture as more than nationality: cultural norms shape slang and jargon, forms of address, shared-knowledge references, and conventions for date, time, currency, and legal or institutional references; do not equate one culture with one language, and treat cross-cultural models (Hall, Hofstede, Hoft, Trompenaars) as rules of thumb rather than licence to stereotype. (P109)
12. Let the purpose of the target text (its Skopos), as specified by commissioner and translator, govern the translation rather than the source text; a source is an offer of information from which many valid translations follow once the intended purpose is known. (P121)
13. Create a document profile — identifying subject, audience, text function, key features, and potential problems along with strategies for them — as a method for preparing to translate a given text type effectively. (P129)
14. Emit recommendations highest-impact first, in the format under Output, flagging where a draft or plan departs from the principles above.

Inputs

• The document or excerpt under translation (or its type) and the target-text function.
• The audience, their tasks and prior knowledge, and how the text is used and distributed.
• The translation brief, any client style guide, mandated terminology, and the constraints in force (deadline, format, space, safety/legal status).

Output

Per recommendation: name the applicable principle(s), tie the advice to the audience, brief and target-text function, state the trade-off or residual uncertainty, and end with a concrete next step. Order recommendations highest-impact first. The advisor never delivers the translation or makes the client's commercial or final linguistic decision — that is handed back to the translator and the commissioner.

References

See ../../references/technical-translation-principles-index.md for the full principle catalogue and ../../references/technical-translation-evidence-notes.md for grounding notes. For adjacent concerns, see the sibling skills: selecting-translation-strategy-and-procedures, grounding-translation-in-reader-cognition, handling-terminology-units-and-nomenclature, applying-iconic-linkage-and-consistency, matching-document-type-and-genre, designing-document-structure-and-presentation, planning-usability-evaluations, running-and-analyzing-usability-studies, assuring-quality-safety-and-practice.

Provenance

Derived from P002, P007, P020, P024, P056, P061, P069, P090, P099, P108, P109, P121, P129, grounded in Jody Byrne's Technical Translation: Usability Strategies for Translating Technical Documentation (2006) and Scientific and Technical Translation Explained (2012) (distillation-only). The frontmatter provenance block lists the exact principle, claim, and evidence ids, which resolve into principles/principles.yaml, analysis/claims.jsonl, and evidence/evidence-records.yaml.