Easy Annotation
Menu

Medical writing workflow

Claim Substantiation Review Workflow for Medical Writers

By Easy Annotation editorial 9 min read · approximately

A claim substantiation review workflow is a repeatable path that takes each claim in a deliverable, records its exact wording and context, links it to a specific passage in a specific reference, checks whether that passage actually supports it, and leaves a traceable record. The reviewer, not the software, makes the final judgment.

What is a claim substantiation review workflow?

Claim substantiation is the practice of showing that a claim is backed by evidence. A review workflow is the sequence of steps that makes this repeatable instead of improvised. For medical writers, the deliverable is usually a manuscript, a slide deck or promotional content that has to survive MLR (medical, legal, regulatory) review. The workflow answers a question reviewers ask over and over: where exactly does this claim come from?

General search results for this topic mix several fields, including advertising law, product marketing and insurance claims. The core logic carries across them: log the claim, gather the proof, match the proof to the claim, and decide. This guide applies that logic to document-based medical writing and describes where Easy Annotation fits.

1. Log the exact claim and its context

Copy the claim verbatim, with the sentence or slide around it. A claim read in isolation can mean something different from the same claim read next to its footnote, chart or headline. Note where the deliverable will be used (manuscript, deck, promotional piece), because the intended use shapes how much scrutiny it needs.

2. Identify what the claim could be taken to mean

Write down the literal meaning and any reasonable takeaway a reader might draw. A claim that is technically accurate can still imply more than the source shows. Catching this early is cheaper than catching it in MLR review.

3. Gather the references into one place

Collect the references that are supposed to support the deliverable. Keep them alongside the deliverable, not scattered across folders and email threads. If you inherited a deck, this stage often means reconstructing the original support from scratch.

4. Map each claim to a passage

For every claim, point to the exact passage in the exact reference. A citation to a whole paper is not enough for a reviewer who must confirm that the claim maps to a specific passage in a specific reference. Record the location so anyone can check it later.

5. Check the type of support

A passage can relate to a claim without supporting it. Assess each pairing with a consistent set of labels (see the table below), and note any uncertainty rather than smoothing it over.

6. Decide, revise and document

Keep the claim, revise it, add a qualification or remove it. Then produce a copy of the deliverable with citations and a reference list, so the reviewer sees the claims and their support together.

What labels should a reviewer use when checking support?

Easy Annotation's review uses four labels. They also work as a plain checklist if you run the workflow by hand.

The labels organise the evidence. They do not replace the reviewer's assessment of whether the source is strong enough for the claim.

  • Label: Support — The question it answers: Does the passage back the claim as written? — Why it matters: Confirms the claim has a traceable basis.
  • Label: Contradiction — The question it answers: Does the passage conflict with the claim? — Why it matters: Surfaces claims that must change or go.
  • Label: Qualification — The question it answers: Does the passage back the claim only under conditions or limits? — Why it matters: Shows where the claim needs a caveat, population or context.
  • Label: Exact numerical check — The question it answers: Do the figures in the claim match the figures in the source? — Why it matters: Catches transcription slips and rounded or shifted numbers.

How do the main ways of running this workflow compare?

The spreadsheet and general annotator rows describe the approach in general, not any specific product.

  • Approach: Spreadsheet plus a folder of PDFs — Keeps claim, context and reference together: Only by manual discipline — Maps claims to exact passages: Manual entry — Cited copy and reference list: Built by hand — Typical limit: Easy to drift out of sync with the deck
  • Approach: General PDF annotator — Keeps claim, context and reference together: Annotations stay on each PDF — Maps claims to exact passages: Manual, per file — Cited copy and reference list: Built by hand — Typical limit: Annotation and comments only, with no claim mapping
  • Approach: Easy Annotation — Keeps claim, context and reference together: Yes, in one project — Maps claims to exact passages: Source-linked claims identified without altering originals — Cited copy and reference list: Yes, produced as cited copies — Typical limit: PDF- and project-centric; per-writer plans

Where does Easy Annotation fit in the workflow?

Easy Annotation is a claim-substantiation workspace for medical writers. It keeps a deliverable, its exact document context and the supporting references in one project. It identifies source-linked claims without altering the originals, searches only the references you uploaded to the project, and produces cited copies with a reference list.

Two design choices are worth knowing about, because they affect how you trust the output:

