NR-702C · Week 8 of 8 · Assembling the plan and briefing the executive reader

NR-702C Week 8 The Assembled Plan: How to Write It

The short answer

The closing stage of NR-702C assembles eight weeks of sections into one document that has to survive being read straight through by someone who was not there. Two products usually matter: the full plan, internally consistent from problem to measurement, and a short brief written for an executive reader who will decide in five minutes whether this project gets support. A reflective written component on the practicum stage frequently sits alongside them. The hours themselves, the log, site paperwork and any evaluation completed about you are your own record and are never drafted, reconstructed or estimated with help. Your section may print this as NR 702C or NR702C; 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.

NR 702C Week 8 grading scale at Chamberlain, the criterion levels this assessment is scored on, from Chamberlain Tutors
How Chamberlain grades NR 702C Week 8, visualized by Chamberlain Tutors.

What NR-702C Week 8 asks for

Assembled documents fail in a specific way. Each section was written well in the week it was assigned, and together they contradict each other: the aim promises a target the timeline cannot evaluate, the intervention chosen in week three does not act on the cause argued in week two, the measurement plan counts a population the scope excluded. Nobody reads a plan the way it was written, and the closing stage exists to make the whole thing agree with itself.

The executive brief is a different skill and is graded as one. Practice audiences read for decision, not for scholarship: the problem with a number, what you propose, what it will cost in time and disruption, what will be measured, what you need from them, and by when. Two pages at most. Doctoral programs teach this because the practice doctorate is defined by producing scholarly work aimed at practice audiences, and a project that cannot be briefed will not be adopted regardless of how well it was researched.

Sustainability belongs in this stage too. A project that improves a measure while you are standing on the unit and reverts three months after you leave has not changed practice. Written sustainability means naming what makes the change survive: a permanent owner, an embedded prompt or standard work document, inclusion in an existing audit cycle, a place on a dashboard someone already reviews, and orientation content for staff who arrive later.

Where a reflective component is assigned, the register is analytic rather than narrative. A doctoral reflection examines decisions: what you judged, what you got wrong, what the organization taught you about how change actually moves, and what you would do differently at the next stage. It does not recount the term chronologically and it does not describe encounters, hours or clinical activity.

What this manual does not touch

The practicum layer stays entirely with you. Hours, the log, encounter counts, site documentation, signatures and evaluations completed by a preceptor, mentor or faculty member are never drafted, reconstructed or estimated with assistance, and no reflective writing here reconstructs clinical activity. The manual teaches assembly, consistency, executive translation and reflective register.

Reflective writing is where de-identification slips most easily, because the material is personal and the details feel harmless. They are not. Write about decisions, structures and roles. Do not write about a patient, a date, a room or anything that would let a reader recognize an individual, and keep the analysis at the level where doctoral reflection actually operates: the system, not the case.

The NR-702C Week 8 method, step by step

Six moves for assembling a plan that holds together.

  1. Run the consistency pass with a single-column table

    Problem, cause, intervention, mechanism, aim, measure, timeline. Write each in one line and read the column. Any break in the chain is visible in seconds and invisible in prose.

  2. Reconcile every number that appears more than once

    Baselines, targets, denominators, dates and volumes drift across eight weeks of drafting. Search the document for each figure and make the versions agree, or explain the difference where it is intentional.

  3. Rebuild the transitions between sections written weeks apart

    Each section should open by taking the handoff from the one before. Without that, an assembled plan reads as a folder rather than as a document, and readers feel the seams even when they cannot name them.

  4. Write the brief from the decision backwards

    Start with what you are asking the reader to approve, then supply only what is needed to make that decision. Everything that does not serve the ask belongs in the full plan, not the brief.

  5. Give sustainability an owner and a mechanism

    A named role, a document or system change that persists, and an existing review cycle the measure joins. Sustainability sections without those three are statements of hope.

  6. Write the reflection as decisions, not as a diary

    Three or four judgment calls, what you decided, what you learned about how the organization behaves, and what changes in your approach for the next stage. Analysis, in the past tense, at systems altitude.

A layout and word budget for the closing stage

Our frame for the assembly, brief and reflective components, sized for roughly 1,800 to 2,200 words across the closing pieces excluding the full plan itself. It is our own outline rather than anything the university issues, and your week's rubric outranks it wherever the two disagree.

SectionWhat belongs in itWord target
Plan abstractProblem, aim, intervention, measurement and timeline compressed into one dense paragraph that stands alone.200 to 250
Executive brief: the askWhat you want approved, from whom, by when, stated in the first three sentences without preamble.120 to 160
Executive brief: the caseThe problem with its number, the proposed change, the resource and disruption cost, and what will be measured.300 to 360
Sustainability planOwner, embedded mechanism, review cycle, orientation content, and what would signal the change is decaying.280 to 340
Consistency and revision noteWhat changed during the term and why, written as decisions with reasons rather than as silent edits.180 to 220
Reflective analysisThree or four judgment calls examined, with what the organization taught you and what you will do differently.400 to 480
Handoff to the next stageWhat is complete, what is pending, what the next stage inherits, and the condition that lets it begin.160 to 200

