Modular content has three layers. Most programs get the middle one wrong

SwishX Team·9 min read
Contents
  1. Introduction
  2. What are the three layers of a modular content framework?
  3. Where does the Notion analogy break in life sciences?
  4. How small should a content module be?
  5. Which components should be locked, and which can flex?
  6. What does one module look like across three assets?
  7. Why do modular content programs stall, and how do you start?
  8. Where SwishX fits
  9. Frequently asked questions

Most modular content programs stall at the middle layer, with modules too small to review or too big to reuse. The three layers explained, where the Notion analogy breaks in life sciences, and one module traced into three finished assets.

A modular content framework organizes promotional content into three layers. Components are the smallest approved pieces, such as a claim with its reference, a chart or the safety information. Modules are pre-approved combinations of components that carry one message. Assets are the finished email, video, detail aid, banner or web page assembled from modules. Meaning is approved once, at the module, and each new asset is reviewed for how the modules are put together rather than for every word.

The idea is not new: pharmaphorum and PharmaTimes were explaining it to brand teams in 2021. Programs stall on where they draw the lines between the layers. This article covers each layer, where the Notion model of blocks and pages misleads, how to size a module, what to lock, and one module from the fictional brand Brevanta traced into three assets. The claims themselves are covered in our guide to building a claims library your MLR team trusts.

What are the three layers of a modular content framework?

Components are the atoms. A single claim in its approved wording, tied to its reference. A statistic with its comparator and confidence interval. A chart. An approved image. A line of copy that makes no claim. The indication statement. The Important Safety Information. Veeva describes modular content components the same way: a claim, copy, a reference link, or a visual asset such as an image or logo.

Modules are the molecules. A module is a pre-approved combination of components that carries one message and is safe to place on its own: the claim, the statistic that supports it, the reference, the qualifier that limits it, and the safety context the claim requires. In the Vault PromoMats help documentation, content modules combine text, images, assets and other data into reusable groups, pass their own Content Module Approval workflow, and carry rulesets: business rules for how their parts may be used.

Assets are what an HCP or patient actually sees: an approved email, a short video, a detail aid page, a banner, a web page. Each one is a template, plus modules, plus the elements specific to that asset, such as a subject line, a call to action and a layout. PromoMats also lets teams group a module's parts into combinations for specific channels, messages or personas, a quiet admission that one module rarely fits every channel unchanged.

If your team uses Notion, the model is familiar. Notion's help pages describe every page as a stack of blocks: a paragraph, an image, a table. A synced block goes further. The same block lives on many pages, and a change to one instance appears everywhere else. Components are blocks, modules are small groups of synced blocks, and assets are the pages.

Where does the Notion analogy break in life sciences?

It breaks first on editing. In Notion, anyone with edit access to the original can change a synced block, and the change appears everywhere at once. An approved component cannot be edited in place. Changing one word of a claim creates a new version that needs review, and every asset using the old version has to be found and then updated or withdrawn. You want the propagation Notion gives you, but only after approval, and with a record of which version went where.

It breaks second on context. A Notion block means the same thing on every page. A claim does not. FDA's advertising regulation, 21 CFR 202.1(e)(5)(ii), says an advertisement fails to present a true statement if it fails to present a fair balance between information on side effects and contraindications and information on effectiveness. Balance is a property of the whole piece, so approving the parts does not approve the whole. The same efficacy claim beside a chart, beside a photo of a patient finishing a half marathon, or straight after a second efficacy claim leaves three different impressions.

It breaks third on audience and dependencies. A module approved for HCPs is not approved for patients, because wording, evidence detail and safety presentation all change. And Notion blocks have no dependencies. A claim may be unusable without a specific qualifier, or barred from sitting next to a specific comparison. Holding those rules, audience included, is the reason a module exists.

How small should a content module be?

Granularity makes or breaks the framework, and teams fail in both directions. Cut too small, and every asset becomes a new arrangement of fragments. Reviewers cannot approve a sentence fragment in isolation, so they review every combination as if it were new, and the promised speed never arrives. Cut too big, and the module is an asset in disguise: a full email body that cannot fit a banner, a video or a different running order.

A workable rule: a module is the smallest unit that carries one complete message and stays accurate and balanced when it appears alone. Veeva's framework calls this being associated, meaning the components in a module must relate to each other so that each grouping delivers a coherent message. pharmaphorum's 2021 explainer used the term atomic design for the same idea.

Three tests settle most arguments. The standalone test: if the module were the only thing on a screen, would a reviewer approve it? If not, it is missing a qualifier or safety context, or it is a fragment of another module. The smallest-channel test: does it fit the most constrained channel on the plan? If not, approve a short variant as its own module instead of letting someone trim the long one at assembly. The reuse test: is it planned for at least two assets? A module used once is overhead.

Which components should be locked, and which can flex?

