HLTH 6051 Week 2 planning manual

1. Capture the live Week 2

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 Diversity, Human Rights, and Social Justice, 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.

Turning the first instructor signal into a repeatable reasoning routine

Week 2 is where a method either becomes a habit or stays improvisation. Take whatever signal the first submission produced, whether a returned score, a comment on a post, or a general announcement to the section, and translate it into a routine you can run every week without rethinking it.

In this subject the routine has a fixed spine: name the population or setting, name the condition or difference, name the evidence, name the standard you are judging against, and name the implication. Practice that sequence aloud on the current prompt before you write anything. If you cannot say which standard your judgment appeals to, whether an entitlement, a distributive principle, or a professional obligation, the paragraph will read as opinion no matter how many citations follow it. Repair the missing element first; drafting around a hole takes longer than filling it. How much of the sequence the activity rewards is decided by your classroom rubric.

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.

Reading the rubric row by row when a row returns from last week

Set this Week's rubric beside the previous one and sort every row into three groups: rows that returned unchanged, rows whose wording shifted, and rows that are new. Unchanged rows are the ones where your last result predicts this one, so any comment you received on that row is a direct instruction for the current draft.

Changed wording matters more than it looks. A row that moves from describe to analyze, or from identify to evaluate, is asking for a different kind of paragraph rather than a longer one, and length will not close that gap. New rows deserve a research task before a writing task. Rebuild the rubric-to-evidence table you used in Week 1 and add one column for the prior result on that row, so the weakest criterion is drafted first and checked twice. Rubric wording, weighting, and row counts vary by section and term, so your classroom rubric decides what is actually being measured.

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.

A weekly source routine that survives a full quarter

Stabilizing the cadence means the search itself becomes routine. Keep a running vocabulary file for this subject: the population terms, condition terms, setting terms, and standard terms your assigned readings use, because searching in the field's own words returns different results than searching in everyday words.

Run each search twice, once for evidence that a condition exists and once for evidence about what has been tried, and keep the two piles apart so descriptive sources are never pressed into service as support for a recommendation. Record the publishing body and the date at the moment you find an item, not at citation time, when the detail is hardest to recover. When you draft, work sources in by sentence: claim, then evidence, then the inference the evidence licenses. A paragraph that ends on a citation with no inference sentence reads as reporting. Assigned readings stay mandatory wherever the live 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.

Making replies do analytical work in the second week

By Week 2 the board holds enough material for real comparison, and that is where reply credit usually lives. Choose a peer post whose population, setting, or standard differs from yours and put the difference to work: ask what changes about the conclusion when the setting changes, or show where the same evidence would lead somewhere else.

A second dependable move is bounding. Accept the peer's claim, then identify the condition under which it stops holding, and bring a source for the boundary rather than for the agreement. Avoid the two weak shapes, which are agreement with restatement and a question the peer's own post already answered. Keep the tone professional and address the argument rather than the person, which matters especially in a subject that touches identity and lived experience. Required reply counts, response windows, and content rules are set by the live discussion instructions for this Week.

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 2 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.

Three Week 2 pitfalls and the fix for each

Pitfall one: repeating the Week 1 argument with fresh citations because the topic feels adjacent. The fix: write the current prompt's question at the top of the working file and test every paragraph against that sentence rather than against the earlier submission.

Pitfall two: treating an undated statistic as current evidence because it appears in many places at once. The fix: trace the number to the publishing body and the year of collection, cite that source directly, and state in text how old the data are whenever the claim depends on currency.

Pitfall three: posting on time and replying late, so the reply row gives back what the initial post earned. The fix: record the reply window in the same ledger row as the post deadline and schedule the replies before you draft the post, since replies depend on other people showing up first.

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 3. 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 2, 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 3.

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

Week 2 questions