Use cases
One situation, recurring across every regulator.
Redlineo exists for one thing: a regulated document was revised, and someone must show — and be able to prove — exactly what changed. The home turf is US insurance filings; the same primitives apply wherever that sentence is true.
The flagship
Insurance filings.
-
Home turf · US (SERFF)
Insurance rate / rule / form filings
Insurers and advisory organizations file rates, rules and forms with each state through SERFF, and state checklists routinely require a marked-up copy showing changes from the previously approved version — the strikeout/underline exhibit this tool produces. The full redline is the filing artifact; every output carries its own proof.
Read the SERFF use case → -
Canada
Provincial rate filings
In regulated provinces, auto insurance rates are filed against previously approved rates — Ontario (FSRA) and Alberta (AIRB) among them. Excel-born rate pages and actuarial exhibits, compared with the rate impact computed — the closest cousin of SERFF practice.
More →
Beyond insurance — same primitive, different regulator
The pattern recurs; the vocabulary changes.
The tool is domain-configurable — the AAIS conventions ship as editable YAML, nothing hardcoded — so these are configuration exercises, not new products. Each industry gets the same verified redline, in that industry's own terms.
-
Utilities / energy
PUC tariff filings
Tariff sheets filed with public utility commissions — the closest cousin of SERFF practice. Analogous rate table: rate schedules in spreadsheets.
More → -
Pharma · EU / UK (EMA)
EMA product information — clean + track changes
EMA variations and renewals expect revised product information — SmPC, labelling, package leaflet — as both a clean and a track-changes version. Generate the marked copy instead of hand-marking it in Word.
More → -
Pharma · US (FDA)
FDA labeling & protocol amendments
Labeling and protocol amendments for FDA submissions; SOP revisions under quality systems — the verification and integrity manifest speak the audit-trail language. Analogous rate table: dosing / stability tables.
More → -
Government / legislative
Bill & regulation drafting
Bills and regulations are natively drafted as strikeout/underline amendments — this is the format. Analogous rate table: fiscal schedules.
More → -
Banking / financial services
Disclosures & policy manuals
Disclosures, terms & conditions, and policy manuals revised under regulatory scrutiny. Analogous rate table: fee schedules.
More → -
Standards bodies
Edition-to-edition deltas
Edition-to-edition deltas of published standards for members and committees. Analogous rate table: requirement matrices.
More → -
Healthcare payers
Provider contract amendments
Provider contract amendments, reviewed and proven. Analogous rate table: fee / reimbursement schedules.
More → -
Legal / contracts
Contract turns with opposing counsel
The differentiators here are self-hosting and the verifiable certificate, not the diff itself. Analogous rate table: pricing exhibits.
More →
What travels, what reconfigures
Same proof stack; per-domain conventions.
Carries over unchanged
- ✔Verified redlines — accept-all rebuilds the revised document, reject-all restores the original, checked on every run.
- ✔The certificate — SHA-256 fingerprints of the exact inputs, recomputable with
sha256sum. - ✔The report with links — every change numbered, none truncated, each a click-to-jump link.
- ✔Excerpts — "changed content only", every omission explicitly marked.
- ✔The scrub policy — no leaked author names, company fields, editing time or revision fingerprints.
- ✔The DMS round-trip — compare from the store, save the verified result back.
Reconfigured per domain
- ›Metadata extraction conventions — which properties to read, and from where.
- ›The assertions — the checks each filing must pass.
- ›The profiles — named bundles selected by the caller.
These live in application.yaml — which is exactly why a new domain is a configuration exercise, not a new build.