NURS 3022 Week 11 planning manual

1. Capture the live Week 11

Open the registered classroom and create one row for every visible activity. Record its exact name and type, complete action verbs and questions, rubric or scoring criteria, points and course weight, due date and time zone, required and permitted resources, length and format, discussion reply rules, dependencies, attempt limits, submission location, and instructor announcements. Save the rubric version beside the working file.

2. State the Week's reasoning question

For Professional Nurses as Change Agents, the durable class question is: What evidence supports the judgment, what alternatives matter, and what remains outside the student's authority? Translate the live activity into one sentence that names the decision or explanation, the required evidence, the audience, and the expected output. If that sentence cannot be written, return to the prompt instead of guessing from a prior Week or third-party example.

3. Build the work in proof order

Move from cue to mechanism or standard, then to prioritized judgment, action, monitoring, and escalation. Use only de-identified authorized context.

Make a rubric-to-evidence matrix before prose: one row per criterion, the evidence or reasoning needed, where it will appear, what the student must personally do, and the test that will prove completion. Draft the highest-risk row first, not necessarily the introduction. Protect time for replies, calculations, format conversion, approvals, and the final upload.

Closing the record, not just the coursework

The final Week has two jobs, and the second is the one that gets skipped. The first is finishing the live work at full discipline: capture the closing activities fresh, because end-of-term instructions sometimes carry their own submission particulars exactly as the classroom displays them, then run the complete arc and the full quality gate one last time, resisting the pull to coast on familiarity. The second job is closing the record. After each final upload, open the submitted artifact from the classroom side, confirm the file, the timestamp, and the completeness of what was received, and save the receipt where it can be produced later. Then reconcile the gradebook line by line against those receipts as results post, and raise any discrepancy promptly, courteously, and through the official channel, with the receipt attached. The student personally performs every close-out step the section requires, and any final clinical, field, or administrative lane completes under the applicable Walden process with its status verified rather than assumed. A term is not closed when the last file uploads; it is closed when the record agrees with the work, and the days this verification takes are part of the course, not an epilogue to it.

Reading the rubric row by row

The last rubric read of the term works in both directions. Forward: read the final activity's live rubric with the full-term tally beside it, because closing work tends to grade the same row families the course has graded throughout, and the tally names the families where this student's points have historically leaked. Spend the final quality gate disproportionately on those rows; the last submission is the wrong place to rediscover a known weakness. Backward: when final results return, record them row by row in the ledger, completing the term's dataset while the context is still fresh. That closing entry turns the ledger into an accurate instrument for the next course rather than a partial history. If a final row result arrives without enough comment to interpret, a brief professional request for clarification is reasonable while the term's channels remain open. To the last upload of the last activity, the version of the rubric attached in the registered classroom stays the deciding document, and nothing remembered or archived outranks it.

4. Use evidence deliberately

Prefer current authoritative clinical guidance and peer-reviewed evidence appropriate to the question; distinguish guideline recommendations from patient-specific facts.

For every source, write a one-line use note before drafting. Distinguish direct evidence from interpretation and local observation. Quote sparingly, paraphrase from understanding, and cite the claim actually supported. If the activity requires current evidence, confirm publication dates and whether an older foundational source is still appropriate.

Archiving the source collection for the next course

Spend one closing session turning the term's evidence work into an asset that travels. Walk the source collection a final time and mark each entry as durable, likely to serve the program's later work, or course-bound, unlikely to be needed again; date the pass so the next course knows how stale the verification is. Keep the use notes attached, because an archived citation without its job description returns to being a bare search result. Alongside the collection, write a short methods memo in plain language: how sources were found and vetted this term, which authority types served which kinds of claims, what the recurring evidence feedback was, and which habits the next course should keep or change. The memo and the collection are the legitimate inheritance; submitted language is not, and the next course's activities will demand fresh authorship under their own instructions and their own rubrics in their own registered classroom. Archived evidence re-enters future work only through re-reading and re-framing against new claims, the same discipline that governed reuse inside this course, now applied across the course boundary.

5. Complete discussions and collaborative work

When the live Week contains a discussion, schedule the initial post by its own deadline and each reply by the response window. A useful reply does more than agree: compare evidence, apply the peer's idea to a different context, identify a boundary, or ask a focused question supported by the course material. The student writes and posts every contribution; a tutor may critique clarity and reasoning before submission.

6. Protect identity, practice, and research boundaries

Do not share protected health information, employer secrets, client identities, private peer content, assessment security material, or unauthorized research data. Clinical encounters, field hours, simulations, observations, interviews, group participation, proctored work, residencies, approvals, attestations, and original data collection must be completed and recorded by the student under the applicable Walden process.

7. Run the Week 11 quality gate

Check safety, scope, differential logic, contraindications, documentation, confidentiality, and every student-performed clinical requirement.

Then perform a literal instruction audit: every prompt part answered, rubric row visible, calculation reproducible, citation matched, heading and format correct, accessibility checked, file opened successfully, and confidential material removed. Compare against the current rubric, not a saved rubric from another section or term.

8. Submit and close the loop

The student performs the final upload or entry, opens the submitted artifact, confirms the timestamp and file, and saves the receipt. When feedback arrives, record each criterion result, instructor comment, correction, and lesson for Week 11. Contact the instructor or official support channel promptly for a missing, late, or technically failed submission.

9. Defend the learning before moving on

Before closing Week 11, the student should explain the live task, central claim or decision, strongest evidence, method or calculation, important limitation, and next action aloud without reading the submitted artifact. For a discussion, explain what the peer exchanges changed. For clinical, field, research, group, or proctored work, identify which parts the student personally performed and how they were verified. Any point that cannot be explained becomes the first short practice item for the next study session. This oral defense tests understanding more honestly than another formatting pass and turns the finished Week into preparation for Week 11.

Week 11 pitfalls and the fix for each

Pitfall one: relaxing at the upload. The moment the final file leaves feels like the finish, and attention leaves with it, but an upload that never registered, a wrong file, or a corrupted attachment discovered after the term closes is the most expensive small error the course offers. The fix is a verification ritual run after every final submission: open what was received, confirm timestamp and contents, save the receipt, and only then stand down.

Pitfall two: vanishing before the feedback lands. Final comments often post after the course has emotionally ended, and unread they are wasted, since they are the term's most considered assessment of the work. The repair is an appointment with the record: a calendared date to collect final results and comments, enter them in the ledger, and close the file properly.

Pitfall three: archiving artifacts instead of lessons. A folder of old submissions invites future reuse trouble and teaches nothing by itself. The fix is selective inheritance: carry forward the weekly routine, the completed ledger, the pruned source collection, and the methods memo, and leave submitted language behind. What any future course requires will be written in its own live classroom, and that classroom's rubric will decide, exactly as this one's did.

Source boundary

Walden's current catalog verifies this Course-Based class context, and the quarter calendar supports positional Weeks. The public catalog does not identify the student's Week 11 activities. The registered syllabus, classroom, rubric, announcements, instructor directions, and official policies remain controlling.

Week 11 questions