NRNP 6567 Week 10 planning manual

1. Capture the live Week 10

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 Critical Care Immersion: Advanced Skills and Patient Management, 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.

Worked reasoning: revision as re-derivation

At this stage revision means re-running the reasoning, not resurfacing the prose. For each weakness the accumulated feedback record names, go back to the cue and walk the chain again, mechanism or standard, prioritized judgment, action, monitoring, escalation, and let the corrected understanding produce new sentences. Patching adjectives onto an ungrounded judgment leaves the ground missing; re-derivation replaces it. Where feedback exposed a boundary error in written reasoning, a judgment stated beyond the student's authority or an escalation condition left unwritten, that repair goes first, because in this discipline the boundary errors are the expensive ones.

Run each repair through a three-step loop: diagnose the gap class, correct it in the draft under revision, then re-test on fresh material, a different paragraph or a spoken explanation, to confirm the fix lives in understanding rather than in one edited sentence. Keep a change log while revising: what changed, why, and which comment or rubric row prompted it. The log proves the revision was directed rather than cosmetic, and it doubles as the method summary this Week is supposed to hand to Week 11.

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.

Repairing the reference layer

Late-course revision includes the sources, because the reference layer has been accumulating its own debts. Audit the near-final drafts' citations against the feedback record and the standing bank: re-verify aged guidelines and replace superseded editions, swap stretched sources for fitted ones, and remove or put to work any entry that only decorates a claim. An entry that cannot be attached to a working sentence does not belong in a closing reference list.

Check paraphrase fidelity specifically in revised passages. Revision is where drift enters, since sentences move away from the source that originally anchored them; re-read each revised claim beside its source line before calling the passage done. Then fix the mechanical layer once, centrally: style edition, entry punctuation, in-text and list agreement, corrected in the evidence bank so every remaining draft inherits the repair instead of each draft being fixed alone. This pass is cheap in Week 10 and expensive inside Week 11's upload window, which is the entire argument for doing it now.

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 10 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.

Reading the rubric row by row

The Week 10 read is a self-scoring exercise. Take the near-final draft, open the live rubric, and honestly assign the column each row currently earns, in writing. Every row self-scored below the top column gets two sentences: what exactly is missing, in the row's own vocabulary, and when the repair is scheduled. The discipline is refusing the halo: a draft that is strong overall does not lift a weak row, because graders score rows, and self-scoring only works when it imitates that indifference.

Give a second pass to the row families the course's feedback record has repeatedly marked, since recurring weaknesses survive first inspections by habit. Where a row was historically lost to literal misses, re-check it against the printed requirement rather than memory. End the read with a single ordered list: remaining work ranked by row weight multiplied by distance from the top column. That list, not general unease, is the Week 10 work plan, and everything on it should be small enough to finish before the close because the mapping Weeks already did their job.

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 10, 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 10 pitfalls and the fix for each

Pitfall one: revising only what was commented on. Instructors sample; they mark instances, not inventories, and uncommented weaknesses of the same class usually exist elsewhere in the draft. The fix is to treat every comment as naming a class of error and sweep the entire draft for the class, using the gap taxonomy the class guide already provides.

Pitfall two: introducing new errors during late edits. Moved sentences orphan their citations, renumbered sections break cross-references, and reformatting disturbs literal rows that were previously safe. The fix is to re-run the literal quality gate on every touched section after each revision session, treating edited text as new text rather than as improved text.

Pitfall three: equating longer with better and inflating the draft toward its limits. Added words dilute the scored ones unless a rubric row actually calls for the depth. The fix is to revise toward the rubric's demands and nothing else: where a row wants more reasoning, add reasoning; where no row wants anything, cut, and let the remaining sentences carry more weight each.

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 10 activities. The registered syllabus, classroom, rubric, announcements, instructor directions, and official policies remain controlling.

Week 10 questions