Traceability reaches beyond technical reproducibility
A script may recreate an output perfectly while concealing a poor scientific choice. Conversely, a qualitative interpretation can be traceable even though it cannot be reproduced like a numerical calculation. The shared requirement is a defensible account: Which version of the material was used? What question guided the step? Which rule applied? What alternatives were considered, and how did the decision affect the conclusion?
The DFG Code of Conduct calls for documentation that makes findings and their development understandable. Proportionate form depends on discipline and method. A dissertation will often need no more than a structured journal linked to files, code, memos and the methods chapter. What matters is that retrospective changes remain visible and that cleaned material does not overwrite the only original state.
Qualitative work: retain the path of interpretation
For interviews, observations and document analysis, integrity does not mean pretending that coding is mechanical. Preserve source material separately from transcripts, version the codebook and write memos when categories emerge, edge cases arise or interpretations are rejected. If one passage changes a category, record the revision and review earlier cases. Choosing vivid quotations must not make contrary passages disappear.
Reflexivity belongs in the trail. Record aspects of role, assumptions or relationship to the field that may shape interpretation. This is methodological context rather than personal confession. Where a team codes material, do not reduce every disagreement to a coefficient. Note how concepts were clarified and rules revised. Anonymisation, consent and access controls will properly limit which raw records can be shared or appended.
Quantitative work: control analytical freedom
Keep raw data read-only and conduct cleaning and analysis through readable code or clearly recorded steps. Define variables, exclusions, outlier rules, transformations and the main analysis before seeing the target result whenever the design allows. Data-prompted analysis can be informative when labelled as exploratory. The integrity problem arises when many variants are tried but only a favourable one is reported as though it had been the original plan.
What an audit trail should leave out
Do not add unnecessary personal data, passwords, credentials or copies of protected material. A decision number can point to a controlled location without exposing confidential records. Nor is an unannotated screen recording of the entire project helpful. It creates volume without explanation. A good trail is selective about routine operations but complete about choices that can change the scientific meaning.
Apply a retention logic early. Decide which evidence must remain available, who may access it, how versions will be named and when lawful deletion is required. These controls are not barriers to openness. They allow appropriate transparency while respecting participants, rights holders and institutional responsibilities.
Translate the private trail into an honest methods section
The internal record may be longer than the submitted work, but every decision affecting sample, data quality, analysis or scope belongs in the account available to readers. Distinguish a planned primary analysis, a reasoned deviation and an exploratory addition. Report robust and conflicting findings in a way that permits uncertainty to be judged. A precise limitation is not a weakness when it follows from the evidence and design.
Before submission, perform a reverse trace. Take each central result statement back to its output, code or analytical memo, then to the correct data version and recorded decision. If a link is missing, restore it or narrow the statement. The audit trail then becomes the working bridge between day-to-day analysis and a faithful research report.