HLTH 6405 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 Ethics and Social Justice, the durable class question is: Which authority, duty, conflict, stakeholder, and consequence control the decision? 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

Name the governing rule accurately, separate law from policy and ethics, apply it to the facts, compare defensible options, and commit to a justified recommendation.

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 primary authority where the task permits, then current scholarly or professional interpretation; never cite a summary as if it were the controlling rule.

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

Verify jurisdiction, date, definitions, exceptions, stakeholder effects, counterarguments, and whether the recommendation exceeds the evidence.

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.

Assemble a defensible position from the whole term

Week 9 is an assembly problem before it is a writing problem. Lay out every element the closing work may need and confirm that each exists in finished form: the governing authority with its jurisdiction line, the facts with sources, the framework applied rather than named, the stakeholder map with the conflict stated, the options compared on a stated basis, the recommendation with an actor and an instrument, the limits sentence, and the counterposition answered. Anything missing from that list is a drafting task with a time estimate rather than a worry.

Then order the tasks by risk instead of by document order. The highest risk element is usually the one where evidence is thinnest or authority is least certain, and it should be drafted first while there is still room to change position. Introductions, transitions, and summaries are the lowest risk and belong last, because they describe a document that does not yet exist.

Assembly also means dependencies. Anything requiring another person or an institutional step, such as a group contribution, an approval, a required reply, a proctoring arrangement, or a particular submission route, belongs in its own lane with its own date, because a polished draft cannot compensate for an unfinished institutional step. Confirm the submission route now rather than on the day.

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

Late-term work often has more than one part, and a rubric may score the parts unevenly. Build a two-way map with rows down the side and document parts across the top, marking every cell where a row will be answered in a part. Empty rows are gaps. Rows answered in three places are usually a sign that the criterion is being restated rather than developed.

Weight the remaining time by the points a row carries where the rubric shows weights, and by the difficulty of its verb where it does not. Then run a coverage pass over the assembled draft, reading only for rows rather than for flow, and record the exact location that answers each one. The rubric in the registered classroom decides the rows, the parts, and the weights, and a late-term rubric is often the one most likely to have been revised.

Auditing the reference list you are about to submit

An audit is a check for correspondence, not for length. Every entry in the reference list should appear in the text; every citation in the text should appear in the list; every claim about what a rule requires should cite the rule rather than a description of it; every empirical claim should cite the study rather than a summary of it. Check the citation style the live activity requires and apply it consistently, including to government documents and legal materials, which is where errors cluster.

Then run a use audit. For each source, name the sentence it carries. Remove anything carrying nothing, and replace it if the removal leaves a claim unsupported. Verify quotations against the original text word for word, especially operative language from an authority, because a misquoted rule is a substantive error rather than a formatting one.

Three assembly pitfalls and the fix for each

The first is the recommendation that appears for the first time in the conclusion. The reader meets a position no earlier paragraph built. The fix is to state the recommendation early and let each analytical section supply one of its supports, so the conclusion confirms rather than announces.

The second is the unanswered strongest objection. Late drafts often answer a weak version of the opposing view because the strong version is inconvenient. The fix is to write the strongest objection in the words its holder would use, place it where it does the most damage, and answer it there. An answered objection strengthens a recommendation more than another supporting citation does.

The third is the compressed last mile. Format conversion, accessibility checks, file naming, submission routes, and receipt confirmation are budgeted as minutes and take an hour. The fix is a scheduled block for them, plus a standing rule that the student opens the submitted artifact after upload, confirms the file and the timestamp, and saves the receipt.

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