HLTH 6475 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 Health and Wellness Education Program Planning, Implementation and Evaluation, the durable class question is: Which population, determinant, stakeholder, and measurable outcome define the problem? 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 population and baseline, trace determinants and system constraints, compare interventions, and connect the recommendation to implementation and evaluation.

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: verifying a close instead of assuming one

The final Week has two jobs, and only the first is writing. The second is verification, which in this subject mirrors the summative evaluation logic the class teaches: evidence that something happened, not confidence that it did. Work from a checklist built out of the control file. Every activity listed for the term has a state, and the states are limited: submitted and confirmed, submitted and unconfirmed, outstanding, or waived by the instructor. Anything unconfirmed is checked by opening the submitted artifact itself and reading the timestamp, the file, and the receipt, because a page that appeared to accept an upload is not the same as an upload that landed.

Then close the reasoning side. Read the term's work as a body and write, in a few sentences, what the course actually taught you about moving from a population and its determinants to a strategy, an implementation requirement, and a measurement plan. That paragraph is not for submission; it is the compression step that turns eleven Weeks of activity into a method you can carry. Add to it the two or three judgments you now make differently, such as writing objectives with denominators attached, or checking the level of a source before citing it, since those specific, small habits are what actually transfer into the next class and into practice.

Reading the rubric row by row one last time

The final rubric pass is a matching exercise, not an improvement exercise, and it works best done slowly with the finished document beside the live rubric. For each row, name the exact location satisfying it, and write that location down. Rows without a location are the remaining work, and knowing that with time left is the entire point of doing this pass before the deadline rather than after the grade.

Then extend the check past the document. Confirm the file type, the naming convention, the length, the citation style, the accessibility requirements, any originality or verification step the classroom requires, and the submission location, since a document that satisfies every content row can still fail on a process step. Keep the rubric itself, along with your row-by-row notes, in the carry-forward file, because rubric language repeats across a program and the reading skill built here is reusable even though the specific rows are not. The registered classroom remains the authority for every row, every threshold, and every deadline, so your classroom rubric decides how this final comparison ends.

4. Use evidence deliberately

Use current surveillance, policy, organizational, and peer-reviewed evidence at the same geographic and population level as 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.

Curating the source library so the next class inherits it

A term's worth of reading is an asset if it is stored as a working library and a liability if it is stored as a downloads folder. Keep three things. Keep the annotated matrix, with each source's date, authority or design, population and setting, usable finding, and limitation, since that matrix is what makes a source reusable without rereading it in full. Keep the search record, meaning the databases, terms, filters, and date ranges that produced good results, because search skill is course-independent and rebuilding it each term is pure waste. Keep the definitional sources, especially indicator and measure documentation, which stay accurate far longer than any prevalence figure.

Prune the rest. Sources that never supported a claim were never evidence, and carrying them forward only makes the library harder to search. One boundary carries into every future class: the library holds sources and method, not submitted prose. A later prompt requires fresh reasoning, fresh evidence use, and your own new authorship even when the concept is familiar, and the library exists to make that faster rather than to make it unnecessary.

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

Test equity, feasibility, stakeholder effects, measurement validity, unintended consequences, and the boundary between association and causation.

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 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

Pitfall: assuming a submission landed. The end of a term produces upload failures, wrong-file submissions, and drafts saved rather than submitted, and each one is invisible until it is too late to repair quietly. The fix is verification by opening: for every final item, open the submitted artifact, confirm it is the correct and complete file, save the receipt or confirmation, and contact the instructor or the official support channel immediately about anything that does not verify.

Pitfall: closing the term without recording criterion-level lessons. Final feedback often arrives after attention has moved on, and it is the most specific information the term produced about your own weakest rows. The fix is a scheduled return to the gradebook after grades post, adding the last results to the criterion ledger with the same fields used all term, so the next class begins with a diagnosis rather than with hope.

Pitfall: planning to reuse the finished work later. Saving a completed document as a template for a future class sets up an authorship problem and, just as often, a relevance problem, since the next prompt will differ in population, setting, or purpose. The fix is to extract the method into a reusable outline, meaning the questions asked and the order they were answered in, and to archive the document itself as a record of work already submitted rather than as raw material.

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