From approved brief to signed-off email.
Email production is the work between an idea and an approved draft in the ESP: brief, copy, build, an edition per market, checks, approval and handover. A small CRM team gets through it by writing one brief, naming one approver, and booking review time before anyone writes copy.
What are the steps from brief to approved draft?
Email production has seven steps, and they run in the same order for every campaign: brief, copy, build, per-market editions, checks, approval and handover to the ESP. A small team skips none of them. It does each one once, in order, and does not go back to an earlier step without saying so.
- Brief. One page that states the objective, the audience, the offer (or “no offer”), the products, the markets, the send window and the approver. The email brief template has a section per market.
- Copy. Subject, preheader, headline, body and button, written in the brand’s voice in one language: the master.
- Build. The master laid out from the brand’s own blocks, with images, alt text, links and UTM tags.
- Per-market editions. The master adapted for each market: language, prices, products, links, legal line and send time. The email localization guide covers what changes.
- Checks. Links, tags, images, personalization, rendering and the market rows, once per campaign and once per market. The email QA checklist lists them.
- Approval. One named person reads the checked editions and approves them, or sends back one list of changes.
- Handover to the ESP. The approved editions go into the ESP as campaigns, get a test send to real inboxes, and are scheduled in each market’s time zone.
The approval step sits after the checks on purpose. An approver who reads an email with a broken link spends approval time on a mistake the checks should have caught.
Who does what, in a team of one or a full team?
In a team of one, you do every step except approval; in a team of two or three, the work splits by step, and the person who checks an email is never the person who built it. The approver is one named person in every case.
| Step | Team of one | Team of two (lead, producer) | Team of three (lead, writer, builder) |
|---|---|---|---|
| Brief | R: you. A: the approver | R: lead. C: producer. A: the approver | R: lead. C: writer, builder. A: the approver |
| Copy (master) | R: you | R: producer. C: lead | R: writer. C: lead |
| Build | R: you | R: producer | R: builder. C: writer |
| Per-market editions | R: you. C: each market’s reviewer | R: producer. C: each market’s reviewer | R: writer. C: each market’s reviewer |
| Checks | R: you, on another day than the build | R: lead | R: lead. C: builder |
| Approval | A: the approver. I: you | A: the approver. I: lead, producer | A: the approver. I: the team |
| Handover to the ESP | R: you | R: producer. I: lead | R: builder. I: lead |
Who is the approver? In a team of one, it is the person you report to or the brand owner, never you: nobody approves their own copy well. In a team of two or three, the lead can approve, as long as the lead did not write the copy. Market reviewers sit outside the team in most small brands: a colleague in the local office, a store manager, a freelancer who knows the market. Name each of them in the brief.
Where does the time go in email production?
In a small team, most of the time goes on waiting and rework, not on writing: waiting for an answer the brief did not give, redoing a build after late feedback, and approving the same email twice because something changed after approval.
Four patterns cost the most time, and each has a fix that belongs to an earlier step:
| Where time goes | Why it happens | The fix, and its step |
|---|---|---|
| Questions in the middle of the build | The brief left the offer, a price or a legal line blank | Brief: no field is blank; an unknown field says “open” and names who will answer it |
| Rebuilding after feedback | Feedback on the idea arrives after the email is built | Brief: the approver signs off the idea before copy starts |
| Market edits that ripple back | A reviewer changes the structure, not only the words | Copy: the master is agreed before editions start; editions change only what the market needs |
| A second approval | A change lands after approval | Approval: one round of consolidated changes; anything later is a new version |
To see where your own time goes, log it for a few campaigns: the step, the hours, and what you were waiting for. The log usually points at one step, and it is rarely the copy.
How do you protect review time?
Protect review time by booking it before the copy is written, and by sending reviewers less to read: one checked edition, the master beside it, and a deadline. Review that is not in anyone’s calendar happens late, in a hurry, or not at all.
- Book the slots when the brief is signed. Put a review slot in each market reviewer’s calendar and an approval slot in the approver’s, for the days the editions will be ready.
- Send a checked email. Run the checks before review, so reviewers spend their time on language and market, not on broken links.
- Send the master beside the edition. A reviewer who can see what changed reviews faster and catches more.
- Ask one question. “Is this right for your market?” is easier to answer than “any thoughts?”, and it keeps the reviewer on their job.
- Set a deadline, and what happens after it. Agree in advance that an edition with no answer by the deadline is held, not sent unreviewed.
What does an approval flow with one approver look like?
An approval flow with one approver collects every reviewer’s comments first, then gives one named person one checked version to approve or return. The approver decides; reviewers advise. Two approvers on the same email means nobody is sure which answer counts.
- Name the approver in the brief, with the markets they cover. One person, not a team or a channel.
- Collect reviews first. Market reviewers, and legal where a legal line or a price claim is involved, send their comments to the person who built the email, not to the approver.
- Apply the comments and run the checks again. The approver sees one version with every review in it.
- The approver answers once: approved, or one list of changes. A list, not a thread.
- Treat any later change as a new version. It goes back to the approver, with the change marked.
- Record the approval: who approved, which version, and when. Keep it with the campaign, so anyone can see what was approved.
If the approver is away, the brief names a stand-in for that campaign. The stand-in is still one person.
What does a weekly email production calendar look like?
A weekly calendar for a small team gives each day one step, and works on next week’s campaign: the brief is signed on Monday, and the email is in the ESP, approved and scheduled, by Friday. A team of one follows the same days and does each step alone.
| Day | Step | Booked with |
|---|---|---|
| Monday | Brief written and signed; open fields named | The approver |
| Tuesday | Copy for the master; build starts | The team |
| Wednesday | Build finished; an edition per market; editions sent for review | Each market’s reviewer |
| Thursday | Review comments applied; checks per campaign and per market; approval | The approver |
| Friday | Handover to the ESP; test sends; scheduling; a short log of what went wrong | The team |
Keep Friday afternoon free of new work. It is the buffer for a held edition or a late legal line, and the time to write next Monday’s brief. Flows and triggered emails follow the same steps but not the same week: give them their own slot, so a campaign deadline never pushes them aside.
Where Caliber fits
Caliber is being built for this workflow. One approved brief will become a draft per market, checked against your brand’s own guide and built from your own blocks, for one named person to approve. Drafts go to your ESP through Caliber’s integrations with Klaviyo, Braze, Salesforce Marketing Cloud Next, Voyado, Customer.io and Iterable.
Questions
How long does it take to create an email campaign?
It depends less on writing than on how many editions the campaign has and how quickly review comes back. Plan in steps, not hours: brief, copy, build, editions, checks, approval and handover. A weekly rhythm with one step a day gives a small team one campaign a week, with Friday as the buffer.
How should a small email marketing team be structured?
Split the work by step, not by market. In a team of two, a lead writes the brief and checks, and a producer writes, builds and makes the editions. In a team of three, writing and building split. In every size, one named approver signs off, and each market has a named reviewer.
What does a CRM manager do in email production?
A CRM manager in a small team owns the brief, the calendar and the result. They decide what each email is for and who receives it, write or commission the copy, make sure every edition is checked, get approval, and load the approved emails into the ESP. In a team of one, they do all of it.
Who should approve a marketing email?
One named person who did not write it, for the markets they cover. Reviewers check language, market and legal lines, and their comments go to the person building the email. The approver then sees one checked version and approves it or returns one list of changes. Any later change is a new version.
Should the person who builds an email also check it?
Not if anyone else can. The builder knows what the email should say and reads that instead of what it says. In a team of one, run the checklist on a different day from the build, and read the edition on a phone, as a reader would.