HLTH 6112 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 Governance and Public Policy, 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.

Worked reasoning: building the spine of a longer argument

When the remaining work concentrates into larger deliverables, structure carries more weight than sentences. Write the spine first: one line per section, each line stating the claim that section proves, in the order a skeptical reader would need them. For a policy argument the usual order is the problem and who owns it, the governing authority and its limits, what the evidence establishes, the options and the criteria used to compare them, the recommendation, and what implementation and later review would require. Read the spine on its own; if it does not argue, no amount of paragraph polish will make the finished work argue.

Then attach evidence to each line before drafting prose. Any line without evidence attached is either a research gap to close this Week or a claim to drop. This is also the moment to notice a section that exists only because it was interesting; if its claim is not needed by the spine, the words belong to a section that is.

Mapping dependencies before the calendar tightens

The close of a quarter fails on dependencies more often than on writing. List everything the remaining work needs from someone other than you: instructor clarification, feedback turnaround, group contributions, approvals, technical access, or a submission route you have not used before. Give each item the date by which its absence becomes a problem, then start the ones with the longest lead time immediately rather than in the order they will be needed.

Do the same for the artifact itself. Format conversion, file size, accessibility checks, and upload behavior all fail at the worst possible moment. Where the classroom allows it, run one end-to-end rehearsal with a partial draft so the final submission is the second time you have used the route rather than the first. Record what the route did, so the last Week holds no surprises.

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.

Closing the evidence gaps while there is still time

Take the spine and mark every claim with the status of its support: settled by primary authority, settled by interpretive evidence, thin, or missing. Work the missing and thin lines first, and set a stopping rule for each search so a single elusive citation cannot consume the Week. Where a claim cannot be supported, the honest moves are to narrow it, to reframe it as an open question, or to cut it entirely.

While the list is open, verify the material gathered earlier. Confirm that each instrument is still the current version, that each pinpoint still lands on the provision you cited, and that every reference entry matches the in-text attribution attached to it. Verification late in a quarter is fast; reconstruction is not, and reconstruction is what happens when a citation can no longer be traced back to the source that produced it.

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.

Reading the rubric row by row for a culminating deliverable

Larger deliverables usually carry more rubric rows, and the rows tend to map onto sections. Lay the rows beside the spine and mark which section satisfies which row. A row with no section is a gap in the plan; a section with no row is a candidate for cutting or for merging into a section that earns credit.

Then look at the weights. The heaviest rows deserve the earliest drafting and the most revision time, while the lightest rows should be closed with a checklist rather than with attention. If a row's wording is ambiguous at this stage, ask now, because ambiguity resolved after submission only helps the next course. Rows, weights, and levels vary by section and version, so your classroom rubric decides.

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.

Three Week 9 pitfalls and the fix for each

The first pitfall is drafting sections in the order they will appear rather than in the order of risk. The introduction gets three passes and the analysis gets one. The fix is to draft the heaviest reasoning section first and to write the introduction last, when there is finally something to introduce.

The second pitfall is discovering late that a controlling instrument was never read in full. A summary carried the argument, and the full text turns out to contain a condition that changes it. The fix is to schedule that primary reading now, before the prose hardens around a version of the rule that may not exist.

The third pitfall is leaving a dependency to the final days on the assumption that it is routine. Approvals, access, and other people's calendars are not routine at the end of a quarter. The fix is the dependency map above, with the longest lead time started first and a written record of what was requested and when.

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