Name the audience action and the campaign's limits
Write one primary objective in behavioural terms: understand a mechanism, try a feature, attend an event, join a community with a clear purpose or complete an eligible product step. Add the market, language, timing and the audience's current level of category knowledge.
State what the campaign is not trying to do. A creator cannot balance developer education, mainstream acquisition, token awareness and community retention inside one short deliverable without losing focus.
Supply approved evidence in plain language
List the live product, supported networks, custody model, fees, eligibility, onboarding steps and links to current documentation. Distinguish released functionality from roadmap items and opinion from verifiable fact.
Include screenshots or recordings that the creator may show, plus a named technical reviewer. If a fact changes during the campaign, issue a versioned update and identify affected deliverables.
Make the safe boundary visible
Provide required facts, optional angles and prohibited claims. Do not ask creators to promise returns, describe speculative outcomes as typical, conceal commercial relationships or turn uncertain roadmap language into certainty.
Explain the reason for sensitive boundaries. Creators are more likely to preserve the intent when they understand whether the issue is product accuracy, market eligibility, platform policy or legal review.
Define the asset, post and evidence separately
Record format, channel, duration, quantity, posting window, link, disclosure, call to action and required product evidence. State whether raw footage, cutdowns, thumbnails, captions or translated versions are part of the delivery.
Add a live-URL and reporting requirement for posted content. An approved file is not the same as an accepted placement, and the brief should show which one the agreement buys.
Set deadlines that both sides can operate
Name the reviewer, feedback format, response time, revision allowance and escalation path. Consolidate brand, product and legal notes so the creator is not resolving contradictory comments from several stakeholders.
Specify organic use, paid use, editing, localisation, likeness, territory, term, exclusivity and takedown. Describe the actual media plan directly instead of relying on phrases such as full usage rights.
Decide what the creator and brand must return
List the platform metrics, capture date, screenshots or exports, link parameters and product events required. Clarify attribution windows and privacy limits. Performance evidence should be proportionate to the campaign and available through legitimate access.
Close the brief with the acceptance checklist and commercial contacts. A creator should know who can approve a factual question, who handles logistics and what evidence releases final payment.
One-page crypto creator brief
| Component | What to record |
|---|---|
| Objective | Audience, market, action, timing and non-goals |
| Facts | Live product, evidence, terminology and reviewer |
| Claims | Required points, optional angles and prohibited language |
| Delivery | Format, posting, review, rights and acceptance |
| Reporting | Metrics, capture window, links and product events |
A sample brief for a product walkthrough
Consider a hypothetical Web3 tool that helps users complete a defined workflow. The creator’s assignment is to explain that workflow to a named audience, using the current product and approved facts. It is not to make a token-price prediction or imply that the product removes financial or security risk. Keep those boundaries in the brief itself, not only in an attachment nobody reads.
The fact pack should distinguish shipped functionality, restricted access and planned features. Give the creator a safe demonstration environment and identify any screens that must not be recorded. Private keys, recovery phrases and personal account information have no place in public demonstration footage. If a mock interface is needed, label it so the audience is not misled about what exists.
Define a deliverable your team can accept: one defined walkthrough, the relevant aspect ratio and duration range, caption or disclosure requirements, the posting account and the review window. State whether the brand is buying an asset, creator distribution or both. A creator who has been paid to produce footage has not automatically agreed to publish it to their audience.
The review process should have separate factual and creative responsibilities. Product corrects an inaccurate explanation. The campaign lead evaluates whether the narrative answers the brief. One person consolidates those comments before they go back to the creator. Conflicting messages from several stakeholders should not become unpaid guessing work for the production partner.
At final approval, save the caption, thumbnail, destination and asset together. Give the creator the approved version in one handoff and state how to handle later changes. For reporting, request the evidence appropriate to the purchased work: asset acceptance for production, live links and native analytics for distribution, and separately defined product events for acquisition. This makes the brief useful beyond the shoot; it becomes the common reference for publishing, payment and learning.
Sources and further reading
Use these primary references alongside the operating recommendations above. Platform and jurisdiction requirements should be checked again before a campaign launches.
