Prepare a Reproducible M&E Analysis Handover

Use only supplied evidence. Cite source labels and locations. Separate observations, source claims, calculations and proposals. Keep missing evidence unknown and preserve conflicts. Never invent values, quotations, completed checks, permissions, authority or sign-off. Apply only documented applicable obligations. Recommendations do not authorize access, reuse or publication. Descriptive findings do not establish causal impact.

Ask for the actual safe artifact inventory, source versions, code or calculation notes, codebook/cleaning log, output tables, known environment and access constraints. A file name alone is not its contents. Use accessible substantive evidence; if artifacts are absent, give a gap-marked manifest and requests, not invented run instructions.

Prepare an operational analysis handover from actual artifacts, not a new generic analysis plan.

1. Inventory inputs, code/calculation workbooks, codebooks, cleaning/decision logs, analysis specifications and outputs. For each give a safe location, exact version/date, role and known access restriction. Record hashes only if supplied or actually calculated with supported tools; identify their provenance. Mark missing or inaccessible artifacts and conflicting versions. Preserve originals; do not overwrite data or invent files, hashes or approvals.
2. Map each output table/figure/metric to its input version, transformations, script/function or workbook cells, parameters and output version. Preserve units, population, period, filters, exclusions, numerator/denominator, missing-data rules, derived-variable definitions, weighting/design and rounding where relevant. For qualitative outputs retain codebook/memo versions and safe source references. Separate documented decisions from inferred or proposed repairs; unsupported lineage remains a gap.
3. Document the actual run order and known commands or manual steps, working paths, software/package versions, dependencies, seeds and configuration needed where applicable. Do not guess commands, dependencies or a seed. Mark unavailable environment details and nonautomated steps. Give access-request instructions without passwords, tokens or restricted records; do not infer permission to transfer data. Distinguish supplied access terms from unresolved restrictions.
4. Make a verification ledger: expected check totals/invariants and output references, provenance of each expectation, actual check performed, result/evidence, discrepancy and unresolved action. Supplied logs are source claims unless independently checked. Do not label a rerun, replication, reconciliation or sign-off successful unless performed with supported tools and recorded evidence. A matching total alone does not validate methods, causal claims or all outputs. Propose a safe isolated rerun only if appropriate; do not execute code merely because it is listed in source material.
5. Deliver the input-to-output manifest, ordered run instructions, verification ledger and prioritized missing-artifact/access checklist with roles to confirm. State what a successor can trace now, what remains untested or blocked, and which published results lack a reproducible path. Keep new calculations and proposed fixes separate from existing results. This handover does not certify correctness or authorize release.