Restraint documentation audits are a useful teaching case for this stage because the numbers almost always tell two stories at once: a compliance rate that looks like a training problem, and a workflow underneath it where the required entry lives three screens away from where the nurse is standing. NR-560 Week 2 asks you to establish the baseline, work out why the gap exists rather than assuming, and make the case that this problem deserves organizational attention. 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 2 asks for
Three tasks share this stage, and they are usually graded together. Establish the baseline, so there is a number the project can be measured against. Analyze the causes, so the intervention is aimed at a mechanism rather than at a symptom. And build the organizational case, so somebody with the authority to allocate time and money can see why this problem should move ahead of the others on their list.
Root cause work is where capstone documents most often go shallow. Students name a cause in a single clause and move on: staff education is inadequate. That conclusion is convenient because it points to an intervention everyone knows how to write. It is also wrong more often than not. Most process failures in health care are structural rather than educational, and a document that reaches for training as the cause has usually skipped the analysis rather than performed it.
Structured tools exist for this and they are worth using because they force the analysis to go deeper than instinct. Repeated why questions drive a symptom back to a mechanism. Cause and effect diagrams sort contributing factors into categories such as people, process, equipment, environment and policy, which surfaces the factors your assumptions were hiding. Whichever you use, name it, cite it, and show the output rather than merely claiming you applied it.
The organizational case is the third piece and the one nursing students are least practised at. Leadership allocates attention to problems connected to things they are accountable for: harm, regulatory exposure, length of stay, readmission, staff turnover and cost. Making that connection is not selling out the clinical argument; it is translating it into the language of the people who can approve the change.
The NR-560 Week 2 method, step by step
Six moves that produce a baseline, a cause and a case.
-
State the baseline with everything a reader needs to check it
Numerator, denominator, period, source and any exclusions. Two of these are routinely missing in student drafts, and their absence resurfaces in the evaluation stage when the post-change comparison turns out not to be measuring the same thing.
-
Describe the current process as it actually runs
Walk the workflow step by step in prose: who does what, in what order, with what tool, at what point in the shift. The gap between the policy version and the real version is usually where the problem lives, and writing both is what makes that visible.
-
Apply a named analysis tool and show its output
Take the problem through repeated why questions or sort contributing factors into categories, then report what the exercise produced. A tool named without output is decoration, and graders read it as a claim rather than as analysis.
-
Distinguish contributing factors from the one you will target
Most problems have five or six contributors and one that an eight-week project could realistically move. Say which you are targeting and why the others are outside scope. That single paragraph prevents an implementation plan that tries to fix everything and lands nothing.
-
Translate the gap into the organization's own units
Extra minutes per shift, additional days of stay, avoidable events per year, or staff hours consumed by rework. Where you estimate, show the arithmetic and label it as an estimate. A transparent estimate is persuasive; a confident unexplained figure is not.
-
Name the stakeholders and what each stands to gain or lose
Frontline nurses, unit leadership, the departments touched by the process, and whoever owns the metric. A stakeholder analysis that only lists supporters has not been done, because the people who will find the change inconvenient are the ones the plan has to answer.
A layout and word budget for a needs assessment
Our frame for this stage, sized for roughly 1,200 to 1,500 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 |
|---|---|---|
| Baseline stated fully | Numerator, denominator, period, source, exclusions, and the comparison the number is judged against. | 160 to 200 |
| The process as it runs | The real workflow step by step, set beside the policy version, with the divergence made explicit. | 230 to 280 |
| Cause analysis | The named tool, the categories it produced, and the contributing factors it surfaced in each. | 250 to 300 |
| The targeted cause | Which factor the project will address, why it is the movable one, and what is deliberately excluded. | 170 to 210 |
| Organizational impact | The gap expressed in time, events or cost, with the arithmetic shown and estimates labelled. | 200 to 250 |
| Stakeholders | Each group with its interest, its likely position, and what the project asks of it. | 200 to 250 |
Evidence craft for a needs assessment
Show the arithmetic behind every derived number. If avoidable events cost a defined amount each and the unit sees a stated number per year, put both figures and the multiplication in the sentence. A number whose derivation is invisible reads as invented, and in a capstone that suspicion spreads to the rest of the document.
Cite unit cost figures rather than estimating them. Published work reports the cost of specific adverse events and process failures. Use those figures with attribution and a year, note that they vary by setting, and never present a national average as your organization's actual cost.
Cite the analysis tool you used. Improvement methods have origins and published descriptions. Naming the tool with a source turns a diagram into a method, and it is a cheap point that most students leave on the table.
Keep process description aggregate and unattributable. Describing a workflow is fine. Describing an individual's behaviour, however anonymously, is not, and a colleague identifiable to anyone who works nearby is identifiable for the purposes that matter.
Support cause claims with literature as well as observation. If you argue that the documentation step is skipped because of where it sits in the workflow, published work on documentation burden and workflow design supports that claim. Observation plus evidence is a stronger paragraph than either alone.
Five mistakes that cost points in this week's territory
- Education named as the root cause by default. It is the conclusion students reach when the analysis was skipped, and experienced faculty recognize it instantly.
- A baseline with no source. An unattributed number cannot be checked and cannot anchor an evaluation eight weeks later.
- An analysis tool claimed but not shown. Saying a cause and effect analysis was performed without reporting what it produced is an assertion, not a method.
- A stakeholder list of allies only. The groups who will resist are the ones the implementation plan needs to answer, and omitting them hides the real problem.
- Cost figures with no derivation. A dollar amount with no arithmetic behind it undermines every other number in the document.
Before you submit
- The baseline carries numerator, denominator, period and source
- The real workflow is described and set beside the policy version
- A named, cited analysis tool is applied and its output reported
- One targeted cause is identified with the others explicitly out of scope
- Impact figures show their arithmetic and label their estimates
- The stakeholder analysis includes groups likely to resist
- No individual is identifiable from any process description
Building the NR-560 needs assessment?
Send the rubric and your problem statement out of Canvas. A premium original draft comes back in 24 to 48 hours with the baseline fully sourced, a real cause analysis rather than a training assumption, and revisions run until the grade lands.