NR-709B Week 8 The Discussion Assembled: How to Write It

What NR-709B Week 8 asks for

A cardiac catheterization laboratory holding area finishes a project on post-procedure access site assessment with six documents written over eight weeks. Read separately, each is sound. Read in sequence, the baseline appears twice with two different denominators, the limitations section concedes a measurement problem the conclusion then ignores, and the final paragraph recommends system-wide adoption of a change tested on one shift pattern. None of those errors is about content. All of them are about assembly, and assembly is what this stage grades.

There are two pieces of new writing. The first is implications: what your local finding means for practice at your site, for the wider organization, and for others considering the same change, written at three different altitudes and with different degrees of confidence at each. The second is the conclusion, which is not a summary. A conclusion states what the project established, what it did not, and what should happen next, in that order, and it is usually the shortest and most heavily revised passage in the document.

Most sections then require a reflection. The distinction that matters is between narrating a journey and analyzing a practice. A reflection that lists what you did is a diary. A reflection that identifies a decision you would make differently, explains the reasoning that led to the original choice, and names what you now know about leading change in a system is doctoral writing. Attach it to your program's competency framework if your section works that way, and attach each claim to something you can point at.

Assembly week also has a scheduling reality worth naming. A 192-hour block ends with the site still operating the change, which means late events can contradict a document written in week six: an owner changes role, a policy submission is deferred, a measure moves again. Decide early in this stage what your document's cutoff date is, state it in the text, and report anything after it as a note rather than rewriting your analysis around it. A dated cutoff is standard scholarly practice and it protects you from an endless revision loop in the final days of the session.

The boundary, one final time, because it holds to the last page. Practicum hours, hour logs, encounter counts, preceptor and mentor evaluations, site paperwork and every signature on them are your own record of your own work, never drafted, reconstructed, estimated or edited toward approval with anyone's help. What is supportable is the written layer: assembly, argument, continuity, register and the analytic quality of a reflection about work you genuinely performed. De-identification is applied as you write, not afterwards.

The NR-709B Week 8 method, step by step

Six moves for assembling a discussion that holds together.

1. Run a figures audit across every document

   Search each number in your final document and in any appendix, poster or summary, and confirm the value, denominator and window match the frozen file. Fix the file if it was wrong, then fix everything downstream from it.

2. Trace each conclusion back to its evidence

   Take every sentence in the conclusion and find the paragraph that earned it. Any sentence without a parent gets removed or demoted into a recommendation for future work.

3. Write implications at three altitudes

   The unit, the organization, and readers elsewhere. Confidence should decline as the altitude rises, and saying so explicitly is more persuasive than claiming the same strength at every level.

4. Check that the limitations govern the conclusion

   If you conceded a measurement problem in the limitations, the conclusion cannot speak as though it did not exist. This inconsistency is the most commonly flagged fault in final documents.

5. Write the reflection around two or three decisions

   Choose actual decision points, state the reasoning at the time, say what you know now, and name what you would do differently. Chronology is not reflection; judgment examined is.

6. Read the whole document aloud in one sitting

   Register drift, repeated paragraphs and the seams between separately written sections are all audible and mostly invisible on screen. Budget two hours; it is the highest yield hours in the block.

A layout and word budget for the closing movement

Our frame for implications, conclusion and reflection, sized for roughly 1,200 to 1,500 words. It is our own outline rather than anything the university issues, and your week's rubric outranks it wherever the two disagree.

Evidence craft for the closing sections

Recommendations name an actor. The unit council should add the measure to its quarterly review is actionable. It is recommended that monitoring continue is not, and passive recommendations are the most common weakness in otherwise strong final documents.

Confidence language should vary deliberately. Your unit-level implication can be stated firmly, your organizational implication with conditions, and your external implication as a possibility. Uniform confidence across three altitudes tells a reader you have not thought about transferability.

Reflection still cites. Claims about leadership, change management or your own competency development belong to literatures, and a reflection that connects a personal decision to a named framework with a year is doing scholarly work rather than journaling.

Keep the conclusion free of anything new. A source, a figure or an idea appearing for the first time in the conclusion signals a document assembled rather than argued, and reviewers read it as a sign that the structure was never checked.

Keep the practice-doctorate frame in the closing language. The conclusion is where research vocabulary creeps back in, usually as findings, subjects or a call for further study. What you have is a local evaluation of a translated change, and the closing sentences should say so: what was implemented, what was observed, what should now happen at this site and under what conditions elsewhere. Precision about the nature of the work is graded in the final paragraphs as much as anywhere in the document.

Check the reference list against the text in both directions. Every citation in the text present in the list, every entry in the list cited somewhere. Eight weeks of drafting and section deletions guarantees drift, and this pass takes twenty minutes.

Five mistakes that cost points in this week's territory

• A conclusion that is a summary. Restating the document wastes the one passage where you say what it all means.
• Recommendations without owners. Nobody is accountable for a sentence in the passive voice.
• Conclusions that outrun the limitations you wrote. The two sections have to be able to sit in the same document.
• A reflection that narrates. Then I met with the manager, then I built the tool is a timeline, and timelines are not analysis.
• Inconsistent figures across documents. One number appearing two ways undermines every other number you reported.

Before you submit

• Every figure matches across the main document and all appendices and summaries
• Each conclusion sentence traces to a paragraph that earned it
• Implications appear at three altitudes with confidence declining as altitude rises
• Recommendations name the role responsible for each action
• The reflection examines decisions rather than reporting chronology
• No hours, logs, evaluations or site paperwork are drafted, reconstructed or estimated anywhere

Questions students ask about this stage

Keep going