NURS 6912 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 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: revision as a decision, not a rewrite

Revision this late is a resource allocation problem, and the class question frames it well. The outcome being chosen is which weaknesses get repaired; the party it is chosen for is a reader scoring against rows; the constraints are the hours left and the work still ahead; the trade-off is that time spent perfecting one passage is time not spent on another item's weakest row.

Triage in three bands. Band one holds defects that break a requirement: a missing required part, an unsupported central claim, a mechanical error that violates a stated rule. Repair these first regardless of how small they look, because they cost more than their size. Band two holds depth defects: reasoning that stops one move early, a criterion applied unevenly, an implication left unstated. This is where genuine improvement lives and it takes real time. Band three holds preference edits, meaning changes that make the prose feel better without changing what a row would score, and band three happens only if the first two bands are finished. Write the triage list before touching the draft, since revision without a list becomes rereading. Which requirements apply is set by the live activity and the rubric in the registered classroom.

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 during revision

Revision reading is different from drafting reading. Take each row and try to fail it. Instead of asking whether the draft addresses the row, ask what a careful reader could point at to say the row is not met, then go looking for that thing. Ask where the required part is thinnest rather than whether it exists. Ask which claim carries the least support rather than whether support is present anywhere. Ask which sentence a reader would call description in a row that asked for evaluation. This adversarial pass finds more than a confirmation pass does, because confirmation reading stops at recognition.

Work the rows in weight order and stop when the remaining ones are all clean or all cheap. Then run one structural check no row states directly: does the order of the response match the order a reader needs in order to follow the reasoning, and does each section still earn its place. Reorganization this late is expensive, so do it only where the current order actively obscures the argument. Row wording and weighting come from the live rubric, which is the standard your revision is aiming at.

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.

Repairing a reference list under revision

Reference work is the most reliably recoverable ground in a late revision, because the standard is objective. Run four sweeps, each in one direction, and do not mix them. Sweep one goes from the text to the list, confirming every in-text citation has an entry. Sweep two goes from the list to the text, removing entries that never appear, since an unused entry is an error rather than a bonus. Sweep three checks each pairing for fit, asking whether the source supports the sentence it is attached to rather than the paragraph's general topic, which is where earlier drafting shortcuts surface. Sweep four checks mechanics against the required style: element order, dates, capitalization, and the details judged for accuracy rather than argument.

If a claim turns out to be unsupported, the fastest honest repair is usually to weaken the claim to what you can support rather than to hunt for a new source in the time remaining. Where a source has been carried a long way from its original purpose, either restate the claim to match it or retire it. The current activity decides source requirements, recency, and citation style, so check the live instructions before assuming the rule you used earlier still applies.

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

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.

Three Week 10 pitfalls and the fix for each

Pitfall one: revising by rereading. Opening the draft and starting at the top produces careful attention to the first pages and very little after them, and the first pages are usually the strongest already. The fix is to revise by list rather than by sequence, working the triage bands in order and entering the document at the point each item names.

Pitfall two: rewriting instead of repairing. A weak passage tempts a fresh draft, and a fresh draft introduces new problems into work that had already been checked. The fix is a rule: rewrite only when the defect is structural, meaning the passage answers a different question than the row asks. Otherwise repair in place with the smallest edit that removes the defect.

Pitfall three: leaving no verification time. Revision expands to fill whatever exists, and the checks that catch requirement failures happen last. The fix is to set the stop time before starting, reserve the final block for the instruction and rubric audit rather than for improvement, and treat that block as unavailable for anything else. The live instructions and rubric are what that audit compares against.

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.

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