HLTH 2500 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 Theories of Health Behavior, 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.

Worked reasoning: turn a construct into a testable weekly claim

The cadence that has to hold for the rest of the term is a four-move loop applied to every activity. Name the construct the work depends on. Define it operationally for this population rather than reciting a textbook definition. Predict what would change in the behavior if the construct moved. Name the measure that would show that change, in a stated denominator, over a stated period.

Written out, the loop produces one sentence: this construct, defined for this population as a specific condition, is expected to raise or lower the behavior for a stated reason, which would appear as a change in a named measure among a named group over a named period. If that sentence cannot be completed, the construct is being used decoratively and the reader will see it.

Attach the loop to fixed days. A capture day, a source day, a drafting day, a checking day, and a reply day give the reasoning somewhere to happen when the calendar tightens. Whichever theory the registered Week names, the loop is the same; only the construct vocabulary changes.

Reading the rubric row by row on a repeating schedule

In Week 2 rubric reading should stop being an event and become a routine. Read the rubric three times per activity. Read it before research, so the search is aimed at the evidence the rows require. Read it at the halfway draft, when a row with no sentence attached is still cheap to fix. Read it immediately before submission as a literal audit rather than an impression.

Keep a two-column log: the rubric row on the left, the exact location in the draft that answers it on the right. Two rows pointing to the same paragraph usually means one of them is unanswered. A row whose requirement never appears anywhere in your own words means the row is being guessed at rather than met.

Rubrics differ between sections, terms, and activity versions, so the log is a working tool and not a template to reuse. The rubric posted in your registered classroom 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.

Scholarly sources at cadence speed

By Week 2 the problem is rarely finding sources. It is finding usable ones fast enough without lowering the standard. Set a standing search order and follow it every time: start at the level of the claim, whether that is national, state, county, organizational, or clinic, then move to peer-reviewed work that explains why the pattern exists.

Rule things out quickly. Undated web pages cannot support a recency requirement. Aggregator summaries that never name the underlying study are not the study. A single-site anecdote generalized to a population is not population evidence. A journal with no visible peer review process is not a shortcut worth taking.

Work the source in from the note, not from the open document. Paraphrasing while looking at the source text pulls the source author's sentence structure into the draft. Write the claim first, then the finding with its population and direction, then the limitation. A source that never earns a use note gets dropped rather than parked in the reference list, because an unused citation costs credibility without buying anything.

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

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.

Three Week 2 traps and the fix for each

The first trap is a routine built around the drafting day alone. Replies, calculations, format conversion, and the upload then compete for the same final hours. The fix is to give every one of those steps a named day in the cadence, and to treat the reply window as a deadline in its own right rather than an afterthought.

The second trap is reusing Week 1 phrasing because it scored acceptably. Method transfers across Weeks. Language does not, since a new prompt requires new reasoning, evidence, and authorship even when the underlying concept returns. The fix is to keep a method note, not a paragraph bank.

The third trap is collecting sources before a claim exists. Search without a claim returns everything and settles nothing, and the resulting draft reads as a tour of the literature. The fix is to write the claim sentence first, even in rough form, and let it define what a relevant source would look like before the first search runs.

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