One brief, five formats: a multi-channel content workflow
The most expensive part of multi-channel content is not writing it — it is re-briefing AI for each format. A team that writes five separate prompts for five formats spends most of its effort on prompt construction, not on the content. And because each prompt is written independently, voice consistency across the five formats is an accident rather than an outcome.
The efficient architecture runs one brand brief through five format-specific structure rules. The brief is written once. The format rules define what changes.
What stays constant across formats
Brand voice does not change with the channel. Your terminology bans apply to LinkedIn the same way they apply to your blog. The sentence structure rules that make your brand sound direct apply to email subject lines the same way they apply to long-form paragraphs. The brand facts that must be stated accurately apply everywhere.
These are the constant layer: the rules that belong in every format because they define what your brand sounds like regardless of medium. They go in the shared brief, applied to every generation.
Constants to include in the shared brief:
- All terminology bans
- Voice rules that are channel-independent (lead placement, hedge prohibition, sentence structure preferences)
- Brand facts with exact required phrasing
- Required terms and where they appear
- Audience specification
What changes by format
Structure changes with the channel. A blog post has sections and headers. A LinkedIn update has no headers and a very different paragraph structure. An email has a subject line, a preview text, and a body that must reach its point within two sentences. A sales one-pager has a three-column structure. A FAQ has questions and answers.
These are the variable layer: the structural rules that apply only to a specific format. They are added to the shared brief for each format-specific generation.
Format-specific structure rules:
| Format | Structure rules |
|---|---|
| Blog post | H2 headings every 300–400 words; answer-first lead paragraph; FAQ section at end |
| Subject ≤50 chars; preview text ≤90 chars; first sentence states the value; single CTA | |
| LinkedIn update | No headers; paragraphs max 2 sentences; hook in first line; CTA in last line |
| Sales one-pager | Problem → solution → proof → CTA structure; one claim per section; no paragraphs longer than 3 sentences |
| FAQ | Exact question format; standalone answers (each answer works without reading others) |
The format rules go in the generation prompt, not in the shared brief. The shared brief is stable; the format rules change per output.
The workflow
The one-brief workflow has four steps:
Step 1: Build the shared brief. Compile the constants — voice rules, terminology bans, brand facts, audience specification, required terms. This is the brand constitution for this content topic. It does not include any format-specific instructions.
Step 2: Add the topic. Define the specific content: what claim or argument the five pieces will make, what the key evidence or supporting points are, what the reader should know or do after consuming any format. Keep this at the argument level, not the format level. The argument is the same across all five formats; the structure is different.
Step 3: Generate each format with format-specific rules. Run the shared brief plus topic through each format's structure rules separately. Each generation gets the full shared brief plus one set of format-specific rules. Do not combine all format rules into one generation — this produces output that does not fit any format well.
Step 4: Review for cross-format consistency. After generating all five, review them as a set. Check that terminology is consistent, that claims match across formats, and that the brand voice reads the same across channels. One round of cross-format review prevents the inconsistencies that accumulate when formats are reviewed in isolation.
The argument layer
The most common failure in multi-format workflows is confusing format with argument. Teams often build separate prompts for separate formats and end up with five pieces that make five different arguments about the same topic. The LinkedIn update emphasizes one claim; the blog post emphasizes a different one; the email focuses on a third.
Audiences who encounter your brand across channels notice inconsistency in argument before they notice inconsistency in voice. A reader who sees your LinkedIn post and then receives your email should recognize that the two pieces are making the same point, in different depths and structures.
Define the argument before generating any format. Write it as a sentence: "The claim every piece in this batch makes is X." Then verify that each generated piece makes that claim, at the appropriate depth for its format. The blog post makes it with evidence and nuance; the LinkedIn update makes it as a hook and a proof point; the email makes it in the subject line and the first sentence.
Repurposing versus reformatting
This workflow is not content repurposing in the traditional sense — taking a blog post and extracting quotes for social. It is content reformatting: generating each format natively from the same brief, rather than extracting from a longer piece.
Repurposing produces content that reads like extraction — the LinkedIn update is clearly a quote from the blog post, the email is clearly an abbreviated blog summary. Reformatting produces content that reads as native to its channel because it was generated with channel-specific structural rules.
The distinction matters for quality. Reformatted content performs better on each channel because its structure matches what audiences expect on that channel. The additional effort is the format-specific structure rules, which are one-time setup.
Copper Sun's multi-format approach
Copper Sun's content modules include format-specific outputs that run from a shared brand context base. Voice rules apply across every format; each module adds the structure rules for its specific channel. A brief built for one module can generate blog, email, and social content with consistent voice and channel-native structure.
For the brief architecture that makes this work, the structured brand brief template covers each component. For the voice rules that stay constant across formats, how to capture brand voice for AI covers the capture process.
Frequently Asked Questions
How much time does building the shared brief take?
The first time: 30 to 60 minutes for a team that has not built a brand brief before. After the first brief, subsequent briefs for new topic batches take 10 to 20 minutes — the voice rules and terminology bans are stable; the topic and argument change. Over time the brief becomes a template where only the topic layer changes.
Can one brief cover fundamentally different audiences?
A brief covers one audience specification. If your five formats target different audiences — for example, a technical blog post for developers and a sales one-pager for procurement — you need a brief layer for each audience. The terminology bans and voice rules may be shared; the audience specification and argument emphasis differ. Build the shared layer first, then add audience-specific layers.
What happens when a format requires a different register?
Format-specific register differences belong in the format rules, not in the shared brief. If your LinkedIn content is slightly more informal than your blog content, specify that in the LinkedIn format rules: "Register: allow contractions; sentences may open with 'I'; casual phrasing acceptable where formal phrasing would read stiff." The shared brief contains your brand's foundational voice; format rules adjust it for the channel.
How often should the shared brief be updated?
The voice rules and terminology bans in the shared brief are stable — update them when you identify a new failure mode in your content. The topic and argument layers change per batch. The format rules change rarely — only when a platform's norms shift significantly or when you identify a structural failure pattern in a specific format.