NURS 4106 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 Patient Safety and Quality Improvement, 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.

Revision as diagnosis, not polish

Reconciliation week separates two activities that usually blur: editing sentences and repairing reasoning. Start from the feedback ledger, not from the draft. Classify every recurring comment from the term into one of the course's gap types: understanding, task interpretation, reasoning, evidence, communication, format, or process. The classification decides the repair. A reasoning gap is not fixed by smoother prose; it is fixed by rebuilding the chain, cue to mechanism to judgment to action to monitoring, for the passage the feedback flagged. An evidence gap is not fixed by adding citations; it is fixed by matching claim strength to source strength, sentence by sentence. A process gap, late drafting, a wrong file, a missed reply window, is fixed on the calendar, not in the document.

Then revise the live work one criterion at a time rather than one page at a time, holding a single rubric row in mind through a full pass of the draft. Criterion passes catch what read-throughs miss, because a reader following the story forgives exactly the gaps a grader scoring the row will not. Save sentence polish for the end; it is real work, but it is the cheapest kind of improvement left this late in the term, and the diagnostic work above it is not.

Reading the rubric row by row

This week's read is a reconciliation scorecard. Take the live rubric for the remaining submission and grade your own draft against it, honestly and in writing: for every row, mark met, partial, or missing, and record where in the draft the proof sits. Two disciplines keep the exercise honest. Judge from the row's top performance language, not from effort; a section rewritten three times can still sit at partial if the row asks for something it does not contain. And require a location for every met, because a met without an address is usually a hope. Fix the partials first: they are cheaper than the missings, more numerous, and mostly created by drift between drafting sessions rather than by misunderstanding. Where a row stays stubbornly unclear after this much course experience, that is a legitimate, specific question for the instructor through the official channel, asked this week while the answer can still shape the submission. The registered rubric stays the authority; the scorecard just forces your reading of it to become explicit before the grader's reading becomes final.

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.

The citation reconciliation pass

Heavy revision breaks citations quietly. A sentence gets sharpened until it claims more than its source shows; a paragraph gets split and its citation stays with the wrong half; a deleted section orphans a reference-list entry; a moved claim leaves its support behind. After substantive revision and before the quality gate, run a dedicated reconciliation: reread every source-bearing sentence in its revised form and confirm the source still supports exactly the claim the sentence now makes, at the strength it now makes it. Downgrade or re-support anything that drifted during the rewrite. Then sweep the mechanical layer: author spellings, years, locators where the style requires them, reference-list completeness in both directions, one citation style applied evenly from the first page to the last. If revision has hollowed out a source, cited once and doing no analytical work in the revised argument, either give it work or remove it; the reference list should describe the argument that exists now, not the argument the draft used to make. The pass takes minutes when done deliberately, and it prevents the small avoidable losses that cluster in exactly the weeks when points matter most.

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.

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: cosmetic revision, rewording sentences the feedback never complained about while the flagged reasoning stands untouched. It feels like progress and changes nothing a grader will score differently. The fix: open each revision session from the ledger's diagnosis, change the reasoning where the reasoning failed, and only then allow yourself the polish.

Pitfall two: revision-induced breakage, where heavy edits damage citations, cross-references, numbering, or formatting that was previously correct, so the draft improves analytically while degrading mechanically. The fix: schedule the reconciliation pass after every substantive revision round, and check the final file against the rubric's format rows one last time before upload.

Pitfall three: version confusion at submission, the classic wrong-file upload after a week of parallel drafts. The fix: one working file with dated saves, a final filename that cannot be mistaken for anything else, and the standing receipt habit: open the submitted artifact from inside the classroom, confirm it is the right version, and save the confirmation before closing the week.

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