Quase toda briga começa com um "achei que você quis dizer". Um briefing define as entregas, as datas, as revisões, o pagamento e o que é proibido, e os dois lados aceitam antes do trabalho começar.
O que tem
Exatamente o que será feito, e quantos.
Quando saem os rascunhos, quando são as aprovações e quando vai ao ar.
Quantas rodadas estão incluídas no preço.
Quanto, e quando é pago.
O que precisa estar e o que não pode.
Você vê quando o briefing foi aberto e quando foi aceito.
Como funciona
A partir de um modelo ou do zero.
Sem anexo para se perder.
O outro lado revisa, responde e aceita.
O briefing vira o contrato, e depois o trabalho.
Funciona com
Um contrato montado a partir das condições já combinadas, assinado online pelos dois lados.
WorkdeckQuadros, tarefas e controle de horas, ao lado do acordo de onde o trabalho veio.
CampanhasCampanhas com criadores em que cada clique, cadastro e venda é creditado ao criador que o gerou.
Tabela de preçosSeus preços por plataforma, entrega e pacote, publicados antes que alguém precise perguntar.
Mais em Combinar e tocar o trabalho
O guia completo está em inglês.
Both sides should know exactly what they agreed to make. Brief puts the deliverables, dates, revisions, compensation, requirements and exclusions in one place.
Then turn it into an Agreement without typing everything again.
Most briefs don't actually exist.
The person commissioning the work has an idea of what they want.
Whatever the actual agreement is. If the deliverable can't be counted, it probably isn't defined clearly enough.
When does the final version go live? Every important stage gets a date.
Without a number, "revisions" can easily become unlimited.
Everyone should know the commercial expectation before the work begins.
Anything that could otherwise be assumed should be named.
The information the creator needs to produce the right first draft.
A Brief gives your creator a clear target.
You don't have to wait for a brand to write the Brief.
If you've agreed the job in messages and nobody has formalised it, write the Brief yourself.
If six creators receive slightly different instructions, you don't have one campaign. You have six interpretations of one campaign. A shared Brief gives everyone the same source.
Everyone can work from the same definition of the job.
You don't need to attach another PDF to an email.
Silence doesn't tell you much.
Brief shows when it has been opened. That gives you a simple answer to a very ordinary question: Have they seen it?
The most useful time to discover disagreement is before anyone starts.
This is one of the most important parts of the workflow.
The Brief also defines what actually needs to be done.
Write down the actual deliverables, dates, revisions, compensation, requirements and exclusions.
Share it as a link. The other side can open it directly in their browser.
See when the Brief has been viewed.
The other side can review the terms. If something is wrong, resolve it before work begins.
Both sides now have a shared understanding of what is being made.
Generate the Agreement from the accepted terms. No retyping. No second version of the deal.
Move the actual work into Workdeck so the team can track what needs to happen.
Now everyone is working from the same definition of the job.
Now the creator can start without wondering whether the brand meant something else.
Instead of six slightly different conversations, the campaign has one clear Brief. Everyone works from the same source. The brand can still handle creator-specific details where needed.
But the foundation stays consistent.
Campaigns are where the wider brand-creator engagement lives.
Brief defines the work inside that campaign. For a campaign with multiple creators, the Brief can give everyone a common source of truth.
What each participant is actually being asked to make.
Brief defines the deliverables.
Some work needs several people to review it before it goes live.
The Brief defines what the final work should contain. Approval Chain handles the process of getting the finished work reviewed and approved.
A Rate Card can establish the creator's standard pricing.
WhatsApp is where a conversation happens.
A Brief is where the result of that conversation becomes clear.
| Klairova Brief | WhatsApp Conversation | |
|---|---|---|
| One place for the terms | Yes | No |
| Deliverables clearly defined | Yes | Often scattered |
| Dates clearly defined | Yes | Often scattered |
| Revision limit | Yes | Easily forgotten |
| Compensation | Yes | Buried in messages |
| Exclusions | Yes | Often omitted |
| Requirements | Yes | Spread across messages |
| Shareable | Yes | Yes |
| Know when it was opened | Yes | No |
| Formal acceptance | Yes | No |
| Converts into Agreement | Yes | No |
| Can become Workdeck tasks | Yes | No |
| Easy to reference months later | Yes | Difficult |
A PDF can describe the work.
Brief makes the work part of the workflow.
| Klairova Brief | Static PDF | |
|---|---|---|
| Shareable link | Yes | Usually requires attachment |
| Track opening | Yes | No |
| Acceptance | Built in | Usually separate |
| Connected to Agreement | Yes | No |
| Connected to Workdeck | Yes | No |
| Easy to update before acceptance | Yes | Requires new version |
| One source of truth | Yes | Version management required |
| Searchable in Klairova | Yes | Depends where saved |
| Part of the campaign workflow | Yes | Usually external |
A few things to check.
Creator work has become commercial.
A Brief is a structured definition of the work both sides agree to before the work begins. It records things such as deliverables, dates, revisions, compensation, exclusions and requirements.
Both brands and creators. A brand can write the Brief. A creator can write the Brief when the brand hasn't provided one. The important thing is that both sides understand and accept the same definition of the work.
Yes. In fact, that can be one of the most useful things a creator does when the terms have been agreed informally but the brand hasn't sent a formal Brief.
Yes. The Brief can be shared as a link so the brand can open it and review the terms.
Yes. Brief tracks when the recipient opens it.
Because silence is ambiguous. If someone hasn't responded, knowing whether they have actually opened the Brief gives you useful context.
Yes. The purpose is for both sides to review the work and resolve disagreements before production begins.
Resolve the disagreement before starting. The Brief can be changed and reviewed again. That's exactly when disagreement is useful, before the work exists.
If the scope changes, the change should be documented and accepted rather than quietly changing the original understanding. The exact versioning behaviour should follow the product's implementation.
No. A Brief defines the work. An Agreement formalises the commercial terms between both sides. The accepted Brief can be used to generate the Agreement without retyping the terms.
Yes. The Brief is designed to be convertible into an Agreement without retyping the information.
Because the Brief and Agreement should not contradict each other. If the Brief says two Reels and the Agreement says three, you've created another problem. Generating the Agreement from the accepted Brief keeps the two connected.
Yes. The deliverables in the Brief can become the basis for Workdeck tasks.
Yes. A campaign can have a Brief attached so participants work from the same requirements.
Yes. A campaign Brief can provide common requirements for multiple participants.
The core Brief model supports defining the work, and campaign workflows can contain participant-specific requirements where applicable. The exact implementation should determine how those variations are represented.
The more important something is to the job, the less you should leave it implied.
There is no universal number. Agree on the number that makes sense for the job. The important thing is that there is a number.
Because people naturally fill gaps with assumptions. If something isn't included, saying so prevents it from quietly becoming part of the expected scope.
Usage should be clear before the work begins. For detailed usage arrangements, Klairova's Content Licences and Ad Rights features provide dedicated infrastructure for those rights.
Yes. Compensation and payment expectations are part of the Brief. The formal Agreement can then carry those terms forward.
Yes. Brief is useful whenever two parties need to define work before it begins.
A Campaign is one context where it becomes especially useful.
Yes. A creator can use a Brief to define what they are delivering to a client before starting the work.
Yes. A brand can define exactly what it wants produced and send the Brief to the creator for review and acceptance.
A Brief is primarily a definition of the work and shared understanding. The formal legal agreement should be handled through Agreement and, where necessary, reviewed by a qualified lawyer.
The core product is built around defining work between parties, particularly brands and creators. The exact range of non-creator workflows should follow the product's supported implementation.
Abra uma conta em poucos minutos. Usar não custa nada; uma pequena taxa só se aplica quando o dinheiro passa pela Klairova.
Criar sua conta grátis