The data management section of a nursing dissertation explains how research files move from collection to storage, use, retention and disposal. It should describe your actual arrangements, with enough detail for a supervisor to understand who handles each file and how you protect it.
Many students write that their data will be kept confidential and password protected. However, that statement leaves important questions unanswered. Which files contain names? Where are recordings stored? Who can open them? What happens when the student finishes the course?
This guide shows how to turn those decisions into clear methodology writing. You will find a planning table, worked examples for different dissertation designs, weak and improved sentences, and a final consistency check. The examples are fictional teaching examples. Adapt them to your approved project and university requirements before using them.
What belongs in the data management section of a nursing dissertation?
Think about the complete journey of the material you use. Research files can include consent forms, recruitment records, interview recordings, transcripts, questionnaire responses, spreadsheets, coding notes and analysis output. A review also creates search exports, screening decisions and extraction tables.
Your section should explain the handling of these materials. By contrast, the analysis section explains how you answer the research question. A description of thematic analysis or regression does not tell a reader how you protect or organise the underlying files.
The UK Data Service describes active data management as including storage, access, file workflows, quality and disposal (UK Data Service, n.d.a). These categories provide a useful planning framework. However, the wording of your dissertation must reflect the systems and responsibilities approved for your study.
For the wider chapter layout, use our nursing dissertation Chapter 3 methodology checklist. This article develops the data-handling subsection rather than repeating the whole methodology chapter.
Plan before you write: map the files your study creates
Start with an inventory. List each type of file, its purpose, whether it contains identifiers and where it will be held. Include temporary materials because recruitment emails, downloaded survey exports and duplicate recordings can be easy to overlook.
Next, map each movement. For example, a recording may move from an approved recorder into institutional storage and then into an authorised transcription workflow. The transcript becomes a separate file, with its own access and retention decisions.
Use this table as a planning aid. The entries are questions to resolve, not universal university rules.
| File type | Decision to explain | Evidence to check |
| Recruitment/contact list | Who needs identifiers and for how long? | Recruitment protocol and information sheet |
| Consent record | How is it stored separately from research responses? | Approved consent procedure |
| Recording | How is it transferred, protected and eventually removed? | Approved recording and storage workflow |
| Transcript or response dataset | How are codes, access and identifiers managed? | Data management plan and institutional policy |
| Working analysis files | How are versions, corrections and decisions recorded? | Project workflow and software arrangements |
| Review records | How are search, screening and extraction decisions preserved? | Review protocol and assessment requirements |
Finally, check whether every proposed step is feasible. Do not name a secure server you cannot access or promise a backup process you have never confirmed.
A practical structure for the data management section of a nursing dissertation
There is no single compulsory structure for every programme. Follow your brief first. If it allows a separate subsection, organise the writing around the following sequence:
- Identify the data and related records.
- Explain collection and transfer arrangements.
- Describe storage, protection and authorised access.
- Explain coding, identifiers and confidentiality checks.
- Describe organisation, version control and quality records.
- State retention, sharing and disposal arrangements.
Use the space available to explain decisions that matter in your design. An interview study needs attention to recordings and transcript disclosure. A survey needs clear response exports and variable definitions. A systematic review needs reproducible search and selection records.
Where the word limit is tight, place a detailed handling matrix in an appendix if your university allows it. Then summarise the essential arrangements in the main text and refer to the appendix. An appendix should support the explanation, rather than hide decisions that the marker needs to assess.
Describe storage and access in concrete terms
Name the approved storage environment at an appropriate level, such as the university-managed research drive. Explain which files are held there and which roles can access them. Distinguish a protected master dataset from files prepared for analysis or reporting.
Avoid treating a password as a complete plan. Access permissions, secure transfer, device arrangements and institutional backup processes may also matter. Describe only controls that apply to your study and that you can verify.
For example, “The student researcher and named supervisor will have access to the coded dataset through the approved university research workspace” is clearer than “Only relevant people will see the data”. If a transcription provider is involved, the section needs to reflect the authorised arrangement and associated access.
Also consider what happens after your student account closes. Responsibility for retained records must remain workable. Confirm the handover or custody arrangement with your supervisor before describing it as settled.
Explain anonymity, pseudonymisation and confidentiality accurately
Do not call a dataset anonymous simply because you replace names with numbers. If a separate key links a participant code to a person, the data remain linkable. Describe that arrangement accurately and explain how the key is stored and accessed.
In interviews, a transcript may also identify someone through a rare job role, a distinctive event or a small clinical team. Therefore, removing direct identifiers is only one part of the review. Consider the combination of details retained in quotations and participant descriptions.
UK Data Service guidance presents privacy protection as a combination of communication, technical measures and governance controls (UK Data Service, n.d.b). Your writing should show how those elements work together in your project.
A useful sentence might state: “Transcripts will use participant codes, and the code key will be stored separately with restricted access. Before reporting quotations, potentially identifying contextual details will be reviewed.” Only use it if that process is approved and planned.
Organise files so another reader can follow the workflow
Organisation supports reliable writing as well as secure handling. Use a consistent folder structure and file-naming approach. Keep original source material distinguishable from working copies, and identify the version used for final analysis.
For example, a fictional coded file could be named “P07transcriptv02”. A survey file could be labelled “surveycleanedv03” alongside a change log. Avoid participant names in ordinary working filenames where codes are appropriate.
Explain how you record corrections. If you change a response code, merge duplicate records or amend a transcript, preserve a reason that allows the decision to be checked. Do not silently overwrite evidence to make the results look cleaner.
Documentation also helps interpretation. The UK Data Service emphasises that research materials need clear organisation and documentation to remain understandable beyond the original project (UK Data Service, n.d.c). For a dissertation, this means making your own workflow traceable without placing confidential source data in the submission.
Write retention and disposal arrangements without inventing a deadline
There is no retention period that automatically applies to all nursing dissertations. Check your institution’s policy, approved protocol, sponsor requirements and any conditions attached to the data source. Different record types may have different arrangements.
State the period or trigger where it is confirmed, the responsible custodian and the planned disposal route. For example, recordings might have a different approved endpoint from consent records or coded analysis files. Do not assume that every file must disappear immediately after marking.
If the required period is still unresolved in a proposal, identify that decision for confirmation before collection. In the completed dissertation, replace uncertainty with an accurate description of the agreed arrangement.
Avoid vague phrases such as “Data will be destroyed later”. Explain what is removed, when and by whom. Also consider copies on collection devices, temporary exports and backup systems. Ask the institution how its approved disposal process handles these copies rather than promising deletion you cannot guarantee.
Worked example: qualitative interview dissertation
The following fictional proposal example assumes that the stated university arrangements have been approved. It illustrates the relationships between files, rather than prescribing a system.
Interview recordings will be transferred from the approved recording device into the university-managed research workspace. After successful transfer has been checked, device copies will be removed through the approved procedure. Transcripts will use participant codes, and the code key will be stored separately with restricted access. The student researcher and named supervisor will access the coded transcripts for the agreed research purpose. Original transcripts and working analysis versions will remain distinguishable, with amendments recorded in a change log. Quotations will be reviewed for identifying contextual details before inclusion in the dissertation. Recordings, consent records and coded research files will follow the separate retention and disposal arrangements specified in the approved data management plan. The university-designated custodian will hold any records retained after the student’s account closes.
Notice how the paragraph answers practical questions. It covers transfer, linked identifiers, access, working versions, quotations and custody. However, the retention sentence would need the actual periods and policy reference where the brief requires them.
For qualitative interpretation itself, consult the relevant analysis guidance separately. Storing a transcript securely does not establish that your coding or theme development is sound.
Worked example: quantitative questionnaire dissertation
For a survey, explain what the platform collects and what enters the analysis file. Do not promise anonymity without checking platform settings and indirect identifiers.
Questionnaire responses will be exported from the institution-approved survey platform into restricted university storage. The export settings will follow the approved protocol and will avoid collecting unnecessary identifying information. The original export will be preserved separately from a working analysis copy. A codebook will define variable names, response categories, missing-value codes and any derived variables. Data-checking decisions will be recorded in a cleaning log, including the reason for excluding duplicate or ineligible records. Access will be limited to the authorised research roles. Reporting will use aggregated results and will consider identification risks in small groups. Retention, permitted sharing and disposal will follow the approved project arrangements and the institutional policy cited in the protocol.
This paragraph describes how the dataset is managed. It does not explain which statistical tests answer the question. Use our guide to analysing nursing dissertation data in SPSS for that separate stage.
Before adopting the example, check whether the platform stores email addresses, account details or technical information. Your written description must match the settings used.
Worked example: systematic review or literature-based dissertation
A review does not usually generate new interview or survey responses. Nevertheless, it creates research records that need organisation. Avoid copying a primary-research paragraph about participant consent into a dissertation based solely on published studies.
Search exports, deduplication records, screening decisions and extraction tables will be held in the university-approved project workspace. Each search record will identify the database, search date and strategy used. Study identifiers will link screening and extraction files to their bibliographic records. Working versions of the extraction table will remain distinguishable, and substantive corrections will be documented. Published articles will be accessed and stored within the terms of the relevant licences. The dissertation will report study-level evidence, while project records will be retained according to the programme’s research-record requirements. Any additional material received from study authors will be handled under the conditions attached to that material.
The key difference is the object being managed. You are preserving a transparent evidence trail rather than describing new participant recruitment. However, secondary datasets, unpublished records or individual-level information may introduce additional restrictions.
Our nursing dissertation literature review guide explains evidence organisation and synthesis. Keep those analytical steps connected to, but distinct from, the management of review files.
Improve weak sentences with study-specific detail
Use the following comparisons to diagnose gaps. The improved versions remain illustrative and need adaptation to your project.
| Weak sentence | Why it leaves a gap | More precise wording |
| All data will be confidential. | It does not explain a process. | Coded transcripts will be held in the approved university workspace, with access restricted to the authorised research roles. |
| Names will be removed, making the data anonymous. | A code key or contextual detail may preserve identifiability. | Direct identifiers will be removed from working transcripts; the separate code key and contextual disclosure risks will be managed through the approved procedure. |
| Data will be kept for five years. | The number has no stated basis. | Each record type will follow the retention period specified in the cited institutional policy and approved project plan. |
| SPSS will manage the data. | Software does not explain storage, access or documentation. | The working dataset will be analysed in SPSS, with a separate codebook and cleaning log held in restricted institutional storage. |
After revising a sentence, ask whether a reader could identify the file, action, responsible role and relevant condition. If not, more detail may be needed.
Keep your documents and verb tenses consistent
Compare the methodology with the ethics application, participant information sheet, consent materials and data management plan. They should agree about storage, access, withdrawal, retention and sharing.
A proposal describes planned arrangements. A completed dissertation reports what actually happened. Therefore, “will be stored” may suit a proposal, while “were stored” may suit a completed project. Do not change the tense alone if the real process differed from the plan.
For example, if an approved transcription workflow changed, explain the actual arrangement and relevant approval rather than retaining an inaccurate original sentence. Likewise, do not imply that ethics approval or organisational permission was obtained when it was not.
Research integrity includes accurate reporting across the research lifecycle. UKRIO’s revised Code of Practice addresses data management and emerging technologies within that wider responsibility (UKRIO, 2025). Use institutional guidance alongside it because local arrangements determine the practical process you must describe.
Address sharing, transcription tools and external support
Explain whether any material can be shared and under which conditions. Open research does not mean that identifiable nursing research data should be uploaded publicly. Permissions, participant communication and institutional governance remain relevant.
Similarly, a convenient transcription tool or cloud account is not automatically authorised for your project. Check the approved workflow before uploading recordings or transcripts. If a tool is permitted, explain the arrangement accurately and verify the output as required by your method.
For external academic support, share only material you are allowed to disclose. A methods question can often be discussed using a fictional example, an approved de-identified extract or a blank planning table. Remove unnecessary patient, participant, staff and placement identifiers.
Our nursing dissertation support can help you review the clarity of your writing. It should not replace institutional approval or invent completed research procedures. Read about our service and how the review process works before sending material.
Final editing checklist
Before submission, check the section against your actual files and approved documents:
- Every important record type is included, including temporary exports and code keys.
- Collection and transfer arrangements are clear and feasible.
- Storage and authorised access are described accurately.
- Anonymity claims match the real possibility of linking or recognising people.
- Versions, corrections and variable definitions are documented where relevant.
- Retention periods have an institutional or project-specific basis.
- Disposal and post-course custody arrangements are workable.
- Sharing and transcription statements match the approved workflow.
- The tense matches a proposal or completed study.
- Confidential source data have not been inserted into public appendices.
Finally, read the paragraph aloud. Replace abstract promises with concrete processes, but keep technical detail proportionate. A short, accurate section is stronger than a longer paragraph filled with controls that your project never used.
Frequently asked questions
Where should the data management section go?
It usually fits within the methodology chapter, often near ethics and governance. However, follow your programme’s required headings. A separate plan or appendix may also be required.
How long should this section be?
There is no universal word count. Use enough space to explain the handling of your study’s files. The complexity of the design and the assessment brief should guide its length.
Does a systematic review need data management?
Yes, review records need organisation and preservation. Describe search exports, screening decisions, extraction files and access conditions rather than inventing participant procedures.
Can I state that all data are anonymous?
Only if that description is accurate. A code key, recording or distinctive contextual details can preserve identification risks. Explain the real arrangement and its safeguards.
Can I choose my own retention period?
Confirm the applicable institutional and project requirements first. Do not select a period because it appears in another student’s dissertation or an online example.
Should I include raw data in an appendix?
Follow the brief and approved governance arrangements. Do not attach identifiable source data. A permitted codebook, blank instrument or de-identified example may demonstrate the workflow more appropriately.
Conclusion
A strong data management section makes the research workflow understandable. Identify the files, explain their movement and access, describe how identifiers and versions are handled, and state the approved retention and disposal arrangements. Then check that the paragraph matches both your documents and your actual practice. Use examples to learn the structure while keeping every claim specific to your own nursing dissertation.
Get help reviewing your methodology writing
If the section is vague or conflicts with supervisor feedback, request a focused review of its clarity and consistency. You can read our student reviews and submit an enquiry with your brief and permitted materials. Keep ownership of your research decisions, and confirm governance questions with your university.
References
UK Data Service (n.d.a) Managing data during the project. Available at: View source (Accessed: 6 October 2026).
UK Data Service (n.d.b) Anonymising data and protecting participants. Available at: View source (Accessed: 6 October 2026).
UK Data Service (n.d.c) Foundations of research data management. Available at: View source (Accessed: 6 October 2026).
UK Research Integrity Office (UKRIO) (2025) Code of Practice for Research. Version 3.5. Available at: View source (Accessed: 6 October 2026).
