The seventh stage of NR-670A asks a harder question than it looks: not what the practicum was like, but what it proves about your capability and where it exposed a limit you have not closed. A competency reflection is an evidenced argument in which your own practice is the case under examination, and the evidence is the set of documents you produced. Your section may print this as NR 670A or NR670A; 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 closing reflection has to establish
A nurse leader finishing an emergency department observation practicum laid two documents side by side at this stage: the escalation criteria she had drafted in her fourth week, and the version that came back from the medical director with two thresholds changed and one whole category removed. Writing about why each edit happened, what argument she had made for the removed category, and why she had not anticipated the objection, produced a reflection that demonstrated negotiation, clinical reasoning and the limits of her own preparation at once. A reflection built on remembered feelings could not have reached any of it.
This is the point where students most often revert to undergraduate habits. Reflection in a concluding graduate experience is not narration and it is not gratitude. It is analysis with a defined object, and the object is the fit between published competency expectations and what your own artifacts show. That means the writing runs in a specific direction: quote the competency in its published language, point at a document you produced, and assess the match candidly, including where the match is partial. A reflection that claims every competency was fully achieved is not read as accomplished; it is read as unexamined.
The most valuable single section in this stage is usually the analysis of a decision that went wrong. Something in every practicum does: a stakeholder consulted too late, a definition that had to be rewritten after the first audit, a step designed for a shift pattern that does not exist at night. Writing that honestly, with what you knew at the time, what you decided, what happened and what you would do differently, demonstrates the reasoning capacity the course is built to develop. Students protect themselves from it and lose points doing so, because a flawless account has nothing in it a grader can score as insight.
The practicum boundary continues to govern this stage completely. Your 144 hours, the hour log, activity counts, site paperwork and the mentor evaluation are your own record of work you personally performed, and none of them is drafted, reconstructed or estimated with outside help. A reflection is written after the practicum has genuinely happened and is about work you actually did; nothing here manufactures experience, and no artifact is described that does not exist. What the written layer supports is the analysis: how to map competencies to evidence, how to write about a failure without either minimizing or dramatizing it, and how to build a development plan with checks in it. Every person, case or incident appearing in the reflection is de-identified, described by role, with no dates and no detail a colleague could trace.
The NR-670A Week 7 method, step by step
Six moves that build a competency argument out of documents you already produced.
-
List your artifacts before you write a single reflective sentence
The scope statement, the assessment, the problem analysis, the synthesis, the drafted standard or tool, the plan, the measurement design, anything you presented. This inventory is the evidence base of the whole piece, and reflections written without it drift into recollection because there was nothing concrete to point at.
-
Quote each competency in its published wording, with a source
Graduate nursing competencies exist as published documents with issuing bodies and years. Paraphrasing them lets the wording drift toward whatever you happen to have done. Quoting them, briefly and with attribution, fixes an external standard your evidence then has to meet.
-
Attach one artifact to each competency and judge the fit out loud
Name the document, say what in it demonstrates the competency, and grade the match honestly as fully demonstrated, partially demonstrated, or exercised only in a limited form. Distinguishing the three grades honestly is what most reliably separates the top scoring band from the middle.
-
Analyze one decision that went badly, in full
The choice, the information you actually had at the time, what resulted, and the specific thing you would change. Resist both minimizing and over-apologizing. A clean analytic account of one misjudgment is worth more than three paragraphs about how much you grew.
-
Separate what you delivered from what advanced in you
These are different claims and rubrics often score them in different rows. The delivered column holds artifacts and outcomes. The advanced column holds the capability you now have, which has to be argued from evidence rather than asserted, and the honest answer is sometimes that a strong deliverable taught you very little.
-
End with a development plan that could be checked
Name the two or three capabilities that are still short, and give each one an action, a window it closes in, and the artifact that would prove closure. Continue to grow as a leader closes nothing. A named certification, a committee role carrying a stated deliverable, or a specified piece of writing does.
A layout and word budget for a competency reflection
The frame our tutors use for a reflective submission of roughly 1,200 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 |
|---|---|---|
| The claim about capability | The capability the practicum established, asserted at the top and ahead of any narrative of events. | 90 to 120 |
| Evidence inventory | The documents and products the practicum generated, listed plainly so every later claim has something to point at. | 130 to 170 |
| Competency mapping | Each competency quoted with its source, matched to an artifact, and the fit graded honestly rather than asserted. | 380 to 460 |
| The misjudgment, examined | One decision that went wrong: what you knew, what you chose, what followed, and the specific change you would make. | 230 to 280 |
| Delivered against advanced | What the setting received from the work, set beside what genuinely changed in your own capability. | 180 to 220 |
| Development plan with checks | Two or three remaining gaps, each with an action, a window and an artifact that would demonstrate closure. | 190 to 240 |
Evidence craft for reflective analysis
Every claim about yourself points at something you made. I developed stakeholder skills is unscoreable. The stakeholder analysis in my plan identified a cost to the night shift that the first draft had missed, and the revision changed the sequencing, is the same claim with evidence under it.
Quote the competency rather than restating it. Restated competencies quietly shrink to match what you achieved. The published wording holds still, and a partial match against fixed wording is more credible than a full match against wording you adjusted while writing.
Report the result of your work accurately, including the flat one. Where your outcome measure stayed flat, report the flat result and interrogate it as you would a stranger's project. Capstone reflections are not graded on whether the project succeeded. They are graded on whether you can read your own result without flattering it, and a candid account of a null finding is genuinely stronger evidence of leadership judgment than a favorable one described uncritically.
Keep appreciation brief. Gratitude toward a mentor is decent and it is not evidence. One sentence is generous; three paragraphs is a scoring problem, because those words came out of the analysis the rubric was actually looking for.
Give feelings a job or leave them out. Emotion is admissible when it explains a decision: unease about a definition prompted the second reviewer check. Emotion is inadmissible as content in itself. Words like challenging and eye-opening label an experience without examining it, and they sit exactly where the analysis belonged.
Five mistakes that cost points in this week's territory
- Chronology instead of analysis. A running account of the placement, week by week, answers nothing the competency rows asked.
- Competencies asserted with no artifact attached. Every unsupported claim is a row a grader has to mark down, however true the claim happens to be.
- A practicum in which nothing went wrong. Read as incomplete self-examination rather than as an unusually smooth placement.
- Gratitude occupying the analytic space. Warm closing paragraphs are the most common way strong students lose points in this exact stage.
- A development plan nobody could check. Keep learning and stay current close no gap and demonstrate no planning capability.
Before you submit
- The capability claim appears before any narrative of events
- The artifacts you produced are inventoried explicitly
- Each competency is quoted with its issuing body and year
- Every competency claim points at a named artifact
- Partial achievement is stated as partial rather than rounded up
- A misjudgment is examined in full rather than noted in passing
- Each development goal has an action, a window and an artifact
- No individual, case or incident is identifiable
Writing the NR-670A 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 revisions run until the grade lands.