The last stage of a 256-hour block closes the term and prepares the evaluation that follows. An evaluation readiness memo states what data exists and in what condition, which comparison the dataset can honestly support, what is still missing, and what the site needs in order to keep the measure running once you stop producing it. It is the least glamorous document in the project and the one that most often determines whether the final analysis is defensible. Your section may print this as NR 705C or NR705C; 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-705C Week 8 asks for
The question a chair will ask at the start of the next block is simple and specific: what can you actually compare. A pediatric project that has eleven baseline weeks at one location and three at the other, an eligibility rule that changed in the fourth operating week, and a two-week gap in the series where a report failed is not in trouble - but it is in a particular condition, and that condition determines what the evaluation can claim. Writing it down honestly now, while every explanation is still recoverable, is the entire function of this stage.
The second half is sustainability, assessed structurally rather than hopefully. Is the step embedded in a template or does it depend on someone remembering? Does a named role own it in a way that survives staff turnover? Does a report reach someone automatically, or only when you run it? Does local leadership have a reason to keep the change that does not depend on your presence? Answer each with what is true at each site, including where the honest answer is no. A negative answer written plainly is a finding; the same answer omitted is a gap a committee will locate.
Resist any conclusion about effect. You may well have a series that looks encouraging. The comparison has not been performed under a stated rule, the operating period is incomplete, and any claim made here will be quoted back at you in a defense. Write the counts, write the conditions, and let the evaluation stage do the evaluating.
Where the boundary sits. The end of a block is when practicum paperwork gets finalized, which makes the line worth restating at its plainest. Your 256 clinical hours, the log that records them, encounter and activity counts, evaluations completed by preceptors or site mentors, agreements and every signature the university verifies are your own record and your own work. They are never drafted, assembled, reconstructed, back-filled or estimated with help from anyone, at any point in the term and least of all in the closing week. Written support covers the scholarly layer only: the readiness memo, the data condition report, the sustainability analysis, the reflection. Keep project figures aggregate and de-identified in your writing. The clinical hours cannot be shortcut, and clearer writing about work you genuinely did is the whole offer.
The NR-705C Week 8 method, step by step
Six moves for closing the block and preparing the evaluation.
-
Inventory the dataset period by period and site by site
Which periods exist, which are missing, which were produced under which definition. A table beats prose here and takes ten minutes now against several hours of reconstruction later.
-
Flag every definitional change with the date it took effect
An eligibility rule that shifted mid-term splits your series whether you acknowledge it or not. Acknowledged, it is a documented condition; unacknowledged, it is a flaw someone else finds in your results.
-
State the comparison the data can support, and the ones it cannot
Pre and post at one site with a stable definition may be supportable. A between-site comparison where the sites differ in volume, staffing and baseline length usually is not, and saying so protects you from being asked for it.
-
Assess sustainability against structure, per site
Embedded or manual, owned by a role or a person, monitored automatically or on request, supported by a local reason that outlives you. Four answers per location, each what is true rather than what is intended.
-
Transfer the measure to a named owner in writing
Which role runs the report, on which schedule, who receives it, and what the escalation is when the figure moves. A measure with no owner stops being produced within weeks of your departure.
-
Write the open-items list with owners and evaluation consequences
For each unresolved item, who owns it, when it must close, and specifically what the evaluation loses if it does not. This becomes the first agenda item of your next block.
A layout and word budget for an evaluation readiness memo
Our frame for a stage-closing readiness document, sized for roughly 1,600 to 2,000 words plus tables. It is our own outline rather than anything the university issues, and your chair's direction and your week's rubric outrank it wherever they disagree.
| Section | What belongs in it | Word target |
|---|---|---|
| Operating status at close | What is running at each site, from which date, under which protocol version, with what measurement in place. | 180 to 230 |
| Dataset inventory | Periods held per measure per site, gaps, and the definition in force for each block of periods. | Table plus 160 |
| Data condition assessment | Completeness, definitional stability, verification performed, and any figure known to be unreliable. | 280 to 340 |
| Supportable comparisons | What the dataset can carry, what it cannot, and the reasoning for each, stated before anyone asks. | 250 to 310 |
| Sustainability by site | Embedding, ownership, monitoring and local rationale answered for each location with the current reality. | 300 to 370 |
| Measure ownership transfer | The role taking the report, the schedule, the recipients, and the escalation when the figure moves. | 190 to 240 |
| Open items | Each unresolved item with an owner, a close-by target, and the specific cost to the evaluation if it stays open. | 230 to 280 |
Evidence craft for a readiness memo
Say pre-evaluation in the document, not just in your head. The most damaging sentence available at this stage is one that reads as a result. State that no comparison has been performed under a stated rule and that the figures are operational counts. Six words of protection for the credibility of everything you report later.
Write data condition as facts, not as reassurance. Eleven weekly periods at one location, three at the other, one two-week gap in June attributable to a failed scheduled report. That is a condition assessment. The data are largely complete is a characterization that will not survive scrutiny.
Cite a sustainability framework and apply it locally. Published frameworks for assessing whether an improvement will persist give your assessment categories a reader recognizes. Name the source with its year, then answer its categories about your sites rather than describing the framework.
Report unfavourable readiness plainly. If one site's step still depends on a paper form you restock personally, write it. Sustainability sections that report only favourable structure are the ones that get returned, because every experienced reader knows what a real clinic looks like.
Aggregate and de-identify throughout. The closing memo tends to travel - to a chair, sometimes to site leadership. No line-level data, no cells small enough to identify a family, no service dates, roles rather than names including for people you want to credit.
Five mistakes that cost points in this week's territory
- Claiming improvement. No stated-rule comparison has been made and the operating period is incomplete. A conclusion here becomes a question you have to answer later.
- A dataset described in adjectives. Robust, complete and sufficient are not condition assessments. Periods, gaps, definitions and dates are.
- Definitional changes left unflagged. The single most common cause of an evaluation that cannot be defended is a denominator rule that moved and was never recorded.
- Sustainability as intention. The practice plans to continue tells a reader nothing. Whether the step exists without a human remembering it tells them everything.
- No named owner for the measure. A report that only you can run is a report that stops when you leave, and the site loses the ability to see the change it just made.
Before you submit
- Operating status is stated per site with dates and protocol versions
- The dataset inventory shows periods, gaps and the definition in force for each block
- Every definitional change carries an effective date
- Supportable and unsupportable comparisons are both named with reasoning
- All figures are labelled operational and pre-evaluation
- Sustainability is answered structurally per site, including unfavourable answers
- The measure has a named role owner, a schedule and recipients
- Every open item has an owner and a stated cost to the evaluation
Closing NR-705C this week?
Send the rubric, your measurement plan and your own aggregate series out of Canvas. A premium original draft comes back in 24 to 48 hours with the data condition written as facts and sustainability assessed structurally per site, revised free until it lands. Practicum hours, logs and evaluations remain entirely and only yours.