HLTH 3115 Week 5 planning manual

1. Capture the live Week 5

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 midpoint check on the reasoning you have built

At the midpoint, audit the argument rather than the files. Read everything you have submitted so far in one sitting and ask four questions with a pen in hand. Is the same population named in every place it appears. Does each determinant you introduced still connect to the outcome you named. Is every number attached to a source, a period, and a denominator. Does anything read as a causal claim that the cited evidence cannot carry. Mark each break where you find it, then rank the breaks by how often they recur, because a break that appears once is an error and a break that appears four times is a method problem worth fixing once at the method level.

The gradebook side of the audit is a written-layer task and should be done as one. List every returned activity with its criterion-level result and the comment attached. List every open activity with its dependencies and with whatever must be requested from someone else. Then lay both lists against the remaining calendar. Anything that depends on another person acting, an approval, a group decision, a technical setup, belongs at the top, because those steps cannot be compressed later the way drafting can. Only the registered classroom shows the current state of any of this, and your classroom rubric decides how each remaining item is scored.

The audit finishes with arithmetic rather than resolve. Count the activities remaining, estimate the hours each has taken so far rather than the hours you intended, and compare the total against the working hours actually left in the term after everything else in your life is subtracted. When the totals do not fit, the decision is which activity gets the reduced version, and making that decision deliberately produces a better result than discovering it under time pressure at the end. Record the decision, because it changes what you should be practicing: if the plan requires you to draft faster, the recurring feedback gap to attack first is whichever one costs the most rework rather than whichever one costs the most points.

Reading the rubric row by row against returned feedback

Put a returned rubric beside the blank rubric for the next activity and work across both. For every row where you did not reach the top level, copy the exact wording of the level you earned and the wording of the level above it, then underline the difference between them. That difference is almost always one of four things: something missing, something present but inaccurate, something accurate but unexplained, or something explained but not evaluated.

Name which of the four applies, then write the single sentence you would have needed in order to move the row. Carry that sentence type forward into the next outline as a required element rather than a hope. This is diagnosis, not appeal: the returned activity is closed, and the point of the exercise is the next one. Levels and wording change between activities, so read the sheet attached to the live work; 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.

Auditing the reference list at the midpoint

Take the list you have accumulated and mark each entry with the specific claim it supports in the current work. Entries that cannot be matched to a claim come out; carrying them costs credibility and adds nothing. Then test the survivors on three properties. Is the date inside any recency window the activity has set. Are the population and setting close enough to yours that the finding is usable without a chain of assumptions. Is the source the right type for the claim it has been assigned. A short list of level-matched sources doing visible work reads stronger than a long list assembled for weight.

Replace rather than accumulate. When a source fails one of those three tests, look for a replacement before rewriting the paragraph around it, because a better source sometimes changes the claim. This is also the right moment to clear citation debris, which is among the fastest and most avoidable ways to lose points: entries sitting in the list with no mention in the text, mentions in the text missing from the list, and author or date mismatches between the two. Run that check as a mechanical pass with the draft open beside the list.

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 5 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 midpoint pitfalls and the correction for each

The first is reading returned feedback for the score and nothing else. The comment is skimmed, the file is closed, and the same gap reappears. The correction is to record five fields for every result: the criterion, the comment, your own diagnosis of what caused it, the smallest corrective practice, and the next live place where you can demonstrate the fix.

The second is rewriting closed work instead of practicing the method. Reworking a submitted activity feels like progress and changes nothing, since the result is recorded. The correction is to convert each lesson into a checklist item for the next activity and spend the time there.

The third is deferring an institutional dependency because the drafting feels more urgent. Anything requiring another person, an approval, a group decision, a technical setup, has a queue time you do not control. The correction is to send the request now, record the date you sent it, and plan the draft so it can progress while the answer is outstanding.

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 6. 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 5, 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 6.

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

Week 5 questions