01
Where it fits and where it does not
Use these four checks before committing implementation time.
- Use it when
- Planning, recording, reporting, and reviewing in vivo experiments so readers can assess methodological rigor and reproduce the work.
- Limits
- ARRIVE is a human-facing reporting guideline rather than a machine-readable study schema. Checklist completion does not establish ethical approval, statistical validity, or reproducibility.
- Best for
- Preclinical and Discovery teams working across Plan → Acquire → Exchange → Learn + reuse.
- Maturity
- EstablishedSuitable for production assessment. Pin the exact release and any implementation profile.
02
See it in the workflow
This view shows the input, the change the standard introduces, and the resulting output.
- InputWhat starts
Preclinical and Discovery source data, metadata, and local mappings
- ARRIVE 2.0What changes
Use ARRIVE 2.0 as a pinned framework across Plan → Acquire → Exchange → Learn + reuse
- OutputWhat becomes possible
A handoff the next system or team can validate against the same release
03
A concrete example
An animal study uses the Essential 10 during protocol design, captures allocation and exclusion decisions as the work proceeds, and completes the Recommended Set before data and manuscript release.
Why it matters: Makes bias-sensitive design and reporting decisions visible for downstream reuse, but narrative compliance must be translated into structured variables and verified against source records.
04
What it fits with
Complements CDISC SEND, which structures nonclinical submission datasets, by preserving design and reporting context that tabulation conformance does not guarantee.
- Metadata profileREMBI
Both support Discovery work and meet around Plan, Acquire, Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship - Metadata profileExpmeta
Both support Discovery work and meet around Plan, Acquire, Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship - FrameworkFAIR
Both contribute at Plan, Acquire, Exchange, Learn + reuse, with different domains or implementation roles.
Explore relationship - StandardCDISC
Both support Preclinical work and meet around Plan, Acquire, Exchange. Compare their roles before treating them as interchangeable.
Explore relationship
05
Implementation starter
Start with one bounded handoff. Pin, test, and review it before scaling.
Define one handoff, its accountable owner, and the decision ARRIVE 2.0 must support.
Pin the exact version and companion artifacts: 2.0 · published 2020 · current.
Map one representative input to the required framework artifacts.
Test the result against the canonical source and record every exception.
Preserve the source data, mappings, and review evidence before scaling.
06
Test the main limitation
ARRIVE is a human-facing reporting guideline rather than a machine-readable study schema. Checklist completion does not establish ethical approval, statistical validity, or reproducibility.
Run one representative end-to-end pilot and record exactly where ARRIVE 2.0 loses context, needs an extension, or depends on another standard.
Machine-readable output may still be unfit for analysis or ML.
Test the output for missing context, provenance, terminology alignment, time leakage, and the intended downstream decision. Makes bias-sensitive design and reporting decisions visible for downstream reuse, but narrative compliance must be translated into structured variables and verified against source records.
07
Official resources
Specifications, diagrams, examples, and guides from the organizations that maintain them.
ARRIVE Guidelines 2.0
Official publisher or steward guidance for this framework profile.
- Publisher
- NC3Rs · international ARRIVE working group