The closing stage of NR-730 assembles seven weeks of parts into one design document and answers the feedback that shaped them. What is graded is coherence: whether the problem, the question, the evidence, the framework, the intervention and the measures form a single chain in which each link follows from the one before. Sections written weeks apart drift, and finding the drift is the actual work of this week. Your section may print this as NR 730 or NR730; 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-730 Week 8 asks for
Here is what drift looks like in a real document. The problem statement, written in week one, is about late escalation of deteriorating patients on a telemetry unit. The evidence synthesis, written in week five, is largely about early warning score implementation in medical-surgical wards. The intervention, specified in week six, is a structured huddle. The primary outcome, written in week seven, is time from qualifying observation to clinician response. Each section is competent. Read end to end, the document proposes a huddle on the basis of evidence about scoring systems, and nobody noticed because nobody read it in one sitting. Reading it in one sitting is the assignment.
Assembly also means handling feedback. Over an eight-week design course a navigator will have raised questions, some of which changed the project and some of which you decided not to act on. Both categories need to be visible. Changes should be present in the document rather than described. Declined suggestions deserve a sentence of reasoning somewhere appropriate, because a design that quietly ignores a raised objection invites the same objection at the next review, this time with less patience.
The third demand is completeness of the operational layer. Design documents are judged partly on whether the project could actually be run from them: a timeline with phases and dates, an identified sponsor or site contact role, an education or preparation plan for the people whose behavior changes, the route for whatever ethics or determination process your program requires, a dissemination intention, and a sustainability paragraph that says what happens after the doctoral student leaves. Sustainability is the section most often written as an afterthought and most often asked about in a review.
Expect a long deliverable, possibly the full proposal or several chapters together, and expect formatting to matter more than it did in earlier stages. Headings, tables, appendices and reference integrity all carry marks in doctoral submissions. If your section closes with a discussion, post the part of the chain you are least confident about, and write it as final copy since posts do not reopen after submission in Canvas.
The NR-730 Week 8 method, step by step
Seven moves for assembling a design document that holds together.
-
Read the rubric as an assembly checklist
Closing rubrics in project courses tend to enumerate required components. Turn every row into a line in a list and tick them physically against the document, because a missing component costs more than a weak one.
-
Print the chain on one page before editing anything
Problem, question, evidence claim, framework, intervention, primary outcome. Six lines. Any break between two adjacent lines is the first thing to fix, and it is almost always faster to fix the later section than the earlier one.
-
Reconcile every number that appears twice
Unit size, current-state figure, eligible population, timeline duration. Numbers written in week two and repeated in week seven are frequently different by then, and inconsistent figures do more damage to a reader's confidence than a weak paragraph.
-
Fold navigator feedback in rather than appending it
A change made in response to a question should look like part of the design, not like a patch. Where you declined a suggestion, put your reasoning in the section it belongs to rather than in a cover note.
-
Build the timeline as a table with owners
Phase, activity, duration, who is responsible, what has to be true before it starts. A timeline in prose reads as intention. A timeline in a table reads as a plan, and readers check it against the terms remaining in your program.
-
Write sustainability as a handoff, not as hope
Who owns the change when you leave, what stays in place structurally, what training exists for new staff, which measure keeps being collected and by whom. Structural answers outperform enthusiasm every time.
-
Do the mechanical pass last and do it properly
Reference integrity in both directions, heading levels consistent, tables numbered and referenced in the text, appendices called out, page formatting per your style guide. This is an hour of work that visibly protects a document reviewers have to navigate.
A layout and word budget for the assembled design document
Our frame for the closing assembly, sized to whatever length your section requires with these proportions. It is our own outline rather than anything the university issues, and your week's rubric outranks it wherever the two disagree.
| Component | What it has to prove at assembly | Share of the document |
|---|---|---|
| Problem and significance | That the shortfall is real here, measured, and consequential at three altitudes. | 15 to 20 percent |
| Question and scope | That the project is bounded, with criteria a stranger could apply and an out-of-scope list. | 8 to 12 percent |
| Evidence synthesis | That the specified intervention is supported and its configuration is drawn from the evidence. | 25 to 30 percent |
| Framework and design | That the rollout has a structure and that framework elements appear as project activities. | 12 to 16 percent |
| Measures and analysis | That every count is operationally defined and the analytic claim fits the design. | 15 to 20 percent |
| Operations and sustainability | That timeline, owners, preparation, determination route and handoff are all specified. | 10 to 14 percent |
Evidence craft for the assembled document
Audit citations in both directions. Every in-text citation appears in the list, every entry in the list appears in the text. Documents built across eight weeks accumulate orphans on both sides, and reference integrity is one of the few things a grader can check exhaustively in minutes.
Keep the ethics route procedural. Describe the determination process your program and site require and say when it will be sought. Do not state the outcome, do not describe the project as exempt before anyone has said so, and do not promise a timeline you do not control.
Say what remains unresolved. A design document that admits two open dependencies with dated plans is more credible than one that presents everything as settled. Reviewers already know a design at this stage has open questions, and volunteering them is faster than being asked.
Protect the site and the people in it. Describe the organization by type and size, refer to roles rather than individuals, and de-identify every clinical example. Anything a preceptor, site or navigator verifies, including hours and logs, is your own record and stays outside the written work entirely.
Write the abstract or summary last and to a reader who will read nothing else. Problem, setting, evidence-based change, measures, and what success will look like, in that order, with numbers. Many of the people who matter to a project read only that page.
Five mistakes that cost points in this week's territory
- A broken chain. Evidence that supports a different intervention from the one proposed is the most consequential assembly error and the easiest for a reviewer to spot.
- Inconsistent numbers. A unit described as 32 beds in one section and 28 in another makes a reader doubt every figure in the document.
- Feedback appended rather than integrated. A patched paragraph reads as a patch, and it signals that the design was not rethought, only amended.
- Sustainability as a sentence. Ongoing monitoring will continue names nobody, funds nothing and survives no staff turnover.
- Claiming an approval or determination. Stating the outcome of a review that has not happened is a fabricated official fact in the most scrutinized document of the course.
Before you submit
- The six-line chain from problem to primary outcome holds without a break
- Every repeated number is consistent across sections
- Navigator feedback is integrated into the design, with declined suggestions reasoned
- The timeline is a table with phases, durations, owners and preconditions
- Sustainability names an owner, a structure and a continuing measure
- No ethics determination, site approval or review outcome is stated in advance
Assembling the NR-730 design document?
Send the rubric and your sections out of Canvas. A premium original draft comes back in 24 to 48 hours with the chain reconciled end to end, numbers made consistent and the operational layer complete, and revisions run until the grade lands.