NR-669 Week 1 Closure Plan and Project Restatement: How to Write It

What NR-669 Week 1 asks for

A student closing a project at a school-based health center inherits her own work from two prior terms: a follow-up recall process for children treated for acute otitis media, put in during the last session, running unevenly since. She knows roughly what happened. What she does not have is a single current statement of the project, and the gap between roughly and precisely is what this stage exists to close. Restating a project you have lived inside for months is harder than describing a new one, because familiarity hides the sentences a reader will need.

The written work at this stage usually has three parts. A restatement: the problem, the aim, the intervention as it currently exists after any adaptations, and the measures as they are actually being collected. A status account: which phases are complete, what data exist, what remains open, and what is at risk. And a closure plan: how the remaining collection, analysis, writing and presentation preparation will fit into the hours and weeks available, with the sequence explicit.

The reason this stage matters more than it looks is arithmetic. A manuscript-ready paper and a presentation to organizational stakeholders both have to be finished inside the same eight weeks, and both depend on a completed data window. A plan that leaves data collection open until week six leaves two weeks for two demanding artifacts, and that compression is visible in the quality of both. Sections that open with a discussion often ask you to post your closure risk. Post it as final copy, since Canvas responses do not reopen.

Where the boundary sits in a closing practicum. The 168 clinical hours are yours. The immersion, the presence at the organization, the relationship with whoever is mentoring you, the conversations that move a project forward, all of it is your own real work and cannot be delegated, shortened or reconstructed. Hour logs, encounter counts, site paperwork, signatures and any evaluation completed about you are your own record, and they are never drafted, reconstructed or estimated with help from anyone. What a manual supports is the written layer: how to restate a project precisely, how to write a status account that does not flatter itself, how to build a plan a reader can hold you to. Anything drawn from the site enters your writing de-identified.

The NR-669 Week 1 method, step by step

Six moves for restating a live project and planning its close.

1. Rewrite the aim as it stands now, not as it was approved

   Projects drift, and the aim that survived contact with the site is the one your paper has to defend. State population, measure, magnitude and window as currently operating, and note in one sentence where this differs from the original.

2. Describe the intervention in its adapted form

   Write what actually happens now at encounter level, including changes made during earlier phases. A paper describing the designed intervention when the site has been running a modified version is describing something that did not occur.

3. Inventory the data you already hold

   List each measure, the periods covered, the number of observations, the source, and any gap. Doing this in week one rather than week five is how students discover in time that a process measure stopped being collected in February.

4. Name the closure date for the data window and defend it

   Pick the date, say why it gives enough post-change observations to interpret, and hold to it. A window that stays open because more data always feels better is the single most reliable way to lose the writing weeks.

5. Sequence the two artifacts backwards from the presentation

   The stakeholder presentation depends on a settled result, and the paper depends on the same. Fix the presentation date first, work backwards to the analysis, and place the writing where it can actually happen rather than where the calendar has room.

6. Write the risks with responses attached

   Two or three realistic threats: a delayed data extract, a stakeholder audience that moves, a staffing change at the site. For each, the response you would use. Risk lists without responses are worry rather than planning.

A layout and word budget for a closure plan

Our frame for an opening closure document, sized for roughly 1,300 to 1,600 words. It is our own outline rather than anything the university issues, and your week's scoring guide outranks it wherever the two disagree.

Evidence craft for a project restatement

Restate for a stranger, not for your faculty. The reader of your final paper will not have seen the earlier phases, and the restatement is where you practise the introduction that paper will need. Assume no shared history, define every term once, and resist the shorthand that months on a project produce.

Carry forward citations that still support the argument. Evidence gathered in an earlier phase may have aged, and guidance may have been revised since. Check the key sources for newer editions and say in a sentence where anything has changed, with the issuing body and year in the text.

Report status in counts, not in adjectives. Post-change data collected for nine of the twelve planned weeks, covering fifty-eight eligible encounters, is a status. Data collection is going well is a feeling. The counted version is also what lets you judge whether the closure date you picked is defensible.

Distinguish adaptation from failure. When the intervention changed shape at the site, write what changed, when and why, in neutral language. Adaptation is normal and reportable; the problem arises only when the paper later describes an intervention nobody was running.

Keep the site and its people unidentifiable from the first draft. Role labels rather than names, practice type rather than location, and no dates precise enough to locate an individual encounter. A closure document circulates further than most coursework, and de-identification is easier to maintain than to retrofit.

Five mistakes that cost points in this week's territory

• Restating the original proposal. A description of the project as approved, rather than as it now runs, guarantees a mismatch between your methods and your results later.
• An open-ended data window. Collection that has no stated end date consumes the weeks the paper and presentation need.
• Status written in adjectives. Mostly complete and going well cannot be assessed, and they hide the gaps that will surface in the analysis stage.
• No named audience. A presentation planned before you know who is in the room gets built for nobody in particular and persuades accordingly.
• Risks without triggers. A risk register that does not say at what point you would act is a document nobody will consult when the delay actually happens.

Before you submit

• The aim is restated as it currently operates, with any drift acknowledged
• The intervention is described in its adapted, actual form
• Every measure appears with periods covered and observation counts
• A specific data closure date is stated and justified
• The stakeholder audience is named in role terms with what it can authorize
• Each risk carries a response and the point at which it triggers

Questions students ask about this stage

Keep going