Academic English revision

Your Data Management Plan Screams "I'm Not Ready Yet"

A DMP isn't bureaucratic filler. It's the one section your supervisor reads word by word — because it tests whether you can be trusted with anything you collect.

The moment your supervisor says "add a data management plan," you open the university template, paste a paragraph about "data will be stored in compliance with institutional policy," and lose sleep. The sleeplessness is correct. Your instinct is telling you the paragraph is a lie. In nine out of ten master's proposals, the DMP is filler. But it isn't filler. It's the only section your supervisor reads word for word. In every other chapter they evaluate your thinking. This one, they evaluate whether you can be trusted with anything you touch.

The biggest trap is copy-pasting a funder template. UKRI, Horizon Europe, ERC boilerplate at six thousand words is not for you. Your master's data volume, retention window, and ethics clearance scale have nothing in common with a research grant. When you write "data will be deposited in Zenodo under CC-BY 4.0," your supervisor doesn't see sophistication. They see twelve interviews going public, no reuse audience, and a storage bill nobody budgeted. You don't look open-science literate. You look like someone who has never touched their own files.

Real requirement: four questions, written in under 500 words. One: where does the data live — local drive, OneDrive, departmental server, cloud. Pick one and say so. Two: where is the second copy — different machine, different location, different account? One or none is a single point of failure. Three: what format — .docx, .wav, .csv, proprietary? If proprietary, name the software and version. Four: what's shareable, what isn't, and why. That's the list. You don't need a destruction protocol, a metadata schema, or version control. None of that is required at master's level. Stop performing compliance.

Compare those two. ❌ "All data collected during the research will be stored securely and in compliance with university policies, and appropriate measures will be taken to ensure data integrity and availability throughout the project duration." ✅ "Interview audio files are stored on an encrypted external drive kept at home and mirrored weekly to the university OneDrive. Both copies are kept until after the viva, then the external drive is wiped and the OneDrive folder deleted." The second one isn't academic English. It's operational English. That's exactly what reviewers pay for. DMP language rewards subjects, objects, and verbs — not adjectives.

Ethics is where students fail in two directions at once. Over-promise: "data will be anonymized using k-anonymization and differential privacy." With twelve interviews, what's k? Add enough noise and your signal is the noise. Under-promise: "all participants will remain anonymous." How? The interview mentions their employer and department, three sentences in, you've identified them. ❌ "All identifiable information will be protected throughout the project." ✅ "Names, employers, and departments are replaced with codes (P01, Org-A) in every transcript and note. The key sits on a separate encrypted drive from the data." Specific rules beat vocabulary. Always.

This is the section where non-native writers sound the worst — because they try to sound institutional, and that effort is the whole problem. ❌ "Data management practices will be implemented in accordance with the highest standards of integrity and professional responsibility." Zero information, all vocabulary. ✅ "I keep two copies and check them weekly." I push easydue in the opposite direction here. Strip the ornament. Keep the verbs. The saved effort goes into figuring out your actual backup path, not your actual adjective.

Your DMP isn't for the university. The university doesn't read it. Your DMP is for the version of you six months from now, at three in the morning, opening a corrupted recording. If writing this section doesn't conjure that scene — the click of a failing drive, the empty folder, the viva in nine weeks — you aren't ready for the viva. You aren't ready for the master's. That's what the DMP actually tests: whether you take your own project seriously enough to plan for losing it.