HLTH 6031 Week 2 planning manual

1. Capture the live Week 2

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: turn the class question into a weekly loop

Cadence is a reasoning habit before it is a schedule. The durable class question names four objects: population, determinant, stakeholder, and measurable outcome. Build a loop that touches all four in the same order every Week so no activity ever starts from a blank page. The loop runs like this: restate the population sentence in the current activity's terms, name the determinant the activity actually asks about, identify which stakeholder can act on it, and state the outcome in a form that could be measured. Once the previous Week's material sits in one file, running those four steps takes minutes, and it removes the sequencing errors that cost the most time later.

The second half of the loop is arithmetic discipline. Before writing about change, settle what is being counted and what it is divided by. A count answers how many, a rate answers how common, and a proportion answers what share of the group. Mixing the three across paragraphs makes a well-written passage unreadable to anyone checking measurement validity. Record the denominator once, in the working file, and reuse it everywhere.

Stabilize the drafting sequence

A cadence that survives a busy Week has a fixed order of operations rather than a fixed number of hours. Draft in this order: the claim sentence, the evidence that carries it, the reasoning that joins the two, then the framing paragraphs. Introductions and conclusions written first tend to promise an argument the body never makes, and a criterion on organization exposes that quickly.

Protect the later part of the Week for work that cannot be compressed: comparing options, checking figures against their sources, format conversion, and the upload itself. Treat replies and any collaborative step as scheduled work with their own slot rather than as leftovers. Stabilizing now matters because later Weeks add analytical difficulty, and difficulty is only survivable when the process has stopped being a decision.

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.

A repeatable source routine and what counts as scholarly

Build a retrieval routine you can repeat without thinking about it. Begin with the assigned readings for the live activity, since they define the vocabulary the scorer expects. Then move to the authority level closest to your population: a public health surveillance system or vital statistics program for magnitude, a state or local health department report for distribution, an organizational or program evaluation for feasibility, and peer-reviewed literature for whether an approach moved an outcome. A source is scholarly in this subject when its method, date, and population are stated and checkable, not when it merely sounds official.

Working a source into the draft is a separate step from finding it. Write the sentence you intend to support, attach the source, then state in the same line what the source cannot support. That third element prevents the most expensive habit here, which is letting one study stand in for a whole determinant. Keep use notes in one running table so the same shelf serves every remaining Week instead of being rebuilt from scratch each time.

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 2 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

In a stabilizing Week, read the rubric twice: once at the start to plan and once mid-draft to test. On the first pass, convert each row into a question the finished work must answer, and note which rows carry the most weight so that time follows points rather than interest. On the second pass, read the draft the way a scorer would, row by row, marking the exact sentence that satisfies each one.

Watch the rows that describe process rather than product, such as those covering sourcing, citation, mechanics, or participation rules. These are usually the easiest to hold and the easiest to lose while attention sits on the argument. Rubric rows, their weights, and the wording of each level differ by section and term, so the registered classroom rubric decides; treat any pattern described here as a way to read yours rather than a substitute for it.

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 3. 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 2, 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 3.

Three cadence pitfalls and their fixes

The first pitfall is drafting before the denominator is settled. Prose written around an unstable number has to be rewritten rather than edited, because the sentences surrounding a figure carry its logic. The fix is a short numbers block at the top of the working file holding every figure with its denominator, date, and source, completed before the first paragraph.

The second pitfall is letting discussion replies drift to the end of the response window, where they turn into agreement instead of analysis. The fix is to schedule replies as their own session with a required move: compare evidence, apply the peer's point to a different population, name a boundary condition, or ask a question the course material can answer.

The third pitfall is a growing source shelf with no use notes. Sources gathered without a stated job reappear as a reference list longer than the analysis it supports. The fix is a standing rule that nothing is saved until its use note exists, and that any source still without a use at the end of a Week is removed rather than carried forward.

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

Week 2 questions