HLTH 6300 Week 11 planning manual
A course-specific Week workflow for capture, reasoning, evidence, student authorship, quality control, and gradebook closure.
Complete the live final work, verify submissions and grades, and preserve the methods and feedback that belong in the next course. This page verifies a position in the Course-Based quarter calendar, not a universal assignment identity.
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.
| Control field | What to verify now |
|---|---|
| Identity | Exact course, Week, activity, and current version |
| Task | Every required action, question, audience, and deliverable part |
| Grading | Rubric rows, points, weights, thresholds, and penalties |
| Evidence | Assigned readings, source rules, dates, authority, and citation style |
| Calendar | Initial post, replies, files, approvals, due time, and time zone |
| Dependencies | Group, field, clinical, residency, proctoring, feedback, or approval steps |
2. State the Week's reasoning question
For Disaster Response and Recovery, 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: write a close that stands on its own
A closing submission, where one is assigned, is read differently from a mid-course one. The reader is asking whether the student can state a position, support it, and say what it does not cover. Build it in that order. Lead with the claim in a single sentence naming the case and the phase. Support it with the strongest two or three pieces of the term's work rather than with all of them. Then state the limits: what the analysis assumed, what evidence was unavailable, and what would change the conclusion. A closing piece that names its own boundary reads as finished rather than as trimmed for length.
Where the live activity asks for reflection, keep it concrete. Reflection that names a specific change in how the student reads guidance, frames a population, or tests a recommendation is substantive; reflection reporting that a great deal was learned is not. Tie each stated change to the point in the course where it happened and to the next place it will be used. Whether reflection is requested, and in what form, is set by the registered prompt and rubric.
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.
Closing the source record and keeping what is useful
The last evidence task has two halves. The first is verification: every citation resolves, every entry matches its in-text use, every version and revision date is current, and nothing from an earlier submission has been carried forward without fresh reasoning behind it. The second is retention. Keep an annotated list of the sources that proved genuinely useful, organized by function rather than by assignment, since a later course in a preparedness or self-designed focus area is likely to need the same bodies of guidance and the same evaluation literature.
Note beside each retained source what it is good for and what it cannot support, because that judgment is expensive to rebuild later. Also record where the record was thin, since a persistent gap in the published literature is worth remembering as a research interest rather than as a frustration. Assigned readings belong to this term's activities; what carries forward is the method for finding and testing sources, not previously submitted language.
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
For a final submission, read the rubric once as a checklist and once as a description of a reader. The checklist pass confirms every row has a visible home in the document. The reader pass asks what impression the rows together describe, and whether someone encountering the work cold would form that impression. Both passes matter, and the second catches drafts that are technically complete and still hard to follow.
Then take one more pass for the mechanical rows: length, format, file type, headings, citation style, and any submission requirement stated separately from the rubric. These carry small weights individually and are the easiest points to lose at the end of a term, when attention sits on content. Confirm each against the live instructions rather than against memory of earlier Weeks, since requirements can differ by activity. Rubric rows, weighting, and level names differ by section and term, so your classroom rubric decides.
Three Week 11 pitfalls and the fix for each
The first is stopping at submission. The upload is not the end of the obligation; the student still confirms the timestamp, opens the submitted file, checks that it is the intended version, and saves the receipt. The fix is to treat those four steps as part of the activity rather than as optional reassurance.
The second is losing the course's working materials. The case statement, glossary, source notes, and feedback ledger are usually deleted or buried within weeks of a term ending, and rebuilding them costs far more than storing them. The fix is one folder, saved outside the classroom, holding those four files and nothing else.
The third is closing without a diagnosis. A term ends, a result posts, and the recurring weakness goes unnamed, which means the next course repeats it. The fix is a short written note stating the one habit that cost the most across the term and the one check that would prevent it, kept where it will actually be read at the start of the next class.
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.
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
What is assigned in HLTH 6300 Week 11?
Only the registered Course-Based classroom can answer that. This positional manual deliberately does not invent a discussion, paper, quiz, project, exam, practicum task, or rubric.
How should I start HLTH 6300 Week 11?
Capture every live activity, instruction, rubric row, point value, deadline, reply rule, dependency, and submission route before researching or drafting.
Can a tutor perform the Week for the student?
No. Tutoring supports understanding, method, practice, and feedback; the student performs required activity, authors the response, verifies it, and submits it.