NR-705A Week 1 Scope Calibration for 128 Hours: How to Write It

What NR-705A Week 1 asks for

A DNP student working in a 96-bed skilled nursing facility arrived at this stage with a project she described as improving care transitions. That is a program of work for a decade. What the term could carry, once we counted the hours honestly, was one arrow: the transfer from the facility to the affiliated hospital's emergency department, and specifically whether the information packet that travels with a resident contains a reconciled medication list and a current code status. One arrow, one document, one measurable step. She lost nothing by narrowing it. She gained a project that could be prepared properly inside 128 hours rather than begun in five places and finished in none.

That narrowing is the intellectual work of the opening stage. A practice doctorate translates evidence that already exists into a change at a site, and the translation only becomes real when it is small enough to specify completely. The written deliverable family here is preparatory: a restated problem statement anchored in a local number, a scope statement, and whatever project documentation your chair has queued for this block. Some sections run a posted discussion where the cohort reports where their projects stand. Treat posted work as final copy, because faculty who read your board posts will later read your project manuscript, and posts do not reopen once submitted in Canvas.

Doctoral register matters from the first paragraph and the vocabulary is where students give themselves away. You do not have participants, subjects or a hypothesis. You have a site, a population served by that site, an evidence-based practice change, and a measurement plan. Saying so accurately is not pedantry; it sets the standard of evidence your later sections will be judged against, and it prevents a reader from evaluating a quality improvement effort as though it were an underpowered trial. Write the words practice change, implementation and evaluation, and the rest of the document tends to follow the right shape.

What separates a strong opening document from an adequate one is usually the baseline. A restated problem that says medication reconciliation at transfer is inconsistent has told the reader an impression. A restated problem that says a documented reconciled list accompanied 38 of 91 transfers to the emergency department across one quarter has given the reader something a project can be measured against. That number, with its denominator and its window, is the anchor everything else in the block hangs from, and getting it early is worth more than any amount of polish elsewhere.

The placement boundary, stated plainly

The 128 clinical hours behind this course belong to you and only to you. Practicum hours, hour logs, activity and encounter records, preceptor or mentor evaluations, site agreements, and any signature or document the facility or the university verifies are your own record. They are never drafted, reconstructed, estimated, back-filled or assembled with help of any kind, and nobody should offer to do it. The clinical experience cannot be shortcut and there is no version of this work in which it is. What a manual like this teaches is the written layer that surrounds work you genuinely did: how to structure a scope statement, how to describe a workflow you have actually observed, how to write a reflection that analyzes instead of narrating, how to build a scholarly section that a committee can follow. Where your writing draws on real transfers, real residents or real site data, de-identify completely: no names, no dates of service, no room numbers, no detail that would let a reader recognize a resident, a family member or a staff member. Clearer written reasoning about real work is the whole of what is on offer here.

The NR-705A Week 1 method, step by step

Six moves that turn a broad project idea into a scope a 128-hour term can carry.

1. Reduce the rubric and your chair's guidance to their verbs

   Restate, define, justify and plan ask for different work, and doctoral project documentation usually carries a chair's expectations alongside the course rubric. Where the two differ, ask early rather than choosing silently.

2. Write the local baseline sentence before anything else

   Numerator, denominator and period, from a source you can name. If the figure does not exist yet, say what source would hold it and what obtaining it through the proper channel requires. An unavailable number named honestly beats an estimated one every time.

3. Count the hours against the work, not the ambition

   Sixteen hours a week across eight weeks, minus the hours already committed to meetings, observation and mentor contact. Whatever remains is the preparation capacity. Write the scope to that remainder rather than to the project you would like to describe.

4. Reduce the project to one step in one workflow

   One setting, one transition or process, one measurable step, one population. Multi-site and multi-process scopes are the most reliable way to end a short block with a partial version of everything.

5. Write the exclusions as a paragraph, not as an apology

   Name what this term is deliberately not doing and why. A committee reading an explicit boundary sees judgment; a committee inferring a boundary from what is missing sees an incomplete document.

6. List the approvals and access the scope depends on

   Who controls the transfer document, who can authorize a data pull, which committee reviews process changes. Describe the status of each factually, and predict no outcome for any review body.

A layout and word budget for a scope and problem restatement

Our frame for the opening written piece of this practicum block, sized for roughly 1,400 to 1,700 words. It is our own outline rather than anything the university issues, and your chair's guidance and your week's rubric outrank it wherever they disagree. Scale proportionally if your assigned length differs.

Evidence craft for an opening project document

Anchor on synthesized guidance rather than a stack of primary studies. A practice change stands on a guideline or a systematic synthesis, cited with its issuing body and year. Listing fourteen primary studies in a scope document signals that you are still writing a proposal instead of preparing an implementation.

Every local figure carries its base and its window. Thirty-eight of 91 transfers across one quarter is a measurement. Forty-two percent is a number the reader cannot weigh, and in a doctoral document the reader's inability to weigh it is your problem rather than theirs.

Attribute observation and report differently. What you watched across several shifts and what a nurse manager told you are different classes of information and both belong in the document. Write observation across six evening handoffs showed, and the director of nursing reports, and let the reader see which is which.

Describe any review process factually and predict nothing. Say what has been submitted, to which body, and when. Do not write that approval is anticipated, that a determination of non-research will be straightforward, or that the project is exempt. A written prediction about a review body's decision is among the fastest ways to have a sound document returned.

Five mistakes that cost points in this week's territory

• A scope written for a longer term. Three units and two processes cannot be prepared properly in 128 hours, and committees recognize the pattern immediately from the breadth of the problem statement.
• An impression where a baseline belongs. Inconsistent, frequently and often are adjectives. The opening document needs a counted figure or an honest statement that one is not yet available.
• Research vocabulary applied to a practice change. Subjects, hypothesis and trial invite an evidentiary standard the design was never built for and misstate what a practice doctorate does.
• Exclusions left implicit. A boundary the reader has to infer reads as incompleteness rather than as judgment, and it costs the same points either way.
• Dependencies unnamed. A scope that quietly assumes access to a data extract somebody else controls has placed its own feasibility outside the document.

Before you submit

• The local baseline appears as a count over a denominator across a named period
• The scope names one setting, one process and one step
• Exclusions are stated explicitly with reasoning tied to the hour load
• No sentence describes your own project as research or predicts a review outcome
• Observed information and reported information are attributed differently
• Every clinical illustration is de-identified beyond recognition

Questions students ask about this stage

Keep going