HLTH 6112 Week 11 planning manual

1. Capture the live Week 11

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: defending the recommendation one last time

Before the final work leaves your hands, argue against it. Take the recommendation and write the strongest objection a reader holding authority would raise: the rule does not reach this far, the evidence does not carry this much weight, the cost falls on a party the response never named, or a simpler option achieves most of the benefit for less. Then answer each objection in a sentence, or change the recommendation. A conclusion that has survived its best objection reads differently from one that has never met one.

Finish with the accountability line the course method implies: who decides, under what authority, by when, and how anyone would later know whether the decision worked. A closing that names a review or monitoring step turns a recommendation into something a governing body could actually adopt, and it is the last opportunity in the course to show the reasoning pass doing real work.

Verifying the close and preserving the method

Closure has two halves. The first is verification: every part of the live final work answered, every rubric row visible, every citation traceable, confidential material removed, the file opened after upload, the timestamp and receipt saved, and any remaining reply or participation requirement met on its own schedule. Nothing in this half is intellectual, and all of it is where finished work is lost.

The second half is preservation, and it is what makes the next course cheaper to run. Keep the method, the checklists, the terms list, and the criterion-level feedback ledger. Keep the source log, cleaned of everything that never earned its place. Do not keep sentences for reuse; a later prompt requires new reasoning, new evidence, and new authorship even when the concept returns. Grades, designations, approvals, and progression remain with Walden and the instructor.

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.

Leaving the quarter with a source library worth reusing

A policy source library has two halves that age differently. Instruments change, since statutes are amended, regulations are revised, and guidance is withdrawn and reissued, so store the citation and the version rather than a saved copy you will later mistake for current. Research does not change, but its relevance does, so store the method note, the population, and the limitation beside the reference so the next course does not have to read it again from scratch.

Sort what remains into what governed, what informed, and what only oriented, then keep the first two. Note beside each entry the claim it supported, because the fastest route back into a source months later is the question you originally asked of it. That note is the whole difference between a folder of files and a working library.

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 11 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 at the final submission

The last rubric read is literal. Open the rows beside the finished artifact and touch each one in order, marking the exact page, heading, or paragraph that satisfies it. Do not mark a row from memory of having written it; find it. Rows that cannot be located in the artifact are unmet, and this is the last moment at which that discovery costs nothing.

Give the process rows the same treatment as the content rows: file type, naming, length, style, submission location, attempt limits, and any reply or participation requirement closing on a different schedule from the file. A finished artifact submitted through the wrong route or in the wrong format is still an unfinished submission. Rows, levels, and weights 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 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 11, 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.

Three Week 11 pitfalls and the fix for each

The first pitfall is submitting without opening the submitted file. Uploads truncate, convert, and occasionally carry the wrong version, and none of that is visible from a confirmation screen alone. The fix is to open the artifact from the submission record, read the first and last pages, confirm the timestamp, and save the receipt.

The second pitfall is treating a final discussion or participation requirement as optional once the major work is uploaded. Those requirements often close on their own schedule and carry their own criteria. The fix is to keep them on the calendar as separate items with separate deadlines until each one is confirmed complete.

The third pitfall is discarding the feedback ledger and the method notes at the end of the quarter, then rebuilding them from nothing in the next course. The fix takes ten minutes: file the ledger, the checklists, and the cleaned source log where the next term will find them, and write one line naming the single habit that most needs work next time.

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 11 activities. The registered syllabus, classroom, rubric, announcements, instructor directions, and official policies remain controlling.

Week 11 questions