Evidence craft for the closing stage

Keep citations in the plan and out of the brief. An executive brief carries at most one or two anchors, and only where they carry weight with that reader. Scholarly apparatus in a decision document signals that the audience was not considered.

Make the abstract a compression, not a preview. It should contain the aim's number, the intervention named, and the measurement approach. Anything that could introduce any project on any topic is filler in the highest-value paragraph you will write.

Cite sustainability thinking rather than asserting it. There is published work on why improvements decay and what preserves them. Two sources used properly turn a hopeful paragraph into an argued one.

Reflect with evidence too. A doctoral reflection that connects a personal judgment to a leadership or implementation concept reads at a different altitude from one that reports feelings, and the concept does not need to be elaborate to do that work.

Do not claim outcomes a planning stage cannot have. This term produced a plan. Writing as though the change has already succeeded is the most damaging overreach available in a closing document, and it is easy to do accidentally in a hopeful conclusion.

Five mistakes that cost points in this week's territory

  • Sections stapled rather than assembled. No transitions, competing terminology for the same measure, and three versions of the baseline in one document.
  • A brief that is a shortened plan. Compression is not translation. An executive brief is organized around a decision, not around your table of contents.
  • Sustainability with no owner. If the plan does not name the role that keeps the change alive, the honest reading is that it ends when you do.
  • A reflection that narrates the term. Chronology is not analysis, and a reflection that recounts activity drifts toward describing clinical work that does not belong in the paper.
  • A conclusion that promises results. A planning stage cannot report improvement, and claiming momentum you have not measured undercuts the whole document.

Before you submit

  • The chain from problem to cause to intervention to aim to measure holds in one line each
  • Every repeated number agrees across the whole document
  • Sections open by taking the handoff from the section before
  • The brief opens with the ask and stays inside two pages
  • Sustainability names an owner, a mechanism and a review cycle
  • The reflection analyzes decisions and contains no clinical or hour detail
  • No sentence claims a result this stage could not have produced

Assembling the NR-702C plan this week?

Send the rubric and your section drafts out of Canvas. A premium original draft comes back in 24 to 48 hours with the plan reconciled end to end, the executive brief written for a decision maker and the reflection kept analytic, and revisions run until the grade lands. Hours, logs and evaluations stay entirely yours.

Questions students ask about this stage

How do I write an executive brief when I have been trained to write academically?
Change the organizing principle rather than the vocabulary. Academic writing builds toward a conclusion; a brief starts with it. Open with the decision you want, then give the problem with its number, the proposed change in plain operational terms, what it asks of staff and systems, what will be measured and when the reader will see results. Cut background that does not change the decision, cut hedging that a decision maker cannot act on, and cut citations except where a source is the reason the reader should believe you. Keep sentences short and use headings a person can scan. The test is simple: hand it to someone outside your specialty and ask what you are asking for. If they cannot say in one sentence, the brief has not done its job yet.
What belongs in a doctoral reflection that would not belong in an undergraduate one?
Altitude and accountability. An undergraduate reflection often reports what an experience felt like and what was learned personally. A doctoral reflection examines judgment: the decisions you made, the information you had when you made them, what the organization's response revealed about how change actually moves there, and what you would do differently with the same information. It connects at least one of those to a named leadership or implementation concept, and it is willing to record a misjudgment plainly, because the ability to analyze your own error is a leadership capability rather than a confession. What it does not do is narrate the term, describe clinical encounters, or account for hours. Those belong to the log and to the record your school verifies, and they are yours alone.
My plan changed a lot since week one. Should the final document show that?
Show it, briefly and deliberately. A short revision note that says what changed, when, and on what basis is a strength: it demonstrates that the plan responded to evidence, data and organizational reality rather than being written once and defended blindly. Keep it to decisions with reasons, and keep the tone matter-of-fact. What you should not do is leave two incompatible versions of an idea in the same document, which is what happens when a section is revised and its dependents are not. Run the consistency pass first, then write the note. If a committee later asks why the aim differs from an earlier draft, you want a documented decision to point at rather than a reconstruction attempted from memory under pressure.
How much of the sustainability plan is realistic for a project I may hand off?
More than students expect, because sustainability is mostly structural rather than personal. The mechanisms that survive a handoff are the ones embedded in things that persist: a documentation prompt built into the workflow, a standard work document owned by the unit's practice council, a measure added to a dashboard someone already reviews monthly, and orientation content that reaches new staff without anyone remembering to arrange it. Personal mechanisms, meaning champions who are enthusiastic and reminders you send, decay quickly. Write the structural ones first, name the role that inherits each, and add one paragraph on what decay would look like in the data so the owner knows what to watch for. That paragraph is often the difference between a plan a unit adopts and one it files.

Keep going

Online now