From request to audit package.
What to provide, what happens during review and exactly what Peer2Paper delivers.
Before you submit
A complete request reduces ambiguity and lets the audit begin with a frozen scope.
- The paper, preprint or claim document
- Analysis code, data and supplementary materials when available
- The exact claim or result that affects your decision
- Access, licence, confidentiality and retention requirements
The audit workflow
Intake and preflight
We confirm scope, permissions, file integrity and whether the supplied materials can support the requested audit.
Study-case freeze
Claims, quantities, datasets, code paths and success tolerances become a versioned assessment case.
Execution and robustness
The original workflow is reproduced, technical repairs are logged and approved sensitivity paths are evaluated.
Verification and delivery
Findings receive independent review, evidence links are checked and the stakeholder and technical outputs are assembled.
Expected outputs
Every completed audit is designed to produce the following views, subject to access and licence constraints.
Results brief
Verdict, confidence, key comparisons, limitations and actions in readable HTML/PDF.
Structured result
Versioned fields for claim status, reproduced quantities, sensitivity findings and provenance.
Evidence manifest
A hashed inventory connecting claims and findings to inputs, executions and review objects.
Replay guidance
Environment details, execution instructions and checks needed to verify eligible outputs.
How to read status language
Status describes the evidence obtained, not the prestige of a paper or the character of its authors.
Data, privacy and restricted material
Requests should contain only data you are authorized to share. Restricted inputs remain separated from public demonstrations and outputs follow request-level release constraints.
Read the security overviewReady to define the case?
Create an account and submit the exact claim your decision depends on.