how it works

From URL to audit trail, in six steps

Audera watches pharmaceutical websites the way your most careful reviewer would: every page, every night, with 34 checks and the screenshots to prove it. Here's the whole flow, drawn to scale.

  1. fig. 01

    01 - add your sites

    Point Audera at a site. That's the whole setup.

    Paste the URL and Audera maps every page from the outside, the way a visitor would. Nothing to install: no tags, no CMS plugins, no server access, and nothing for your client's IT team to approve.

    → input: one URL · output: every page

  2. fig. 02

    02 - accept your baseline

    Tell Audera what "approved" looks like.

    The first scan captures every page as it stands: content, code and a full screenshot. Review it, accept it, and that becomes your baseline, the reference every future scan is measured against. When the site is meant to change, you accept a new one.

    → the reference state, sealed

  3. fig. 03

    03 - the nightly scan

    Every page, every night, overnight.

    Scans run overnight in each site's own timezone. Every page is re-crawled, re-screenshotted, and run through the same checks: job codes, ISI and PI links, black triangles, dates of preparation, broken links and the rest of the catalogue. For linked products we also watch the EMA EPAR source itself, flagging additional-monitoring changes, Product information date updates, and the gate or Yellow Card obligations those statuses trigger.

    → sweep interval: 24h · site-local

    See every check we run

  4. fig. 04

    04 - findings with evidence

    Issues arrive as findings, not surprises.

    When a check fails or a page drifts from baseline, a finding is filed with the page, what was found and a screenshot attached. Assign it to a teammate, add notes, resolve it. Every action lands on an audit trail, and you're emailed only if something changed.

    → issue + page + screenshot, pinned

  5. fig. 05

    05 - releases & environments

    Review releases in minutes, not afternoons.

    Deployments are detected and batched automatically, with before/after screenshots of every affected page. And before anything ships, point Audera at staging and compare it page by page against production, running the same checks before they can reach live.

    → offset measured on both axes

  6. fig. 06

    06 - the sign-off pack

    Prove what was live, whenever you're asked.

    Export any page, or a whole site, as print-ready PDFs or full-page PNGs, named, dated and zipped. MLR submission packs, client records at campaign close, and "what was live on this date" evidence, one click each.

    → n pages → one archive

See it running on your sites

Start a 14-day free trial, add your sites, and your first scan runs that night.