HLTH 3115 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 Public and Global Health, 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.

A worked pass at building the argument spine

Longer deliverables rarely fail inside a section; they fail at the joints between sections. Before writing, list the section headings and write beside each one a single sentence stating the claim that section will prove. Then read those sentences alone, in order, ignoring everything else on the page. If they form an argument, the spine is sound and the drafting is bookkeeping. If they read as a list of topics, the finished paper will read as a list of topics no matter how well each part is written. Fix the sentences before writing the sections, and check that each claim uses the same population, determinant, and outcome established at the start, or says explicitly why it has moved.

Then draft in dependency order rather than in reading order. Whatever depends on someone else goes first as a request, since it cannot be compressed later. Whatever depends on your own earlier output goes after it: the evidence table before the discussion of evidence, the comparison before the recommendation, the recommendation before any evaluation element, and the opening summary last of all, because it summarizes what now exists rather than what was planned. Reserve a separate block of time for assembly itself. Sections written on different days produce repeated definitions, figures that disagree with each other, and references that appear in one place and not the other, and none of that is visible while you are inside a single section.

When the sections exist, reverse-outline the assembled draft before editing a word of it. Read the finished document and write, from what is actually on the page rather than from the plan, one sentence per section stating what that section proves. Then set the reverse outline beside the spine you wrote at the start. Differences between the two are the real edit list, and they fall into three kinds: a section that proves something other than what it promised, a section that proves nothing, and a claim in the spine that no section proves at all. Each has a different repair, and identifying which kind you have is faster than rereading the whole document looking for problems.

Reading the rubric row by row across a long deliverable

Long rubrics reward mapping more than they reward effort. Number every row, write the number beside the section that will satisfy it, then check that each number appears somewhere and that no section exists without a number attached to it. Weighting matters here in a way it does not on short activities: a row carrying a large share of the total deserves proportionate depth, and effort spread evenly under an uneven sheet loses more than it gains.

Where one row bundles several requirements into a sentence, split it into its parts and treat each part as its own checkpoint, since partial satisfaction of a bundled row is the most common quiet loss. If evidence for a row lives in a table or an appendix, put a pointer to it in the prose so a reader does not have to hunt for it. Weights, structure, and what counts as complete belong to the live sheet; your classroom rubric decides.

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.

Source architecture for a long synthesis

A synthesis needs its sources arranged by function rather than in the order they were found. Sort them into four groups. Problem sources establish level and trend. Mechanism sources establish the relationship between determinant and outcome. Option sources establish what has been tried and what happened when it was. Constraint sources establish policy, funding, and authority. A gap in any one group is visible from the outside: a piece with no constraint sources recommends things nobody has the power to do, and a piece with no option sources invents an intervention with no track record.

Within each group, resolve disagreement rather than listing it. When two sources report different figures or reach opposite conclusions, write the paragraph that says what differs between them, whether it is population, period, definition, or design, and which one governs your case and why. That paragraph is frequently where the highest analysis credit in a long deliverable sits, and it is the part most often replaced by a sentence noting that findings are mixed. Mixed findings are the beginning of the analysis, not a substitute for 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

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.

Three assembly pitfalls and how to fix them

The first is writing sections in isolation, which produces the same definition three times and figures that disagree between sections. The fix is a single reconciliation pass done with the whole document open, keeping one definition and one figure per concept and deleting the duplicates rather than reconciling them in the reader's head.

The second is leaving any evaluation element as a single vague sentence at the end. The fix is to name the measure, the population, the baseline, the period, the data source, and who would review the result, which turns a closing gesture into something a reader can assess.

The third is an introduction written first and never revisited, promising a paper that the body did not become. The fix is to rewrite the opening after the body is finished so that it describes what the work actually does, and then check the closing against the rewritten opening.

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