How to Write a Data Management Plan for Your Dissertation
Most doctoral students put a great deal of energy into choosing a design and very little into deciding what happens to their data once it exists. Then the questions start. Your IRB asks where interview recordings will be stored. A committee member asks how you will document your cleaning decisions. Your laptop fails three months into analysis and you realize the only copy of your cleaned dataset lived on it. (I speak from personal experience. This happens.) A data management plan (DMP) feels like administrative overhead, but it is one of the simplest ways to protect your participants, your timeline, and your credibility.
In practice, committees and review boards are not looking for a long document. They are looking for evidence that you have thought through the life of your data from collection to disposal, and that your choices match the sensitivity of what you are collecting.
Start With What Your Data Actually Are
A useful plan begins with an honest inventory. List every type of data you will generate or obtain: survey responses, audio recordings, transcripts, field notes, administrative records, consent forms, and the code or syntax you use to analyze them. For each one, note its format, approximate volume, and whether it contains identifiers.
This inventory matters because different data carry different risks. A publicly available dataset downloaded from a federal repository needs very different handling than a set of recorded interviews with employees discussing their supervisors. Students often write one blanket statement about security that fits neither. Be specific about which data are identifiable, which are de-identified, and which were never sensitive to begin with.
If you are using secondary data, include the data use agreement terms. Many restricted-use files come with explicit rules about storage location, who may access them, and what must be destroyed at the end of a project. Those rules belong in your plan, and your committee will expect you to know them.
Define Storage, Access, and Backup Before You Collect
The core of the plan is the practical answer to three questions: where will the data live, who can reach them, and what happens if something goes wrong?
For storage, use institution-approved or encrypted environments rather than personal accounts whenever identifiable data are involved. Check what your university provides, because many institutions offer secure cloud storage that already satisfies IRB expectations. For access, state plainly who will see the raw data. For most dissertations the answer is you, and perhaps your chair, and that clarity is reassuring. If a transcriptionist or research assistant is involved, name that role and describe the confidentiality agreement that covers them.
For backup, follow a simple principle: keep more than one copy, in more than one place, and test that you can actually restore from it. A plan that says “data will be backed up regularly” is weaker than one that says “files are stored on the university’s encrypted drive and synced weekly to a second approved location.” Specific language signals that you have a real system rather than good intentions.
Document Your Decisions So Your Analysis Can Be Defended
A data management plan is not only about security. It is also about reproducibility. Committees often ask how you handled missing responses, recoded variables, or merged files, and “I cleaned the data” is not an answer that holds up under questioning.
Build documentation into the plan from the beginning. Keep a codebook that defines every variable and its values. Save your raw data in a read-only form and never edit it directly. Do all cleaning and analysis through scripts or logged steps so that someone could rerun your work and arrive at the same results. For qualitative projects, the equivalent is a running analytic memo and a codebook that records when and why codes were created, merged, or dropped.
A consistent file-naming convention and a short README file in each project folder cost almost nothing and save enormous time. They also make it far easier to answer a committee member’s question months later, when you no longer remember why you made a particular choice.
Plan the End of the Project, Too
Finally, state what will happen to your data after the dissertation is complete. I just want to quickly note that this is one of the most overlooked parts of an IRB/data plan proposal, and is often the one least adhered to and the most likely to get you in trouble. Your consent forms and IRB protocol likely promised something specific, such as destroying recordings after transcription or retaining de-identified data for a set number of years. Your plan should match those promises exactly (and make sure you follow through with them). Inconsistency between your consent language and your retention practices is one of the more common reasons protocols are sent back for revision.
If you plan to share de-identified data or deposit it in a repository, make sure your consent process allows it. It is much easier to ask for permission up front than to seek it after the fact.
Bringing It Together
A strong data management plan is short, specific, and aligned with your IRB protocol and consent forms. It names your data types, explains where they are stored and who can access them, describes how you will document your decisions, and commits to a retention and disposal timeline. Writing it early prevents expensive surprises and shows your committee that your work is built to be trusted.
As a next step, open your current IRB protocol and compare it line by line with how you actually plan to handle your data this semester. Any gap you find is worth closing before collection begins.
Work With Matt
Good data practices are easy to overlook until a protocol is returned or a dataset is compromised, and they are much easier to build in at the design stage. Matt works with doctoral students to develop research designs, IRB materials, and analysis workflows that are organized, ethical, and ready for committee scrutiny. Learn more about Matt’s consulting approach or schedule a consultation.
