A resident is discharged to an assisted living community at three on a Friday afternoon with an order for continuous oxygen. The equipment is supplied by a contracted vendor whose delivery window closes at five, the referral is faxed at four twenty, and the resident spends a weekend without the therapy that justified the discharge plan. Every previous week of NR-588 has been building toward the question this stage asks: given that hazard, what control do you place, where in the sequence do you place it, and why will it hold on a Friday when the person who designed it has gone home. Your section may print this as NR 588 or NR588; 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-588 Week 6 asks for
By this stage the paper stops describing and starts proposing, and the quality of a proposal in a systems course is decided almost entirely by two properties: the strength of the control and its position in the sequence. Strength is the familiar hierarchy. A change that removes the hazard entirely is stronger than one that makes the failure impossible to complete, which is stronger than one that reminds people, which is stronger than one that trains them, which is stronger than one that writes a policy and hopes. Most student proposals cluster at the weak end because education and policy are the interventions a nurse leader can enact alone.
Position is the property this course adds. In a single organization a control can sit anywhere. Across a boundary, a control placed on the other side of the line is a request, not a design. If your control depends on the contracted vendor changing its delivery window, you have written a wish with an implementation timeline attached. The strongest realistic proposals in this course place the control at the last point your own organization still holds the process, and use the boundary crossing itself as the trigger.
The rows in this territory usually ask for feasibility as well as effectiveness, and feasibility in cross-organization work means four concrete things: who has to agree, what it costs in labor and money, what existing process it displaces, and how long approval realistically takes. A proposal that could be enacted by the writer's own authority next Monday is often worth more than a stronger control that requires two boards and a contract amendment, and saying that trade-off out loud is the graduate move.
Expect a written proposal, plan or recommendation as the deliverable, frequently the largest single piece of writing in the session, sometimes with an implementation timeline and occasionally a posted response defending your chosen intervention against an alternative. If your section runs a discussion this week, be prepared for the classmate who says education would solve it; the answer is not that education is worthless but that it decays, and decay rates are the reason the hierarchy exists. Posts do not reopen after submission in Canvas.
One more expectation deserves naming. Every control creates new work somewhere, and the paragraph students omit is the one that says where. A required confirmation call costs three minutes per transfer and those minutes come out of a shift that is already full. Writing that cost explicitly, and saying whose shift absorbs it, is what separates a proposal from an aspiration.
The NR-588 Week 6 method, step by step
Six moves for designing a control that survives contact with two organizations.
-
Read the rubric for whether it wants a recommendation or a plan
A recommendation argues for a course of action. A plan specifies who does what by when, with resources and approvals named. Rows containing implementation, feasibility or resources are asking for the second, and an elegantly argued recommendation will lose those rows no matter how persuasive it is.
-
Place your candidate controls on the strength hierarchy explicitly
Name where each option sits and say so in the paper: elimination, forcing function, automation, reminder, education, policy. This single passage does more for the analysis rows than any amount of enthusiasm, because it shows you know your chosen intervention's limits before a grader points them out.
-
Locate the last point of unilateral control
Walk the sequence backwards from the failure until you reach the final step your own organization fully owns. That step is where a control can be placed without anyone's permission, and in cross-boundary work it is usually the most valuable real estate in the entire process.
-
Convert the control into an observable event
A control that cannot be seen cannot be audited or measured. Write it as something that leaves a trace: a field that must be completed before a record can be closed, a confirmation logged with a timestamp, a form that returns signed. If your week five measures cannot detect your week six control, one of them is wrong.
-
Price the new work and assign it
Minutes per case, multiplied by cases per month, attributed to a named role. Then say what that role stops doing to make room, or say who funds the addition. Proposals that add work to a shift with no accounting for it are the most common realism failure at this stage.
-
State the residual risk and the escalation path
Say what still fails after your control is in place, how often you expect that, who is notified when it does, and what they are empowered to do. Closing a proposal with an honest residual and a named escalation reads as experience; closing it with a hazard fully solved reads as inexperience to anybody who has implemented anything.
A layout and word budget for a cross-boundary intervention proposal
Our frame for a proposal placing a control at an organizational boundary, sized for roughly 1,400 to 1,800 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 failure and the aim | The de-identified failure in three sentences, then the change stated as a measurable aim rather than a value. | 140 to 180 |
| Options on the hierarchy | Three candidate controls placed by strength, each with what it would prevent and what it would not. | 250 to 300 |
| The chosen control and its position | The intervention described as an observable event, sited at the last point of unilateral control, with the trigger named. | 280 to 340 |
| Who must agree | Approvals, contract touchpoints and the realistic route and timeline for each, distinguished from what you can do alone. | 200 to 250 |
| Cost and displacement | Minutes per case, volume per month, the role absorbing it, and what gives way to make room. | 200 to 250 |
| Residual risk and escalation | What still fails, how it is detected, who is notified, and what that person is authorized to do. | 190 to 240 |
Evidence craft for proposal writing
Attribute the hierarchy you are using. Hierarchies of intervention effectiveness are published in the patient safety literature and by safety organizations, and naming your source with a year converts a claim about strength into a checkable one. Inventing your own tiers is the fastest way to lose an otherwise strong analysis section.
Support the mechanism, not only the intent. The claim that a structured checklist reduces omissions at a handoff is an empirical claim with literature behind it. Cite the mechanism specifically rather than citing general work on communication, because a grader reading for evidence-based practice is looking for support attached to the thing you are actually proposing.
Report expected effect honestly and in real units. If the studies you assembled in the evidence stage showed a reduction of a few transfers per hundred, say that, and do not let a relative percentage do work the absolute number cannot. A proposal that promises what the literature did not deliver is scored as an evidence failure rather than an ambition.
Distinguish what exists from what you propose, sentence by sentence. Present tense for the current process, explicit conditional language for your recommendation. In documents that may be read by a second organization, the blur between the two is not merely a style problem; it is a misrepresentation of the current state.
Keep every party and person de-identified. A contracted durable medical equipment supplier, a regional acute care hospital, an assisted living community. The rubric rewards the relationship, never the brand, and naming real entities creates exposure the assignment never required.
Five mistakes that cost points in this week's territory
- Education as the whole intervention. Staff education is a legitimate component and a weak control, and a proposal that rests on it alone concedes the effectiveness argument before it starts.
- A control placed on the other side of the boundary. If the partner has to change first, you have written a request and the feasibility rows will read it as one.
- Unpriced labor. Additional work assigned to no role, costed at no minutes, funded by nobody, will not exist ninety days after implementation.
- No trigger. A control that depends on somebody remembering to apply it has the same decay curve as the failure it replaces.
- A perfect ending. Proposals that eliminate the hazard entirely are read as inexperienced, because every implemented control in the real world leaves a residual.
Before you submit
- Candidate controls are placed explicitly on a named and cited strength hierarchy
- The chosen control sits at a step your own organization actually owns
- The control is written as an observable event with a trace and a trigger
- New work is priced in minutes, multiplied by volume and assigned to a role
- Approvals and their realistic timelines are separated from what you can do alone
- Residual risk is stated, detected by a named measure, and escalated to a named role
Writing the proposal for NR-588?
Send the rubric and the failure you are designing against. A premium original draft comes back in 24 to 48 hours with the control placed on the hierarchy, sited on your own side of the boundary and priced in real minutes, and revisions run until the grade lands.