eduKate Singapore

VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

Next useful routeCanonical hubHELP

Why English? | Reading a Research Data Management Plan Before Collecting Study Data

—

by

eduKate Asia
RESEARCH DATA · MANAGEMENT PLAN · STUDY DESIGN

Turn a data management plan into everyday research practice

Authenticate the plan; describe data types and sources; design naming, versioning and documentation; separate storage from backup; classify sensitive data; align consent and ethics; clarify ownership; assign roles; date retention and disposal; plan proportionate sharing; control revisions; and preserve the complete stewardship record.

ROUTE 1Verify planStart with the closest decision, then continue through the full guide.ROUTE 2Map dataStart with the closest decision, then continue through the full guide.ROUTE 3Protect accessStart with the closest decision, then continue through the full guide.ROUTE 4Plan sharingStart with the closest decision, then continue through the full guide.ROUTE 5Preserve evidenceStart with the closest decision, then continue through the full guide.

Open the full chapter index ↓

Why this English matters now

A research data management plan is not paperwork for the end of a project. It is the working map for every file created from the first day of study data collection.

Researchers searching data management plan, DMP checklist, research data storage, sensitive data or data sharing need to connect abstract policy words to folders, people, permissions and dates.

Current NUS sources checked on 27 October 2026 show that good planning spans organisation, storage, documentation, rights, security, preservation and reuse.

Clear English makes those connections visible before a preventable loss, privacy breach or ownership dispute occurs.

Checked against the official sources on 27 October 2026. The article explains how to read a document and make a safer next decision; it does not replace the issuing institution.

The reading method

Build a data register with project, owner, version, data type, source, format, volume, naming rule, version method, README, primary storage, backup, recovery test, sensitivity, identifiers, encryption, access roles, consent basis, ethics reference, rights, retention rule, disposal, repository, licence, embargo, incident route, revision date and final disposition.

  • NUS describes a DMP as the plan for what data exists, where it is stored, who manages it, how it is looked after and when it becomes public.
  • The NUS checklist covers data types, organisation, versioning, formats, metadata, documentation, sensitive data, storage, backup, recovery, sharing and responsibilities.
  • NUS policy guidance says its research-data policy applies to researchers across the university and links data stewardship to integrity and validation.

Read with every responsible person in view

  • Read from researcher, participant, principal investigator, collaborator, data steward and future reuser perspectives.
  • Keep collected, stored, backed up, approved for access, de-identified, shared and retained as separate states.
  • Use a data-risk-role-lifecycle model.

Different people can read the same sentence for different jobs. The student needs the next action; the administrator needs a routable record; the family needs a realistic timeline; the eventual recipient needs evidence that fits its stated purpose. Good English keeps those needs aligned without inventing authority.

Official factual floor

These first-party sources support the factual claims and should be reopened for any live transaction:

Scope: This article does not approve a research protocol, select a storage service, decide whether data is anonymous, interpret law or contracts, authorise sharing or replace the current DMP, consent form, ethics decision, funder terms, institutional policy, data steward or information-security team.

Did you know?

A synchronised folder can give several people the latest file and still fail as a true backup if one deletion or corrupted file propagates everywhere. Collaboration and recovery are different design jobs.

Full chapter index

  1. 1. Authenticate the plan and its version
  2. 2. Name the data before naming the storage
  3. 3. Design the filing and version system
  4. 4. Separate storage from backup
  5. 5. Read sensitivity as a handling rule
  6. 6. Align the plan with ethics review
  7. 7. Clarify ownership and rights early
  8. 8. Assign people, not vague teams
  9. 9. Date retention and disposal
  10. 10. Plan sharing without promising everything
  11. 11. Treat the plan as a living control
  12. 12. Keep the complete data-management chain
CHAPTER 1 OF 12

1. Authenticate the plan and its version

Back to contents

What this part of the document is doing

Open the project or funder's official record and match the project title, principal investigator, plan owner, version, date and approving or reviewing route. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.

