HEXWAVE / BRAND VOICE REFERENCE
Keep factual product context separate from writing choices.

VOICE SHEET
Reader and immediate situation:
What the brand notices about that situation:
Terms to use (match the real interface where relevant):
How we address the reader:
Humor that fits / humor that doesn't:
Approved example 1:
Why it works (specific editorial decision):
Approved example 2, in a different context:
Why it works:
Rejected example:
What the revision must change:
Reference owner / revision date:

SEPARATE PRODUCT FACTS
Confirmed capability / source / checked date / owner:
Current limits:
Claims requiring evidence we do not yet have:

WORKED EXAMPLE — FICTIONAL THREADWELL
Fact: user manually assigns a comment to a colleague.
Unestablished: automatic routing, AI assignment, time savings.
Weak: Effortlessly elevate your team's collaboration.
Demo revision: Open a comment, choose an assignee, then mark it resolved when the answer is in.
Decision: name the actual action; don't replace a vague benefit with an invented capability.

DRAFTING ASSIGNMENT
Write [opening / spoken explanation / caption] for [reader and task].
The actual footage shows [actions]. Use only these facts: [facts and sources].
Use these approved voice examples: [examples with reasons].
Do not infer [missing capabilities or outcomes].
The viewer should understand [specific thing] and can next [available action].
List necessary missing facts separately rather than inventing answers.

REVIEW
Nouns and verbs match supplied facts:
Example data labeled:
Text can be spoken over the visible action:
Each sentence adds useful information or connection:
Actual export, not just draft, reviewed:
Repeated correction worth adding to reference: