HLTH 6051 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 Diversity, Human Rights, and Social Justice, 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.

Sequencing the assembly so the argument is settled first

Assembly fails when it starts with the document instead of the argument. Before any section is built, write the controlling claim of the culminating work in one sentence and check that every remaining piece serves it. Then order the build by dependency rather than by page order: the claim, then the analysis that establishes it, then the support that carries the analysis, then the background and front matter that orient a reader.

Background written first tends to expand until it fills the space, and then it survives revision because it took effort to produce. In this subject the piece most often left until it is too late is the standard: the sentence saying by what principle the situation is being judged. Write that sentence early and keep it visible while everything else is assembled around it. What the final work must contain, and in what form, is set by the live instructions and by your classroom rubric.

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.

Reading the rubric row by row while the sections are still moving

With sections in motion, the rubric is a map of where each one belongs. Build a two-column list: the row on the left, the section and paragraph that satisfies it on the right. A row with no address is either missing content or content buried where a reader will not credit it, and both are cheap to repair now and expensive to repair later.

Rows pointing at more than one section need a decision about where the reader should find the answer, since spreading a criterion thin across a document is a common way to lose points on work that already contains everything it needs. Check the mechanical rows in the same pass, including length, format, headings, citation style, and file type, because those are the ones most often repaired at the last minute under pressure. Row wording, weighting, and format requirements are decided by your classroom rubric.

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.

Making every source in the final list do a job

Assembly is where a reference list quietly stops matching its document. Work through the draft marking each in-text citation, then through the list marking each entry, and reconcile the two directions before anything else. Next, test every surviving source for function: it establishes the condition, it carries a step in the reasoning, it supports the proposed action, it supplies a definition, or it provides the standard being applied.

A source that fits none of those roles is padding and should come out. Where a central claim rests on one source alone, look for a second independent source now rather than during the final read. Check dates once more against any row that asks for current evidence. Assigned readings remain mandatory wherever the live activity requires them.

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.

Discussion and dependency work during an assembly Week

Assembly Weeks are lost on other people's clocks more often than on writing. If the live Week contains a discussion, treat the initial post as a rehearsal of the controlling claim: post the claim with its strongest support and use the replies you receive as an early review at no cost.

If any activity depends on a peer, a group, an approval, or a technical step, contact whoever controls it at the start of the Week and record what you are told, because a dependency discovered late cannot be compressed. Meanwhile, write the parts that do not need the missing input, so the waiting costs as little as possible. Reply counts, group requirements, submission routes, and deadlines are set by the live instructions for this Week, and an announcement can change them.

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.

Three Week 9 pitfalls and the fix for each

Pitfall one: beginning assembly before the controlling claim is settled, which produces sections that pull in different directions and a conclusion that cannot summarize them. The fix: write the claim in one sentence, read every section heading against it, and cut or rebuild whatever does not serve it.

Pitfall two: an expanding background section that pushes the analysis into the final pages, where the criteria carrying the most points get the least room. The fix: set a cap on the background before drafting it and hold the cap, moving detail into the analysis only where it earns a criterion.

Pitfall three: a synthesis section written from memory, which ends up carrying the strongest claims on the thinnest support. The fix: draft synthesis with the sources open and cite at the point of use, exactly as you would in any earlier section.

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.

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