By the third stage of a 256-hour block the change is running and being adjusted, and the written task is to make those adjustments legible as method rather than as improvisation. Improvement work proceeds through small tested cycles, each with a prediction, a defined test, an observation, and a decision, and a doctoral document records them in that form. A block with this many hours can run several cycles; the writing is what turns them into evidence. Your section may print this as NR 707C or NR707C; 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-707C Week 3 asks for
A telehealth triage line adopted a new escalation script and the first week produced two complaints and one enthusiastic nurse. The change that fixed it was small: the script was moved from a separate document into the call template, and one question was cut because it duplicated something the intake already asked. That adjustment took two days. Written as "we made some changes based on feedback," it is worth nothing. Written as a cycle with a prediction, a two-day test on one shift, an observed result across eleven calls, and a decision to adopt, it is doctoral evidence about how the change reached a workable form.
The boundary that governs this manual. Practicum hours, hour logs, encounter counts, site paperwork, and any evaluation completed by a preceptor or mentor are your own record of work you personally performed and are never drafted, reconstructed, or estimated with help. What can be supported is the written layer: how a test cycle is documented, how a prediction is stated, how an adaptation is justified in scholarly prose. Real calls, visits, and encounters appear in your writing de-identified, described by class and count rather than by case.
The discipline that makes this stage work is prediction before observation. Anyone can explain a result afterward. A cycle record that states, in advance, what you expected the change to produce and what would count as success, and then reports what happened including the times you were wrong, is doing something categorically different from a narrative assembled from memory. It is also the hardest habit to install, because it requires writing something down on a busy Tuesday when nothing has happened yet.
Expect the deliverable to be a written account of the tests conducted so far, often with a cycle table, sometimes embedded in a progress document, and frequently a posted discussion where classmates describe what their first adjustments taught them. The register that scores is neutral and specific: dates, counts, decisions. Enthusiasm about how the team pulled together is not the finding.
The NR-707C Week 3 method, step by step
Six analytic moves for turning adjustments into a defensible cycle record.
-
1. State the prediction before the test runs
One sentence naming what you expect to change and by roughly how much, written and dated ahead of the test. A prediction recorded afterward is a rationalization, and a reader cannot tell the difference unless the dates are visible.
-
2. Bound each test to a scale you can observe
One shift, one nurse, five calls, two days. Small scale is not timidity; it is what makes an observation attributable. A change tested across an entire service for two weeks cannot be separated from everything else that happened.
-
3. Record the observation with counts, not impressions
How many cases, what happened in each category, what was said and by how many people. Eleven calls with the revised template, escalation reached in nine, two abandoned at the second question, is data. It went better is not.
-
4. Decide explicitly: adopt, adapt, or abandon
Every cycle closes with one of three words and a sentence of reasoning. The decision is the part a doctoral reader is scoring, because it demonstrates whether the observation actually governed your behavior.
-
5. Sequence cycles so each one tests a single question
Two simultaneous changes produce an uninterpretable result. If speed requires parallel tests, say so and accept the interpretive cost in writing rather than pretending the design was clean.
-
6. Distinguish a tested adaptation from drift
An adaptation is a change you predicted, tested, and adopted. Drift is erosion nobody decided. Both alter the intervention, and your evaluation later depends on your having marked which is which, with dates.
A layout for a cycle record and its narrative
Our frame for this stage's written work, sized for roughly 1,200 to 1,500 words plus a cycle table. It is our own outline rather than anything the university issues, and your week's rubric outranks it wherever the two disagree.
| Section | What belongs in it | Word target |
|---|---|---|
| State of the change at entry | What is live, since when, and the specific weakness the cycles in this stage were aimed at. | 150 to 190 |
| Cycle one, in full | Prediction, scale, dates, observation with counts, decision, and the reasoning behind it. | 230 to 280 |
| Subsequent cycles, compressed | The same five elements for each later cycle, written tightly, with the sequence made explicit. | 250 to 300 |
| What the cycles established | The form the change has now taken and which elements are settled versus still under test. | 190 to 230 |
| Adaptations versus drift | Deliberate tested modifications listed with dates, separated from erosion you observed and corrected. | 180 to 220 |
| Implications for evaluation | How a mid-course change affects the way your before and after comparison must be read. | 170 to 210 |
Evidence craft for cycle documentation
Dates carry the argument. A cycle record without dates is a story; with them it becomes a chronology a reader can align against your outcome data. Put the date of the prediction, the dates of the test, and the date of the decision in the text, and keep them consistent with every other document in the block.
Report the cycles that failed. A record showing only successful adaptations is either incomplete or describes a project where nothing was genuinely tested. The failed cycle, honestly reported with what it taught, is often the strongest paragraph in the section, because it is the clearest evidence that observation changed your behavior.
Attribute the improvement model you are using. Structured small-cycle testing has a documented lineage in improvement science, and naming the model with a year situates your work. Use its terms accurately rather than borrowing the diagram and inventing the language.
Keep the frame local and translational. These are tests of implementation in one setting, not experiments about whether an intervention works. Nothing in a cycle record supports an efficacy claim, and the writing should stay inside that limit. Where your organization requires a determination about human subjects oversight, describe the process you followed and its date rather than characterizing an outcome.
De-identify by class and count. Write "nine of eleven calls in the test window" rather than describing a particular call, and use roles rather than names for the staff involved. On a small telehealth team, even a shift reference can identify a person, so aggregate the shift as well when the team is small.
Five mistakes that cost points in this week's territory
- Predictions written after the result. Undated retrospective predictions are the most visible weakness in a cycle record and they invalidate the method.
- Tests too large to interpret. A change rolled out everywhere at once cannot be attributed to anything, and calling it a cycle does not fix that.
- Cycles with no decision. An observation that leads to no stated adopt, adapt, or abandon has not completed, and the reader will notice the loose end.
- Only successes reported. A record with no failed cycle reads as curated, and curation is the opposite of what this section is for.
- Adaptations left undated. If the intervention changed mid-block and the date is missing, your outcome comparison cannot be interpreted by anyone, including you.
Before you submit
- Each cycle carries a dated prediction written before the test
- Each test states its scale: how many cases, over what period, with whom
- Observations are reported as counts within stated categories
- Every cycle closes with adopt, adapt, or abandon plus reasoning
- At least one unsuccessful cycle is reported honestly
- Adaptations are dated and separated from drift, with implications for the evaluation stated
Writing the cycle record for NR-707C?
Send the rubric and your working notes out of Canvas. A premium original draft comes back in 24 to 48 hours with predictions, test scales, counted observations, and explicit decisions, and revisions run until the grade lands.