HLTH 1015 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 Exploring Your Path: Foundations Across Fields, 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.

A worked pass: hold one axis while you compare

By the second Week the novelty has worn off and the real difficulty appears, which is comparison that stays disciplined. Foundations Across Fields keeps setting two or more health settings, roles, or approaches beside each other, and the untrained response describes each in turn and stops. Description is not comparison. Run the course method with one axis held fixed. Define the axis precisely: who is served, who pays, what counts as a good outcome, who holds the authority to decide, or what the field accepts as evidence. Apply the axis to both items in the same order and the same words. Make the reasoning visible by writing the sentence that names the difference rather than leaving a reader to infer it from two paragraphs. Then close with the implication the activity asked for.

A worked pass looks like five lines in your notes. Axis: one phrase. Item one on that axis: one clause. Item two on that axis: one clause. The difference: one sentence. Why the difference exists, pointing at structure rather than at personality: one sentence. So what, tied to the prompt: one sentence. Five lines written before prose will outperform six paragraphs assembled without them, because the paragraphs will otherwise drift back into description. If the live activity names more than one axis, build the same five lines for each, and let the rubric weighting tell you how much room each deserves.

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.

Build a source shelf you will reuse

Week 2 is the right moment to stop searching from scratch every time. Build a three-tier shelf. The first tier is the assigned readings, which come first whenever the activity requires them. The second tier is a short standing list of issuing bodies whose material recurs across health fields, saved with the exact page you used rather than a homepage link. The third tier is claim-specific evidence, sought only after you know which claim needs support. Searching in that order prevents the most wasteful habit in a survey course, which is collecting interesting reading that never attaches to anything you have to argue.

Store each entry with five fields: the full citation in the required style, the issuing authority, the date, the one finding you can actually use, and the limitation you would have to state if you used it. Working the source in then follows a fixed trio of sentences: the claim in your own words, the evidence with its source named in the same sentence, and the consequence that only you can write. Avoid stacking three citations behind one general statement. A reader takes that as coverage rather than support, and it usually means the claim was never sharp enough to need a specific source.

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.

Reading the rubric row by row against Week 1's

Put this Week's rubric beside the one you worked from first and read them together, row by row. Rows that repeat are the course's real spine, and they tell you what will be scored again later no matter what the topic turns out to be. Copy the repeating rows into a standing checklist you will reuse for the rest of the term. Rows that changed deserve a short note about what changed: a new verb, a new evidence requirement, a different length, a different audience, a different submission form.

Then read the row where your first graded work came back weakest, if feedback has arrived, and convert that row into a drafting instruction rather than a wish. A row asking for supported analysis becomes the instruction to write no analytical claim without an evidence sentence beside it. A row about organization becomes the instruction to write the topic sentence of every paragraph before writing the paragraph. Cadence means these become moves you make without deciding to make them. What each row is worth and how it is applied, your classroom rubric decides.

Keep the standing checklist as one short document rather than as notes scattered across files. Give it the course code in the name so it is easy to find at speed, list the repeating rows in the order you will check them, and leave room to add a line whenever a new row appears. Then use it in the same place every time, at the end of drafting and before submission, so that checking becomes part of the routine rather than an act of willpower on a tired evening. A checklist consulted occasionally has almost no effect. A checklist run on every activity is what turns this Week's discoveries into the rest of the term's default behavior, and it costs only a few minutes against work that is already finished.

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 pitfalls and the fix for each

The first pitfall is reusing the shape of the first Week's response on a different verb. A structure that suited an introductory overview will not carry a comparison or an application, and a reused outline quietly answers the wrong question in a well-organized way. The fix is to build the outline from this Week's rubric rows every time, even when the activity looks familiar, and to accept that some Weeks need a structure you have not used before.

The second pitfall is the agreeable reply. A response that praises a classmate and restates their point costs time and earns nothing on a row asking you to advance the discussion. The fix is a three-move rule: quote or name one specific point from the peer post, add something the course material supplies, and end with a question or a boundary the peer can actually answer. Post early enough that a reply can return to you before the window closes.

The third pitfall is gathering sources after the draft exists. Evidence found late gets attached to sentences written without it, and the mismatch shows. The fix is to place a bracketed evidence slot in the outline at the moment you write the claim, then fill every slot before prose begins. If a slot cannot be filled by a source you can name and date, narrow the claim until it can be.

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