HLTH 6031 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 Leadership and Advocacy in Health Education, the durable class question is: Which population, determinant, stakeholder, and measurable outcome define the problem? 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

Define the population and baseline, trace determinants and system constraints, compare interventions, and connect the recommendation to implementation and evaluation.

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: a final coherence pass across the four objects

Close the class by testing the four objects against one another a final time. The population named at the start, the determinants analyzed, the stakeholders addressed, and the outcome measured should form a closed loop: the outcome is measured in that population, the determinants are the ones the recommendation acts on, and the stakeholder named is the party who could actually act. Read the finished work only for that loop, ignoring style entirely, and repair any place where one of the four objects has quietly changed.

Then check the implementation and evaluation link, which is the part most often left thin at the end of a class. An implementation statement names who begins, with what resources, in what sequence. An evaluation statement names the measure, the comparison, the interval, and who reviews the result. Both are written at the level of the actor who owns them rather than as general intentions.

Carry the method forward instead of the text

What transfers to the next course is method: the population sentence, the level sort, the determinant chain, the comparison criteria, the use note discipline, and the rubric reading pass. Write each of these as a short procedure in a file that lives outside any single class, so the next course begins with a process instead of a blank page.

Previously submitted work does not travel. A later prompt requires new reasoning, new evidence, and new authorship even when the concept returns, and the lesson worth preserving is how the analysis was built rather than the sentences it produced. Keep the feedback ledger beside the procedures, because the recurring criterion gap identified in this class is the most valuable thing to test deliberately in the next one.

4. Use evidence deliberately

Use current surveillance, policy, organizational, and peer-reviewed evidence at the same geographic and population level as 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.

Close the source library so it stays usable later

Before the class ends, convert the working shelf into a small library organized by job rather than by activity: authority-level surveillance sources for magnitude, disaggregated datasets for disparity, reviews and strong-design studies for effect, and policy or organizational documents for feasibility and authority. Keep the use note, the date, the population, and the limitation with each entry, because that is what makes a source reusable rather than merely rediscoverable.

Record where each figure came from precisely enough to reproduce it, including the data year and the release consulted, since public health figures are reissued and a later release can change what you cited. Note which sources were assigned readings, because those carry the vocabulary of this subject and are the fastest route back into it. Reusing a source in a later course still requires reading it again against the new claim.

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

Test equity, feasibility, stakeholder effects, measurement validity, unintended consequences, and the boundary between association and causation.

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

On a final activity, run the rubric pass twice with a gap between them. The first pass annotates every row with the location that satisfies it. The second pass, done after a break, reads only the annotations and asks whether a scorer who saw nothing else would agree. Rows that survive both passes are finished; the rest are the last of the work.

End with the mechanical requirements, which are fully within your control: citation format, structure, length, file type, and the submission route itself. Then verify that the submission actually landed, open the uploaded file, and keep the receipt. Grades, designations, and progression are determined by Walden and the instructor, and the registered classroom rubric decides in every case; this page describes method only.

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 closing pitfalls and their fixes

The first pitfall is treating upload as completion. A submission that failed silently is indistinguishable from work never done. The fix is to open the submitted artifact after uploading, confirm the file and timestamp, save the receipt, and contact the instructor or the official support channel immediately if anything is missing.

The second pitfall is discarding the feedback ledger once the class closes. The pattern it holds is the most transferable thing produced all term. The fix is to write a two-line summary of the recurring criterion gap and the practice that addresses it, then store it where the next course will begin.

The third pitfall is carrying language forward instead of method. Reusing submitted text creates an authorship and originality problem and skips the reasoning the next prompt requires. The fix is to keep procedures and use notes rather than paragraphs, and to re-derive every claim against the new activity.

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