NR-707A carries 2 practicum credits and 128 clinical hours, which is roughly sixteen hours a week across an eight-week session, and it is the block where an already-approved practice change is put into operation at a site. The opening stage is where you decide what the written record of that implementation will be, and start keeping it from day one rather than reconstructing it in week seven. Your section may print this as NR 707A or NR707A; 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-707A Week 1 asks for
The document that separates a strong implementation block from a painful one is unglamorous: a dated working log of what happened, kept by you, in your own words, as events occur. Not the hour log your school requires, which is a separate and formal record, but a running account of decisions and events with dates and counts beside them. Students who keep it write their later sections in an evening. Students who do not spend week seven trying to remember whether the second training session happened before or after the eligibility rule changed, and it shows in the prose, because reconstructed narrative loses exactly the specificity a doctoral reader is looking for.
The boundary, stated plainly, because it governs every page of this manual. Your practicum hours, your hour log, your encounter counts, your preceptor or mentor evaluations, your site paperwork and every signature on any of it are your own record of your own work. They are never drafted, reconstructed, estimated or filled in with anyone's help, and no writing support of any kind extends to them. What can be supported is the written and scholarly layer that surrounds the clinical work: how an implementation narrative is structured, how an audit is written up, how interim results are presented, how a progress report is organized for a doctoral reader. The implementation itself, and the hours it consumes, are yours. Where real encounters or site data appear in your writing, every detail is de-identified before it reaches the page.
The other opening task is arithmetic. One hundred and twenty-eight hours is a real but finite budget, and a 2-credit block cannot carry an implementation designed for a full academic year. This stage is the moment to write what the block will realistically deliver: which components launch, on which units, over how many weeks of live operation, and what will still be running when the session closes. A written scope that concedes limits is a doctoral document. A scope that assumes everything proceeds on schedule is a document that will be contradicted by events in week four.
Expect the deliverable to be a planning or contracting document of some kind, often with a timeline, sometimes with objectives tied to your program's competency framework, and usually a posted discussion introducing the project. Whatever the format, the audience is faculty who will read your later sections against this one, so write it precisely enough to be checked and honestly enough that being checked is survivable.
The NR-707A Week 1 method, step by step
Six moves for setting up the written layer of an implementation block before it gets busy.
-
Reduce the rubric to deliverables and dates
List every written product the session will require and put a date beside each. Doctoral blocks fail on collisions between a site milestone and a submission, and the collision is visible in week one if anyone looks for it.
-
Write the scope in operational terms
Name the units, the eligible population, the components launching, the start date and the number of live weeks the session actually contains. Then subtract the setup time honestly, because implementation rarely begins on the first day of a session.
-
Set up the contemporaneous record before anything happens
One file, one dated entry per event, each carrying what happened, who was involved by role, a count where one exists and the decision taken. Ten minutes at the end of a practicum day, kept de-identified from the first keystroke.
-
Fix the data you will need before you need it
Write down which measures you will report, where each number comes from, who can produce it, and how long a request takes at your site. Discovering in week six that a report requires a two-week queue is the classic 128-hour failure.
-
Name what would count as trouble, in advance
Write the two or three conditions that would mean the implementation is not going as designed: uptake below a level you name, a component not launched by a date you name, a data source unavailable. Pre-committing to those signals is what makes your later analysis credible.
-
Write the objectives so a faculty reader can verify them
Each objective needs a verb, a deliverable and a window inside these eight weeks. Anything that could still be true at the end of the session whether or not you did anything is not an objective a reader can score.
A layout that makes an opening practicum document verifiable
Our frame for a block-opening planning document, sized for roughly 1,100 to 1,400 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.
| Section | What belongs in it | Word target |
|---|---|---|
| Project and current stage | The approved change in two sentences, what has already been completed, and what this block is expected to add. | 140 to 180 |
| Site and scope for this block | Units, eligible population, components launching, live weeks available after setup, and what is deferred. | 200 to 250 |
| Hour reality | How 128 hours distribute across implementation activity, meetings, data work and writing, stated as a plan you own. | 140 to 180 |
| Documentation plan | What record you will keep, in what form, how often, and how de-identification is handled from entry one. | 170 to 210 |
| Data and access plan | Each measure, its source, the person who produces it, and the lead time a request requires at your site. | 200 to 250 |
| Objectives and trouble signals | Verifiable objectives for this block, plus the pre-named conditions that would indicate the plan is off course. | 190 to 240 |
Evidence craft for practice-doctorate writing
Write translation, not discovery. A DNP project takes evidence that already exists and moves it into practice at a site. Your language should say so: implement, adapt, embed, evaluate. Words that belong to original research, such as hypothesis, subjects and findings that generalize, misdescribe what you are doing and doctoral faculty correct them every session.
Keep improvement and research distinct in every sentence. A quality improvement evaluation asks whether a local process changed. It is not a trial, it does not establish causation the way a trial does, and it should never be written as though it did. Where a determination about human subjects review applies at your site, describe the process you followed rather than predicting an outcome from it.
Cite the frameworks you are actually using. Implementation science and improvement literature supply named models for staging a rollout and evaluating it. Attribute the ones you have adopted with a year, and use their vocabulary consistently, because a document that borrows one framework's diagram and another's terminology reads as unread.
Every number carries its source and its date. Baseline figures, eligible volumes and site counts should each be written with where the number came from and when it was pulled. In an implementation block the reader's trust in your later data rests on this habit starting now.
De-identify at the point of writing. No names, no record numbers, no dates of service that could locate a case, no descriptions specific enough to identify a staff member on a small unit. Roles and aggregates only, and say in your documentation plan that this is your standing rule.
Five mistakes that cost points in this week's territory
- Scope written for a year in a 128-hour block. A plan that cannot fit the hours available will be contradicted by the record you are about to start keeping.
- No contemporaneous record. Everything later in this session is easier or harder depending on this one decision, and the difference is visible in the writing.
- Objectives nobody could check. Support the implementation is not an objective; it is a mood.
- Research vocabulary in a translation project. Calling the work a study or a thesis misdescribes the degree and is corrected quickly at doctoral level.
- Assuming data will be available. Access, lead time and who runs the query are logistics that decide whether week five is calm or catastrophic.
Before you submit
- The block's scope names units, population, components and the live weeks actually available
- The 128-hour budget is distributed in writing across implementation, meetings, data and writing
- A documentation plan states the record's form, frequency and de-identification rule
- Each measure has a named source, a named producer and a stated lead time
- Objectives carry a verb, a deliverable and a window inside this session
- Nothing in the document drafts, estimates or reconstructs hours, logs or evaluations
Opening the NR-707A block this week?
Send the rubric and your project documents out of Canvas. A premium original draft of the written layer comes back in 24 to 48 hours, scoped to the hours you actually have, with hours and logs left entirely to you where they belong.