Midway through NR-702C the project has to compress into a single sentence that everything else is checked against. An aim statement names the population, the measure, the direction and size of the change, and the date it is claimed by. It is the shortest thing you will write in this course and the most heavily scored per word, because a vague aim makes every later section unfalsifiable. With 256 practicum hours the term can support the baseline work an honest, numbered aim requires, which is exactly why an unnumbered aim reads badly in this variant. Practicum hours, hour logs, site forms and mentor evaluations are your own record and are never drafted, reconstructed or estimated with help. Your section may print this as NR 702C or NR702C; 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-702C Week 4 asks for
On a cardiac surgery step-down unit, early postoperative mobility is the intervention everyone agrees with and nobody can define. Ambulate early is not an aim. Increase the proportion of eligible postoperative patients who complete a first documented ambulation within a stated number of hours of extubation, from a measured baseline to a stated target, on this unit, by a stated date, is an aim. The difference is not style. The second version tells a committee what will be counted, in whom, by when, and how anyone would know whether it happened.
An aim does four jobs at once. It fixes the target so the project cannot drift. It fixes the population so scope creep has to be argued rather than assumed. It fixes the measure so the evaluation design is already half determined. And it fixes the timeline so the plan and the aim can be checked against each other, which is the most common internal contradiction a reviewer finds in a first-stage document.
Sizing the target is where doctoral judgment shows. A target with no justification is a wish; a target justified from the literature, the local baseline and the time available is an argument. If comparable implementations produced a certain magnitude of change and your term is short, claiming more than they achieved needs a reason, and claiming so little that nobody would notice needs a different one.
Scope belongs beside the aim in the same document because the two constrain each other. A wide population with a short window forces a modest target. A tight population with a strong intervention can carry a bolder one. Writing them together lets a reader see that you understand the trade instead of discovering the mismatch in your timeline three sections later.
What this manual does not touch
Everything a preceptor, mentor, site or school verifies stays with you. Hours, the hour log, encounter counts, evaluation forms and signatures are never drafted, reconstructed or estimated here. The written layer is what a manual can improve: the aim sentence, the justification behind the target, the scope boundary and the internal consistency of the document that carries them.
Where the aim draws on real unit performance, that data is aggregate and de-identified before it becomes prose. Populations are described by clinical category and eligibility criteria, never by anything that identifies a person or an encounter. An aim written at population level is compliant by construction, which is one more reason to write it that way.
The NR-702C Week 4 method, step by step
Six moves for building an aim that survives review.
-
Write the measure first, then build the sentence around it
Numerator, denominator, eligibility, and the clock. If those four are settled the aim writes itself; if they are not, the sentence you produce will look complete and mean nothing.
-
Set the baseline value inside the aim's reach
State where performance stands now, in the same measure and the same units the target uses. An aim that names a target without naming the starting point cannot be evaluated by anyone, including you.
-
Justify the magnitude from three inputs
What comparable implementations achieved, what the local baseline allows room for, and what the time window can support. One sentence per input, immediately after the aim, is usually enough and is almost always missing.
-
Attach a date, not a duration
By the end of a stated implementation window reads as vague; a named date anchors the timeline section that follows and forces you to check that the plan can actually reach it.
-
Write the scope boundary as inclusions and exclusions
Which units, which shifts, which patient categories are in, and which are out with a reason each. Exclusions protect a project more than inclusions define it.
-
Run the consistency check backwards
Take the aim to the plan and the plan to the aim. Can the timeline deliver enough post-implementation data to evaluate the target by the stated date? If not, one of the two numbers is wrong, and fixing it now costs a paragraph rather than a stage.
A layout and word budget for an aim and scope section
Our frame for the aim section of a first-stage plan, sized for roughly 1,300 to 1,600 words. 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 |
|---|---|---|
| The aim sentence | Population, measure, direction, magnitude, setting and date, in one sentence that stands alone on the page. | 50 to 80 |
| Measure definition | Numerator, denominator, eligibility rules, exclusions, the clock, and the field or report the data comes from. | 220 to 270 |
| Baseline and target logic | Current performance stated in the same units, then the three-input justification for the size of the change claimed. | 280 to 340 |
| Population and setting scope | Units, shifts and patient categories included, each exclusion with a reason, and the volume the scope implies. | 240 to 290 |
| Time window | Pre-implementation, implementation and evaluation periods, with the date in the aim located inside them. | 180 to 220 |
| Assumptions and dependencies | What has to remain true for the aim to be reachable: access, staffing stability, technology, competing initiatives. | 200 to 250 |
| Consistency statement | One short paragraph confirming the plan can produce the evidence the aim promises, written as a check rather than a claim. | 110 to 150 |
Evidence craft for aim writing
Anchor the target in a cited magnitude. If published implementations moved a measure by a certain amount under similar conditions, cite one and let your target sit in a defensible relationship to it. An uncited target is the easiest thing in the document to challenge.
Keep the aim's units identical to the baseline's units. Percentage points and percentages are different quantities and mixing them is a classic error that a numerate reviewer will catch in the first pass.
Do not promise an outcome that your window cannot observe. Some outcomes take months to appear. If your evaluation period is short, aim at the process measure that leads to the outcome and say explicitly that the outcome is beyond the window. That is honest design, not a weakness.
Write the aim in the language of quality improvement, not of research. No hypotheses, no independent and dependent variables, no claim of generalizability. An aim states an intended change at a site, and the evaluation asks whether it occurred, not whether it would occur elsewhere.
State assumptions rather than relying on them. Every aim rests on conditions holding steady. Naming them protects the project and gives you the honest sentence you will need later if a staffing change or a competing rollout shifts the ground under the plan.
Five mistakes that cost points in this week's territory
- An aim with a verb and no number. Improve, enhance and strengthen are directions of travel, not aims. The measure and the magnitude are what make the sentence scoreable.
- A target invented for its roundness. Ninety percent is not a justification. Three sentences of reasoning behind a less tidy number outscore a tidy one every time.
- Aim and timeline that contradict each other. If the date arrives before enough post-implementation data exists, the document has failed its own internal check.
- Scope defined only by inclusion. Without exclusions, the population is whatever the reader assumes, and each reader assumes something different.
- Multiple aims wearing one sentence. Two measures joined by and is two projects. Pick the one your intervention acts on directly and demote the other to a secondary measure.
Before you submit
- The aim states population, measure, direction, magnitude, setting and date
- The measure is defined with numerator, denominator, eligibility and clock
- The baseline appears in the same units as the target
- The magnitude is justified from literature, baseline headroom and time
- Exclusions are listed with a reason attached to each
- The timeline can produce evaluable data before the aim's date
- Assumptions and dependencies are stated rather than assumed
Fixing the NR-702C aim statement?
Send the rubric and your baseline work out of Canvas. A premium original draft comes back in 24 to 48 hours with the aim numbered, the target justified and the plan checked against its own timeline, and revisions run until the grade lands. Hours, logs and evaluations stay entirely yours.