NR-581 Week 7 Advocacy and Interprofessional Voice: How to Write It

What NR-581 Week 7 asks for

Advocacy stages read differently from every stage before them. Weeks one through six were addressed to a grader who wanted your reasoning displayed. An advocacy piece is addressed to somebody who can act, and the writing has to behave accordingly: shorter sentences, a request stated early, evidence selected for the decision rather than for completeness. Students who carry the analytic register of the theory paper straight into this stage produce something accurate that nobody could act on, and the rubric row for audience awareness reads that immediately.

The word advocacy covers three different scales, and a good paper says which one it is working at. Individual advocacy is speaking for one patient inside a system that is not hearing them: the sedated postoperative patient whose daughter has been on hold with the unit phone for two days, the transfer that keeps getting deferred. Organizational advocacy addresses a process rather than a person, arguing that a practice on a unit should change. Professional and policy advocacy argues for the role itself, or for a population, in front of an audience outside nursing. Pick one scale and hold it. A paper that starts with a patient and ends with a legislature has usually lost the argument in the middle.

The interprofessional half of this stage is where nurses tend to write vaguely. Collaboration is not an attitude; it is a set of communication behaviours with published structure behind them. Structured handoff formats, shared decision-making processes, escalation pathways, team debriefing and the recognized competencies for interprofessional practice all exist as documents you can cite. Faculty at this stage are testing whether you can name a mechanism rather than praise teamwork. A sentence saying communication between disciplines should improve earns nothing. A sentence naming which structured tool the team lacks, at which handoff point, and what a published account says it changes, earns the row.

The simulation lab is worth borrowing from here, because it is the one setting where interprofessional communication is deliberately observed. Anyone who has run a mock code with respiratory therapy and pharmacy in the room has watched the same failure that happens on the unit, only with a facilitator naming it afterward: the closed-loop confirmation that never closes, the concern raised in a hedge so soft that nobody registers it as a concern. That is usable material. A scene where you can say exactly what was said and what happened next gives your advocacy argument a foundation that a general observation about hierarchy cannot.

The NR-581 Week 7 method, step by step

Six moves for writing an advocacy piece that could actually move somebody.

1. Name the decision-maker first

   Not an abstract audience. The unit practice council, the chief nursing officer, a specific committee, a legislator's health staffer. Everything in the paper is sized to what that person controls, and a paper written to nobody in particular argues for nothing in particular.

2. Write the ask as one imperative sentence

   What you want done, by whom, at what scale. Put it inside the first paragraph. Advocacy writing that withholds its request until the conclusion has spent its most-read paragraph on background.

3. Establish the problem with a number and a scene

   The number gives it size and the scene gives it weight. Neither works alone. How often it happens, out of how many opportunities, over what period, and then one de-identified instance the reader can picture.

4. Choose evidence for the objection, not for the case

   You know your position. Spend your sources on what would be said against it: cost, workload, unit disruption, evidence quality. A paragraph that answers the strongest counterargument does more work than three that restate the problem.

5. Name the interprofessional mechanism

   Say through which structure the change happens: which committee, which handoff, which escalation pathway, which shared protocol. Cite the framework or competency set you are drawing on rather than describing collaboration in adjectives.

6. Close with the cost of doing nothing

   Advocacy fails on inertia more often than on disagreement. End with what continues if nothing changes, stated in the same units you used to size the problem, so the reader is choosing between two futures rather than between action and rest.

A layout and word budget for an advocacy piece

Our frame for an advocacy paper or brief of roughly 1,100 to 1,400 words. It is our own outline rather than anything the university issues, and your week's rubric outranks it wherever they disagree. If your section assigns a letter or a one-page brief, keep the same order and compress each block proportionally.

Evidence craft for advocacy writing

Position statements are sources, and they are dated. Professional organizations publish positions on scope, staffing, workplace safety and access. They carry real weight in an advocacy argument because they represent an organized professional judgment rather than yours alone. Name the organization and the year in the sentence, and quote the operative clause rather than paraphrasing it into something softer.

Distinguish evidence about the problem from evidence about the solution. These are two different literatures and weak papers blur them. One set of sources establishes that the gap exists and matters; another establishes that the intervention you are proposing does something about it. A grader looking for support will check whether your proposal paragraph has citations of its own, and it very often does not.

Every number carries its base and its window. Nineteen of 240 handoffs over one quarter is evidence a committee can act on. Eight percent is a figure that invites a question you did not answer. If the number came from your own unit rather than from a published source, say so plainly and say how it was counted.

Report the cost side honestly. Any proposal consumes something: hours, training time, a slot in an already full onboarding schedule. Naming the cost and then arguing it is worth paying reads as competence. Omitting it reads as advocacy that has not been thought through, and a reader whose job is resources will notice the omission before anything else.

Keep the institution unnamed and the details de-identified. Write your setting generically, alter incidental particulars, and remove anything that would let a reader identify a patient or a colleague. Advocacy writing runs on specificity, which is exactly why this stage is where identifiable detail slips in.

Five mistakes that cost points in this week's territory

• No named audience. A paper addressed to whom it may concern cannot be evaluated for audience awareness, and the row exists in almost every advocacy rubric.
• Teamwork as a virtue rather than a mechanism. Praising collaboration without naming a structure, a tool or a competency set gives the interprofessional row nothing to score.
• The ask buried in the conclusion. If a reader has to reach paragraph seven to learn what you want, the writing has not done the persuasive work the stage is testing.
• Objections handled with reassurance. Saying that staff will adapt is not an answer to a workload objection. Evidence is.
• Scale drift. Starting with one patient and ending with national policy leaves both arguments underdeveloped and neither properly supported.

Before you submit

• The decision-maker is named and their authority is described
• The ask appears as one imperative sentence in the first paragraph
• The problem carries both a number with its denominator and one concrete instance
• The proposal paragraph has citations of its own, not only the problem paragraph
• A named interprofessional structure or competency set is cited, not just praised
• The two strongest objections are stated in their strongest form and answered

Questions students ask about this stage

Keep going