Choosing a method for a master’s nursing dissertation requires a feasibility decision you can defend to your supervisor. A method may fit the question yet still be impossible within your programme’s access, approval, supervision or submission arrangements.
If feasibility checks expose a mismatch, revisit the nursing research-question framework before committing to a smaller project. Once the decision is agreed, the methodology chapter structure checklist helps you document the chosen approach and its practical limits.
This guide helps you build a master’s project feasibility dossier and decide whether to proceed, narrow the plan or change the question. For comparing qualitative, quantitative and review designs, use the separate methodology selection guide. Here, the main task is checking whether your preferred project can actually be completed.
Start with the programme’s permitted project routes
Write down the project types your course permits before making a design commitment. Check the module handbook and supervisor guidance for restrictions on primary data, secondary analysis, reviews, quality improvement or service evaluation. Programme-specific instructions control your submission.
Keep confirmed requirements separate from assumptions. If a classmate completed interviews in a previous year, that does not establish that your project can use the same route. Ask about your own cohort, placement and proposed population.
Create a one-page requirements record with the assessment format, submission date, approval route and supervisor decisions. Add a source for each entry, such as the handbook section or a dated meeting note. This record becomes the starting point for feasibility planning.
Define the minimum study that answers your question
Describe the smallest coherent version of the project. Include the population or evidence set, setting, central phenomenon or outcome, and intended analysis. Then identify which elements are essential and which are optional additions.
For instance, a proposal about nurses’ experiences across several hospitals may contain more access demands than a master’s timetable can support. Narrowing to one clearly justified setting may be defensible if the revised question matches that scope. Keeping the broader question while collecting a much narrower dataset creates an alignment problem.
Do not use sample size alone as a shortcut for feasibility. Consider whether the available information can answer the question and whether you can analyse it credibly. Discuss the judgement with your supervisor and document the limits you accept.
Build an access record before promising data collection
List every person or organisation whose agreement is needed. Distinguish an encouraging conversation from formal permission. The record should identify what access is requested, who can authorise it, the current status and the next action.
| Access dependency | Evidence to obtain | Question to resolve |
|---|---|---|
| Participants | Approved recruitment arrangement | Can eligible people be approached through this route? |
| Existing dataset | Authorised access and usable documentation | Are the needed variables actually available? |
| Service site | Relevant organisational agreement | Can the planned activity happen during the project period? |
| Published evidence | Access to relevant full texts | Can the review be completed beyond abstracts? |
| Software and support | Working access and supervision arrangements | Can the proposed analysis be performed and checked? |
Do not describe a dataset as available merely because a service routinely collects information. You need to establish what you may access for this project, in which form, and under which conditions.
Work backwards from the submission date
Build a dependency schedule rather than dividing the remaining weeks equally between chapters. Recruitment cannot begin before the necessary permissions. Analysis depends on usable data, and a discussion needs time after findings have been checked.
Include review time for supervisor feedback and your response to it. Also allow for practical interruptions such as rota changes, leave, delayed correspondence or unavailable reports. A plan that works only if every dependency finishes immediately is fragile.
Write decision dates beside the main dependencies. For example: if access remains unconfirmed by the agreed checkpoint, discuss narrowing the project before the remaining analysis window becomes unrealistic. The appropriate checkpoint depends on your actual course timetable.
Check analytical readiness through a small practice task
Test the proposed analytical work before committing. For quantitative work, use suitable practice data to check whether you understand coding, assumptions and reporting. With qualitative work, practise documenting coding decisions on an approved teaching extract. When planning a review, trial the search and extraction process.
This is a skills check, not a substitute for the actual study. Do not report practice material as collected data. The useful output is a list of tasks you can complete, tasks requiring support and tasks that need a different plan.
For each gap, identify a specific learning activity and a realistic time allowance. “Learn statistics” is too vague. “Practise interpreting the planned model output with supervisor feedback” gives you an assessable action.
Prepare a proportionate governance plan
Identify the university and organisational processes relevant to your project. Do not assume that calling work a review, audit or service evaluation determines all permissions. Establish the classification and requirements through the appropriate local route.
Describe the information you intend to handle, where it will be stored, who may access it and what will happen at the end of the project. If those arrangements are unresolved, record them as outstanding dependencies rather than writing that approval has been obtained.
Where the proposed work involves sensitive accounts or relationships, discuss participant welfare, confidentiality and researcher responsibilities before collecting information. Keep the plan specific to the population and setting.
Use a feasibility decision table
The following table is a planning aid, not a validated scoring instrument. Use it to expose unresolved decisions. A project should not receive an overall “ready” label simply because several easy items are complete.
| Domain | Ready when | If unresolved |
|---|---|---|
| Programme fit | The route meets the current assessment requirements | Clarify before further development |
| Question | The proposed evidence can address the stated question | Narrow or reformulate the question |
| Access | Necessary permissions and materials are realistically obtainable | Set an access checkpoint |
| Analysis | The work is within available skills and support | Arrange focused training or simplify appropriately |
| Time | Dependencies leave room for analysis and revision | Revise the scope or schedule |
| Governance | The required process and responsibilities are understood | Resolve before starting the relevant activity |
Explain difficult judgements in a short note. A transparent limitation is more useful than an unexplained numerical score that makes the project appear feasible.
Worked example: when access changes the master’s plan
Consider a fictional student planning to compare discharge communication in several services. The initial question assumes access to staff in each setting. At the feasibility checkpoint, only one site has a realistic route for participation.
The student has three discussion options: narrow the question to that setting; develop a different authorised evidence source; or change the project route if the programme permits it. These options produce different questions and limitations. They are not interchangeable ways to preserve the original claim.
A useful supervisor note would explain which access assumption failed, how the revised scope changes the question, and what can still be completed within the timetable. The student would then update the aim, methods and intended conclusions together.
Write a contingency that protects the research question
A contingency needs a trigger, response and consequence. “Use fewer participants if recruitment is slow” is incomplete because it does not explain whether the resulting information can answer the question.
Instead, state when the problem will be reviewed, what alternatives can be considered and which approvals or question changes might be required. Do not collect different data or change the method without following the relevant supervisory and governance process.
For a review, the problem might be inaccessible reports or unexpectedly sparse evidence. A proportionate response could involve discussing the question or eligibility criteria before further work, with any amendment recorded transparently.
Prepare for the method-approval meeting
Bring five short items: your focused question, the programme requirements record, access status, dependency timetable and analytical readiness check. Add the main unresolved decision you need help making.
Ask concrete questions. “Is this project feasible?” is broad; “If access is not confirmed by this checkpoint, would the narrower question still meet the module requirements?” gives the supervisor something specific to assess.
After the meeting, record what was agreed, what remains provisional and who will take each action. Use the record to update the project plan rather than treating supervision as a separate administrative event.
Write the final methodological justification
Your dissertation should explain why the chosen method fits the question and how the actual constraints shaped its implementation. Distinguish planned procedures from what happened. If access or scope changed, describe the effect on the study and its conclusions.
A master’s project does not become stronger simply by adding methods. A clear, justified study can be more defensible than a complicated design whose components cannot be completed or integrated. Use the QAA master’s characteristics statement as a qualification-level reference alongside your programme’s assessment criteria.
Frequently asked questions
Is a literature-based dissertation automatically the easiest route?
No route should be chosen on that assumption. Check full-text access, review scope, screening workload, extraction and synthesis requirements against the time and support available.
What if my preferred analysis is beyond my current skills?
Identify the exact skills gap and discuss training or supervision early. If the support cannot be arranged, reconsider the plan while keeping the question and intended analysis aligned.
Can I change the question after an access problem?
Discuss the proposed change with your supervisor and follow the required approval process. Update all affected parts of the proposal and document what the change means for the project.
Conclusion
Finish method planning with a clear feasibility decision: proceed, narrow or revise. Keep access, approvals, analytical readiness and time visible so the chosen master’s project can deliver the answer it promises.
Reference
Quality Assurance Agency for Higher Education (2020) Characteristics statement: Master’s degree. QAA master’s degree characteristics statement.
