How-to articleResearch designEngineering & technology

Whose Data Is It? A Data Passport for Engineering PhD Researchers in the United States

At many US universities, the data an engineering PhD student collects belongs to the university, not the student, and the partner who supplied it keeps rights over its own records. A one-page “data passport” kept with each dataset records who owns it, who may see it, which tools may process it, where it will be published and what happens when you leave.

What you will learn

  • Who owns, stewards and may see engineering PhD data under a US university research data policy
  • How to record the terms attached to each dataset in a six-field data passport
  • How IRB, funder and repository rules shape what you can do with the data during and after the PhD

What you will unlearn

  • Data I collected myself belongs to me.At many US universities the institution owns research data and the principal investigator stewards it.
  • Any AI tool is fine for transcribing or cleaning data.Identifiable data should only go into tools your IRB or IT office has approved.
  • Data management can wait until the thesis is written.Repository metadata and exit plans are easiest to meet from the first day of collection.

Skills you will practise

  • Reading a university research data policy for ownership and stewardship terms
  • Mapping every agreement (data-use, NDA, sponsor contract) to the dataset it covers
  • Choosing a repository and adopting its metadata template early
  • Writing a README and an exit plan with your PI

Why PhD data needs a passport

Advice on PhD data collection usually concentrates on getting the data: gaining access, building the instrument, reaching respondents. Far less is said about what happens to the data once it exists. In the United States, engineering data passes through many hands. A student records it, a supervisor and a university are responsible for it, a company or agency may have supplied it, software and collaborators process it, and a repository or an examiner may eventually see it. At each hand-over, someone else’s rules apply.

A data passport is a short record kept alongside the data that states the terms under which it was collected and may be used. It is deliberately brief so that it actually stays up to date. Table 1 lists six fields, with an illustrative entry for a hypothetical structural-monitoring dataset. The entries are examples only. The correct answers depend on your university, sponsor and partner.

The six fields of an engineering data passport
Passport field Question it answers Illustrative entry
Owner Which institution or organisation owns the data? University, under its research data policy; the partner keeps ownership of its own source records
Custodian Who is responsible for the original data after the project ends? Principal investigator, with a copy in institution-approved storage
Permitted users Who may see raw, identifiable or restricted values? Named research team only; examiners see anonymised or aggregated values
Permitted tools Which software, cloud services and AI tools may process the data? Approved analysis environment; no public AI tools for identifiable data
Destination Where will the dataset, or a derivative of it, be published? Anonymised subset in a domain repository with a DOI; restricted values withheld
Exit plan What stays, and what may be copied, when the researcher leaves? Originals stay with the PI; approved copy for the researcher
Custody chain of engineering research data
Figure 1. The custody chain of engineering research data. Source: PhD Assistance.

Figure 1 shows why the passport matters: the same dataset is held in turn by five different parties, and each hand-over raises a different question.

1. Who owns the data?

Many students assume that data they collected themselves belongs to them. At many US universities it does not. Virginia Tech’s Policy 13015, for example, states that the university owns research data, results and related materials from projects conducted under its auspices or with its resources. Principal investigators act as stewards and custodians, and access for collaborators is at the investigator’s discretion, subject to any data use or transfer agreements [1]. Other institutions word their policies differently, and a company that supplies data usually keeps ownership of its own records. Fill in the owner and custodian fields from your institution’s written policy and the signed agreements, not from assumption.

2. Who may see the data?

More people see the data than the researcher expects: the supervisory team, partner staff, collaborators at other institutions, examiners and, if it is published, anyone. Earlier promises limit who may be shown what, such as the terms of a data-use agreement or what participants were told when they consented. It is easier to decide in advance which fields could ever leave the lab than to retrofit anonymisation afterwards.

