HLTH 6300 Week 3 planning manual
A course-specific Week workflow for capture, reasoning, evidence, student authorship, quality control, and gradebook closure.
Move beyond definitions by making mechanisms, comparisons, calculations, or decision criteria visible in the order the current rubric can score. This page verifies a position in the Course-Based quarter calendar, not a universal assignment identity.
1. Capture the live Week 3
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.
| Control field | What to verify now |
|---|---|
| Identity | Exact course, Week, activity, and current version |
| Task | Every required action, question, audience, and deliverable part |
| Grading | Rubric rows, points, weights, thresholds, and penalties |
| Evidence | Assigned readings, source rules, dates, authority, and citation style |
| Calendar | Initial post, replies, files, approvals, due time, and time zone |
| Dependencies | Group, field, clinical, residency, proctoring, feedback, or approval steps |
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: make the mechanism visible
Showing reasoning means writing the middle of the thought, not only the ends. In this subject the middle is usually a mechanism: the chain by which a hazard produces a health consequence, or by which an intervention interrupts that chain. Put it on the page as an explicit sequence. A hazard exposes a population; exposure meets an existing vulnerability such as chronic illness, dependence on powered medical equipment, or distance from a facility; the vulnerability converts exposure into a specific health outcome; a named function such as evacuation support or continuity of medication supply is the point where the chain can be broken.
Once the chain is written, the analytical work becomes obvious: say which link is best supported by evidence, which is assumed, and which is contested. A paragraph that names its own weakest link reads as stronger, not weaker, because it shows the student can locate the limit of a claim. Avoid the shortcut of asserting that a factor is important. Importance is a conclusion; the mechanism is the argument that earns it. What the live activity actually asks for remains defined by the registered prompt and rubric.
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.
Choosing sources that can carry a mechanism
Not every credible source can support a mechanism claim. Descriptive reports tell you what was distributed or how many people were served; they establish magnitude, not causation. Evaluations, controlled comparisons, modeling studies, and structured after-action analyses are the source types that speak to why something worked. For a claim about a mechanism, prefer a source that measured or tested the link, and say inside the sentence what kind of study it was.
Work the source in at the point of the chain it supports rather than at the end of the paragraph. If a source establishes that households without transportation evacuate later, it belongs beside the vulnerability link, not appended to a conclusion about policy. Where evidence is thin, say so plainly and name what would settle the question. A sentence that identifies the missing study is a legitimate scholarly move and it protects the draft from overstating. Assigned readings remain 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 3 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
A reasoning-focused rubric row often hides its real demand inside a verb pair. Explain and justify are not the same operation: explain asks how something works, justify asks why this option is preferable to another. Compare and contrast is two operations, and a row naming both expects both. Evaluate almost always presumes a stated criterion, and a submission that evaluates without naming the criterion has answered a different question than the one asked.
For each row, write the verb, then write the visible artifact that proves the verb happened: a labeled sequence for explain, a stated criterion plus a comparison for evaluate, parallel paragraphs or a table for compare. Reasoning that lives only in the student's head cannot be scored, and reasoning buried mid-paragraph is easy to miss. Make it findable. Row wording, counts, and weighting differ by section and term, so your classroom rubric decides what each verb requires here.
Three Week 3 pitfalls and the fix for each
The first is the definition paragraph that never becomes an argument. A student states a framework accurately, then stops, and the rubric row asking for application goes unmet. The fix is a rule: every definition is followed immediately by a sentence that begins with the case, showing the definition doing work on the named jurisdiction or population.
The second is the citation that supports the sentence before it rather than the claim being made. This happens when sources are inserted after drafting. The fix is to read the draft once with only the citations in view and ask, for each, what exact assertion it is standing behind. Any citation that cannot answer is moved or removed.
The third is treating a plan document as proof that the plan works. Existence is not effectiveness. The fix is to separate, inside the sentence itself, what a document requires from what an evaluation found, and to keep those two kinds of statement out of the same voice.
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 4. 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 3, 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 4.
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 3 activities. The registered syllabus, classroom, rubric, announcements, instructor directions, and official policies remain controlling.
Week 3 questions
What is assigned in HLTH 6300 Week 3?
Only the registered Course-Based classroom can answer that. This positional manual deliberately does not invent a discussion, paper, quiz, project, exam, practicum task, or rubric.
How should I start HLTH 6300 Week 3?
Capture every live activity, instruction, rubric row, point value, deadline, reply rule, dependency, and submission route before researching or drafting.
Can a tutor perform the Week for the student?
No. Tutoring supports understanding, method, practice, and feedback; the student performs required activity, authors the response, verifies it, and submits it.