Medication reconciliation is a good illustration of what a capstone problem statement has to do, because everyone agrees it matters and almost nobody can say how often it fails where they work. NR-560 opens by asking you to move from that shared conviction to a defined problem in a defined setting: what is happening, to whom, how often, measured against what standard, and what it costs the organization. Everything else in the capstone inherits the precision of this paragraph. Your section may print this as NR 560 or NR560; it is the same course. Chamberlain publishes no syllabi outside Canvas. The placement here is our teaching judgment from the course's catalog arc; your section's rubric decides what your week actually asks.
What NR-560 Week 1 asks for
A capstone is a synthesis course, which means the opening stage is not a warm-up. It is the foundation the remaining seven stages are built on, and in an eight-week session there is no room to rebuild it later. The written work usually asks for a problem identified in a real setting, sized with data, and connected to something the organization already cares about.
The distinction that decides the grade is between a topic and a problem. A topic is alarm fatigue. A problem is that on a defined telemetry unit, a large share of monitor alarms over a measured period were non-actionable, against a published expectation that most alarms should require a response. The second version can be measured, changed and evaluated. The first can only be discussed, and a capstone built on a topic produces an aim with no number, an intervention with no target and an evaluation plan with nothing to evaluate.
Two things separate this course from the research work that preceded it. First, the object is a change rather than a study: you are proposing to improve one system rather than to produce generalizable knowledge, and the writing should sound like a project document rather than a research report. Second, feasibility is graded. A problem nobody could address inside the resources available is a poor capstone problem however important it is, and part of what this stage asks is that you choose something the setting could actually move.
One boundary is worth stating early. Any hours, on-site activity, sign-offs, approvals or contact with a real organization that your capstone involves are yours and only yours. A manual like this one supports the written layer: how the document is built, argued and evidenced. Nothing in it substitutes for the work you do, and nobody else can document activity you performed.
The NR-560 Week 1 method, step by step
Six moves that turn a familiar frustration into a capstone problem worth eight weeks.
-
Choose a problem with an existing measurement trail
Look for something the organization already counts: an audit, a dashboard indicator, an incident category, a documentation field, a satisfaction domain. A problem that is already measured gives you a baseline without any new data collection, and it is far easier to defend because the numbers are the organization's own.
-
Bound the setting tightly
One unit, one clinic, one shift, one patient population. A capstone scoped to an entire hospital collapses under the weight of its own stakeholder list, and the narrower version is not a smaller project, it is a more credible one. Say the setting in the first sentence.
-
Size the gap with counts, denominators and a window
Thirty-one of 486 admissions over one quarter. Not frequently, not a concerning number. If you cannot obtain local figures, size the problem from published rates in comparable settings and say plainly which you are doing, because an honest published baseline beats an invented local one every time.
-
Name the standard the gap fails against
A gap only exists relative to an expectation. Cite the guideline, national safety goal, regulatory requirement or organizational policy that defines what should be happening, with its issuing body and year in the sentence.
-
Translate the problem into consequences the organization tracks
Harm, length of stay, readmission, staff time, turnover, regulatory exposure, reimbursement. A problem statement that connects a clinical gap to something leadership already watches is the difference between a proposal that gets read and one that gets filed.
-
Write the significance paragraph from literature, not from conviction
Why this matters is a claim requiring support. Two or three recent sources establishing that the problem is recognized in similar settings, and that it has known consequences, convert your conviction into an argument a grader can score.
A layout and word budget for a capstone problem statement
The frame our tutors keep beside an opening capstone section, sized for roughly 1,000 to 1,300 words. It is our own outline rather than anything the university issues, and your week's rubric outranks it wherever the two disagree.
| Section | What belongs in it | Word target |
|---|---|---|
| The problem in one paragraph | Setting, population, the measured gap with its denominator and window, before any background. | 120 to 150 |
| The setting described | Unit type, size, patient population, staffing model and anything about it that shapes the problem. | 170 to 200 |
| Baseline and its source | The numbers you have, where they came from, and an honest note where local data are unavailable. | 180 to 220 |
| Standard and expectation | The guideline, safety goal or policy defining what should occur, named with issuing body and year. | 150 to 180 |
| Significance | Consequences for patients, staff and the organization, supported by recent published evidence. | 230 to 280 |
| Scope and feasibility | What is inside the project and what is deliberately outside it, with the reason for each boundary. | 150 to 190 |
Evidence craft for a capstone opening
Separate what you observed from what is published. Local observation establishes that the problem exists here. Published evidence establishes that it matters and has known causes. A paragraph that puts the published claim first and the local number second as illustration is the shape that scores; reversed, it reads as a story with a citation attached.
Attribute every organizational figure. Say where a number came from: an internal dashboard, a quality report, an audit summary. Numbers with no stated source cannot be checked, and in a capstone they will be relied on for six more stages.
Keep the evidence recent for anything describing current practice. Graduate work usually expects sources from roughly the last five years for prevalence, consequences and current recommendations. Reaching back is legitimate for a foundational model or an instrument, but say why you did.
Write in project language, not research language. This is an improvement initiative, so it has an aim rather than a hypothesis, participants who are staff rather than subjects, and measures rather than dependent variables. Language borrowed from research reporting signals a misunderstanding of what the document is.
Protect confidentiality in every sentence about your setting. Describe the unit by type and size rather than by name, keep all data aggregate, and include nothing that could identify a patient or a colleague. A course document is not a confidential record.
Five mistakes that cost points in this week's territory
- A topic in place of a problem. Nurse burnout, alarm fatigue and communication failures are subject headings that cannot carry an aim.
- An unbounded setting. A problem defined across a whole health system produces a stakeholder list no eight-week project could manage.
- A baseline with no denominator. A rate with no base, or an assertion with no rate, leaves the evaluation stage nothing to measure against.
- An intervention chosen before the problem was defined. Deciding you will do hourly rounding and then finding a problem it fits inverts the entire logic of the project.
- Significance argued from experience alone. Years on the unit is credibility, and a graduate rubric scores the support row separately.
Before you submit
- The setting is named by type and bounded in the first paragraph
- The gap appears with a count, a denominator and a period
- The source of every number is stated, including where data are unavailable
- A named standard with a year defines the expectation being missed
- Significance is supported by recent published evidence, not by conviction
- The problem is connected to an outcome the organization already tracks
- No patient, colleague or named facility is identifiable from the text
Starting the NR-560 capstone?
Send the instructions and the rubric out of Canvas. A premium original draft comes back in 24 to 48 hours with the problem bounded, the baseline sourced and the significance evidenced, and revisions run until the grade lands.