HLTH 6300 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 Disaster Response and Recovery, the durable class question is: What does the prompt ask the student to understand, apply, compare, create, or evaluate? 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 required concept precisely, apply it to the stated context, make the reasoning visible, and close with the implication the current rubric requests.

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: audit the work, not only the gradebook

A midpoint audit that checks scores alone is half an audit. Run it in three passes. The first is administrative: every activity accounted for, every reply posted, every file confirmed as opened, every dependency such as a group step or an approval either finished or scheduled. The second is diagnostic: read all returned feedback at once and sort the comments into task interpretation, reasoning, evidence, format, and process. The comment that appears twice is the one worth engineering against; a comment that appears once may be about a single draft.

The third pass is structural and specific to this subject. Read your own earlier work and ask whether the jurisdiction, population, and phase have stayed consistent, or whether the case quietly changed between submissions. Drift is common as a course moves from preparedness material into response and then recovery, because the same case looks different in each phase and a student can end up writing about three situations under one name. Repair it by writing a one-paragraph case statement and keeping it at the top of every working file for the rest of the course.

4. Use evidence deliberately

Use the assigned readings first when required, then add current authoritative or peer-reviewed support matched to 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 source shelf at the midpoint

Halfway through, most students have accumulated sources without reviewing them as a set. Lay them out and check four things: how many fall inside the currency window the classroom names, how many come from bodies with actual responsibility for the function discussed, how many were merely cited rather than used, and how many were reused across submissions without new reasoning. Reuse of a source is ordinary; reuse of a paragraph is not, and later prompts require new reasoning and new authorship even when the concept returns.

Then look for the gap. In disaster response and recovery the most common gap is population specificity: plenty of general guidance, nothing about the particular group the case names. Fill it deliberately by searching for the population and the function together rather than the hazard alone. Record for each new source what it adds that the existing shelf does not, and retire any source that has never supported a claim. Assigned readings continue to come first where the activity requires them.

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

Check task completion, reasoning, evidence fit, examples, organization, citations, file rules, and the student's own explanation of the result.

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

At the midpoint, read the rubric backwards against work already returned. Take a graded submission, place each row beside the part of the draft that was supposed to satisfy it, and mark where the score and your expectation disagreed. Those disagreements are the most useful information available all term, because they show how this instructor reads a row rather than how the row reads in the abstract.

Where a row scored lower than expected, look for the modifier that was missed rather than assuming the whole section was weak. Often a single required feature was absent: a stated criterion, a current source, an explicit connection to the named population. Write the missing feature as a line in a personal pre-submission checklist and run it every remaining Week. Rows, wording, and weighting differ by section and term, so your classroom rubric remains the authority on all of it.

Three Week 5 pitfalls and the fix for each

The first is deferring a recovery. Students notice a gap at the midpoint and plan to close it later, when later has fewer free hours than now. The fix is to schedule the repair this Week with a date and a defined scope, and to protect that block the way a deadline is protected.

The second is mistaking a format problem for a thinking problem, or the reverse. A run of middling results can come from citation mechanics or from unsupported reasoning, and the responses are completely different. The fix is to separate them: re-read one returned submission twice, once ignoring content and once ignoring form, and see which pass surfaces the comments.

The third is silence about a stalled dependency. Approvals, group steps, and technical submissions fail quietly and get discovered at a deadline. The fix is a dependency line in the audit naming each pending step, the person or office responsible, the date it was requested, and the date it must resolve, with contact to the instructor or official support channel as soon as a date slips.

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