NR-612 Week 1 Restating the Project for Delivery: How to Write It

What NR-612 Week 1 asks for

Open a folder of past capstone submissions and audit the opening documents, and one pattern shows up before any other: the strong ones read like a delivery specification and the weak ones read like a proposal that has been pasted forward. A proposal argues that a project should be allowed to happen. A delivery specification says what will happen, to whom, starting when, measured how, and by whose hand. This second session of the concluding graduate experience exists because the first one produced a plan, and the opening written work almost always asks you to convert that plan into terms that can be executed and then evaluated.

The first thing that has to tighten is the aim. Population health aims written in a planning course tend to survive review while still carrying soft language: improve screening uptake, increase follow-up, reduce missed appointments. None of those can be evaluated, because none of them says by how much, among whom, or by when. An aim that can carry a capstone reads closer to a specification: raise documented screening completion among eligible adults seen in the clinic from its current level to a stated target between two named dates. You are not being asked to promise the target will be met. You are being asked to state it clearly enough that at the end of eight weeks a reader can tell whether it was.

The second thing that has to tighten is the population definition. In a plan, the population is a description. In a delivery document, it is an inclusion rule. Who counts as eligible, on what basis, drawn from which list or which report, with which exclusions and why. This is the sentence that decides whether your denominator will exist in week five, and students who leave it vague at the start spend week five inventing a base retrospectively, which is exactly the move a capstone grader is trained to catch.

The third thing is the delta. Time has passed between planning and implementation. Staffing has changed, a workflow was updated, the champion who agreed to help moved units, a competing initiative launched. The opening written work is the honest place to record that, because a difference named in week one is context and the same difference discovered in week seven is an excuse. Faculty read the week one document again when they grade the final one, and a project whose constraints were declared early reads as controlled rather than improvised.

Where our help stops in a practicum course

NR-612 carries 72 practicum hours, and those hours are yours in a way nothing on this page changes. Hours, logs, encounter records, site paperwork, mentor evaluations and signatures are your own record, and they are never drafted, reconstructed, or estimated with help. The same applies to the project activity itself: the meetings you attend, the education you deliver, the chart reviews you conduct and the data you pull are work you do, and nobody can do them for you or write them into existence afterwards. A capstone whose hours were fabricated is not a writing problem, it is an integrity problem, and it ends programs.

What can be taught is the written layer that surrounds the real work: how to state an aim so it can be evaluated, how to build a data definition that will hold up in week five, how to write an implementation account that a grader can follow, and how to interpret results honestly against the limits of the design you actually ran. Every patient detail that enters your writing must be de-identified before it goes anywhere near a document, which in practice means no names, no medical record numbers, no dates of service precise enough to identify one person, and no combination of small details that reconstructs an individual on a small unit. Where this page discusses using your own encounters as examples, it assumes that de-identification has already happened.

The NR-612 Week 1 method, step by step

Six moves that convert an approved plan into a document you can execute against.

1. Audit your own plan against the scoring rows before rewriting anything

   Copy each row out of Canvas into a blank file and mark, next to it, the paragraph of your existing plan that answers it. Rows with nothing beside them are the week's real work. This audit takes twenty minutes and saves the rewrite that follows from being uniformly light.

2. Rewrite the aim until it contains a number and two dates

   A measure, a starting level, a target, a start date and an end date. If your baseline level is not yet known, say so explicitly and name the report you will draw it from rather than leaving the sentence unfinished.

3. Turn the population into an inclusion rule someone else could apply

   Write it as criteria: age band, diagnosis or risk status, encounter type, time window, and the exclusions with a reason attached to each. Then test it by asking whether a colleague reading only that paragraph would build the same list you would.

4. Name the data source and confirm it exists before you commit to it

   A registry report, a scheduling extract, an audit tool, a log kept by staff. Say who can run it, how often, and what fields it returns. Projects fail on availability far more often than on analysis, and week one is when that is cheap to discover.

5. Write the delivery sequence as a dated table, not a paragraph

   What happens in which week, delivered by whom, to which group, using which materials. A grader reading a dated sequence can see feasibility instantly, and you get a document you will reuse in every progress report for the rest of the session.

6. Declare the constraints in the same document that declares the plan

   Short post-intervention window, small eligible population, dependence on one staff member, a competing initiative running in parallel. Each constraint gets one sentence naming what it limits. This paragraph is the one that protects your interpretation section seven weeks from now.

A layout and word budget for an implementation restatement

The frame our tutors keep beside an opening capstone document, sized for roughly 1,200 to 1,500 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 an opening capstone document

Your baseline is evidence and needs a source line. Any level you report for the period before the project starts should carry the report it came from, the date range it covers and the number of records behind it. A baseline stated without provenance cannot anchor a comparison, and a grader who cannot see where it came from will not credit the change you claim against it.

Keep the literature working rather than decorative. The planning course produced a synthesis; this document needs only the part that justifies the specific dose and delivery route you are about to use. One well chosen study that describes an intervention resembling yours, attributed with its year and its setting, does more than six citations attached to the general importance of the problem.

Every proportion arrives with its base and its window. Write that 41 of 268 eligible adults had a documented screening in the quarter before the project, not that screening ran at fifteen percent. Denominators travel with counts throughout this course, and the habit installed in week one is the habit that makes week five defensible.

Attribute local information the way you attribute published information. When a figure comes from a clinic report, a quality dashboard or a conversation with a manager, say so in the sentence and give the date. Internal data is legitimate evidence in population health work, and its credibility rests entirely on being labelled honestly rather than presented as though it were published.

Five mistakes that cost points in this week's territory

• Forwarding the proposal unchanged. Future tense hedging that was appropriate during approval reads as unpreparedness once the delivery window has started.
• An aim with no number in it. If the sentence cannot be tested at the end of the session, everything built on it becomes unevaluable, including your own results section.
• A population described rather than defined. High-risk patients in our clinic is a phrase, not a rule, and it will not produce the same denominator twice.
• Assuming the data will be there. Committing to a measure nobody can extract is the single most common way a capstone loses its evaluation rows in week six.
• Hiding the constraints. A short measurement window declared in week one is a design limit; the same window revealed in week seven reads as a discovery you tried to avoid making.

Before you submit

• The aim contains a measure, a target and two dates
• Inclusion and exclusion criteria are written so a colleague could reproduce your list
• Numerator and denominator are each defined in one sentence apiece
• The data source is named along with who can actually run it
• The delivery sequence appears as dated rows with a responsible role in each
• Known constraints are declared with the claim each one will limit
• No identifiable patient detail appears anywhere in the document

Questions students ask about this stage

Keep going