Manuel B. Garcia

Manuel B. Garcia serves as the Senior Director for Educational Technology and Digital Learning at FEU Institute of Technology, Manila, Philippines. Read More

Contact Info

1607, FEU Tech Building,
P. Paredes St, Sampaloc,
Manila, Philippines
mbgarcia@feutech.edu.ph

Follow Me

What Research Records Should You Keep, and Why Does Research Integrity Depend on Them?

Research records are more than the data reported in a paper. Learn what evidence researchers should preserve and why trustworthy records are essential for reconstructing, verifying, and defending research.

524
Research Records and Research Integrity Guide 524 of 530
01 · The Question

What Evidence of Your Research Should Still Exist After the Paper Is Written?

A published paper is a compressed account of a much larger research process. It may report the final sample, methods, analyses, and conclusions, but it rarely preserves every observation, protocol version, coding decision, instrument setting, exclusion, correction, or analytical step that produced those conclusions.

That creates a practical question: what should you keep?

The answer matters because research integrity depends partly on whether there is reliable evidence of what actually happened. If a result is questioned months or years later, the manuscript alone may not be enough to determine how the study was conducted or how a particular number was produced.

02 · The Short Answer

Keep Enough of the Research Record to Reconstruct and Support the Work

In Brief

You should preserve the records needed to show what was planned, what was actually done, what evidence was collected, how that evidence was processed and analyzed, and how the reported findings were produced.

Exactly what must be retained depends on the research design, discipline, institution, funder, applicable law, ethics requirements, agreements, and other policies. Good record keeping is therefore not about saving every file indiscriminately. It is about preserving an intelligible and trustworthy evidentiary history of the research.

03 · What You Need to Know

A Research Record Is Broader Than the Dataset in Your Final Analysis

Researchers sometimes treat “research records” as another name for “research data.” That is too narrow. Data may be central to the record, but the record can also include materials that establish where the data came from, what happened to them, which procedures were followed, and how decisions were made.

Under the U.S. federal research misconduct framework, for example, the research record includes the record of data or results embodying the facts resulting from scientific inquiry and may include research proposals, laboratory records in physical or electronic form, progress reports, abstracts, theses, oral presentations, internal reports, and journal articles. This is a useful illustration of how broad the concept can be, although the precise legal or institutional definition applicable to your own work may differ.

Research data The recorded observations, measurements, responses, images, recordings, outputs, or other factual material generated or collected through research, subject to the definition used by the relevant policy or discipline.
Research records The broader documentary evidence of the research process, which may include data as well as protocols, notebooks, logs, documentation, analysis materials, approvals, reports, and other records showing what occurred.

The distinction becomes important when deciding what to preserve. A clean dataset may show the values you analyzed, but it may not explain why certain observations disappeared, which version of an instrument produced them, or how raw responses became analytical variables. The difference between research data and research records therefore affects what a defensible archive needs to contain.

Keep Records of What You Planned

Depending on the study, relevant planning records may include research proposals, protocols, preregistrations, analysis plans, sampling plans, codebooks, instrument versions, interview guides, laboratory procedures, ethics approvals, amendments, data-management plans, and other documents that define how the research was intended to proceed.

These materials provide a baseline against which later changes can be understood. A protocol that changed during the project is not necessarily evidence of a problem. Research often requires legitimate adaptation. The important issue is whether the history of those changes remains understandable.

Keep Evidence of What You Actually Did

A protocol tells you what was supposed to happen. Records created during the research help establish what did happen.

Depending on the methodology, these could include laboratory notebooks, field notes, recruitment and screening logs, instrument records, survey administration documentation, interview or observation records, calibration information, experimental logs, case report forms, electronic system records, or other contemporaneous documentation.

The appropriate record varies considerably across disciplines. A historian working with archives, an education researcher conducting classroom observations, a computational scientist running simulations, and a laboratory researcher performing experiments will not produce identical documentation. The relevant question is whether the records are appropriate to the methods and sufficient to establish how the work was carried out.

Preserve the Connection Between Raw Evidence and Reported Results

Keeping the final spreadsheet is useful, but often insufficient. A trustworthy record should preserve the provenance of important research outputs: where information originated and what happened to it before it appeared in a table, figure, model, quotation, or conclusion.

That may require retaining original or source data where permitted, cleaned datasets, codebooks, transformation documentation, analysis scripts, software settings, coding frameworks, calculation files, version histories, or other materials needed to understand the analytical path.

