The bridge sequence tends to end by cashing in everything it taught: a modest, evidence-supported practice change proposal, where the question you built, the sources you appraised and the synthesis you wrote converge on one feasible improvement, argued on paper for a real setting. It is a capstone in miniature, graded on coherence across its parts. Your section may print this as NR 300B or NR300B; 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.
Scope what a closing proposal must deliver
Think of the parent at a family practice checkout window, holding a prescription and a memory of dosing instructions already going soft at the edges. A nurse who has watched that scene for years, and who has just spent seven weeks learning to question, search, appraise and synthesize, now gets asked to connect the two: propose one change, weight-based dosing cards handed out and talked through at every relevant visit, perhaps, argued from evidence and costed against the clinic's real constraints. The closing assignment is that connection, formalized.
What distinguishes a proposal from a complaint with citations is its anatomy, and rubrics in this territory score the anatomy piece by piece. A defined problem with local evidence that it exists, even informal counts. A specific proposed change, small enough to survive contact with an actual workweek. An evidence base carried over from your synthesis, cited at the moments it justifies choices. An implementation sketch naming who does what, when, with what training and materials. A measurement plan that says what number or observation would indicate success, over what window. And a feasibility reckoning: costs in time and money, the likeliest objection, and your answer to it. Each element can be brief; none can be missing, because the elements are the assignment.
Hold the scale honest. This is an undergraduate proposal, a paper arguing for a change, not a mandate to implement one, and nothing in it obligates your workplace. Write it as if a receptive manager might read it, because that imagined reader enforces exactly the concreteness and courtesy the rubric wants.
Propose the change, step by step
Six moves that assemble seven weeks of skills into one document.
-
Choose a change sized like a habit, not a program
One workflow, one artifact, one added step: dosing cards at checkout, a callback script, a standard teaching moment. If your proposal needs a committee, a budget line and a quarter to launch, shrink it until one team could try it in a month.
-
Evidence the problem locally before citing globally
A sentence of honest local texture, how often the confusion call comes, what the front desk sees, grounds the problem. Keep it observational and de-identified; rough patterns you have genuinely noticed, presented as exactly that.
-
Carry your synthesis forward, not your bibliography
The proposal cites evidence at decision points: why this intervention, why this population, why this measure. Two or three sources doing real work beat a re-summarized literature review; the synthesis already happened, and this paper spends it.
-
Sketch implementation as a week, not a vision
Who prepares the materials, who gets a ten-minute huddle briefing, when the change starts, and who answers questions in week one. Concrete verbs and named roles, no proper names, are what make the sketch credible.
-
Define success as something countable, twice
One process measure, are we actually doing the new thing, and one outcome signal, did the confusion calls drop. Say how each would be counted without new infrastructure, because a measurement plan that requires a data analyst has left the clinic it was written for.
-
Pre-argue the strongest objection
Time is the usual one: the checkout conversation adds a minute nobody has. Name it, cost it honestly, and answer it, with the change trimmed, the moment moved, or the trade justified. A proposal that has already heard its critics reads as ready.
Sketch the proposal and its word budget
Our frame for a practice change proposal, sized for roughly 900 to 1,150 words. It is our own outline rather than anything the university issues, and your week's rubric outranks it wherever they disagree.
| Section | What belongs in it | Word target |
|---|---|---|
| Problem with local texture | The recurring failure, evidenced by de-identified observation and framed as a pattern, not an anecdote. | 130 to 170 |
| The change, specified | Exactly what would be done differently, by whom, at which moment in the visit flow. | 120 to 160 |
| Evidence at the joints | Sources cited where they justify choices: the intervention, the population, the expected effect, with calibrated verbs. | 180 to 230 |
| Implementation week | Materials, briefing, start date logic, first-week ownership, in concrete verbs and named roles. | 140 to 180 |
| Measurement plan | One process measure and one outcome signal, each with its counting method and window. | 120 to 150 |
| Feasibility and objection | Time and material costs stated plainly, the strongest objection named, and your answer to it. | 130 to 170 |
Support a proposal without overpromising
Promise what your synthesis found, at the size it found it. If the literature showed modest improvements in comprehension with written-plus-verbal instruction, your proposal predicts modest improvement, cited. Inflating the expected effect to sell the change is the closing assignment's version of the causal-verb error, and it is graded as such.
Cite at decision points, not in a wall. The evidence paragraph is not a second literature review; it is justification placed exactly where a skeptical reader would ask why. Each citation should sit beside the choice it defends.
Label local observations as local. Your clinic patterns are legitimate motivating evidence when presented honestly: roughly, often, in my observation. The moment informal counts dress up as data, the proposal's credibility inverts.
Keep the measurement plan inside existing tools. Counts from the phone log, a tally sheet at checkout, a question added to the huddle: measures a clinic already can take. Cite a source for your outcome measure if one exists, and resist inventing instruments this paper cannot validate.
Avoid the five mistakes of this week's territory
- The program disguised as a change. Proposals needing committees, budgets and quarters read as fantasy at this scale; the graded skill is feasible specificity.
- The re-run literature review. Spending half the paper re-summarizing sources spends words the implementation and measurement sections needed, and those are the sections that distinguish this assignment.
- Success undefined. A proposal with no countable indicator cannot fail, and a change that cannot fail is not a proposal; it is a hope.
- The unheard objection. Ignoring the obvious time cost tells the reader you have not imagined the change inside a real Tuesday, which undoes every other paragraph.
- Workplace specifics that identify. Real colleague names, identifiable practice details or anything resembling internal documentation do not belong in coursework; roles and patterns carry the proposal fine.
Run this list before you submit
- The change is small enough for one team to try in a month
- Local texture is labeled observational and fully de-identified
- Every citation sits beside the decision it justifies
- Implementation names roles, materials, timing and first-week ownership
- One process measure and one outcome signal are countable with existing tools
- The strongest objection is named, costed and answered
Closing NR-300B with the proposal?
Send the prompt and the rubric out of Canvas. A premium original draft comes back in 24 to 48 hours with the change specified, evidenced and costed like a document a manager could act on, and revisions run until the grade lands.