NR-652 Week 1 Implementation Readiness: How to Write It

What NR-652 Week 1 asks for

A 140-bed nonprofit nursing home approved a post-hospital admission huddle in June: fifteen minutes within four hours of arrival, charge nurse, therapy, and whoever from social services is in the building. By the time the second course starts, the therapy manager who championed it has moved to a sister facility, the electronic record has been upgraded, and admissions after 4 p.m. have grown because a partner hospital changed its discharge pattern. Nothing in the proposal is wrong. Several things in it are now out of date, and the opening stage of a capstone practicum exists to find them before go-live rather than in the third week of data.

Readiness writing has a specific structure that distinguishes it from proposal writing. A proposal argues that something should be done. A readiness document verifies that it can be done now, and verification means a list of preconditions each marked confirmed, pending or lost, with a named owner and a date beside every one. Approval in hand or approval expected at the September committee are different states, and a document that blurs them will produce a launch that slips while everyone believes it is on schedule.

The stage also asks for a decision about the baseline. If your first course did not establish one, this is the last honest opportunity, because a baseline collected after staff know the intervention is coming is already contaminated by the attention the project has created. Write what your baseline is, what period it covers, how it was abstracted and by whom, and if it does not exist, say what you will use instead and what that substitution costs your later conclusions.

Finally, expect this stage to ask for a working schedule rather than a proposal timeline. The difference is granularity and ownership: not implementation in weeks two through six, but the training sessions on named dates with a named facilitator, the go-live date, the first audit date, and the point at which measurement begins to count. Where your section runs an opening discussion, write it as final copy; contributions do not reopen after submission in Canvas, and this is a stage where peers catch a precondition you forgot.

Boundary setting: the practicum is yours to perform and to record

A capstone practicum is real work at a real site, and none of it can be shortened by writing. The hours you spend, the log or timesheet that records them, activity or encounter documentation, site attendance verification, and any evaluation completed about you by a preceptor, mentor, sponsor or faculty member are your own record. They are never drafted, reconstructed or estimated with outside help, and the fact that a second-course practicum is heavier than a first-course one changes nothing about that.

What structured help legitimately supports is the written layer around the work: how a readiness document is organized so preconditions cannot hide, how a baseline description is written so a reader can judge its quality, how a schedule is built so it can be managed, and how the whole thing is aligned to a scoring guide. The site work is yours. The architecture of the document reporting it is teachable, and getting it right is the difference between a capstone that runs and one that improvises.

Every reference to a resident, patient, family member or staff member in anything you submit must be de-identified. In a capstone this matters more than earlier, because you will be handling real records and real names for months. Keep identifiers inside site systems, take only what you are authorized to take, work from aggregate or de-identified extracts, and write about roles rather than individuals. Where a single case is unavoidable to show a mechanism, alter every non-essential detail and say that you have.

The NR-652 Week 1 method, step by step

Six moves for turning an approved proposal into a launch you can defend.

1. Re-read the proposal against the site as it is today

   Take each assumption in the plan and mark it still true, changed or unknown. Staffing, systems, volumes, sponsors, competing initiatives and the physical location of anything your workflow depends on. Most capstone trouble is an assumption that quietly expired between the two courses.

2. Build a precondition list with owners and dates

   Every item that must be true before go-live, one line each, with the person accountable and the date it is expected. Approvals, access to data, printed materials, training delivered, a place in the shift routine, a named person to call when something breaks. Mark each confirmed, pending or lost rather than writing prose about progress.

3. Fix the baseline in writing before anyone is trained

   Period, source, abstraction method, who pulled it, and the measure definitions it was counted under. If a true baseline is not available, name the substitute, say why it is imperfect, and state exactly what it weakens in your later conclusions. This paragraph will be quoted back to you in the results stage, so write it carefully now.

4. Revise the plan where reality demands it, and log the revision

   Where a component no longer fits, change it and record the change: what it was, what it is now, why, and who agreed. A capstone with a documented amendment reads as managed. A capstone whose final report silently describes a different intervention from its proposal reads as something else entirely.

5. Convert the timeline into a working schedule

   Named dates, named people, named outputs, dependencies marked. Then work backwards from the last week of the session to find the real go-live deadline, because measurement needs weeks after launch and every day of slippage comes out of the measurement window rather than out of the term.

6. Write the launch risk paragraph while you can still act on it

   Two or three things most likely to stop go-live, each with the early sign you would see and the response you will take. Keep it short and specific. Written in the first stage, it is a plan; written in the fifth, it is an explanation.

A layout and word budget for a readiness document

Our frame for an implementation readiness submission at the start of a capstone practicum, sized for roughly 1,100 to 1,500 words plus the precondition and schedule tables. It is our own outline rather than anything the university issues, and your week's rubric outranks it wherever they disagree.

Evidence craft for readiness writing

State status, not effort. Training materials printed and delivered to the unit on a named date is a status. Training materials are in progress is a description of your week. Readiness documents are read for status, and a reader who cannot find one will assume the worst.

Attribute every approval to a person or body and a form. Verbal support from a manager, an item minuted at a quality committee and a signed authorization are three different levels of commitment. Write which one you hold. Overstating this at the start of a capstone is the error that becomes unrecoverable in the seventh week.

Keep the aim and the measure definitions verbatim from the approved proposal. Copy them rather than retyping from memory. A definition that drifts by one word between the two courses will produce a results section that cannot be compared with its own baseline.

Cite implementation literature for the readiness concept itself. Organizational readiness for change is a studied construct with published assessment approaches. Naming one and using its categories turns your list into an assessment, which is what a graduate rubric is looking for.

Date everything. Every status, every approval, every count. A readiness document is a snapshot and it is useless without the date of the photograph, especially when a grader reads it two weeks after you wrote it.

Five mistakes that cost points in this week's territory

• Restating the proposal instead of assessing readiness. A summary of what you plan to do is not a verification that you can do it now.
• Preconditions written as prose. A paragraph about progress hides the two items that are not done; a status list cannot.
• No baseline decision. Postponing this to the results stage guarantees an argument about what the numbers are being compared with.
• Silent plan changes. Amending the intervention without recording the amendment turns a managed project into an inconsistent one.
• A schedule that ignores the measurement window. Planning go-live for the fifth week leaves too few eligible events to say anything at all.

Before you submit

• The aim and measure definitions are copied verbatim from the approved proposal
• Every changed assumption since approval is named with its consequence
• Each precondition carries a status, an owner and a date
• The baseline is described with period, source and abstraction method, or its absence is stated
• Any amendment to the plan is logged with a reason and an approver
• The schedule works backwards from the end of the session to a real go-live date
• No resident, family member or staff member is identifiable anywhere in the document

Questions students ask about this stage

Keep going