The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.

A realistic situation

Example: A draft copied from another project is treated as the active plan because its headings look complete. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.

Practical reading sequence
  1. 1. match the project
  2. 2. match the owner
  3. 3. check the version
  4. 4. save the active record

Put into one sentence, the sequence is to match the project, match the owner, check the version, and save the active record. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.

Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.

Important boundary: A useful template is not evidence that its answers apply to this study. A boundary is not a reason to give up. It tells the reader exactly where official clarification, fresh evidence or a different process is needed.

Transfer: Authentication supports trustworthy research. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.

CHAPTER 2 OF 12

2. Name the data before naming the storage

Back to contents

What this part of the document is doing

A workable plan describes what will be collected or generated, including formats, approximate volume, sources and any conditions attached to reused data. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.

The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.

A realistic situation

Example: The plan says research files without separating interview audio, transcripts, code, images and derived tables. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.

Practical reading sequence
  1. 1. list data types
  2. 2. record data sources
  3. 3. estimate scale
  4. 4. name reuse conditions

Put into one sentence, the sequence is to list data types, record data sources, estimate scale, and name reuse conditions. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.

Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.

Important boundary: Different data types can require different controls, retention and sharing decisions. A boundary is not a reason to give up. It tells the reader exactly where official clarification, fresh evidence or a different process is needed.

Transfer: Classification supports science and digital work. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.

CHAPTER 3 OF 12

3. Design the filing and version system

Back to contents

What this part of the document is doing

NUS's checklist asks how files will be organised, named, versioned and documented so later users can identify the correct record. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.

The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.

A realistic situation

Example: Researchers add final, final2 and newest to filenames until no one knows which analysis produced the paper. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.

Practical reading sequence
  1. 1. set naming rules
  2. 2. set folder structure
  3. 3. set version method
  4. 4. create a README

Put into one sentence, the sequence is to set naming rules, set folder structure, set version method, and create a README. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.

Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.

Important boundary: A folder that makes sense today may be unreadable after staff or software changes. A boundary is not a reason to give up. It tells the reader exactly where official clarification, fresh evidence or a different process is needed.

Transfer: Documentation supports reproducibility. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.

CHAPTER 4 OF 12

4. Separate storage from backup

Back to contents

What this part of the document is doing

Primary storage is where work happens; backup is an independent recovery copy with a tested restoration route. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.

The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.

A realistic situation

Example: A synchronised folder is described as a backup even though accidental deletion immediately propagates to every device. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.

Practical reading sequence
  1. 1. name primary storage
  2. 2. name backup storage
  3. 3. set backup frequency
  4. 4. test recovery

Put into one sentence, the sequence is to name primary storage, name backup storage, set backup frequency, and test recovery. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.

Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.

Important boundary: Multiple copies are not a resilient backup if one error can remove all of them. A boundary is not a reason to give up. It tells the reader exactly where official clarification, fresh evidence or a different process is needed.

Transfer: Systems English supports resilience. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.

CHAPTER 5 OF 12

5. Read sensitivity as a handling rule

Back to contents

What this part of the document is doing

The plan should identify personal, health, confidential, proprietary or otherwise sensitive data and connect each class to access, encryption and approved environments. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.

The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.

A realistic situation

Example: A participant code is called anonymous while the re-identification key sits beside the dataset. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.

Practical reading sequence
  1. 1. classify sensitivity
  2. 2. locate identifiers
  3. 3. separate the key
  4. 4. limit access

Put into one sentence, the sequence is to classify sensitivity, locate identifiers, separate the key, and limit access. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.

Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.

Important boundary: Pseudonymised and anonymous are not interchangeable claims. A boundary is not a reason to give up. It tells the reader exactly where official clarification, fresh evidence or a different process is needed.

Transfer: Privacy language supports ethical research. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.

CHAPTER 6 OF 12

6. Align the plan with ethics review

Back to contents

What this part of the document is doing

