Near the end of a skills session the course usually turns to the skill that carries all the others: communication. Documentation principles, structured handoff in the SBAR shape, and the phone report to a provider are psychomotor skills of the mouth and keyboard, practiced like any other. Written work here asks you to produce and critique structured communication and to explain why the structure exists. Your section may print this as NR 224 or NR224; 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-224 Week 7 asks for
What does a nurse at a mobile health van actually say when she calls a clinic provider about a client whose leg looks worse than yesterday? She has perhaps forty-five seconds of the provider's attention, no shared chart on the van's spotty connection, and a decision she needs made. The call that works has a shape: who is calling about whom and the one-sentence situation; the background that earns its place; the assessment, meaning what she thinks is going on; the recommendation, meaning what she is asking for. That shape is SBAR, and this week's written work asks you to build such communications, take them apart, and explain why unstructured versions fail exactly when stakes are highest.
Documentation is the other half of the week, and it is graded as a writing discipline: objective language, observable findings, completeness, timeliness, and the legal reality that the record is the version of events that outlives everyone's memory. Sections typically assign a documentation-principles piece, a practice SBAR built from a scenario, a critique of a flawed handoff, or a discussion comparing what belongs in a chart versus what belongs in a report. All of these are pure writing tasks, which makes this the week where strong writers quietly pull ahead.
The boundary here has a specific edge worth naming. Real charting, in a real record about a real patient, is legally your act and no one else's; nobody may draft it, edit it, or reconstruct it for you, ever. Classroom exercises are different: a practice SBAR from an invented scenario, an essay on documentation principles, a critique of a sample note. Those are coursework, and coursework support is legitimate. Keep the two categories separated by a wall, because after licensure the wall is what protects you.
The NR-224 Week 7 method, step by step
Six moves for building structured communication that scores.
-
Check whether the rubric grades the product, the critique, or both
Some sections want a polished SBAR; others want you to explain why each element matters; many want both in one submission. The split determines whether your words go into the artifact or into the reasoning around it.
-
Write the situation sentence to survive interruption
Assume the listener may hear only your first sentence. Name yourself, the patient, and the concern in one breath. If that sentence alone would make the provider ask the right next question, the SBAR is already half built.
-
Ration the background ruthlessly
Background is where practice SBARs bloat. Include only history that changes what the listener should do next; everything else is chart material. Writing the cut is the graded skill, because beginners cut nothing.
-
Commit to an assessment within your scope
A beginning student's assessment is not a diagnosis; it is a stated concern with the findings behind it. I am concerned this wound is deteriorating, based on these three changes, is exactly the level rubrics want.
-
Make the recommendation a request the listener can grant
Come see the patient, give me an order for, tell me your threshold for calling again. Vague closings like just wanted to let you know are the single most-marked flaw in student SBAR work.
-
Apply the objectivity test to every documentation sentence
Could two observers agree it happened as written? Patient rude fails; patient stated, followed by the quote, passes. Run the test line by line and the objectivity row takes care of itself.
A layout and word budget for an SBAR-and-principles piece
How do artifact and analysis share one submission? This frame sizes the combined piece at roughly 650 to 850 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 |
|---|---|---|
| Why structure exists | The opening claim: critical information fails in transmission, and structure is the fix, sourced. | 90 to 120 |
| The SBAR artifact itself | The four elements written out for your scenario, tight enough to read aloud in under a minute. | 150 to 190 |
| Element-by-element rationale | What each part accomplishes and what its absence costs, argued with one concrete failure example. | 160 to 200 |
| Documentation principles | Objectivity, completeness, timeliness and the record's legal weight, each in a sentence or two. | 120 to 150 |
| Chart versus report | What belongs in the permanent record versus the verbal handoff, and why the two diverge. | 90 to 120 |
| Close on the receiving end | What it is like to be the nurse who inherits a bad handoff, and the habit that prevents it. | 50 to 70 |
Evidence craft for communication writing
Structured communication has a literature; touch it. Handoff frameworks and documentation standards are described in your fundamentals text and in published patient safety material. One named, dated source under your why-structure-exists claim anchors the whole piece.
Quote your own artifact when you analyze it. The strongest rationale sections point at their own SBAR: this situation sentence names the concern in eleven words, and here is what the listener can do with it. Self-reference turns two separate answers into one argued piece.
Show, do not describe, the objectivity standard. Give a failing sentence and its passing revision side by side: patient uncooperative, versus patient declined morning medications and stated the reason. Paired examples are worth more than a paragraph of definition, and they prove you can do the thing.
Keep invented scenarios visibly invented. Build your practice SBAR from the assignment's scenario or a clearly hypothetical clinic case, never from a real patient with details you half-remember. In communication writing the integrity of the example is part of the evidence.
Five mistakes that cost points in this week's territory
- Novel-length background. An SBAR that buries the request under history recreates the exact failure the tool exists to prevent, and graders mark the irony.
- No recommendation. Ending a report without asking for something specific leaves the listener to guess why you called, and it is the most common student flaw by a wide margin.
- Judgment words in documentation examples. Rude, difficult, non-compliant: each one fails the two-observer test and hands back the objectivity points.
- Structure recited, never used. Defining the four letters without producing a working example answers a knowledge question when the rubric asked for a skill.
- Treating this as the easy week. Because there is no manikin, students coast, but communication rows are graded as exactingly as sterile technique, and the writing shows every shortcut.
Before you submit
- The situation sentence identifies caller, patient and concern in one breath
- Background contains only what changes the listener's next move
- The assessment states a concern with findings, inside a student's scope
- The recommendation is a grantable request
- Documentation examples pass the two-observer objectivity test
- Every reference appears in the text and every in-text citation appears in the list
Building the SBAR piece for NR-224?
Send the scenario and the rubric out of Canvas. A premium original draft comes back in 24 to 48 hours with the artifact tight and the rationale argued, and revisions run until the grade lands.