Every capstone report has to end somewhere, and in an executive course it ends in a decision. The late stages of NR-632 usually ask for a recommendation with a sustainability plan behind it: sustain, expand, modify or stop, said in one sentence, defended by your own evidence, and made operable by naming who owns the process after you finish the course. A report that stops at findings has left the heaviest work undone, and this is the row where that shows most plainly. Your section may print this as NR 632 or NR632; 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-632 Week 7 asks for
What happens to a pilot the week its graduate student stops showing up? In most community clinics, exactly what you would expect. The reminder call list stops being worked because the person who worked it was you. The screening prompt stays in the huddle script for a fortnight and then quietly drops out. A late-stage capstone asks you to write against that outcome, and the writing has a name in executive practice: a handover that assigns the process to a standing role rather than to a project.
The recommendation itself has to be one sentence and it has to pick one of four things. Sustain the change as delivered. Expand it to named additional units or populations. Modify it in stated ways before it continues. Stop it, because the evidence does not support the resources it consumes. Students avoid the fourth option almost universally, which is a mistake, because a well-evidenced recommendation to stop demonstrates exactly the judgment the degree is meant to develop and is often the honest reading of a small result achieved at a large cost.
Sustainability is the second half and it is more concrete than students expect. It is not a paragraph of hopeful language about embedding a culture of improvement. It is a short set of specific answers: which existing role absorbs the task, what document or standing procedure it gets written into, what training new staff receive and when, which indicator continues to be monitored and at what interval, and who sees the number. Where those answers exist the change tends to survive. Where they do not, the change ends when your enrollment does, and any experienced reader knows it.
The third element is the risk of the recommendation itself. Recommending expansion to three more sites carries a different risk profile from recommending continuation on one, and naming that risk before your reader does is the last credibility move available in the report. A recommendation offered without its own risks reads as advocacy. A recommendation offered with them reads as counsel, and counsel is what the nurse executive role actually supplies.
Where our help stops and your practicum begins
The practicum hours in this course and everything the school or your site verifies remain yours. We do not complete hours, attend meetings, contact your mentor or your organization, or produce site documentation. Hour logs, activity and encounter records, mentor and preceptor evaluations and any signed or verified form are your own record and are never drafted, reconstructed or estimated with our help. Nor do we negotiate a handover on your behalf; the agreement about who owns the process after you leave is a real conversation you have to have with real people.
The written layer is where we work: how a recommendation is worded so it cannot be misread as a preference, how a sustainability plan is made specific enough to be actionable, how a risk paragraph is written without undermining the recommendation it accompanies, and how the whole section is sourced so a practical document remains a graduate one. The value on offer is clearer written reasoning about work you genuinely did.
De-identification carries through to the end of the report. Clients never appear in identifiable form, and the roles you name in a handover plan are roles, not people: the clinic manager, the panel coordinator, the nurse supervisor on the evening rotation. Naming an individual as the future owner of a process in a document that will be read outside your organization commits somebody who did not agree to be committed, and graders in executive courses notice the difference between assigning a role and assigning a colleague.
The NR-632 Week 7 method, step by step
Six moves for writing a recommendation somebody could actually act on.
-
Write the recommendation sentence first and build backward
One sentence naming the action, the scope and the condition: sustain the referral pathway at both east-side sites, contingent on the coordinator vacancy being filled. Everything above it in the document exists to make that sentence supportable.
-
Tie each clause of it to a specific finding
Scope comes from where the result held. Conditions come from what your variance analysis showed was fragile. If a clause has no evidence behind it, cut the clause rather than defending it with adjectives.
-
Name the decision-maker and the forum
A recommendation is addressed to somebody with authority to act, and saying which role and which committee or meeting it goes to converts a paper into a proposal. Vague addressing is why real projects stall.
-
Assign the process to a standing role, in writing
Not to a person and not to a project. Then name the document it lives in: a standing procedure, an orientation checklist, a huddle script, a job description. Ownership that is not written down is not ownership.
-
Set the monitoring interval and the trigger
Which indicator continues, at what interval, who reviews it, and at what level it prompts action. A number nobody looks at is not monitoring, and a number with no trigger is not accountability.
-
State the risks of your own recommendation and the mitigation for each
Two or three, honestly. Staffing dependency, competing priorities, a data source that may be decommissioned. Naming them makes the recommendation stronger, not weaker, because it shows you have stress-tested your own advice.
A layout and word budget for a recommendation and sustainability section
Our frame for a closing recommendation section of roughly 1,100 to 1,400 words. It is our own outline rather than anything the university issues, and your scoring guide outranks it wherever the two disagree.
| Section | What belongs in it | Word target |
|---|---|---|
| The recommendation | One sentence with the action, the scope and any condition, placed before the reasoning rather than after it. | 60 to 90 |
| Evidence behind it | The findings that support each clause, in the order the clauses appear, with the weakest one acknowledged. | 230 to 280 |
| Decision route | Who decides, in which forum, what they are being asked to approve, and by when it matters. | 120 to 160 |
| Ownership and embedding | The standing role that takes the process and the document or procedure it gets written into. | 200 to 250 |
| Monitoring plan | The continuing indicator, its interval, its reviewer and the level at which it triggers action. | 190 to 240 |
| Risks of the recommendation | Two or three specific risks with a mitigation for each, written plainly rather than defensively. | 200 to 250 |
Evidence craft for recommendation writing
Ground sustainability in a named framework. Published models of sustainment and spread exist and give your plan a vocabulary a reader can check. Cite one with its year and use its categories rather than inventing headings that mean the same thing less clearly.
Match the strength of the verb to the strength of the evidence. Recommend, suggest and propose are not interchangeable. A single-site process finding supports proposing a trial elsewhere; it does not support recommending system-wide adoption, and the mismatch is the most common overreach in closing sections.
Keep the reasoning traceable to your own results. Every clause in the recommendation should point back at a number or an observation the reader has already seen. A recommendation supported mainly by external literature is a literature review's conclusion, not a capstone's.
Write conditions as testable states. Contingent on the vacancy being filled is testable. Contingent on adequate staffing is not, and an untestable condition lets everyone agree with a recommendation nobody has to implement.
Five mistakes that cost points in this week's territory
- A recommendation buried in the last paragraph. Executive readers expect the decision near the front of the section; hiding it reads as reluctance to commit.
- Sustainability written as sentiment. Language about embedding, culture and ongoing commitment without a role, a document and an interval is decoration.
- Ownership assigned to a named individual. People leave, and committing a colleague in writing is both operationally fragile and professionally presumptuous.
- Expansion recommended from single-site evidence. The most frequent overreach in capstone reports, and the easiest for a grader to mark down.
- No stop option considered. A report that never entertained discontinuation has not evaluated anything; it has advocated.
Before you submit
- The recommendation is one sentence and appears before its justification
- Each clause traces to a specific finding in your own results
- A decision-maker and a forum are both named
- The process is assigned to a standing role and to a written document
- Monitoring has an indicator, an interval, a reviewer and a trigger level
- At least two risks of the recommendation are named with mitigations
Writing the recommendation your capstone ends on?
Send the scoring guide and your findings so far. A premium original draft comes back in 24 to 48 hours with the recommendation stated in one sentence and the sustainability plan made specific enough to act on, and revisions run until the grade lands.