Brand Design
Sonic branding briefs: Describe the behaviour people will hear
Build a sonic branding brief around touchpoints, listening conditions, creative boundaries and delivery checks, using a practical fictional example.
A cheerful closing sound in a coworking space’s promotional film may feel intrusive when a booking is completed in a quiet room. Reusing one sound everywhere does not establish consistency on its own. A sonic branding brief should explain what the sound must do, rather than simply list music the team likes. The coworking space below is fictional: it is a way to test production decisions, not a claim about a successful client project.
Define the job of the sound and where silence belongs
Choose three touchpoints for the example business: a promotional film’s closing frame, a telephone waiting segment and a booking confirmation. The first may need a recognisable signature, the second a calm background and the third clear feedback about an action. Do not treat them as different lengths of the same file. A person must still understand a completed booking with sound disabled. Adding audio to every brand interaction should not become the objective.
Translate adjectives into audible decisions
Friendly, innovative and premium suggest different music to different people. Add an observable decision beside each adjective: a soft entrance for warmth, fewer dense layers that mask speech for clarity, or a short rhythmic accent rather than a prolonged build for movement. These are possible creative choices, not universal rules. Describe unwanted associations too. Use references as annotated listening examples that identify the quality under discussion, rather than as melodies to reproduce.
Show the listening conditions with a realistic sample
Do not approve the draft only on studio headphones. Listen through a phone speaker, a laptop and a video containing speech. Ask someone to listen quietly and note whether the intended meaning survives. Review the closing signature in a sample film of realistic length, rather than behind an otherwise silent image. This separates liking a piece of music from seeing whether it works in use. Agree technical output levels against the distribution channel’s current requirements.
Make user control a design decision
Do not make automatically playing audio the default website solution. W3C’s explanation of WCAG 1.4.2 requires a pause/stop mechanism or volume control independent of system volume for automatic audio lasting more than three seconds. A listening sample started by the visitor may be clearer. Also communicate important information through text or appropriate visual feedback. A short sonic logo does not, by itself, demonstrate that the complete experience is accessible.
Specify the handover through use cases
Name the required variations separately, such as a master recording, an arrangement beneath speech and a short ending. Record the version, intended placement and approval state for each file. Ask the producer for documentation of the sources used and the agreed usage scope; receiving a file does not establish unlimited permission to use it. Discuss editable sources and export formats in the brief. The next video team should not need to guess which sound is current.
Approve the work in a focused listening session
Let participants hear the examples before showing them the brand adjectives. Ask when the sound begins, whether it masks speech and whether repetition becomes tiring, as well as how it feels. Then return to the brief. One acceptance record for the fictional space might state that booking confirmation is understandable in text, sound is optional and the film signature does not interrupt the closing words. Attach each correction to a file version and time position.
Frequently asked questions
Does every brand need a sonic logo?
No. If there is no meaningful, recurring place for sound, resolving the existing experience may be more useful.
Can a favourite song be a reference?
Explain the quality you want to discuss; do not assume permission to use its melody or recording.
What should we check in the first delivery?
Review realistic usage, versions, technical outputs, accessibility behaviour and usage documentation together.
Connect sonic identity with visual identity and brand messages in the same brief. Bringing realistic usage examples to a BiKreatif scope discussion makes the production requirement easier to define.
Source
W3C — Understanding SC 1.4.2 Audio Control — https://www.w3.org/WAI/WCAG22/Understanding/audio-control.html