NURS 6910 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 Introduction to Palliative Care: Principles of Hospice and Palliative Care, the durable class question is: What does the prompt ask the student to understand, apply, compare, create, or evaluate? 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

Define the required concept precisely, apply it to the stated context, make the reasoning visible, and close with the implication the current rubric requests.

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.

4. Use evidence deliberately

Use the assigned readings first when required, then add current authoritative or peer-reviewed support matched to the claim.

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.

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

Check task completion, reasoning, evidence fit, examples, organization, citations, file rules, and the student's own explanation of the result.

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.

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.

Using an ethical spine to hold a longer deliverable together

Longer Week 9 work needs a spine, and the decision-making layer of this subject supplies a strong one. Where the readings treat autonomy, beneficence, nonmaleficence, and justice as competing rather than sequential obligations, that tension is a structure: state the obligation that dominates the situation the prompt names, state the obligation it is in tension with, show what the course's concepts contribute to resolving the tension, and state what remains unresolved. Related distinctions do similar work, including the difference between withholding and withdrawing an intervention, the difference between a decision made by the person and one made by a surrogate on their behalf, and the difference between an intention to relieve symptoms and any other intention. Choose one axis and run it the length of the deliverable. A long piece organized by a live tension holds together, while one organized as a topic sequence tends to sag in the middle.

Reading the rubric row by row on a multi-part deliverable

Larger assignments usually pair a rubric with a set of required parts, and the two do not map one to one. Build the map explicitly. List every required part down one column and every rubric row down another, then draw the links. Two failures surface immediately: a rubric row with no part assigned to it, which is a row you will lose, and a part with no rubric row, which is graded somewhere less obvious or absorbed into an overall row. Then assign a word budget per part in proportion to row weight rather than to your own interest, and draft the heaviest row first while attention is fresh. Your classroom rubric decides the rows, the parts, and the weighting, so build the map from the live document in your section and rebuild it if the instructor posts a revision.

Building a reference list that survives a long draft

At Week 9 scale, source control becomes a process problem rather than a memory problem. Keep one ledger row per source recording the claim it supports and the section it appears in, and update it while drafting rather than afterward. Apply the one-claim test, so every source is traceable to at least one sentence that would be unsupported without it. Balance the list by type deliberately, since a long deliverable resting entirely on single studies reads as thin and one resting entirely on guidance documents reads as secondhand; the mix should include primary work, at least one synthesis, and the assigned readings where required. Check the recency profile against whatever the classroom states. Finally, build the reference list from the ledger rather than from the draft, then verify in both directions so nothing is cited but unlisted or listed but uncited.

Three assembly failures in Week 9

The first is parts that each answer a slightly different question. Individually competent sections can still add up to an incoherent whole. Fix it by writing the single question the deliverable answers at the top of your working file and rereading it before each drafting session.

The second is the front-loaded introduction that promises material the body never delivers, usually because it was written first and never revised. Fix it by writing the introduction last, or rewriting it last against what the body actually contains.

The third is the homeless rubric row, satisfied nowhere because it fell between two sections. Fix it with the part-to-row map above, checked once before drafting and once before submission, since sections move during revision and a row that had a home in the outline can lose it in the draft.

Sequencing the last stretch so nothing lands on the deadline

Work backwards from the due time in the classroom's stated time zone and place real blocks. Reserve the final block for verification only and not for writing: format, citation check, file conversion, accessibility, length, and the upload itself, with the artifact reopened afterward and the receipt saved. Reserve the block before it for a full cold read against the prompt. Everything earlier is drafting and revision. Then identify every dependency that is not yours to control, including anything requiring approval, feedback, a group contribution, or a technical step, and move each one several days ahead of where it feels comfortable. Week 9 work rarely fails on writing quality. It fails when a step that needed someone else's time was scheduled as though it needed only yours.

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