Key takeaway
Define one content source for facts, numbers, quotes, and assets. Reorder information for each format rather than copying word for word. Label asset versions, crop ratios, and usage scope, and keep text editable. Update the source once, then export each format, so three outputs do not drift apart.

Consider a hypothetical case. A product launch requires three deliverables at once: a website page update, a long image from marketing, and a deck for sales. Three teams start separately with their own source material. After launch: the website says maximum load 500 kg, the long image says 450 kg, and the deck says "up to 500 kg, 450 kg with the optional configuration." None is entirely wrong; they describe different configurations, but readers think they describe the same thing.
Nobody copied wrong. There was no shared content source. Three formats maintaining their own facts will drift over time.
Three formats, not three copies
The reading modes differ:
- A website scrolls and links; information can layer and expand, suited to complete explanations and search.
- A long image appears at once, read top to bottom; information must compress, pacing must be strong, suited to sharing and on-site display.
- A deck is paced by a speaker, one point per slide, little text, with the speaker adding detail.
Copy word for word and the long image becomes dense while the deck becomes a document. Write separate versions and facts drift. The correct approach: one content source, reordered per format.
Define the content source
The source includes at least: product facts and specifications, service scope and conditions, key numbers and definitions, approved quotes and cases, and an asset list with rights.
It can be a structured document or spreadsheet; no complex system required. The point: every format takes facts from here and never edits numbers locally.
The source needs an owner and a version. When specifications change, the owner updates the source and notifies the three format maintainers.
Information hierarchy per format
Website: the first screen answers what it is and whom it helps; below, expand features, conditions, evidence, and FAQs. Information can be complete and paragraphs longer.
Long image: open with the problem, develop three to five points, end with an action entrance. One point per screen, short text, visible numbers, but never drop key conditions.
Deck: one argument per slide with one image or set of numbers; detail lives in speaker notes. A deck is not a document; do not move website paragraphs into slides.
Sections may appear in different orders. That is not inconsistency as long as facts, numbers, and conditions agree.
Asset versions and crops
One product photo may be 16:9 on the website, vertical in the long image, square in the deck. Hand off:
- The original high-resolution file, not only cropped versions.
- Required crop ratios and safe areas per format.
- Asset version or date, so an old image does not replace a new one.
- Usage scope and restrictions.
If an image contains text or data, provide an editable text layer instead of burning it in. Then language or number changes do not require regenerating the image.
Keep text editable
Deliver editable source files for long images and decks, not only exported images or PDFs. At minimum, keep titles, body text, numbers, and captions editable.
Next time a price, date, or specification changes, edit text instead of rebuilding the image. Proofreading and language versions also become easier before publishing.
Updates and versions
Use a common version marker: content source version, export date per format, and the facts version. Any update changes the source first, then the three outputs.
If only one format changes, note it in the handoff table so others do not assume the rest are updated. Before publishing, cross-check key numbers, conditions, and dates across the three.
A handoff table
Format | Information hierarchy | Asset ratio | Text state | Version and owner |
|---|---|---|---|---|
Website page | First screen, features, conditions, evidence, FAQ | 16:9 plus mobile crop | Editable page fields | Source v3; website editor |
Long image | Problem, three points, action entrance | Vertical, screen safe areas | Editable source and export | Source v3; marketing design |
Deck | One argument per slide, speaker notes | 16:9 slides | Editable deck | Source v3; sales enablement |
The table need not be complex, but it must answer which source this version uses, who owns it, and where to change it next time.
The content source needs explicit edit rights. Not everyone may change product specifications and external commitments; anyone can propose a change, but the owner confirms it. Each change records the version, editor, reason, and affected formats, so two teams do not overwrite each other.
A simple change log is enough: date, field, old value, new value, owner, and which outputs were updated. When a number is questioned later, the log answers where it came from and who approved it. If the source lives in a spreadsheet, protect the cells that define facts and commitments, and let comments carry proposals. If it lives in a document, use suggestions rather than direct edits for those sections. The format matters less than the rule that facts have one owner.
Use One Fact Sheet Across All Three Formats
[Cross-format content handoff checklist]
1. Content source
- Do facts, numbers, conditions, and quotes come from one source:
- Does the source have an owner and version:
- Do all three formats cite the same version:
2. Formats
- Is hierarchy reordered for website, long image, and deck:
- Is word-for-word copying avoided so the image stays readable and the deck stays a deck:
- Are key conditions and limits kept in all three:
3. Assets
- Are original high-resolution files and crop ratios provided:
- Do assets carry a version or date:
- Are text and data in images editable:
- Is usage scope recorded:
4. Updates
- Does updating start from the source and then the outputs:
- Is a single-format change noted:
- Are key numbers, conditions, and dates cross-checked before publishing:Before publishing, place all three formats on one screen and compare specifications, conditions, and dates. If they do not describe the same thing, return to the source rather than editing three files separately. The scope of cross-format content and visual material can be discussed within content and interactive support.
Naming and rights ledgers for enterprise assets are in how to manage an enterprise asset library; restructuring content per platform is in publishing one piece everywhere is not simple.
Use a brand imagery brief for illustrations and hand off chart sources and definitions separately, rather than flattening everything into one image.