HLTH 1015 Week 11 planning manual

1. Capture the live Week 11

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.

The last three reads and what each is for

Give the final work three separate reads with three different jobs, and do not blend them. The first is a completion read against the prompt: take the prompt sentence by sentence, and for each required element point at the text that satisfies it. The second is a reasoning read of the claims alone: read your topic sentences in sequence, ignoring everything else, and ask whether they form an argument someone could follow. The third is a mechanical read for citations, headings, length, format, and the file itself.

Then run a closing test that costs five minutes. Without looking at the document, say what you concluded, what evidence carried the most weight, and what your response does not settle. If any of the three is hard to say, the draft is still standing on assembly rather than on understanding, and the last available hour is better spent there than on another formatting pass. Make sure the closing paragraph does the same work in writing: state the conclusion and its limit rather than restating the introduction with different adjectives.

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.

Turn the term's sources into a starting shelf

The most valuable thing a foundations course leaves behind is a small set of sources you actually understand. Before the term closes, build a durable annotated list: the full citation in the required style, one line on what the source establishes, one line on where you used it, and one line on its limitation. Ten well-annotated entries are worth more than a folder of downloads, because the annotation is what lets you find the right one months later without rereading everything.

Carry the sources and the notes forward, never the sentences. A later course will ask a different question, and a paragraph written for this term will not answer it; reusing submitted text also creates an originality problem in the new classroom. Keep instead the issuing bodies you learned to trust, the search order that worked, the citation style rules you had to look up twice, and the definitions in your working glossary. Those transfer cleanly and legitimately, and they are what makes the next course faster rather than merely familiar.

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 11 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 one last time

Do the final row-by-row read before submission rather than after it. Take each row of every remaining graded activity and point at the text, the file, or the posted reply that answers it, including the rows easiest to assume: source count, format, reply timing, length, and file type. Then submit, open the submitted artifact from inside the classroom rather than from your own folder, confirm what actually uploaded, and save the receipt somewhere you will find it again.

Read the rubric once more after results post, this time as feedback rather than as instruction. For each row, write one sentence naming what the result tells you about your method, and add it to the ledger you have kept all term. That last pass is what converts a finished course into something usable, and it takes about fifteen minutes. Grades, designations, approvals, and progression are determined by Walden and your instructor; what any row is worth and how it was applied, your classroom rubric decides.

Archive the rubrics themselves along with the results. Save each rubric as it appeared, the returned version with its marks, and your one-sentence lesson per row, in a single folder named for the course. Later courses bring rubrics that look different on the surface and score the same underlying things: task completion, reasoning, evidence, organization, mechanics, and process. Having the earlier documents means you can compare rather than start over, and it means the feedback you paid for in effort stays available to you. Grades, designations, approvals, and progression decisions belong to Walden and your instructor, and what any row was worth was decided in your classroom. What belongs to you afterward is the record of how you learned to read one.

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 11. 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 11, 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 11.

Three Week 11 pitfalls and the fix for each

The first pitfall is submitting without opening what was submitted. A file can upload as a draft, upload empty, upload in a format the classroom cannot display, or land in the wrong place, and none of that is visible from a confirmation screen alone. The fix is to reopen the artifact from inside the classroom, read the first and last page, confirm the timestamp, and save the receipt.

The second pitfall is treating a final activity as ceremonial. A closing Week often carries real weight, and a response written as a farewell rather than as work will still be read as work. The fix is to run the same capture, outline, evidence, and quality steps you used in the middle of the term, at whatever scale the remaining time allows.

The third pitfall is closing the course without recording the method. The feedback ledger, the working glossary, the annotated source shelf, and the drafting rules you built are all easy to abandon in the relief of finishing, and rebuilding them next term costs far more than saving them costs now. The fix is one short session: name the three habits that worked, the one weakness that persisted, and the first move you will make in the next course to test it.

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

Week 11 questions