This does not mean that every intermediate file must necessarily be preserved forever. Rather, the records you retain should make consequential transformations understandable. The more difficult it would be to explain a result without a particular record, the stronger the case for preserving that record.

Document Decisions That Affect the Evidentiary Chain

Some of the most important research records contain decisions rather than measurements. Why was an observation excluded? Why was a coding category revised? Why did recruitment stop? Why was one analytical model reported instead of another? Why did the team depart from an original procedure?

Not every research decision belongs in the published article, but that does not make the underlying documentation disposable. Records of decisions that never appear in the final paper may later be essential for understanding how the published work was produced.

Preserve Corrections Rather Than Making the History Disappear

Research records can contain mistakes. A transcription error may be discovered, a sample identifier may need correction, or a field entry may turn out to be wrong. Correcting such problems can be entirely appropriate.

The integrity issue is whether the correction obscures the history of the record. Where feasible and appropriate to the system being used, corrections should preserve what was changed, when it was changed, and enough information to understand the reason for the change. The specific procedures should follow applicable institutional, regulatory, laboratory, or system requirements. Detailed questions about documenting corrections to research records deserve particular care because poorly controlled editing can make legitimate corrections difficult to distinguish from retrospective alteration.

Keep Metadata and Context That Make Records Interpretable

A file can technically survive while becoming scientifically useless. A folder containing “finaldata2_revised_REALFINAL.csv” may be evidence that academia remains undefeated in file naming, but the filename alone does not explain what its variables mean or how it relates to the study.

Useful records therefore need context. Depending on the project, this can include dates, identifiers, variable definitions, units, version information, software or code dependencies, instrument details, file relationships, provenance information, and explanations of processing steps.

This is part of what makes an adequate research record more than a collection of surviving files.

Preserve Records of Oversight and Compliance When They Matter

Research may also generate records associated with ethical, regulatory, contractual, or administrative requirements. Examples can include ethics approvals and amendments, consent documentation where retention is required and permitted, permissions, safety documentation, data-use agreements, monitoring records, or correspondence documenting consequential approvals and decisions.

These materials should be handled according to the applicable requirements, particularly when they contain identifiable, confidential, proprietary, or otherwise sensitive information. “Keep the record” does not mean “make the record broadly accessible.” Preservation and access are separate questions.

Watch Out

Do not interpret good record keeping as permission to retain sensitive information indefinitely. Human-participant information, confidential records, proprietary materials, and other protected information may be subject to specific requirements governing retention, security, access, de-identification, transfer, and destruction. Follow the requirements that actually apply to your study.

Research Integrity Depends on Traceability, Not Just Trust

Good research records allow claims about the research process to be checked against contemporaneous evidence. This matters during ordinary collaboration, manuscript preparation, replication attempts, audits, monitoring, corrections, data reuse, and investigations of possible problems.

Research misconduct frameworks make the connection especially visible. The U.S. Office of Research Integrity defines falsification to include changing or omitting data or results so that research is not accurately represented in the research record. The point is broader than misconduct proceedings, however. Records help distinguish documented research practice from reconstruction based largely on memory.

That distinction can protect researchers as well as expose problems. If a disputed result was produced legitimately, contemporaneous records may demonstrate exactly what happened. If an honest error occurred, a coherent record may help identify where it entered the workflow and what findings it affected.

Good Records Also Make Research More Reproducible and Reusable

NIH describes data management as involving the validation, organization, protection, maintenance, and processing of scientific data to support accessibility, reliability, and quality. It also notes that careful documentation helps researchers and collaborators use data consistently and accurately and can support future use.

Record keeping and data sharing are nevertheless not identical. NIH's Data Management and Sharing Policy, for example, defines “scientific data” for that policy in a way that specifically excludes materials such as laboratory notebooks, preliminary analyses, completed case report forms, paper drafts, peer reviews, and communications with colleagues. Some materials can therefore be important research records without being scientific data that must be shared under a particular data-sharing policy.

There Is No Universal Retention Period for Every Research Record

How long records must be kept depends on the rules governing the project. Requirements can come from institutions, funders, sponsors, laws, regulations, ethics bodies, contracts, journals, repositories, or disciplinary standards, and different categories of records may be governed by different periods.

For example, NIH states that recipient institutions generally must retain records pertinent to an award for three years from the date of submission of the final expenditure report, subject to exceptions and other applicable requirements. NSF likewise specifies a general three-year retention period for records pertinent to an award from financial closeout, subject to the federal rules it cites. These examples should not be converted into a universal “three-year rule” for research records.

