NR-707B Week 1 Delimiting the 192-Hour Block: How to Write It

What NR-707B Week 1 asks for

Picture a thirty-four bed medical-surgical unit on a Monday morning. Two travelers are on the schedule, the charge nurse is covering an assignment because someone called out, and the discharge board already shows eleven anticipated departures. Into that morning you are about to introduce a change that a committee approved eight weeks ago in a conference room where nobody was answering a call light. The opening written work of this block is where you show a doctoral reader that you understand the difference between those two rooms, and that your plan for the next eight weeks was built for the first one.

The boundary, stated plainly, because it governs every page of this manual. Practicum hours, the hour log itself, encounter counts, site attendance records, preceptor or mentor evaluations, and every signature attached to any of them are your own record of work you personally performed. They are never drafted, reconstructed, estimated, or phrased into acceptability with anyone's help, and no writing support of any kind reaches them. What can be supported is the written and scholarly layer that surrounds the clinical work: how a scoping document is organized, how a fidelity write-up is argued, how results are presented without overclaiming, how a closing report is assembled for a doctoral audience. The implementation is yours, the hours are yours, and every patient or staff detail that enters your writing is de-identified before it reaches the page.

The intellectual task of an opening stage is delimitation, which is a stronger word than planning. Planning describes what you intend to do. Delimiting states what you are deliberately not doing, and why, and it is the move that separates a doctoral scoping document from a project charter written by an enthusiastic committee. One hundred and ninety-two hours is a genuine budget. It is more than a two-credit block can carry, which means a second unit, a longer observation window, or a fuller process evaluation becomes realistic. It is also far less than a year, which means an implementation designed for four service lines will be half-launched when the session closes and your evaluation will describe nothing.

Expect the deliverable to be a scoping, planning, or contracting document of some kind, frequently accompanied by a timeline and by objectives written against your program's competency expectations, and often a posted discussion that introduces the project to your classmates. Whatever the format, the reader is faculty who will hold your week seven and week eight writing against this document. Write it precisely enough to be checked, and honestly enough that being checked costs you nothing.

The NR-707B Week 1 method, step by step

Six analytic moves that turn an intention into a scoping document a doctoral reader can verify.

1. 1. Delimit the block before you describe it

   Write the sentence that says what is out of scope first: which units are excluded, which components are deferred, which populations are not touched this session. A scope defined only by inclusions grows quietly for eight weeks. A scope with an explicit boundary can be defended when a stakeholder asks for one more unit in week three.

2. 2. Convert 192 hours into live operating weeks

   Subtract setup honestly. Badge access, a huddle cycle to introduce the change, an order set build, or a telehealth queue configuration each consume days that never appear on a Gantt chart. If setup takes two weeks, you have six weeks of live operation and roughly four weeks of data worth reporting. Write that number down, because every later claim rests on it.

3. 3. Specify the record you will keep from day one

   One file, one dated entry per event, each carrying what happened, who was involved by role, a count where a count exists, and the decision taken. This is separate from any formal log your school requires. It is your working account, written the same day, de-identified from the first keystroke, and it is the difference between an evening of writing in week seven and a weekend of guessing.

4. 4. Trace each measure back to a person and a lead time

   For every number you intend to report, name the source system, the person or department who produces it, and how many working days a request takes at your site. A readmission report that requires a two-week analyst queue is a week five problem discovered in week one or a week seven catastrophe discovered too late.

5. 5. Pre-commit to what would count as trouble

   Name, in advance, the two or three conditions that would mean the change is not operating as designed: adoption below a level you state, a component not live by a date you state, a data feed unavailable. Pre-naming those signals is what allows your later analysis to read as evaluation rather than as justification written after the fact.

6. 6. Write objectives a faculty reader could audit

   Each objective needs a verb, a written deliverable, and a window inside these eight weeks. Anything that could still be true at the close of the session whether or not you existed is not an objective; it is a description of the site. Three auditable objectives outperform seven aspirational ones every time.

A layout for a scoping document sized to 192 hours

Our frame for an opening scoping and contracting document, sized for roughly 1,200 to 1,500 words plus a timeline. 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 practice-doctorate writing

Write translation, not discovery. A DNP project moves evidence that already exists into practice at a named site and evaluates what happened there. The verbs that belong to it are implement, adapt, embed, spread, and evaluate. Hypothesis, subjects, and findings that generalize belong to a different enterprise, and using them tells a doctoral reader you have not settled what kind of work this is. The project is not a thesis and it does not generate new knowledge; it produces a local change and a defensible account of it.

Keep improvement and research separated in every sentence. A quality improvement evaluation asks whether a local process moved and whether the movement is plausibly attributable to the change you made. It is not a trial. It does not carry a trial's protection against confounding, and writing it as though it does is the fastest way to lose credibility at doctoral level. Where a determination about human subjects oversight applies at your organization, describe the process you followed rather than predicting its outcome.

Attribute the frameworks you are actually using. Implementation science and improvement literature supply named models for staging a rollout, assessing readiness, and structuring evaluation. Name the ones you adopted with a year, and then use that model's vocabulary consistently. A document that borrows one framework's diagram while speaking another's language reads as a document assembled rather than read.

Every number arrives with its source and its pull date. Baseline rates, eligible volumes, unit census, telehealth visit counts: each one gets a clause saying where it came from and when it was extracted. In an evaluation block the reader's trust in your week seven numbers is built entirely by how you handle numbers in week one.

De-identify at the point of writing, not afterward. No names, no medical record numbers, no service dates precise enough to locate a case, and no descriptions detailed enough to identify a nurse on a small unit. Roles and aggregates only. Say in your documentation plan that this is your standing rule, because a reader who sees the rule stated stops wondering about the entries you did not show them.

Five mistakes that cost points in this week's territory

• A scope with no exclusions. If nothing is named as out of scope, the scope is not delimited, and it will drift every time a stakeholder makes a reasonable request.
• Treating eight weeks as eight weeks of data. Setup consumes real calendar. A document that ignores it promises an evaluation window that will not exist.
• No contemporaneous working record. Everything else in this session gets easier or harder on this one decision, and reconstructed narrative always reads thinner than written-that-day narrative.
• Research vocabulary in a translation project. Calling the work a study, a thesis, or an experiment misdescribes the degree, and doctoral faculty correct it every session.
• Assuming the data will simply be there. Access, queue time, and the name of the person who runs the query decide whether week six is orderly or frantic.

Before you submit

• The document states explicitly what is out of scope, not only what is in
• Setup weeks and live operating weeks are separated, with the resulting data window named
• The 192-hour budget is distributed in writing across implementation, meetings, data, and writing
• Every measure carries a source, a named producer, a lead time, and a fixed definition
• Objectives each carry a verb, a deliverable, and a window inside this session
• Nothing anywhere in the document drafts, estimates, or reconstructs hours, logs, or evaluations

Questions students ask about this stage

Keep going