Typical users are freelance medical writers, writing teams inside agencies who need a repeatable review path across clients and projects, reviewers who must confirm each claim maps to a specific passage, and writers auditing an inherited deck.

  • Closed evidence set. Because searching is limited to uploaded project references, every suggested passage comes from a document you chose. Nothing is pulled from outside the project.
  • Human judgment stays human. The tool does not decide whether a source supports a claim, and it does not make regulatory or substantiation decisions. You assess the uncertainty. The tool keeps the evidence traceable.

What does it cost to run this workflow in Easy Annotation?

Uploading, organising and annotating PDFs in Quick Annotation never uses credits. Claim review and cited copies consume AI Processing Credits.

Other pricing details:

Plans are per writer. The published pricing has no team or seat-based tier.

  • Plan: Writer — Monthly price: USD $149.00 per month — Annual price: $1,490.00 per year billed annually — Monthly allowance: 5,000 AI Processing Credits per month
  • Plan: Writer Plus — Monthly price: USD $299.00 per month — Annual price: $2,990.00 per year billed annually — Monthly allowance: 12,000 AI Processing Credits per month
  • New subscribers get the first month of Writer monthly at USD $111.75 (25% off), then USD $149.00, until 31 December 2026.
  • Unused monthly credits carry into the next billing period, up to one month's worth.
  • Subscribers can buy one-time credit packs, which are used only after monthly credits and expire after 12 months.
  • The free trial lasts 14 days and includes 1,000 AI Processing Credits. It needs no payment details and never converts automatically into a paid subscription.
  • Payments are non-refundable.

What commonly goes wrong in claim review?

No workflow or tool guarantees that a deliverable will pass review. What a good workflow gives you is a clear, checkable record of what supports each claim.

  • Reviewing the claim without its context. A claim copied into a spreadsheet loses the slide, footnote or paragraph that changes its meaning. Keep the exact document context attached.
  • Treating relevance as support. A paper on the right topic may not back the specific claim. This is why the contradiction and qualification labels exist.
  • Citing whole papers instead of passages. Reviewers need to see where in the reference the support sits.
  • Letting numbers drift. Figures get rounded, re-typed or taken from a different table. A dedicated numerical check catches this.
  • Losing the trail on inherited material. When the original support for a deck is unknown, reconstruct it claim by claim and record the result, rather than assuming earlier authors got it right.

When to use something else

Easy Annotation is not the right fit for every team:

  • Real-time co-authoring in Word. The workflow is PDF- and project-centric. If your team needs simultaneous editing in Word documents, use a document collaboration suite.
  • Annotations and comments only. If you do not need claim mapping or cited copies, a general PDF annotator can do the job at lower cost.
  • Seat-based team billing. Plans are per writer, and there is no published team or seat-based tier.
  • Automated substantiation decisions. The tool does not decide whether a source supports a claim. If you want a system that rules on substantiation for you, this is not it, and you should be cautious about any tool that claims to.
  • A spreadsheet is enough. For a handful of claims and a few references, a manual log may be all you need.

What is claim substantiation?

Claim substantiation is the practice of showing that a specific claim is backed by specific evidence. In medical writing, that means tying each claim in a manuscript, slide deck or promotional piece to an exact passage in a named reference, so a reviewer can verify it.

What does reviewing a claim mean?

It means checking the claim as written against its cited source: does the passage support it, contradict it, only partly support it, or match its numbers exactly? The reviewer then decides whether the claim stays, changes or goes.

Does Easy Annotation decide whether a claim is substantiated?

No. Easy Annotation keeps the deliverable, its document context and the supporting references together and keeps the evidence traceable, but the human reviewer makes every judgment. A relevant source does not necessarily support a claim.

Does Easy Annotation search the whole internet for supporting evidence?

No. It searches only the references uploaded to the project, so every cited passage can be traced to a document you chose to include.

Can I try the workflow before paying?

Yes. The free trial lasts 14 days and includes 1,000 AI Processing Credits. It needs no payment details and never converts automatically into a paid subscription. Payments for paid plans are non-refundable.

The takeaway

Yes. The free trial lasts 14 days and includes 1,000 AI Processing Credits. It needs no payment details and never converts automatically into a paid subscription. Payments for paid plans are non-refundable.

Put it into practice

Start with a reference PDF.

Open Quick Annotation to organize and annotate your PDFs. Evidence interpretation and review decisions stay with your team.