Before destroying anything consequential, determine which requirements apply to the particular record and whether circumstances such as an audit, dispute, investigation, patent matter, participant-protection requirement, or institutional hold require longer preservation.

04 · A Practical Example

What a Defensible Record Looks Like When a Result Is Questioned

Hypothetical Example

A surprising exclusion changes the main result

An education research team collects survey responses from 420 participants. During cleaning, 18 cases are excluded because they fail a prespecified eligibility condition. Two years after publication, a collaborator asks why the published sample contains only 402 cases and whether those exclusions were decided after seeing the results.

Planning record The archived protocol and eligibility criteria show that the relevant exclusion condition was specified before the final analysis.
Source record The team retains the original data in appropriately protected storage rather than only the cleaned analytical dataset.
Processing record A cleaning script identifies the 18 excluded records using the documented eligibility rule and produces the analytical dataset.
Decision record A dated project note records the application of the exclusion rule and explains an ambiguous case discussed by the team.
Analysis record The preserved analysis code reproduces the sample size and principal result reported in the article.

No single file proves the integrity of the entire study. Together, however, these records establish a traceable path from the original evidence through the exclusion decision to the published result. The team does not have to reconstruct the story from memory two years later.

That is the practical value of documentation: not paperwork for its own sake, but evidence that allows the research process to be examined.

05 · What Researchers Often Get Wrong

Research Records Are Often Lost Through Ordinary Assumptions

Misconception

If It Is Not in the Paper, It Does Not Matter

A journal article necessarily compresses the research process. Important records can therefore remain outside the publication, including source documentation, intermediate transformations, protocol versions, analytical code, and records explaining consequential decisions. Publication does not make those materials irrelevant.

Misconception

The Final Dataset Is the Complete Research Record

A final dataset may show what was analyzed without showing how it was produced. If raw evidence was cleaned, recoded, excluded, aggregated, transformed, or otherwise processed, additional documentation may be necessary to reconstruct those steps.

Misconception

Saving Everything Automatically Means You Have Good Records

A terabyte of unexplained files is not necessarily a usable research record. Documentation needs organization, context, appropriate metadata, controlled versions, and relationships that can be understood. The question is not merely whether files exist, but whether the evidence remains interpretable.

Misconception

Good Documentation Means Anyone Should Be Able to Access Everything

Preservation does not eliminate privacy, confidentiality, security, contractual, ethical, or intellectual-property obligations. Some records need to be preserved precisely because they are important, while access to them remains tightly controlled.

Misconception

Three Years Is the Universal Retention Rule

It is not. Certain U.S. federal award rules use three-year retention periods in specified circumstances, but research can be subject to longer periods or entirely different requirements. Never infer your retention obligation from a rule that governs another funder, institution, jurisdiction, record type, or study.

Misconception

Records Matter Only If Someone Suspects Misconduct

Investigations are only one reason records matter. Documentation supports routine quality control, collaboration, error correction, analysis verification, continuity when personnel change, data reuse, and responses to legitimate questions about completed work. An audit trail supporting research integrity is useful long before anyone alleges wrongdoing.

06 · What This Means for You

Decide What to Keep by Asking What the Record Must Be Able to Show

A useful record-keeping strategy begins with reconstruction rather than storage capacity. Imagine that a knowledgeable person later asks how one important finding in your paper was produced. What evidence would they need to follow the chain from the research plan to the original observations, through processing and analysis, to that finding?

The answer will vary by methodology, but this question exposes documentation gaps remarkably quickly.

A simple decision framework

If a record establishes what you planned or were authorized to do
Preserve the relevant version and associated approvals according to applicable requirements.
If a record contains or identifies original research evidence
Preserve it securely when required and permitted, with enough context to interpret it.
If a file documents a consequential transformation or analysis
Keep enough of the workflow, code, settings, or documentation to understand how the output was produced.
If a decision could materially affect the reported findings
Document the decision and its rationale rather than relying on later recollection.
If a record contains sensitive or restricted information
Apply the relevant security, access, retention, and destruction requirements rather than treating preservation as unrestricted storage.
If you are unsure whether documentation is sufficient
Ask whether an informed person could determine what actually happened without needing you to remember it. The documentation needed to defend what you actually did should be judged against the specific research process and governing requirements.

Set these practices at the beginning of a project where possible. Retrospective documentation is inherently more difficult because files disappear, software changes, team members leave, and memories become less reliable. Record keeping works best as part of the research workflow rather than as an archival exercise performed after manuscript acceptance.

