NR-575 opens with the one decision that governs the remaining seven stages: what practice problem your capstone is going to solve, and for whom. The written work at this point is a scoping argument rather than a paper about a topic, and it has to survive a hostile question the first time you say it out loud at the intensive. Everything downstream, the synthesis, the product, the implementation section, the evaluation plan, inherits whatever precision or vagueness you settle for now. Your section may print this as NR 575 or NR575; 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. Your clinical hours, your logs and your preceptor evaluations are your own record and are never drafted, reconstructed or estimated with help; this manual covers the written layer only.
What NR-575 Week 1 has to establish
Sit with a unit's charts for an afternoon and the capstone problem usually announces itself. A quality reviewer pulling twenty consecutive rapid response records is not looking for a topic; she is looking for the same gap appearing in enough of them that a fix would be worth building. Nine notes with no documented reassessment interval after the team left the bedside is a practice problem. Rapid response outcomes in the acute care setting is a subject heading. The opening stage of a closing practicum is where you make that conversion, and the conversion is the graded work.
A scoping argument at this level carries four load-bearing claims. There is a specific gap between what is happening and what should be happening. The gap has a size, expressed in whatever unit the setting actually counts in. It has a consequence somebody in the organization cares about. And a product of the kind you can build in eight weeks could plausibly move it. Miss any one of those and the capstone that follows is unanchored, because a synthesis has nothing to synthesize toward and an evaluation plan has nothing to measure.
The acute care context tightens the frame further. You are writing as an advanced practice clinician preparing for adult-gerontology acute care certification, which means the problem should live in the territory the role actually owns: management of physiologically unstable adults, transitions between levels of care, procedural and diagnostic decision making, or the handoff points where those things fail. A staffing complaint or a general education wish is neither ownable by the role nor buildable into a product a grader can score.
Say plainly here, and in every stage of this course, where the boundary sits. The precepted hours, the encounter volume, the site paperwork, the signatures and the evaluation your preceptor completes are yours alone. They are the part of the practicum that has to be lived. What can be sharpened on paper is the reasoning you write about work you genuinely did, and any detail from a real encounter that reaches your document must be de-identified before it does: no names, no record numbers, no dates of service, no unit identifiers that would let a reader reconstruct a person.
Opening stages in a capstone course usually carry a short scoping submission, a posted introduction of the proposed problem, or both. Treat the post as final copy. Posts do not reopen once submitted in Canvas, and in a course where you may be presenting to the same peers at an on-ground intensive, a loose first statement of your problem is one you will be answering for in person.
The NR-575 Week 1 method, step by step
Six moves that turn a subject into a defensible practice problem.
-
Read every scoring row for the whole course before you scope anything
A capstone grades several distinct objects across eight stages. Copy each rubric out of Canvas into its own file now, reduce each row to its verb, and check that the problem you are about to choose can actually feed all of them. A problem with no measurable outcome will strand you in the evaluation stage six weeks from now.
-
Start from a documentation pattern you have seen repeatedly
Real problems show up as repetition. Look for the thing you have watched go wrong more than twice in your own precepted time: the reassessment that is never charted, the discharge instruction nobody can find, the escalation criteria that live in three different formats. Repetition is what makes the problem real and what makes a product worth building.
-
Put a number on the gap using a count you can defend
Say how many, out of how many, over what window. If publicly reported measures exist for your setting or setting type, use them and cite them. If your evidence is your own structured observation, describe how you counted and say so; an honest small count is stronger than a national statistic wearing a local costume.
-
Name the consequence in the organization's own currency
Length of stay, readmission, unplanned transfer to a higher level of care, time to intervention, avoidable escalation, harm events. Choose the one that follows most directly from your gap and argue the causal chain in two sentences rather than asserting that the problem is important.
-
Write the question in a structured format and keep it narrow
Population, the change you are proposing, what it is being compared against, the outcome, and the window. If the question takes more than one sentence, it is two questions and you should keep the one you can evidence.
-
State the product in one sentence before you leave this stage
An algorithm, a documentation template, a structured handoff tool, a teaching module, a decision aid. Naming the form now forces the problem to be the size of a thing you can build, and it tells you immediately whether your evaluation measure exists.
A layout and word budget for a capstone scoping piece
The frame our tutors keep beside a first capstone submission, sized for roughly 1,000 to 1,300 words. It is our own outline rather than anything the university issues, and your week's rubric outranks it wherever the two disagree. Scale the targets proportionally if your assigned length differs.
| Section | What belongs in it | Word target |
|---|---|---|
| The gap, stated first | What is happening against what should be happening, in one sentence, before any background arrives. | 70 to 100 |
| Setting and population | Unit type, acuity, patient population and the scope of the advanced practice role inside it, without identifying the facility. | 140 to 180 |
| Size of the problem | The count with its denominator and window, the source of that count, and how it compares with published expectations. | 200 to 250 |
| Consequence argued, not asserted | The outcome the gap drives, the chain that connects them, and who in the organization owns that outcome. | 200 to 240 |
| The structured question | Population, proposed change, comparison, outcome, window, in a single sentence with the elements labelled if the rubric asks. | 90 to 120 |
| Proposed product and feasibility | The form the deliverable will take, who would use it, and what makes it buildable inside an eight-week session. | 180 to 220 |
| Close | What the reader should now accept as established, not a summary of the paragraphs above. | 60 to 90 |
Evidence craft for a practice problem argument
Local evidence and published evidence do different jobs. Published work establishes that the problem exists as a class and that something has been shown to help it. Local observation establishes that it exists here. A scoping argument needs both, and the sentence that scores highest is the one that puts them side by side: the literature reports this failure mode in step-down populations, and in the records I reviewed it appeared in nine of twenty consecutive cases over one quarter.
Every number arrives with its base, its window and its origin. Nine of twenty over three months, drawn from a structured review of consecutive records, is evidence a grader can weigh. Forty-five percent is a figure with no weight at all. In a capstone the origin clause matters as much as the count, because the evaluation stage will ask you to collect the same measure again and a number whose source you never specified cannot be recollected.
Do not import a national statistic as if it were a local one. Published incidence figures describe populations that may look nothing like the unit you are writing about. Use them to establish that the problem class is real and consequential, then say explicitly what you do and do not know about its magnitude in your own setting. Naming that limit reads as rigour, not weakness.
Attribute and date professional standards inside the sentence. Scope statements, competency documents and certification blueprints are revised on schedules of their own. Name the issuing body and the edition in the clause where the claim appears rather than leaving the reader to reconstruct it from a reference list, especially where you are arguing that a task belongs to the advanced practice role.
De-identify before the detail reaches the page. If a real case motivated your problem, write it as an aggregate or as a composite pattern with no age precise enough to identify, no dates, no room numbers, no facility name. This is a writing discipline, not an afterthought applied at proofreading, and a capstone that discusses real records without demonstrating it invites a question at the intensive nobody wants to answer in front of a room.
Five mistakes that cost points at this stage
- A topic where a problem should be. Delirium in critical care is a heading. Delirium screening documented on arrival in only a minority of transfers is something a product can move.
- A problem the advanced practice role does not own. If the fix requires a budget decision or a staffing ratio change, you have chosen a management problem and your capstone will have nothing to build.
- Magnitude by adjective. Frequently, significant and a growing concern are not sizes. A grader scoring a significance row is looking for a count, a denominator and a window.
- Deferring the product to a later stage. Problems chosen without a product in mind reliably turn out to have no measurable outcome, and that discovery in week six is expensive.
- Writing the scoping piece as narrative. An anecdote about a shift is not an argument. Use the encounter as illustration after the claim and the count, never in place of them.
Before you submit
- The gap appears in the first two sentences, stated as a difference rather than a subject
- Your magnitude claim carries a count, a denominator, a window and a source
- The consequence is argued through a stated chain, not asserted as importance
- The question names population, change, comparison, outcome and window
- The product is named in a form somebody could actually pick up and use
- No patient, preceptor, colleague or facility is identifiable anywhere in the document
- Every in-text citation appears in the reference list and every reference appears in the text
Starting the NR-575 capstone this week?
Send the instructions and the rubric out of Canvas. A premium original draft of the scoping argument comes back in 24 to 48 hours with the gap sized and the question built to carry the rest of the session, and revisions run until the grade lands.