HLTH 6207 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 Grant Writing, 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: building a statement of need one link at a time

A statement of need is an argument rather than a description, and Week 2 is where a repeatable routine can be built around its links. The chain runs in a fixed order: name the population and the place; establish the magnitude of the problem with a comparison that gives the number meaning; state the consequence if nothing changes; show what current services do and where they stop; and only then explain why this applicant is positioned to close that gap.

Work the second link slowly, because that is where most drafts lose a reader. A raw count carries almost no argumentative force by itself. A rate acquires force when it is set beside a referent: the same measure for a larger geography, the same measure for a comparison population, or the same measure over time in the same place. What the reader then needs is the sentence immediately after the comparison, stating what the difference means for the people named in the first link. If that sentence cannot be written, the statistic is decoration and should be replaced rather than reworded.

A cadence that produces one finished link per working session, with the comparison and its meaning sentence always written together, converts a difficult section into predictable work. Whether the live activity asks for a full need statement, a shorter problem framing, or something else entirely is determined by the registered prompt and its rubric.

Reading the rubric row by row as the weekly cadence settles

By Week 2 the rubric should stop being a document opened at the end and become the checklist that shapes the working routine. Convert each row into a line on a standing checklist, ordered the way the artifact will actually be built rather than the way the rubric prints, and mark each line with the evidence or reasoning that will satisfy it.

Layer the first instructor signals onto those rows. Announcements, returned comments, and clarifications posted in the classroom often state in plain language what a rubric row means in this section, and that plain-language version is the operational definition to work from. Note which rows reappear across activities, because those are the criteria the course will keep testing and the ones worth building durable habits around.

Recheck the rows against the live rubric for each new activity instead of reusing a checklist blindly. Rows, weights, and wording belong to the rubric attached to the current activity in the registered classroom.

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.

Source work that survives a weekly cadence

The evidence habits set now decide what the later Weeks cost. Keep one standing evidence file rather than a folder of downloads, with a row for each source recording the publisher, the year, the geography, the population, the measure as that source defines it, the usable finding, and the limitation. Surveillance data, peer-reviewed evaluations of health promotion programs, and official agency guidance answer different questions, and blurring their roles is what produces a reference list that looks strong and argues weakly.

Apply one rule while drafting: one source, one job. A source brought in to establish the size of a problem should not also be asked to justify the choice of intervention, because the study that measured prevalence almost certainly never tested a program. Paraphrase from understanding rather than from the sentence on the screen, and place each citation on the claim it actually supports instead of at the end of a paragraph that made several.

Assigned readings remain mandatory wherever the live activity requires them, and the citation style in force is the one named in the registered classroom.

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

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.

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 the national figure standing in for local need. A widely quoted national statistic feels authoritative and tells a reader nothing about the community the proposal names. The fix is to pair every national figure with a state, county, or service-area indicator and to name the geography inside the sentence, so that no reader has to guess which population a number describes.

The second trap is a cadence built around the largest artifact. Written work expands to fill the week and discussion replies get compressed into the final hours, which is exactly where reply quality collapses into agreement. The fix is to schedule reply work as its own calendar block with its own preparation, and to draft replies from the assigned material rather than from the peer post alone.

The third trap is treating the Week 1 capture as permanently valid. Instructions get amended, announcements add conditions, and rubric versions change. The fix is a short re-capture at the opening of every Week that compares the live classroom against the ledger and logs any difference before drafting resumes.

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