HLTH 3115 Week 10 planning manual

1. Capture the live Week 10

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 repairing the weakest link

Revision at this stage is triage, and triage needs a count. List every criterion-level comment you have received in the course so far, group the comments by type, and count each group. Useful groups are understanding, task interpretation, reasoning, evidence, calculation, professional communication, format, and process. The largest group is the weakest link and deserves the largest share of the remaining effort, even when a different group is more annoying to read. Then repair at the level of method rather than at the level of the sentence: if evidence is the recurring group, change how sources are chosen and attached across the whole draft, and if task interpretation recurs, add a step in which the prompt is rewritten as a checklist before any drafting begins.

Revising for reasoning is a different activity from proofreading and should not be attempted in the same pass. Read only the topic sentences and check that each one is a claim rather than a topic. Read only the evidence sentences and check that each names a source, a population, and a period. Read only the interpretation sentences and check that each says what the evidence changes about the case. Three narrow passes find more than one broad one. Revision is not obliged to reverse a conclusion; if the evidence still supports it, keep it and make the support honest. Where old feedback and the current sheet point different directions, the live activity governs, and your classroom rubric decides.

Reading aloud is the cheapest revision instrument available and the most consistently skipped. Read the draft out at normal speed without stopping to fix anything, marking only the places where you hesitate, reread a line, or run short of breath. Hesitation marks a sentence whose logic you do not fully hold; a reread marks an unclear referent or a buried claim; a long sentence marks a paragraph carrying two ideas that should be separated. Then go back and repair the marks rather than the whole document. This finds different problems than silent editing does, and it finds them in the order a reader would meet them, which is the order that matters for a criterion written about clarity.

Reading the rubric row by row during revision

Score your own draft against the live rubric before submitting it. For each row, write the level you believe the draft reaches and then quote the exact words in the draft that justify that level. A row you cannot justify with specific text is a row you have not yet earned, however confident the draft feels while you are reading it.

Then work upward from the lowest-scoring rows rather than polishing the strongest ones, because moving a weak row costs less effort and returns more than improving a row that is already met. Do this with the current sheet open rather than from memory of an earlier one, since rows and level language change between activities and your classroom rubric decides which sheet governs this submission.

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.

Replacing the sources feedback flagged

When feedback names a source problem, diagnose which of four problems it actually is, because each has a different repair. A type mismatch means the source design cannot carry the claim, and the repair is a different design rather than a stronger sentence. A level mismatch means the evidence describes a different population or geography than the claim does, and the repair is either evidence at your level or an explicit statement that you are reasoning across levels. An age problem means the figure or policy state no longer describes the present, and the repair is a current replacement or, where none exists, a sentence saying so and explaining why the older figure remains the best available. An unused source is simply removed.

Do the replacement before rewriting the prose that surrounds it. New evidence sometimes changes the claim it was meant to support, and rewriting a paragraph around a source you are about to swap wastes the work twice. Then rerun the mechanical check: every in-text citation present in the list, every list entry present in the text, authors and dates matching between them, and the style following what the registered classroom specifies.

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 10 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 revision pitfalls and the repair for each

The first is revising in page order, which spends the best attention on the opening and leaves the weakest criterion untouched. The repair is to revise by criterion instead, working from the rows you scored lowest against the live sheet, and to accept that the resulting order will feel disorganized while it is happening.

The second is adding length in place of support, usually by expanding a paragraph that was already complete. The repair is a rule for every new paragraph: it must carry a claim, evidence for that claim, and an interpretation of what the evidence changes, or it does not go in.

The third is revising a copy on your own machine while a different version sits in the classroom. The repair is version discipline, naming files by activity and date, keeping one working file rather than several, and confirming at the end which file was actually submitted rather than which one you last edited.

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 10, 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.

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

Week 10 questions