Repositories add their own conditions. DesignSafe, the data repository of the NSF-supported Natural Hazards Engineering Research Infrastructure, requires human-subjects data to follow its protected-data policies and expects depositors to supply the licences and permissions their data needs [2]. A permitted-users rule in the passport turns these conditions into something any team member can check in seconds.

3. Which tools may touch the data?

Generative AI has added a question earlier PhD students did not face. Interview recordings are transcribed by online services, cleaning scripts are drafted with code assistants and survey comments are summarised by chatbots, often without anyone checking where the data goes.

The University of Michigan’s human research protection programme is one example of how universities are responding. It advises researchers not to submit personally identifiable or sensitive information to third-party or public AI tools. Researchers should use only tools approved for the data’s classification level and covered by appropriate data protection agreements, and remember that AI can re-identify data previously considered de-identified. It also asks protocols to describe what data goes into and out of an AI system and whether participant data will be used to train it, and it requires IRB approval before any change in AI use [3]. Practice differs between universities, so check with your local IRB and information security office and record the answer in the tools field.

4. Where will the data go next?

A dataset that ends its life on a laptop is a missed contribution and a risk to the thesis. Many engineering fields now have repositories built for their data. DesignSafe accepts datasets, documentation, research software and reports in natural hazards engineering, assigns DOIs and expects submissions to be documented well enough for reuse [2].

Funder expectations point the same way. In August 2022 the White House Office of Science and Technology Policy told federal agencies to update their public access policies so that publications from federally funded research are available without the previous 12-month embargo, and to set out how the supporting data will be shared [4].

The practical lesson is to choose the destination early. A repository’s metadata and documentation requirements are easiest to meet when you log the data that way from day one. That is what the FAIR Guiding Principles (findable, accessible, interoperable, reusable) ask for in practice [5].

5. What happens when you leave?

The PhD ends, but the data does not. Under Virginia Tech’s policy, original data must be kept by the principal investigator at the university. Team members who remain keep the right to use it, and researchers who leave may take copies only subject to confidentiality restrictions, project requirements and their department head’s approval [1]. If you want to continue the work or publish further papers after graduating, settle the exit-plan field while you are still in the lab. Ask your graduate school separately about thesis embargo options if a partner needs time before results become public.

A short README that explains the file structure, variables and processing steps lets the next researcher continue without you, and gives examiners the same confidence.

What to do now

  1. Find your university’s research data policy and note who owns and who stewards the data.
  2. List every agreement (data-use, NDA, sponsor contract) that touches each dataset.
  3. Ask your IRB which AI and cloud tools are approved for your data classification.
  4. Pick a target repository and adopt its metadata template now.
  5. Write the exit plan with your PI and file it with the passport.

Frequently asked questions

Who owns PhD research data in the US?

Usually the university, under its research data policy, with the principal investigator as steward. Data supplied by a company or agency normally stays the partner’s property. Check your institution’s written policy and your signed agreements.

Can I use ChatGPT or other public AI tools on interview transcripts?

Not for identifiable or sensitive data at universities that follow guidance like Michigan’s. Use only tools approved for that data class, and get IRB approval before changing how AI is used in a study.

Can I take my PhD data with me when I graduate?

Often only a copy, and only with approval. Originals typically stay with the PI and the university. Agree the terms before you leave.

Do I have to make my PhD data public?

Not always, but federally funded projects increasingly expect data sharing, and many repositories and journals require it. Restricted values can be withheld while an anonymised subset is published.

Related reading: Research data management in universities: a critical review · Planning engineering PhD data collection in Saudi Arabia · PhD data analysis support

Key takeaways

  • Ownership is set by your university’s research data policy and your signed agreements, not by who collected the data.
  • Write the passport before the data arrives, and update it whenever an agreement, protocol or tool changes.
  • Public generative-AI tools are a new risk. Check your IRB’s rules before you put any participant data into one.
  • Choose the repository early, because its metadata rules are easiest to meet from day one.
  • Settle your exit plan while you are still in the lab.
Your next step