Lock anything that carries meaning about the product. That means the claim wording, the statistic and how it is expressed, the reference and its exact location, the study population and endpoint qualifiers, the indication statement, dosing, and the safety information. Lock charts too, including the axis scale and where it starts, because a redrawn chart with a truncated axis makes a new claim.

Let form flex within written rules. Headlines that make no product claim, calls to action, layout, the order of modules and an email subject line can be written fresh, as long as each new piece is marked as new for review. Approved length variants of a claim are not flex. Each one is a separate locked component.

Images sit in between and need the most care. A photo has no words but can still imply who the patient is or what the outcome looks like. Treat images as components with their own approval and allowed pairings, not as decoration.

What does one module look like across three assets?

Take Brevanta, a fictional brand used here only as an illustration. Its team approves one efficacy module, EFF-01, built from six components: the primary endpoint claim in its approved wording; the result, stated as the difference from placebo with its confidence interval; the study population qualifier; the reference to the pivotal trial publication, pinned to the table; a bar chart of the primary endpoint on a fixed scale; and a pointer to the ISI the claim requires. Its rules say HCP audiences only, never adjacent to the comparative module, and use the approved short variant, EFF-01S, wherever space is tight.

In a rep-triggered approved email, EFF-01 sits as the second block of an approved template, under a subject line and opening line written for this send. The ISI follows in full, with the prescribing information linked. Review covers the new subject line, the opening, and whether the email as a whole is balanced. The claim, chart and reference were reviewed when EFF-01 was approved.

In a 45-second HCP video, the claim is spoken verbatim in voiceover and set on screen as a super, while the chart animates in on the approved scale with the reference on screen. Safety information runs in audio and on screen with comparable prominence. Review covers pacing and the visuals around the claim. Animation is the trap: a chart that builds bar by bar must land on the approved figure without overshooting on the way.

On a detail aid spread, EFF-01 gets room: the full chart, the qualifier set directly beneath it, and a safety module, SAF-02, on the same spread so the pages balance. The one place EFF-01 does not go is a 300 by 250 banner. It fails the smallest-channel test, so the banner carries EFF-01S, approved as its own module, with the ISI scrolling beside it.

Why do modular content programs stall, and how do you start?

The failures repeat. Forking: someone copies module text into a working file, changes a word, and two versions now circulate with no record of which is approved. Fragments: thousands of sentences nobody can find. Channel drift: a module built inside an email template, labelled channel-agnostic. Cumulative imbalance: an asset built entirely from approved efficacy modules that still overweights benefit. And no agreed review tiers, so reviewers sensibly treat every assembly as new.

Start narrow. Veeva's own guidance is to pilot on a new brand, channel or indication, so the team builds the framework from scratch instead of retrofitting a mature brand. Pick one message area for one brand, usually the primary efficacy story, and write a handful of modules with the components, rules and variants described above.

Agree review tiers with MLR in writing before the first asset: a reused module in an approved template follows a lighter path, and anything new is marked as new. Then build three assets in three channels and watch where the modules bend. Those that needed changes everywhere were sized wrong; fix them before adding a second brand. Settle ownership, versioning and expiry before you scale, because those decide whether reviewers keep trusting the library.

Where SwishX fits

Magic Studio works from the same layers. Each brand's Brand Dossier holds its claims, evidence, ISI, fair balance language, audience definitions and channel requirements, and the studios inside it, Video, Visual Aids, Ads, Approved Email and Web, write from that dossier rather than around it. Every claim in a finished asset is cited to its source and checked against the label for its market, and fair balance and safety information are placed in the asset as it is made.

Anyone can ask an asset where a line came from, so a reviewer checking a new combination of modules starts from the source, not from a blank page. Finished work goes into the MLR queue and on into Veeva PromoMats with every claim and its reference attached, so the system your MLR team already runs stays the system of record.

Frequently asked questions

What is a modular content framework?

A modular content framework organizes promotional content into three layers: approved components such as claims, statistics, charts and safety information; modules that combine components into one approved message; and finished assets assembled from modules.

What is the difference between a component and a module in modular content?

A component is a single approved piece, such as a claim with its reference or a chart. A module is a pre-approved combination of components that carries one complete message and can stand alone.

How big should a content module be?

A module should be the smallest unit that carries one complete message and stays accurate and balanced when it appears alone. If it cannot stand alone it is too small. If it cannot fit the most constrained planned channel, it needs an approved short variant.

Does Veeva PromoMats support content modules?

Yes. Vault PromoMats manages content modules in a Modular Content tab, where modules combine text, images, assets and other data, go through a Content Module Approval workflow, and can carry rulesets of business rules and combinations for specific channels, messages or personas.

Can you edit an approved content module?

Not in place. Any change to an approved module or component creates a new version that needs review, and every asset that used the old version has to be updated or withdrawn.

Filed underPlatform

Keep reading

All articles

Want to see Magic Studio on your brand?

Video, visual aids, ads, approved email and web, made from your approved claims and ready for MLR review.