HLTH 6110 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 Health and Wellness Education Competency Based Practice, the durable class question is: What evidence supports the judgment, what alternatives matter, and what remains outside the student's authority? 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

Move from cue to mechanism or standard, then to prioritized judgment, action, monitoring, and escalation. Use only de-identified authorized context.

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.

Building a multi part deliverable in dependency order

Late Week work usually has parts, and parts have dependencies. Assembly fails when a student drafts in reading order instead of build order. Map it first. List every component the live activity names. For each one, record what it needs before it can be finished: a decision made elsewhere in the document, a source, a calculation, a file conversion, an approval, or a step that another person or an institutional process controls.

Sort the list into three lanes. Lane one is work you control entirely and can do at any time. Lane two is work that depends on something you have already produced. Lane three is work that depends on someone else or on an institutional step, including any approval, registration, technical setup, or documentation associated with field or practice requirements. Lane three items get started first regardless of where they appear in the finished document, because waiting time is not yours to compress.

For any field or practice element, keep your own preparation to the written layer: what forms, records, or descriptions the applicable Walden process requires you to complete, and by when. The activity itself remains yours to perform under that process. The live instructions define the components, and the rubric in your registered classroom decides how the assembled work is scored.

Reading the rubric row by row

A rubric for an assembled deliverable behaves differently from a weekly one. It usually grades across the whole document rather than section by section, which means a single row can be won or lost in three separate places. Read it with that in mind.

Take each row and mark every section of your planned deliverable where it could be evaluated. A coherence row touches every transition. An evidence row touches every claim. A specific content row may touch only one section. This mapping tells you which rows need a whole document pass at the end and which can be closed out section by section as you build.

Then convert weights into working time. If one row carries a quarter of the score, it deserves roughly a quarter of your remaining sessions, which is almost never how drafts are actually built. Write the intended allocation next to each row before you start and check it midway.

Finally, note any row that depends on a step outside the document itself: submission format, file type, or a required accompanying item. Those behave as pass or fail in practice. Rubric structure, weighting, and level names are set by your section, so use the current version in your registered classroom and not an earlier one.

4. Use evidence deliberately

Prefer current authoritative clinical guidance and peer-reviewed evidence appropriate to the question; distinguish guideline recommendations from patient-specific facts.

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.

Consolidating a reference list that matches the argument

Assembly is where a source ledger becomes a reference list, and the conversion is a checking exercise rather than a formatting one. List your sections down one side and your sources across the other, then mark which source supports which section. Three things become visible immediately.

Sections with no source are either your own reasoning, which should be signaled as such, or unsupported claims, which need evidence or narrowing. Sources supporting no section are shelf weight and should come out. Sections leaning on a single source are fragile, and if that source is weak in authority or population fit, the whole section is weak with it.

Then balance the classes of evidence. A deliverable resting entirely on guidance documents can say what is advised but not what has been observed, and one resting entirely on individual studies can report findings without connecting them to professional standards. Health and wellness education work usually needs both, kept distinct.

Finish by confirming that every in text citation resolves and every entry is cited, in the style the activity requires. Required counts, types, dates, and style come from the live instructions, and the rubric posted in your registered classroom decides whether the evidence work qualifies.

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 safety, scope, differential logic, contraindications, documentation, confidentiality, and every student-performed clinical requirement.

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 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 how to fix them

The first pitfall is leaving lane three to the end. Approvals, registrations, technical setup, and any documentation tied to field or practice requirements move on institutional time rather than yours, and a finished draft cannot compensate for an unfinished process step. The fix is to open every lane three item in the first working session of this Week, even if only to confirm what it requires and how long it usually takes.

The second pitfall is a reference list that has outgrown the argument. Long lists look thorough and read as padding when half the entries never appear in the reasoning. The fix is the section by source map above, applied without sentiment.

The third pitfall is front loading polish. Students format headings and fix citations on a draft whose central section is still missing, because polishing feels productive. The fix is to keep a single ordered build list and to forbid formatting work until every component exists in rough form. Formatting is a fast pass at the end, while a missing component is not. What components are required, and what the submission must contain, is defined by the live instructions and judged by the rubric in your registered classroom.

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