NUS's checklist asks how data practices comply with IRB review where applicable, so consent, collection, access and sharing descriptions should agree. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.

The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.

A realistic situation

Example: The consent form promises deletion after analysis while the DMP promises indefinite public deposit. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.

Practical reading sequence
  1. 1. compare consent
  2. 2. compare protocol
  3. 3. compare DMP
  4. 4. resolve contradictions

Put into one sentence, the sequence is to compare consent, compare protocol, compare DMP, and resolve contradictions. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.

Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.

Important boundary: One document cannot quietly widen permission granted in another. A boundary is not a reason to give up. It tells the reader exactly where official clarification, fresh evidence or a different process is needed.

Transfer: Consistency supports participant trust. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.

CHAPTER 7 OF 12

7. Clarify ownership and rights early

Back to contents

What this part of the document is doing

NUS advises researchers to clarify ownership and rights before a project starts because funding, collaboration and source-data conditions can shape future use. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.

The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.

A realistic situation

Example: The person who created a spreadsheet assumes sole ownership despite an institutional collaboration agreement. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.

Practical reading sequence
  1. 1. identify creators
  2. 2. identify agreements
  3. 3. identify funder terms
  4. 4. record the rights owner

Put into one sentence, the sequence is to identify creators, identify agreements, identify funder terms, and record the rights owner. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.

Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.

Important boundary: Possession of a working copy does not by itself settle ownership or licensing. A boundary is not a reason to give up. It tells the reader exactly where official clarification, fresh evidence or a different process is needed.

Transfer: Rights literacy supports collaboration. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.

CHAPTER 8 OF 12

8. Assign people, not vague teams

Back to contents

What this part of the document is doing

A plan becomes operational when every recurring task has an owner: access approval, backup checks, metadata, incident response, retention review and deposit. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.

The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.

A realistic situation

Example: The plan says the team will manage data after the only data manager leaves the project. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.

Practical reading sequence
  1. 1. name each role
  2. 2. name a deputy
  3. 3. record handover
  4. 4. review access

Put into one sentence, the sequence is to name each role, name a deputy, record handover, and review access. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.

Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.

Important boundary: Shared responsibility without named owners can become unowned work. A boundary is not a reason to give up. It tells the reader exactly where official clarification, fresh evidence or a different process is needed.

Transfer: Role clarity supports organisations. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.

CHAPTER 9 OF 12

9. Date retention and disposal

Back to contents

What this part of the document is doing

Current NUS policy guidance describes durable archiving of research results for a minimum period unless ethical, professional or funding guidance requires otherwise; the applicable rule must be matched to the study. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.

The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.

A realistic situation

Example: Every file is kept forever because deletion feels risky, including identifiers no longer permitted by the protocol. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.

Practical reading sequence
  1. 1. identify the rule
  2. 2. calculate review dates
  3. 3. separate record classes
  4. 4. document disposal

Put into one sentence, the sequence is to identify the rule, calculate review dates, separate record classes, and document disposal. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.

Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.

Important boundary: Retention is not a universal instruction to preserve every copy indefinitely. A boundary is not a reason to give up. It tells the reader exactly where official clarification, fresh evidence or a different process is needed.

Transfer: Time language supports compliance. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.

CHAPTER 10 OF 12

10. Plan sharing without promising everything

Back to contents

What this part of the document is doing

A DMP can explain what will be shared, with whom, under what access route, licence, embargo or limitation, while protecting legitimate restrictions. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.

The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.

A realistic situation

Example: Open science is translated as uploading raw participant data to a public folder. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.

Practical reading sequence
  1. 1. identify shareable outputs
  2. 2. apply de-identification
  3. 3. choose access level
  4. 4. record limitations

Put into one sentence, the sequence is to identify shareable outputs, apply de-identification, choose access level, and record limitations. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.

Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.

Important boundary: Transparent research can include justified controlled access rather than unrestricted release. A boundary is not a reason to give up. It tells the reader exactly where official clarification, fresh evidence or a different process is needed.

