HLTH 6207 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 Grant Writing, 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.

Worked reasoning: the final read of work that has to stand without its author

Closure ends with a read that no earlier Week can substitute for, because the finished work will be assessed by someone who was not present while it was made. Run it as three separate passes asking three different questions. The compliance pass asks only whether every required element is present in the required form, and it is done with a checklist rather than with judgment. The reviewer pass asks, criterion by criterion, what each section earns and what a skeptical reader could withhold. The plain reader pass asks whether someone outside the subject can state the problem, the plan, and how success would be recognized after a single reading.

The plain reader pass is the one most often skipped and the one that catches what the other two cannot. Work that has been revised many times becomes legible to its author long before it becomes legible to a stranger, and the passages surviving on the author's memory of what they meant are exactly the passages a new reader stalls on.

If the live work includes forward-looking sections such as sustainability or dissemination, read them last and check that they describe specific commitments rather than intentions. What the final activity actually requires is set by the registered classroom.

Reading the rubric row by row one last time

The final row-by-row pass is a verification, not an exploration. Take the live rubric, take the finished artifact, and confirm for each row that a specific passage answers it, that the passage sits where a reader would look for it, and that nothing in the row is left unaddressed. Mark each row as verified rather than reading the rubric as prose, because a prose read confirms familiarity rather than coverage.

Then archive the row-level history from the whole course: which criteria recurred, which improved, and which one is still weakest. That record is the most portable thing the course produces, and it belongs in the first study session of the next one.

Grades, designations, and progression decisions are made by Walden and the instructor. This page describes a method and cannot anticipate the result of any rubric row.

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.

Source work at closure

Close the evidence file rather than abandoning it. Reconcile citations against the reference list one final time, confirm every retrieval still resolves, and check whether any figure has been superseded by a newer data release since the draft was written. Where a number has changed, decide deliberately whether to update it or to state the year the draft used.

Then annotate the file for reuse. Mark which sources are foundational and likely to stay useful, which are current data that will need refreshing within a year, and which were specific to this activity and can be retired. Keep the definitions and the population notes, because that is the part which is expensive to reconstruct later.

Preserve the method and the shelf, never the submitted language: a later course requires new reasoning, new evidence, and original authorship even when the subject returns. Required readings for any future activity come from that classroom.

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.

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

The first trap is submitting without opening what was submitted. A file can upload as the wrong version, convert badly, or arrive empty, and none of that is visible from a confirmation screen alone. The fix is to open the submitted artifact from inside the submission record, read the first and last pages, and save the receipt with its timestamp.

The second trap is treating the final Week as formatting while a dependency is unfinished. An outstanding approval, an unposted reply, or an incomplete institutional step does not resolve itself, and a polished artifact cannot compensate for it. The fix is to check the dependency lanes before the content passes, and to raise anything unresolved through the official channel immediately.

The third trap is discarding the course record. The feedback ledger, the rubric history, the evidence file, and the working checklists get deleted along with the drafts, and the next course starts from nothing. The fix is to archive the method artifacts separately from the submitted work, so that what carries forward is the way the work was done. Grades, progression, and any post-submission remedy remain decisions of Walden and the instructor.

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