HLTH 1015 Week 9 planning manual

1. Capture the live Week 9

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.

Plan backward from the submission window

A closing stretch rewards scheduling treated as a reasoning task. Write the last step first and work upward: submission and receipt, file conversion and format check, final read against the rubric, citation verification, complete draft, evidence gathered, outline built from rubric rows, prompt and rubric captured. Put a date on each step in reverse order from the deadline shown in your own classroom, then look for the first date that has already passed. That date, not the deadline, is the one telling you what to do today.

Then sort the steps into serial and parallel. Anything requiring another person is serial and cannot be compressed: replies that need a peer to post first, approvals, feedback you asked for, technical help with a submission problem. Anything you do alone can be moved and interleaved. Most late submissions in a final stretch are not caused by too much writing; they are caused by a serial step discovered too late to wait for. Identify every serial step this Week and start it now, even in an unfinished state, because a request sent early buys days that no amount of drafting speed can recover.

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.

Freeze the reference list before the final drafting

Set a point in this Week after which no new source enters the argument, and hold it. A source found late is rarely additive, because it usually implies a claim you did not make and tempts a re-argument at the moment your remaining hours belong to verification. Keep a separate holding list for anything interesting that arrives after the freeze, and treat that list as material for a later course rather than as a problem for this one.

Before the freeze, run a completeness pass built for cumulative work. Confirm that every claim carrying weight has a source or a stated reason it does not need one. Confirm that every reference entry has an in-text partner and that every in-text citation has an entry. Check that older sources still deserve their place and that anything the activity requires to be current actually is. Then read the list as a stranger would and ask which field it looks like it came from, because in a survey course a list drawn entirely from one corner can undercut a response that claims to reason across fields.

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 9 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 across the whole close

For cumulative work, build a two-column map. In the left column, every rubric row in the order the rubric gives them. In the right column, the section or paragraph of your draft where that row is answered, named specifically enough that you could point at it. Rows with an empty right column are your drafting queue, and they should be drafted in order of weight rather than in the order they appear. The map takes fifteen minutes and replaces the vague feeling that something is missing with a list you can work through.

Then check the reverse direction. Read your sections and find any that no rubric row asks for. Material no row scores is not automatically wrong, but in a tight final stretch it is the first place to reclaim time and words. Keep what the prompt requires even where the rubric is silent, since prompt and rubric are both controlling documents, and ask your instructor where they seem to disagree. What each row demands, your classroom rubric decides.

Note which rows are attached to something other than a file. In a closing stretch a rubric may score a posted reply, a timing requirement, a peer interaction, an approval, or a step completed inside the classroom rather than inside a document, and those rows cannot be satisfied at the last minute by writing more. Mark them separately on your map, put each on the calendar with its own date, and treat them as the serial items they are. A cumulative response that is complete on the page and short one required posting loses on a row it could have satisfied in ten minutes, which is the most avoidable kind of loss available this late in a 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 10. 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 9, 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 10.

Three Week 9 pitfalls and the fix for each

The first pitfall is saving the largest item for last because it is the most intimidating. The heavy piece then arrives with the least time and the least energy behind it. The fix is to draft the highest-weighted rubric row first, in a rough form you will improve later, so that the version you cannot avoid finishing already exists on the page.

The second pitfall is an outline that mirrors the prompt's sentence order rather than the rubric's weighting. Prompts often list a small requirement first and the major analytical demand last, and a draft following that order tends to spend its best pages on the least valuable row. The fix is to allocate pages by weight, then arrange those sections in whatever order reads well.

The third pitfall is discovering a submission requirement at the end. A file type, a naming convention, a template, a specific submission location, or an attempt limit found in the final hour turns a finished draft into a crisis. The fix is to read the submission instructions during the capture pass at the start of the Week, and to do one practice upload well before the deadline if the classroom allows it, so the mechanics are proven rather than assumed.

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

Week 9 questions