NR-705C Week 1 Scope the Term Against Your Hours: How to Write It

What NR-705C Week 1 asks for

A pediatric group with four locations under one management structure gives the reader a good picture of what a 256-hour term changes. In a lighter block a student implements a new medication reconciliation step at a single clinic and measures it. At this hour load a student can run the same change at two locations, hold a comparison of how it behaves in a high-volume site versus a low-volume one, and still have time for the meeting cadence that multi-site work demands. That is not a bigger project for its own sake; it is a project whose findings say something about the conditions the change needs, which is the translation contribution a practice doctorate is built to make.

Hold the doctoral framing steady from the first paragraph. This is translation science. Your project takes evidence that already exists and moves it into practice, then evaluates whether the move worked at your site. It does not generate new knowledge about the intervention itself, it is not a dissertation, and it is not a trial. Students who write participants, hypothesis and study design into an opening scoping document invite a standard of evidence their project was never designed to meet, and the correction costs them credibility for the rest of the block.

The deliverable family in this opening stage is usually a scoping or readiness document plus whatever manuscript section your chair has queued, sometimes with a cohort discussion where students describe their setting and their plan. Treat posted work as final copy. Doctoral boards are read by the faculty who will later read your manuscript, and a loose post in the first stage sets an expectation that is difficult to reset.

Where the boundary sits. The 256 clinical hours belong to you completely. Hours, the log that records them, activity or encounter counts, evaluations completed by preceptors or site mentors, site agreements and signatures are your own record and your own work, never drafted, reconstructed, back-filled or estimated with help of any kind, and nothing here is an offer to do so. What a manual can teach is the written layer around real work: how to structure a scoping document, how to write a reflection that analyzes rather than narrates, how to prepare your reasoning before a site meeting. Every clinical detail in your writing must be de-identified - roles rather than names, no service dates, nothing that would let a colleague recognize a family. The clinical experience cannot be shortcut by anyone, and clearer writing about work you genuinely did is the whole of what is on offer.

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

Six moves for a scoping document that matches its hour load.

1. Write the local problem as a counted fact in the opening lines

   Reconciliation documented at 96 of 341 visits across two locations in one quarter tells a reader more than a paragraph on medication safety. That count is the anchor every later comparison in the project hangs from, so get it in early and get its denominator right.

2. Draw the scope boundary in units the reader can count

   Locations, visit types, provider panels, weeks of operating time. A boundary expressed in nouns rather than in adjectives is a boundary a committee can assess, and this is the section where a heavier hour load earns its keep or fails to.

3. Budget the hours against the phases before you commit to scope

   Preparation, launch, monitoring, data work, meetings, writing. Write the rough distribution down. Students who skip this discover in week five that a two-site implementation needed twice the meeting time they allowed and half the data time they will need.

4. Describe the current state per site, not in aggregate

   Two locations under one brand run differently, and an aggregated description hides the exact variation your project will run into. Separate paragraphs, separate counts, and one paragraph naming what differs.

5. Name every role whose cooperation the change requires, by site

   Multi-site work multiplies stakeholders rather than sharing them. The pharmacy lead at one location and the practice manager at another may control the same step, and a single combined list will lose one of them.

6. Close on readiness gaps written as tasks with owners

   Not concerns. Extract specification not written, second-site briefing not scheduled, reconciliation field not yet visible in the template. Each with a role and a target, so the document functions as this block's work plan.

A layout and word budget for a scoping and readiness document

Our frame for the opening written piece of the heaviest practicum block, sized for roughly 1,600 to 2,000 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.

Evidence craft for an opening scoping document

Translate from a synthesized recommendation, not from primary studies. The strongest opening evidence sentence names a professional body's guidance with its year and one or two syntheses behind it. A scoping document that relists twelve primary papers is a proposal that has not noticed the stage changed.

Report every local figure as a count over a base with a period. Documented at 96 of 341 visits between April and June is assessable. Twenty-eight percent leaves the reader guessing at both the denominator and the window, and in multi-site work the denominators are exactly what a committee will want to see.

Keep site-level figures separate. Pooling two locations in the opening document hides the variation your project exists to handle and makes any later site comparison look like a decision made after seeing the data. Report separately from the beginning.

Describe review processes factually and predict nothing. Say what was submitted, to which body, and when. Do not write that determination is expected, that the work is exempt, or that approval will be straightforward. Predicting a review outcome in writing is the fastest way to have a strong document returned.

De-identify every illustration. If a real encounter illustrates the gap - a caregiver arriving with two bottles of the same medication under different names - strip the date, the location and any clinical specificity that narrows it. The point survives; the identifiable detail should not be there in the first place.

Five mistakes that cost points in this week's territory

• Scope written to the hours on paper rather than to the calendar. A term's hours include holidays, closed weeks and site availability, and a plan that assumes even distribution across eight weeks rarely survives contact with a clinic schedule.
• Aggregating sites into one description. The differences between locations are your project's most interesting variable, and pooling them at the start forfeits it.
• Calling the project research. Study, subjects, hypothesis and trial misstate what a practice doctorate does and set an evidentiary bar your design will not clear.
• No hour budget at all. At this load, a scope claim with no phase distribution behind it is an assertion, and it is the first thing an experienced chair will test.
• Readiness written as optimism. A document reporting full readiness in the first stage is not believed by anyone who has implemented anything in a working clinic.

Before you submit

• The local baseline appears as a count over a denominator with a named period
• Each site carries its own current-state description and its own figure
• The scope statement names what is excluded as well as what is included
• An hour and phase budget appears and constrains the scope claim
• The word research is not used to describe your own project
• No sentence predicts the outcome of an organizational or ethics review
• Every clinical illustration is de-identified beyond recognition

Questions students ask about this stage

Keep going