Late in NR-670 the writing turns back on the practitioner. The task is a reflective analysis mapped to graduate leadership competencies: what you did, what it demonstrates about capability you can now claim, and where the practicum exposed a limit you have not closed. Reflection at this level is analysis with yourself as the case, not a diary of a good experience. Your section may print this as NR 670 or NR670; 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 a graduate reflection has to demonstrate
A nurse leader finishing a care-coordination practicum sat with two documents side by side: the audit tool she had drafted in her third week, and the version the practice council had actually adopted in her sixth. Four fields had been cut and one added. Writing about why each change happened, who asked for it and what she conceded, produced a reflection that demonstrated negotiation, systems thinking and evidence-informed compromise, all without a single sentence about how much she had grown.
That contrast is the whole stage. Reflective writing that narrates is worth almost nothing at graduate level; reflective writing that analyzes evidence of your own practice is worth a great deal. The discipline is to treat episodes of your practicum as data, apply a competency framework to them, and reach conclusions about capability that a reader could check against the artifacts you produced. Mapping is the mechanism: name the competency in its published language, name the artifact or decision that evidences it, and say what the evidence does and does not establish.
Expect a written reflective analysis, often structured around a competency set or the program's stated outcomes, sometimes accompanied by a posted response about a turning point in the practicum. A named reflective model can help, and, as with any framework in this course, applying it beats citing it. What lifts a reflection from adequate to strong is almost always the same move: writing honestly about a decision that did not go well and analyzing it rather than apologizing for it.
The boundary that has governed every stage governs this one too, and it matters here because reflection sits so close to the clinical record. Your practicum hours, your activity log, your site paperwork and your mentor's evaluation are your own verified documents and are never drafted, reconstructed or estimated with help. A reflective analysis is an academic essay about experience you personally had, and the writing support that is legitimate is help in structuring, evidencing and sharpening that analysis, never in supplying the experience. Every encounter, colleague and case that appears is de-identified before it reaches the page, described by role and pattern rather than by person and episode.
The NR-670 Week 7 method, step by step
Six moves that turn practicum experience into an evidenced claim about capability.
-
Inventory your artifacts before you write a sentence
List what physically exists because of your practicum: an audit tool, a draft standard, a synthesis, a presentation, a revised workflow. Artifacts are the evidence base of a reflection, and writing from memory instead produces the vague prose this stage is notorious for.
-
Quote the competency in its published language
Take the wording from the professional or program competency set and put it on the page with its source and year. Paraphrase drifts toward whatever you happen to have done, which is exactly the drift a mapping exercise exists to prevent.
-
Attach one artifact to each competency and grade the fit
Say whether the artifact demonstrates the competency fully, partially or only in one dimension. A reflection that claims every competency at full strength is not read as accomplished, it is read as unexamined.
-
Analyze one decision that went badly
Describe the choice, the information available at the time, the outcome, and what you would do differently with reasons. Use a named reflective model if it helps, and keep the analysis on the decision rather than on your feelings about it.
-
Separate what you learned from what you delivered
Two different claims, often confused. The change may have stalled while your capability clearly advanced, or the project may have succeeded largely because the setting was ready. Naming which is which is the mark of a mature reflection.
-
End with a development plan that has checks
Two or three capabilities still short, each with the specific route to closing them and the artifact that would show it happened. Continue to grow as a leader is not a plan; presenting a business case to a governing council within a year is.
A layout and word budget for a competency reflection
Our frame for a reflective competency analysis, sized for roughly 1,300 to 1,600 words. It is our own outline rather than anything the university issues, and your section's rubric outranks it wherever the two disagree. Scale proportionally if your assigned length differs.
| Section | What belongs in it | Word target |
|---|---|---|
| Claim about capability | What the practicum established about your practice, stated before any account of what you did. | 90 to 120 |
| Artifact inventory | What exists because of this practicum, described briefly and neutrally, with its current status. | 170 to 210 |
| Competency mapping | Each competency in published wording, the artifact evidencing it, and an honest grading of the fit. | 380 to 460 |
| The decision that went wrong | The choice, the information you had, the result, and the revised approach with reasoning attached. | 260 to 320 |
| Learning versus delivery | What advanced in you as distinct from what changed in the system, and the evidence for each claim. | 190 to 240 |
| Development plan | Two or three remaining gaps, each with a route, a window and an artifact that would prove closure. | 190 to 240 |
Evidence craft for reflective analysis
Anchor every claim to something that exists. I developed stakeholder engagement skills is unverifiable. The audit tool was revised twice after review by the practice council, and the second revision removed two fields that could not be completed at the point of care, is evidence a reader can weigh.
Cite the competency set and the reflective model. Both are published documents with issuing bodies and years, and naming them puts your self-assessment on a standard rather than on your own authority. It also stops the mapping from quietly becoming a list of things you enjoyed doing.
Write about others by role and pattern. Your mentor, your council members and your colleagues appear as functions, never as identifiable individuals, and never as characters in a story with a moral. This is both a confidentiality requirement and better analysis, because roles generalize and personalities do not.
Keep first person working. Where the rubric permits it, first person in a reflection should carry decisions rather than emotions: I chose, I underestimated, I escalated, I conceded. Feelings can appear once, briefly, when they explain a decision. Sustained emotional narration is what pulls reflective papers into the low bands.
Do not overclaim the project's effect. If the outcome measure did not move, say so, and analyze why with the same rigor you would apply to someone else's project. A reflection that quietly upgrades a stalled implementation into a success contradicts your own measurement stage, and graders read the two together.
Five mistakes that cost points in this week's territory
- Chronology instead of analysis. A week-by-week account of the practicum answers a question the competency rows did not ask.
- Gratitude as content. Appreciation for a mentor is decent and it is not evidence; one sentence is generous, three paragraphs is a scoring problem.
- Every competency claimed at full strength. Uniform self-assessment reads as absent self-assessment, and the honest partial claim scores better.
- Feelings standing in for decisions. Challenging, rewarding and eye-opening describe an experience rather than a judgment you made under uncertainty.
- Identifiable people in the narrative. A recognizable colleague in a reflection is a professional exposure that no grade is worth.
Before you submit
- The opening states a claim about capability, not a summary of the practicum
- Every competency is quoted in published wording with a source and year
- Each competency claim is attached to an artifact that exists
- At least one claim is graded as partial, with the reason given
- One decision that went wrong is analyzed rather than apologized for
- The development plan names windows and artifacts, not intentions
- No colleague, mentor or patient is identifiable in any passage
Writing the NR-670 reflective analysis?
Send the rubric and your artifact list out of Canvas. A premium original draft of the written analysis comes back in 24 to 48 hours mapped to competencies in their published wording and evidenced from what you actually produced, and revisions run until the grade lands.