NR-702C Week 1 Scoping the Practicum Term: How to Write It

What NR-702C Week 1 asks for

A DNP student walks onto a 32-bed progressive care unit in week one holding a project idea that sounds fine out loud and collapses the moment it has to be written down. The idea is usually a noun phrase: mobility, alarm fatigue, handoff, discharge follow-up. The opening stage of a project practicum asks you to turn that noun phrase into a problem statement with an owner, a boundary and a number attached, because everything you write for the rest of the sequence is measured against it.

The doctoral distinction matters from the first paragraph. A practice doctorate project translates evidence that already exists into a change at one site. It does not generate new knowledge, it is not a thesis, and writing it as if it were is the single most common register error in this course. Your literature is not there to reveal an unknown; it is there to establish that a practice is already supported and that your site is not doing it. That is a translation argument, and it reads very differently from a research argument.

Written work at this stage usually clusters around three things: a statement of the practice problem, an early description of the setting and its readiness, and some form of practicum planning narrative that says what the term's hours will be spent on. Sections often run a discussion alongside, and doctoral discussion posts are graded as scholarly writing rather than as conversation, so treat the post as final copy. Posts do not reopen once submitted in Canvas.

The hour load is not decoration. With 256 hours available across eight weeks, a plan can realistically include a full baseline data pull, repeated stakeholder meetings, direct observation of the current workflow, and pre-implementation groundwork such as drafting education materials or booking simulation time. Write the plan to that reality. A plan that could be executed inside a 128-hour term is under-promising in this variant, and a plan that assumes a year of access is over-promising in any variant. The honest middle is what earns the specificity points.

What this manual does not touch

The clinical experience in a project practicum cannot be shortcut, and nothing here tries to. Hours are yours. The log is yours. Site forms, mentor signatures, encounter records, census entries and any evaluation your school or your site verifies are your own record, and no part of that layer is ever drafted, reconstructed or estimated with assistance. What a manual can do is make the written reasoning about work you genuinely did clearer, tighter and easier for a committee to score.

The same boundary shapes how you use real material in prose. When a paragraph describes a workflow you observed, the patients in it are de-identified before a single word is typed: no names, no dates of service, no room numbers, no identifiers that would let a reader reconstruct an individual. Aggregate counts drawn from unit-level reports are the safe currency of doctoral writing, and they are also the currency that scores, because a committee is reading for system behavior rather than for cases.

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

Six moves that turn an idea into a scoped written problem.

1. Read the rubric as a table of contents

   Copy each scored row into a blank file and make it a heading, in the guide's own order. Rows in project courses tend to be descriptive of a document rather than of a skill, which means the guide is telling you the shape of the deliverable. Any row you cannot turn into a heading is a row you have not decoded, and week one is the cheap week to ask.

2. Write the problem as a gap between two observable states

   Not a topic. A gap. What the evidence says should happen on this unit, what actually happens, and the distance between them expressed in something countable. A progressive care unit where mobility is ordered for most patients and documented for a minority has a gap you can write; a unit with a mobility problem does not.

3. Anchor the gap in local, aggregate data you can actually get

   Name the report, the system it comes from, the level it is reported at and who owns access to it. If the number will take four weeks to obtain, say so and build it into the term. A plan that leans on data nobody has agreed to release is the most common way a first-stage project stalls in week five.

4. Draw the scope boundary in and out, explicitly

   One unit or three. One shift or all shifts. Adults only. Which patient population is excluded and why. Write the exclusions down, because an unstated boundary is renegotiated by every stakeholder who reads the document, and each renegotiation costs you hours you have already budgeted.

5. Say who owns the outcome and who owns the process

   The person accountable for the measured result is rarely the person who has to change their behavior. Naming both early, in the document, prevents the polite ambiguity that lets a project be approved by everyone and executed by no one.

6. Budget the 256 hours in writing before you spend them

   Rough proportions across the term: assessment and observation, stakeholder work, planning and writing, and pre-implementation preparation. This is a planning narrative, not a log. It tells a reader that the hours are being directed by the project rather than absorbed by whatever the unit needed that day.

A layout and word budget for an opening problem and scope piece

The frame our doctoral bench keeps beside a first-stage problem statement, sized for roughly 1,600 to 2,000 words. It is our own outline rather than anything the university issues, and your week's rubric outranks it wherever the two disagree. Scale each target proportionally if your assigned length differs.

Evidence craft for a first-stage project document

Cite to establish that the practice is settled, not that it is novel. Translation writing uses the literature as a floor. Two or three strong syntheses that say a practice works are worth more here than fifteen primary studies, because your claim is that the evidence is stable enough to implement rather than interesting enough to investigate.

Every number arrives with its base, its definition and its window. Forty-one of 388 eligible admissions across one quarter is evidence. Eleven percent is a number a reader cannot weigh, and a committee that cannot weigh your baseline cannot approve the aim that will be built on it in a later stage.

Name the organizational source by role, not by person. The quality department, the unit manager, the informatics analyst who owns the report. Writing roles keeps the document usable after staff turn over, and it keeps you inside the de-identification boundary that governs everything you write from a live setting.

Do not promise regulatory or review outcomes. Describe the determination process your school and site require and where your project sits in it, without stating what any board will decide. Predicting a determination in writing is a factual claim you cannot support and a credibility loss a committee will notice immediately.

Distinguish quality improvement from research in your own sentences. A QI evaluation asks whether a known good practice took hold at this site. A trial asks whether the practice works. The verbs, the design language and the claims you are entitled to make all follow from that difference, and doctoral graders mark it consistently.

Five mistakes that cost points in this week's territory

• A topic where a problem belongs. Alarm fatigue is a subject heading. A unit generating a high volume of non-actionable alarms per monitored bed per shift is a problem with a shape.
• Research framing on a translation project. Hypotheses, novelty claims and language about generating new knowledge signal that the doctoral distinction has not landed.
• Scope that quietly includes everything. A document with no exclusions is a document that will be widened by three separate stakeholders before week four.
• Baseline data assumed rather than sourced. If nobody has named the report and confirmed access, the number in your problem statement is a placeholder wearing a decimal point.
• Treating the hour plan as paperwork. The hour narrative is where a committee reads whether you understand what 256 hours can and cannot buy at one site.

Before you submit

• The problem is written as a gap between two observable states, not as a topic
• The countable thing appears in the opening paragraph with its base and window
• Every local data point names its source, its definition and its date range
• Scope states what is excluded as clearly as what is included
• The setting is described as a system, with staffing model and reporting lines
• No patient-level detail appears anywhere, and de-identification is stated
• The hour plan reads as direction of effort rather than as a log

Questions students ask about this stage

Keep going