Finally, establish responsibility. Team members should know where authoritative records are stored, which versions are controlled, who can access them, how corrections are made, and what happens to records when personnel leave. A research record that exists only on one researcher's personal device is a continuity problem waiting for excellent timing.

07 · A Quick Checklist

Before You Consider Your Research Record Complete

Check whether your records can:
Show the protocol, plan, instrument, procedure, or other authoritative version relevant to the work actually performed.
Identify the original or source evidence and preserve it where retention is permitted and required.
Explain consequential cleaning, exclusions, transformations, coding, calculations, and analytical steps.
Connect the evidence and analysis to the principal tables, figures, results, or conclusions you report.
Preserve enough metadata, version information, definitions, and context for important files to remain interpretable.
Document consequential deviations, corrections, and decisions rather than silently replacing their history.
Protect confidential, identifiable, proprietary, or restricted records using the security and access controls applicable to the project.
Verify retention requirements with your institution, funder, sponsor, ethics requirements, contracts, applicable regulations, and other governing policies before deleting records.
Store authoritative records in an approved location that will remain accessible to the responsible research organization or team rather than relying solely on personal devices or accounts.
08 · Frequently Asked Questions

Common Questions About Research Records

Do I need to keep every research file I create?

Not necessarily. Retention should reflect applicable requirements and the evidentiary value of the record. Temporary duplicates and inconsequential working files may not warrant the same treatment as source data, authoritative protocols, analytical code, or records of consequential decisions. Follow your institution's records-management and project-specific requirements.

Are emails and messages part of the research record?

They can be. A communication that documents a consequential methodological decision, approval, instruction, interpretation, or change may have evidentiary significance. Whether it must be retained depends on its content and the policies governing the project, not simply on the fact that it was sent by email or messaging software.

Are laboratory notebooks research records?

Yes, laboratory notebooks are a classic example of research records and are expressly included in some formal definitions. Their ownership, custody, and retention, however, may be governed by institutional or sponsor policy rather than belonging automatically to the individual researcher.

Are field notes and qualitative research notes research records?

They may be important research records when they document observations, context, methodological decisions, coding, interpretation, or other aspects of the inquiry. Because such records can contain identifiable or sensitive information, their preservation and access should also follow applicable ethics, consent, privacy, and institutional requirements.

Should I keep analyses that did not appear in the published paper?

Sometimes. Unreported analyses can be important when they explain how analytical choices developed, document robustness checks, or help establish the provenance of reported results. This does not mean every exploratory output must always be retained, but consequential analytical history should not disappear merely because it was absent from the final article.

How long should research records be retained?

There is no single period applicable to all research. Check the requirements of your institution, funder, sponsor, contracts, applicable laws or regulations, ethics arrangements, repositories, and other governing policies. Certain events, including investigations, audits, disputes, or legal holds, can also affect when records may be destroyed.

What happens if important research records are missing?

Do not quietly reconstruct missing evidence and present it as if it were contemporaneous. Determine what is missing, preserve the records that remain, document the gap and any legitimate reconstruction, and consult the responsible institutional office when the loss is consequential. The appropriate response to missing research records depends on what was lost and what claims can still be supported.

Does keeping good records prove that the research is correct?

No. Excellent documentation cannot make a flawed design, biased measurement, incorrect analysis, or unsupported conclusion correct. What it does provide is evidence that makes the research process more transparent, traceable, reviewable, and capable of being checked.

09 · The Bottom Line

Preserve the Evidence Behind the Research, Not Just the Paper

The Bottom Line

Keep the research records needed to establish what you planned, what you actually did, what evidence you collected, how that evidence changed through the workflow, and how your reported findings were produced.

Research integrity depends on this evidentiary continuity because trustworthy records make the work traceable and help researchers verify results, identify errors, answer legitimate questions, and distinguish documented practice from retrospective recollection. What must be kept and for how long is context-dependent, so preserve records systematically and verify the requirements governing your particular study.

10 · Sources and Further Reading

Authoritative Sources on Research Records and Data Management

11 · Cite this Guide

How to Cite This Guide

This guide is intended to be read, shared, and used in research, teaching, and academic work. If you draw on its ideas, explanations, or other content, please acknowledge the source by citing the guide. Doing so gives appropriate credit and helps your readers locate the original resource.

Has the Field Guide helped your research?

If a guide helped clarify a question, inform a research decision, or move your work forward, I would love to hear about your experience. Your story may also help other researchers discover the Field Guide.

Share Your Experience
Takes only a few minutes