NR-643 concludes the scholarly project begun in the first concluding graduate experience and carries its own 72 clinical hours. The opening stage is re-entry: restating the project as it now stands, reconciling what changed while the session break ran, and converting a proposal into a document a working team could execute. Your section may print this as NR 643 or NR643; 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-643 Week 1 asks for
Six weeks off, and the handoff template pilot in the post-anesthesia care unit is not where it was left. Two of the three charge nurses who agreed to champion it have rotated. The analyst who was going to build the report has been pulled onto a system upgrade. The department reorganized its shift structure, which changes the denominator on the measure. None of that is failure. It is what happens to any project that lives inside a working department, and the first written task of a capstone stage is to say so accurately and rebuild the plan around it.
The deliverable at this stage is usually a restated project document: purpose, aims, scope, stakeholders and measures updated to current reality, plus the changes from the proposal made explicit rather than silently absorbed. Some sections call this a charter, some a revised proposal, some a project plan. The genre is the same. It is a short, dense, executable document written for people who will act on it, which is a different register from the scholarly sections that surrounded it in the first course.
The register shift is the thing most students underestimate. A proposal argues. A charter commits. Sentences get shorter, hedging comes out, and every line answers a question an implementer would ask: what exactly, by when, with whose help, measured how. The scholarly apparatus stays in the paper that surrounds it, but the charter itself should read like something you could put in front of a nurse manager on a Tuesday.
Expect the restated plan plus possibly a posted summary where classmates catch up on each other's projects. Posts do not reopen once submitted in Canvas, so restate the project accurately rather than optimistically, because the version you post is the version people will remember when you report results in six stages.
The NR-643 Week 1 method, step by step
Six moves for restarting a project on paper.
-
Write a change log before you rewrite anything
Every difference between the proposal and the present: people, systems, timelines, data availability, organizational priorities. The log is not for the reader yet. It is what keeps the rewrite honest.
-
Reconfirm your stakeholders in the present tense
Who currently holds each role, who has actually agreed to what, and what has lapsed. Then write the stakeholder section from what is true now rather than from the table you built last session.
-
Cut the aims to what the hours can carry
Seventy-two hours across eight stages is a real constraint. If the plan carried three aims and one is now impossible, remove it explicitly and say why rather than letting it fail quietly in the final paper.
-
Convert argument into commitment
Rewrite each aim in the imperative shape a plan uses. Deliver, present, analyze, produce. Then attach the date window, the person whose participation it depends on, and the artifact it ends in.
-
Rebuild the measures against current data reality
If a denominator changed, the measure changed. Restate operational definitions in full rather than referring back to the earlier document, because a charter has to stand alone.
-
Write the changes into the paper as reasoning
One short passage saying what shifted and why the revised plan is better supported. Silently different documents read as carelessness. Explicitly revised ones read as project management.
A layout and word budget for a revised project charter
Our frame for a restated project document, sized for roughly 1,100 to 1,400 words. It is our own outline rather than anything the university issues, and your week's rubric outranks it wherever they disagree.
| Section | What belongs in it | Word target |
|---|---|---|
| Purpose and current problem | The problem restated in present conditions, with any change in its magnitude or urgency noted. | 160 to 200 |
| Scope in and out | What this phase will do and, in its own sentences, what it explicitly will not. | 140 to 180 |
| Aims and deliverables | Two or three aims in committing language, each with a window, a dependency and a named artifact. | 240 to 300 |
| Stakeholders now | Current role holders, what each has agreed to, what has lapsed, and what you still need to secure. | 210 to 260 |
| Measures restated | Operational definitions written out in full against current data availability and current denominators. | 200 to 250 |
| Changes from the proposal | What differs from the first-course document and the reasoning behind each change. | 170 to 210 |
Evidence craft for a charter document
Write agreements as agreements, not intentions. The unit manager has confirmed release time for two education sessions is a statement of fact. Support is anticipated is a statement about your hopes. Readers of project documents calibrate on exactly that distinction.
Carry the evidence forward by reference, not by repetition. A charter does not re-argue the literature. It cites the synthesis that justified the design in a clause and moves on, so that the reader gets a plan rather than a second copy of the proposal.
Update numbers rather than reusing them. A baseline figure from the previous session is now several months old, and in a moving department that matters. Either refresh it or state the period it covers and say plainly that it is the most recent available.
Name the dependency for every dated commitment. If a deliverable requires an analyst, a committee slot or a manager's approval, the sentence containing the date should also contain the dependency. That single habit prevents most of the timeline failures in practicum projects.
Keep the register consistent through the document. Charters slide back into proposal voice around the third page, usually at the measures section. Read the finished document for hedging words and remove them wherever a commitment is being made.
Where help stops in a practicum course
NR-643 is a mentored capstone practicum carrying 72 clinical hours, and the boundary around clinical work is absolute. Your hours, your log, your activity and encounter records, your mentor's evaluation of you and every signature attached to any of it are your own record of your own work. They are never drafted, reconstructed, estimated or completed with outside help. Nothing on this page is a route to producing documentation that a mentor, a site or the university verifies.
What is teachable is the written layer: how to restate a project so it commits rather than argues, how to build a stakeholder section from current fact, how to write operational definitions that stand alone, how to document a change as reasoning. What has to come from you is the knowledge of what actually changed while you were away, because that comes from conversations only you can have. A charter written from assumptions about the setting collapses the first time somebody in it reads a sentence about themselves.
De-identification governs this document too, even though it reads as administrative. Stakeholders appear by role rather than by name. Any illustration of the problem is written at process level, with no patient names, record numbers or dates of service, and no combination of unit, condition and timing that would let a colleague identify a person.
Five mistakes that cost points in this week's territory
- Resubmitting the proposal. Copying last session's document forward ignores everything that moved and produces a plan that is already wrong on submission.
- Aims that outgrew the hours. A capstone stage with 72 hours cannot deliver a plan scoped for a funded program, and the arithmetic is checkable.
- Lapsed agreements written as current. A champion who has rotated off the unit has not agreed to anything, and claiming otherwise is a fabricated fact.
- Measures referred to rather than restated. A charter that points back to another document cannot be handed to anyone, which defeats the genre.
- Silent revision. Changes absorbed without explanation make the whole project look like it drifted rather than adapted.
Before you submit
- The problem is restated in present conditions rather than copied forward
- Scope includes explicit exclusions in their own sentences
- Every aim carries a window, a dependency and a named artifact
- Stakeholders reflect who currently holds each role and what is actually agreed
- Operational definitions are written in full and match current denominators
- A changes passage explains each difference from the earlier proposal
- Hedging language has been removed from every commitment
- No names of individuals and nothing patient-identifiable appear anywhere
Restarting the capstone project in NR-643?
Send the rubric and your first-course proposal out of Canvas. A premium original draft of the written layer comes back in 24 to 48 hours rewritten into charter register with changes documented as reasoning, hours and evaluations left entirely to you, and revisions run until the grade lands.