HLTH 4925 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 Seminar in Reflective and Applied Learning, 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.

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.

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

Building a larger artifact in dependency order

Late-course work in a capstone concentrates the stakes, and the failure mode is almost never writing ability. It is sequencing. Begin by reverse-scheduling from the due date and time zone shown in the classroom: submission and verification, then the final format and citation pass, then the full read against the rubric, then the drafting blocks, then any dependency that must be complete before drafting can start. Whatever date that arithmetic produces for the first block is the real start date, and it usually lands earlier than it feels.

Then build in dependency order rather than reading order. Create the skeleton from the rubric rows, one heading per row, so the structure is scored by construction. Draft the heaviest analytic section first, because it determines what the rest of the artifact has to say. Draft the supporting sections next, then the connective material that links them. Write the introduction and any abstract or summary last, when there is something real to introduce. Front matter written first is a prediction, front matter written last is a description, and only one of those matches the finished work.

Control scope while building. A capstone artifact grows by accretion unless a boundary is declared, so write the scope sentence into the working file: what the artifact covers, what it does not, and why the exclusion is defensible. When new material arrives that falls outside that sentence, it goes into a notes file rather than into the draft. Whether the activity carries a length limit, and what that limit counts, is a question only the live instructions answer.

Reading the rubric row by row for a multi-part artifact

A longer artifact usually has more rows, and the rows stop being independent. Map them before drafting. Write each row on its own line with its points, then mark which section will satisfy it and which other rows depend on the same content. Rows that share content have to be planned together, because a section written for one row and never checked against the other is how a well-written artifact loses points on a criterion the writer believed was covered.

Then look for structural rows that no single section can satisfy: organization, coherence, adherence to the required format, and use of course content throughout. Those are verified by reading the whole artifact rather than by writing one more section, so schedule that whole-artifact read as its own block instead of assuming it will happen during editing. Use the rubric version attached to the live activity, since your classroom rubric decides how rows and sections finally map, and if a required element in the instructions has no matching row, include it anyway, because instructions and rubrics do not always cover identical ground.

Freezing the source shelf and reconciling the reference list

Set a date after which no new source enters the artifact, and place it before the final drafting block. Late sources force late restructuring and are the most common cause of a citation error in an otherwise careful document. Before that date, close the gaps deliberately: read the skeleton, mark every claim whose support is thin, weak in authority, or carried by a source that has already done too much work, then fill only those gaps.

After the freeze, reconcile in both directions. Every in-text citation must appear in the reference list, and every reference-list entry must appear in the text, with names, years, and titles matched exactly. Check that each entry still has a live use note, because an entry that no longer supports anything should be removed rather than left as evidence of effort. Confirm the required style and any activity-specific citation instruction from the live classroom rather than from habit carried over from another course.

Three assembly traps, and the fix for each

The first is starting the final artifact at the introduction. It produces a confident opening for an argument that does not yet exist and spends the freshest working hours on the part most likely to be rewritten. The fix is the build order above: skeleton, heaviest section, support, connective material, introduction last.

The second is the late dependency, an approval, a group contribution, a required step, or a technical arrangement discovered after drafting is underway. The fix is a dependency sweep in the first block of the Week, listing every step that involves another person or an institutional process, each with its own earlier deadline.

The third is unbounded scope, where the artifact keeps absorbing interesting material until nothing is finished well. The fix is the scope sentence plus a notes file, and a rule that no new section is added once the skeleton has been checked against the rubric.

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