Transfer: Nuance supports open science. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.

CHAPTER 11 OF 12

11. Treat the plan as a living control

Back to contents

What this part of the document is doing

New instruments, collaborators, incidents and publication requirements can change the data route, so revisions should be dated and approved through the applicable process. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.

The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.

A realistic situation

Example: A plan written for grant submission is never revisited after the study begins collecting a new data type. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.

Practical reading sequence
  1. 1. schedule reviews
  2. 2. log changes
  3. 3. recheck approvals
  4. 4. notify affected roles

Put into one sentence, the sequence is to schedule reviews, log changes, recheck approvals, and notify affected roles. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.

Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.

Important boundary: A revision should not retrospectively authorise work that required prior approval. A boundary is not a reason to give up. It tells the reader exactly where official clarification, fresh evidence or a different process is needed.

Transfer: Change control supports long projects. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.

CHAPTER 12 OF 12

12. Keep the complete data-management chain

Back to contents

What this part of the document is doing

Archive the applicable policies, funder terms, DMP versions, reviews, access decisions, incidents, handovers, deposits and final retention actions separately. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.

The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.

A realistic situation

Example: Only the final dataset is preserved, so no one can explain how access and transformations were governed. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.

Practical reading sequence
  1. 1. archive the basis
  2. 2. archive plan versions
  3. 3. archive operational records
  4. 4. archive final disposition

Put into one sentence, the sequence is to archive the basis, archive plan versions, archive operational records, and archive final disposition. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.

Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.

Important boundary: Good records make stewardship visible without pretending that every risk disappeared. A boundary is not a reason to give up. It tells the reader exactly where official clarification, fresh evidence or a different process is needed.

Transfer: Evidence chains support research careers. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.

Evidence examples: what the wording can and cannot prove

Label and operative sentence

Use a heading to locate the research-data management plan, then read the whole sentence that controls the decision.

Check: Navigation words help; complete clauses decide.

Current source and saved evidence

Keep a dated copy, but reopen the official source before a live deadline.

Check: An authentic record can still be out of date.

Requirement and recommendation

Preserve must, should, may, encouraged and recommended.

Check: Modal verbs change responsibility.

Interim and final state

Record an interim state without expanding it into a promise.

Check: Evidence is reliable only within its stated scope.

Practice studio

Data map

Describe the material before choosing controls.

  • type
  • source
  • format
  • volume
  • sensitivity

Responsibility matrix

Give every recurring task an owner.

  • access
  • backup
  • metadata
  • incident
  • retention

Lifecycle calendar

Connect decisions to dates.

  • collection
  • review
  • sharing
  • retention
  • disposal

Advice for students, families and advisers

For students and researchers

  • Write the plan before collection and revise it when the project changes.
  • Compare the DMP with consent, ethics, funding and collaboration records.

For supervisors and principal investigators

  • Name owners, backups and handover routes rather than assigning work to the team.
  • Review access and retention alongside scientific milestones.

For families and future researchers

  • Support careful organisation without asking for confidential study data.
  • Remember that open research can use controlled access where restriction is justified.

Frequently asked questions

Is a DMP only for grant submission?

No; it should guide daily data work.

Is cloud sync the same as backup?

Not necessarily.

Does a code make data anonymous?

Not automatically.

Should all data be public?

No; consent, ethics, rights and sensitivity matter.

Who owns research data?

Use the applicable institutional and agreement records.

How long should data be kept?

Use the matched institutional, ethical, professional and funder requirements.

Can the plan change?

Yes, but revisions should be dated and authorised where required.

What belongs in a README?

Enough context to interpret structure, variables, transformations and versions.

What should I save?

Policies, DMP versions, access decisions, incidents, deposits and final actions.

Why English?

Because stored, backed up, approved, de-identified, shared and retained are different data states.

Useful next reading

Closing thought

A good DMP makes invisible care visible. Every dataset has a source, owner, protection route, useful future and ending—and the research team can explain each one before collection begins.