Want to apply this to your own study?

  1. 1Tell us your topic, data and deadline
  2. 2A subject mentor reviews your work with you
  3. 3You get a plan and a quote
Research methodology support

References

  1. Virginia Tech. (2021). Ownership and control of research data, results, and related materials (Policy No. 13015). https://www.policies.vt.edu/assets/13015.pdf
  2. DesignSafe-CI. (n.d.). About the Data Depot. https://www.designsafe-ci.org/user-guide/datadepotrepo/about/
  3. University of Michigan Human Research Protection Program. (n.d.). Artificial intelligence in human research. https://hrpp.umich.edu/aiinhumanresearch/
  4. Nelson, A. (2022). Ensuring free, immediate, and equitable access to federally funded research [Memorandum]. White House Office of Science and Technology Policy. https://www.whitehouse.gov/wp-content/uploads/2022/08/08-2022-OSTP-Public-Access-Memo.pdf
  5. Wilkinson, M. D., Dumontier, M., Aalbersberg, I. J., et al. (2016). The FAIR Guiding Principles for scientific data management and stewardship. Scientific Data, 3, 160018. https://doi.org/10.1038/sdata.2016.18

How to cite this article

Choose your referencing style, then copy. Check your university's or journal's guide for local variations.

PhD Research Lab Academy. (2026, November 19). Whose Data Is It? A Data Passport for Engineering PhD Researchers in the United States. PhD Research Lab. https://www.phdassistance.com/academy/how-to-article/engineering-phd-research-data-ownership-usa/

PhD Research Lab Academy. “Whose Data Is It? a Data Passport for Engineering PhD Researchers in the United States.” PhD Research Lab, 19 Nov. 2026, www.phdassistance.com/academy/how-to-article/engineering-phd-research-data-ownership-usa. Accessed [access date].

PhD Research Lab Academy (2026) Whose Data Is It? A Data Passport for Engineering PhD Researchers in the United States. PhD Research Lab. Available at: https://www.phdassistance.com/academy/how-to-article/engineering-phd-research-data-ownership-usa/ (Accessed: [access date]).

PhD Research Lab Academy. “Whose Data Is It? a Data Passport for Engineering PhD Researchers in the United States.” PhD Research Lab. November 19, 2026. https://www.phdassistance.com/academy/how-to-article/engineering-phd-research-data-ownership-usa.

PhD Research Lab Academy, ‘Whose Data Is It? a Data Passport for Engineering PhD Researchers in the United States’ (PhD Research Lab, 19 November 2026) <https://www.phdassistance.com/academy/how-to-article/engineering-phd-research-data-ownership-usa> accessed [access date].

PhD Research Lab Academy. Whose Data Is It? A Data Passport for Engineering PhD Researchers in the United States [Internet]. PhD Research Lab; 2026 Nov 19 [cited [access date]]. Available from: https://www.phdassistance.com/academy/how-to-article/engineering-phd-research-data-ownership-usa/

PhD Research Lab Academy, “Whose Data Is It? A Data Passport for Engineering PhD Researchers in the United States,” PhD Research Lab, Nov. 19, 2026. [Online]. Available: https://www.phdassistance.com/academy/how-to-article/engineering-phd-research-data-ownership-usa. [Accessed: [access date]].

@online{engineering_phd_research_data_ownership_usa_2026,
  author = {{PhD Research Lab Academy}},
  title = {{Whose Data Is It? A Data Passport for Engineering PhD Researchers in the United States}},
  organization = {PhD Research Lab},
  date = {2026-11-19},
  url = {https://www.phdassistance.com/academy/how-to-article/engineering-phd-research-data-ownership-usa},
  urldate = {[access date]}
}

This article is for learning. Use it to understand the method and cite the original sources above in your own work; do not copy or submit it as your own.

Whose Data Is It? A Data Passport for Engineering PhD Researchers in the United Need help applying it to your study?
Research methodology support