By the seventh stage of NR-703 the diagnosis is built and the recommendation has to be paid for. This is where doctoral organizational writing separates from academic commentary: a recommendation with no cost, no owner and no return is a suggestion, and executives do not act on suggestions. The written task is a case that states what is proposed, what it costs in dollars and in hours, what it is expected to return and over what horizon, what the assumptions are, and what happens if the assumptions are wrong. Your section may print this as NR 703 or NR703; 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-703 Week 7 asks for
A proposal to add a dedicated resource nurse to the night shift on two medical units costs roughly the premium hours it consumes, and it is argued for on the grounds that it will reduce delayed escalations and unplanned transfers to a higher level of care. Whether it is approved depends almost entirely on whether the proposal states the annual cost, the number of transfers it expects to avoid, the value of an avoided transfer in that organization's own terms, and the assumptions holding those numbers together. A nurse leader who brings the clinical argument alone will lose to a service line that brought arithmetic.
Three categories of value carry most nursing recommendations and they are not interchangeable. Avoided cost is the strongest and most common: harm events not occurring, days not consumed, overtime not incurred, turnover not replaced. Revenue effects appear where throughput or capacity changes. Risk reduction covers regulatory and reputational exposure and is real but harder to quantify, so it belongs as a supporting argument rather than as the headline. Choose the category your recommendation actually acts on and build the case there.
Assumptions are the part that separates a credible case from an optimistic one. Every projection rests on a chain: this many eligible episodes, this proportion affected, this size of effect, this value per event. Write the chain visibly, one line per link, and state the source of each figure. A reader who can see your arithmetic can argue with one number instead of dismissing the whole case.
Sensitivity is the doctoral finishing move. Show what happens to the case if the effect size is half what you assumed, or if the cost runs a quarter higher. A recommendation that still holds under a pessimistic assumption is far more persuasive than one that only works at its best estimate, and executives read specifically for that.
The NR-703 Week 7 method, step by step
Six moves for building a case an executive could act on.
-
State the recommendation as a decision, in one sentence
What is being approved, by whom, at what cost, starting when. If the reader has to hunt for the ask, the document has already failed at its main job.
-
Cost the inputs completely, including the invisible ones
Salary and premium hours, backfill for training time, technology or build effort, supplies, and the ongoing cost of maintaining the change after the launch. Implementation costs that appear only in year one should be labeled as such.
-
Build the benefit chain one line at a time
Eligible volume, proportion affected, effect size from the literature, and value per event from your organization's own figures where possible. Each line gets a source.
-
Use your own organization's unit values where they exist
Finance and quality departments hold internal figures for what a day, a transfer, a turnover or an event costs, and internal numbers are far more persuasive than published national averages a reader can dispute.
-
Run the case at three assumptions
Conservative, expected and optimistic, changing only the effect size and the cost. Presenting the conservative case first is a credibility move that experienced readers notice.
-
Name the owner, the horizon and the review point
Who is accountable, when the return is expected to appear, and the date at which the organization should look and decide whether to continue. Cases without a review point rarely get approved twice.
A layout and word budget for a costed recommendation
Our frame for this paper, sized for roughly 1,800 to 2,200 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 ask | The decision requested, the approver, the cost and the start date, in the first three sentences. | 110 to 150 |
| Problem restated in value terms | The diagnosed problem expressed in what it currently costs the organization, with the arithmetic shown. | 250 to 300 |
| The proposed change | What will be different operationally, described so a reader outside nursing understands what is being bought. | 230 to 280 |
| Cost of inputs | Every input priced, separated into one-time and recurring, with the source of each figure. | 280 to 330 |
| Benefit chain | Volume, proportion, effect size and unit value, one line each, each with an attribution. | 300 to 360 |
| Sensitivity | The case at conservative, expected and optimistic assumptions, and the point at which it stops working. | 250 to 300 |
| Owner, horizon and risks | Accountable role, when the return should appear, the two largest risks and what would signal them early. | 230 to 280 |
Evidence craft for the business case
Prefer internal unit costs to published averages. An internal figure survives challenge in the room; a national average invites the observation that your organization is different, which is usually true.
Attribute effect sizes to specific studies with their settings. Borrowing an effect from a study in a different care model without noting the difference is the most common arithmetic weakness in these papers.
Separate hard from soft benefits visibly. Avoided cost that appears in a budget line is different from improved satisfaction that may appear later in retention. Put them in different columns and do not add them together.
Show the arithmetic rather than the conclusion. A single sentence stating an annual return with no chain behind it is not usable by anyone. Four lines of visible calculation invite a reader to engage with a number rather than reject a claim.
Be explicit about what you cannot quantify. Some real benefits resist costing, and saying so plainly preserves credibility far better than converting them into an estimate you cannot defend.
Five mistakes that cost points in this week's territory
- A recommendation with no price. If the paper never says what it costs, no reader can act on it and the recommendation row cannot be scored well.
- Benefits with no chain. An annual saving figure with no volume, proportion or effect size behind it is a number nobody can check.
- Only the optimistic case. A case presented at its best assumption reads as advocacy and is the first thing an experienced reader tests.
- National averages used as local values. Published cost figures describe other organizations, and a reader who knows the internal number will say so.
- No owner. A proposal that nobody is named to run is a proposal that will not be approved and would not survive if it were.
Before you submit
- The ask, the approver, the cost and the start date appear at the top
- Costs are separated into one-time and recurring with sources
- The benefit chain shows volume, proportion, effect size and unit value
- Internal organizational values are used wherever they were obtainable
- The case is presented at three assumption levels
- Hard and soft benefits are kept in separate columns
- An accountable owner, a horizon and a review point are named
Costing the NR-703 recommendation?
Send the rubric and your diagnosis out of Canvas. A premium original draft comes back in 24 to 48 hours with the ask stated first, the benefit chain built line by line and the case tested at conservative assumptions, and revisions run until the grade lands.