Skip to content

Inside · Pre-check

Clear the asset before MLR.

Drop in a marketing asset. Juncture shows how much of it reuses content you already approved, then checks every claim, figure and visual against the label. The reviewer opens to a decision, with every verdict tied to a clause.

01/Inside · the value

See how much you are reusing, not just what you are claiming.

Pre-check does not just check claims. It shows how much of an asset is reused verbatim from content you already approved, block by block, tagged exact-match, light-edit or new. Reuse is the tangible value: less new-claim risk, a faster approval.

Illustrative view, fictional brand Varigel. Each block is matched back to the approved module it reuses, so the new copy is the only thing that needs fresh review.

Reuse, measured

A reuse percentage and a block-by-block breakdown show exactly how much of the asset is already-approved content.

Risk, narrowed

Exact-match and light-edit blocks carry no new claim. Only the genuinely new copy needs fresh review.

Approval, faster

Reviewers spend their time on what changed, not on re-reading what they already cleared.

02/Inside · the review

Every claim, figure and visual, checked to the label.

Alongside the reuse breakdown, Pre-check resolves a verdict line by line. Claims present, images verified, rules cleared, off-label caught. Each line cites the clause it was checked against, so the verdict is defensible the moment it lands.

Illustrative view, fictional brand Varigel. Five checks cleared and one off-label use caught, before the asset ever reaches MLR.

03/Inside · MLR-review-ready

Built to back the reviewer, not replace them.

Pre-check makes MLR faster and safer. It flags issues before review, keeps a 21 CFR Part 11 audit trail, and routes each asset to a named reviewer for an e-signature sign-off. The reviewer still decides.

Illustrative view, fictional brand and reviewers. Flag, assign, sign off, publish, with every step logged for the record.

Backs the reviewer

It does not replace MLR.

Pre-check catches rule breaks before the asset reaches MLR. The reviewer still decides, and now opens to a shortlist instead of a blank page.

On the record

A 21 CFR Part 11 trail.

Every check, assignment and edit is time-stamped and attributed, so the review stands up to scrutiny long after it ships.

Signed off

A named e-signature.

The asset is assigned to a reviewer who signs off with an e-signature. Faster and safer, with accountability intact.

01/Inside · what it does

Four checks that hold the message to the label.

Pre-check is the inside half of Juncture. It reads the asset, checks it against the source of truth, and records the decision.

Before MLR

See what passes before you submit

Upload a marketing asset and Juncture reads every claim, figure and visual, then checks each one against the label. The reviewer opens to a decision, not a blank canvas.

  • Claims and figures checked to the label
  • A clean verdict per line
  • Fewer review cycles with MLR

Approved assets

Confirm it is the approved image

Juncture verifies that the pack shot, device render and logo are the approved versions, not a look-alike. It catches "not the approved image" and "not the approved package" before they ship.

  • Pixel match to the asset library
  • Old or altered visuals flagged
  • Version and source recorded

Stringency

Set how strict the check runs

Tune stringency against the label by market and channel. Run a tight check for a regulated DTC piece, a lighter pass for internal drafts. The rule set is yours, and every change is logged.

  • Per-market, per-channel rule sets
  • Editable rules, no black box
  • Calibrated to your risk posture

Compliance

A 21 CFR Part 11 audit trail

Every check, verdict and override is recorded with the asset, the clause, the user and the time. The audit trail is built for 21 CFR Part 11, so the decision is defensible long after it is made.

  • Who checked what, against which clause
  • Time-stamped, tamper-evident records
  • Export for inspection on demand

02/Stringency and trail

Set how strict it runs. Keep a record of every decision.

Stringency is yours to set against the label. Whatever you decide, the trail records it: who checked what, against which clause, and when.

Stringency vs the label

18 rules active

Internal review. Core label rules only.

Audit trail

21 CFR Part 11
TimeActionClause
  • 09:14:02a.rao Asset uploadedVARIA-DTC-08
  • 09:14:09system Indication claim clearedLabel 1.1
  • 09:14:11system Efficacy figure clearedLabel 14.2
  • 09:14:13system Visual verifiedAsset 4471
  • 09:14:15system Off-label use caughtLabel 1.1
  • 09:21:40m.feld Routed to MLR with noteLabel 1.1

Every record is time-stamped and tamper-evident. Export the full trail for inspection whenever it is asked for.

03/The flow

From upload to a routed decision.

The whole path runs in seconds, and it ends with a decision you can defend.

  1. 01

    Upload the asset

    Drop in a marketing asset. Juncture reads its claims, figures and visuals.

  2. 02

    Check against the label

    Each element is checked against the label and the approved asset library.

  3. 03

    Read the verdict

    The reviewer opens to a decision, with every line tied to a clause.

  4. 04

    Route to MLR

    Send a clean asset on, or route a flagged one with the reason attached.

Pre-check · questions

Questions about Pre-check.

Plain answers to what teams ask before they bring Pre-check into the MLR flow.

See it on your asset

Run Pre-check on a real asset.

Bring one marketing asset and the label it answers to. We will pre-check it live and show you how much reuses approved content and the verdict, clause by clause.

Book a demoSee the outside half