PlanMeasureCreate

Every claim, traced
from evidence to asset.

Purple Pen connects evidence, claims, messages and assets on one governed backbone. When a claim or ISI changes, every piece of content it touches gets flagged. A working pilot runs this today, end to end.

Settings
Scene
Speed 0.85
Gooeyness 1.20
Dot Matrix
Enabled
Dot Size 5.0
Dot Gap 2.5
Brightness 0.85
Contrast 0.60
Crosshatch
Enabled
Intensity 0.95
Bloom
Enabled
Intensity 0.55
Size 1.50
CRT
Enabled
Scanlines 0.75
Curvature 0.0
Vignette 2.00
Chroma 0.0
GPU Tier: detecting…
Live Working pilot today
3 Libraries: claims, messages, references
5 Steps from evidence to review
Scroll to explore

When a claim changes, nothing stale stays in market.

Purple Pen knows where every claim came from and where it is used. So when evidence or ISI changes, the content it affects flags itself.

01 A claim change means hunting through every asset

Someone updates a claim, a reference or the ISI, and a team combs channels, formats and agencies by hand to find what it touched.

02 Purple Pen traces every claim from evidence to asset

Evidence, claims, messages, variations and assets live on one governed backbone, with the lineage between them recorded end to end.

03 Changed evidence flags its own content

When a claim, reference or ISI changes, every affected piece of content is automatically flagged for update.

04 Review starts clean instead of starting over

MLR gets a chain of custody for every decision, and every submission carries a frozen ISI snapshot of exactly what was approved.

Watch a claim travel from evidence to audit trail

Demo video · coming soon

How it's offered

Purple Pen sits between the systems you already run: evidence, authoring workflows, DAMs and MLR. It owns the lineage layer none of them do.

01

The governance layer between your systems

It does not replace your MLR system or your DAM. It records how evidence becomes claims, messages and assets across all of them.

Evidence systems Authoring workflows DAMs MLR systems
02

Built for the teams that own claims

Brand teams Strategy Regulatory MLR Content operations Creative production

Brand, regulatory, MLR and content operations read the same lineage, so a change conversation starts from facts instead of archaeology.

03

What you need to bring

  • Your approved evidence, references, claims and business rules
  • The content and asset channels where those claims appear today

From evidence to clean review

01
Start with evidence
Approved evidence, references, claims and business rules form the source layer.
02
Build messages
AI-guided drafting keeps copy inside approved claims and channel limits.
03
Track usage
See where each claim and message appears across channels and assets.
04
Flag changes
When evidence or ISI changes, affected content is flagged automatically.
05
Support review
MLR gets a clear chain of custody, with a frozen ISI snapshot per submission.

It maps the lineage, cascades the changes, and keeps drafting inside the claims.

01

Claim-to-asset lineage graph

An interactive map of where every claim came from and every place it is used, with reuse analytics built in.

02

Automated change cascades

A claim, reference or ISI change flags every piece of downstream content it affects, so nothing stale stays in market.

03

AI-assisted copy workspace

Drafting that stays inside the approved claim envelope, and approved copy that populates straight into design files.

What lives on the backbone

One governed home for the pieces that today live in decks, trackers and inboxes.

Claims, message and reference librariesThe approved source of truth, with permitted variations
Compliance audit trailEvery decision and update traceable, with frozen ISI snapshots
MLR-ready submission packetsReview packages with the traceability already organized
Integration-ready exportsLineage data your DAM, authoring and MLR systems can consume

Built for the content that has to hold up

01

Claim governance

One source of truth for approved claims and the variations each one permits.

02

Content refresh

A claim, ISI or reference changes: find every affected asset at once.

03

Content automation

Feed approved claims and messages into modular and creative workflows.

04

Multi-agency governance

One lineage layer across brands, agencies, formats and channels.

Now

Today, a live pilot runs claims from evidence to MLR packet, traced end to end.

Next

Next, it plugs into the systems around it: evidence, authoring, DAMs and MLR.

The payoff

So compliance becomes infrastructure instead of a final checkpoint.

The full picture.

Now

The full claim lifecycle

Evidence intake, AI-guided authoring, MLR submission packets, automated change cascades and design-tool handoff, running on live claims today.

Live in pilot
Next

Native integrations

Direct connections to the evidence systems, authoring workflows, DAMs and MLR systems it sits between.

In build
Later

Every brand on one backbone

One lineage layer across brands, agencies, formats and channels.

On the roadmap
Later

A packaged product

From pilot engagement to a productized offering teams can buy into.

On the roadmap
Implementation timeline
NowLive in pilot
NextIn build
LaterOn the roadmap

Full milestone dates confirming with the product team.

Stop hunting assets by hand.

When a claim changes, you already know what it touches. The lineage answers in seconds what used to take a team days of digging.

Questions, answered

Is Purple Pen an MLR system?
No. It is the lineage and governance layer between your evidence systems, authoring workflows, DAMs and MLR systems. Review still happens where it happens today; it just starts cleaner.
How mature is it today?
More than a concept. A working pilot manages live claims, messages and market variations through the full review lifecycle, with audit trails, MLR-ready submission packets and design-tool integration already demonstrated.
Does it replace EVIE?
No. EVIE governs clinical evidence. Purple Pen owns what happens to that evidence commercially: claims, messages, assets and the lineage between them.
What does it own?
Claim-level lineage, reuse tracking, the claims, message and reference libraries, and auditability across content and assets.
Why does lineage matter?
Because evidence, ISI and rules change. Without lineage, every change means manually hunting through every asset to find what is affected.

Take it into the room

Stakeholder brief
What Purple Pen is and the problem it removes.
[NEEDS INPUT: link]
Stakeholder review
The pilot walkthrough, as shown to stakeholders.
[NEEDS INPUT: link]
Business case
Why the lineage layer pays for itself.
[NEEDS INPUT: link]

Track every claim from evidence to asset.

Bring one brand and we will map its claims onto the backbone. See the lineage, the change cascade and the audit trail on your own content.

Questions about Purple Pen?

ISG
[NEEDS INPUT: named contact]
Product owner · Purple Pen
Contact pending