A programme manager may need a decision summary while an analyst needs code and diagnostics. Agree both layers before writing the report. Do not assume a polished executive summary replaces enough technical detail to inspect the result.
Begin with the audience
A programme manager may need a decision summary while an analyst needs code and diagnostics. Agree both layers before writing the report. Do not assume a polished executive summary replaces enough technical detail to inspect the result.
Connect the chain
Link accepted scope, source/clean versions, issue decisions, analysis run and reviewed candidate. Each major table should have a discoverable input and method. A folder full of files without these relationships is storage, not a reproducibility pack.
Worked example: reporting denominator
Illustrative example: a report states a proportion but omits the eligible denominator. Add the inclusion window, numerator, denominator and missing outcome count. Explain whether weights or clusters were used. This makes a reporting claim inspectable without publishing participant-level records.
Original pack index
Use Asset ID | Purpose | Version | Input dependency | Owner | Review state | Recipient/access boundary. Add a limitations memo and a README. Keep identifiable or licensed source material out of public samples; controlled access may be the correct sharing outcome.
Release and corrections
Record who approved the final candidate and when. If a later correction changes a conclusion, identify the affected outputs and replace the released version through the controlled process. Do not silently edit a public proof claim while retaining an old approval label.
Review this research decision
We can review your actual form, dataset and reporting requirement, then scope the smallest service that solves the risk.
Explore the service ↗