NURS 6912 Week 9 planning manual

1. Capture the live Week 9

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 Symptom Management for the Hospice and Palliative Care Clinician, the durable class question is: What outcome is being chosen, for whom, under which constraints and trade-offs? 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.

Worked reasoning: the close as a scheduling decision

The closing stretch turns the class question inward again. What outcome is being chosen is the shape of the final result; for whom is the finishing version of you; the constraints are a calendar with less slack than it appears to have and any dependency involving another party; the trade-offs are between the items competing for the same hours. Build a single assembly map. List every remaining graded item with its calendar position, its dependency lane, and its critical path, meaning the step that has to happen before any other step can.

Mark which items require someone else, because anything requiring another party has a queue you do not control and belongs earliest. Mark which items are cumulative, meaning they consume the output of earlier work, and confirm that the inputs they need already exist in usable form rather than as intentions. Then sequence by risk rather than by due date. The last item to be scheduled should be the one you could finish quickly and alone. Nothing in this map is a claim about what your section assigns; the registered classroom supplies the actual remaining activities, dates, and rules.

3. Build the work in proof order

Convert theory into criteria, compare options against evidence and constraints, quantify material effects where possible, then state implementation, ownership, and measurement.

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.

Reading the rubric row by row across the closing stack

Read the remaining rubrics together rather than one at a time. Lay the rows side by side and look for three things. Overlap: rows asking for the same capability across items, which is where preparation pays twice, since building the proof shape once serves both. Escalation: rows whose wording is heavier than their earlier equivalents, often moving from apply to evaluate or from describe to justify, which tells you where the standard has risen. Uniqueness: rows appearing in only one item, which are the easiest to overlook precisely because they do not match the habits the quarter built.

Give the unique rows their own note. Then estimate effort per row rather than per item, because item-level estimates hide the fact that a single row can consume more time than the rest combined. If a row asks for something you have not yet done well this quarter, schedule practice for it before the item that needs it rather than learning inside a graded attempt. Rubrics differ by activity and by section, and the live versions in the registered classroom are the only ones that decide anything.

4. Use evidence deliberately

Combine relevant scholarly literature with current market, organizational, or policy evidence while labeling assumptions and protecting confidential information.

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.

Consolidating sources for the closing stack

Closing work usually needs fewer new sources and better use of the ones you have. Start by consolidating into one list, sorted by the job each source can do, with duplicates merged and dead entries removed. Then look at coverage against the remaining items rather than against the Weeks already finished. Where a remaining item needs support you do not have, note it now, because searching under deadline pressure produces the entries most likely to be misused.

Keep any late search targeted by writing the claim first and hunting support for that specific claim rather than for the topic. For a source carried since early in the quarter, reread the part you cite before citing it again, since a use note written many Weeks ago may not survive contact with a heavier activity. Watch currency, because material that met a recency rule at the start of a quarter is older now and the live activity sets the standard. Finally, confirm your evidence still covers both sides of the benefit and burden question this course keeps asking, since closing drafts drift toward advocacy as deadlines approach.

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 9 quality gate

Stress-test feasibility, incentives, ethics, risk, counterarguments, implementation ownership, and the metric that would show the decision worked.

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 10. Contact the instructor or official support channel promptly for a missing, late, or technically failed submission.

Three Week 9 pitfalls and the fix for each

Pitfall one: front-loading the item you enjoy. Interest is a poor scheduler, and the enjoyable item is rarely the one with the longest queue. The fix is to sequence by dependency and risk first, then let interest decide the order only among items that are equally safe.

Pitfall two: assuming inputs exist. Closing items often need something produced earlier, and intentions look identical to assets on a list. The fix is a verification pass in which you open each required input and confirm it is finished, current, and usable rather than merely remembered.

Pitfall three: leaving submission mechanics for last. File conversion, formatting, upload routes, attempt rules, and receipts all take time and all fail at inconvenient moments. The fix is a dry run on the least risky item: produce the file in its final format, confirm it opens cleanly, and confirm where and how it is submitted. Any rule about attempts, formats, or late work is set in the registered classroom, and the instructor or official support channel is where a technical failure gets resolved.

9. Defend the learning before moving on

Before closing Week 9, 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 10.

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

Week 9 questions