HLTH 4925 Week 10 planning manual

1. Capture the live Week 10

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

Revision as diagnosis, in three ordered passes

Revision late in a course fails when it starts at the sentence level, because sentence work cannot repair a structural problem and it consumes the hours structural work needs. Run three passes in order and do not mix them. The structural pass asks whether the artifact contains what the rubric rows require and whether the sections stand in a defensible order. The paragraph pass asks whether each paragraph carries one claim, supports it, and connects to the next. The sentence pass asks whether every sentence is precise, attributed, and readable. Only the third pass touches wording.

Run the structural pass as a reverse outline. Read the draft and write, for each paragraph, the claim it actually makes rather than the claim it was meant to make. Then read the resulting list on its own. Duplicated claims mean two paragraphs should merge. A claim that appears nowhere in the list but is required by a rubric row means a section is missing. A list whose order does not build means sections should move. Restructuring at this point is cheap, and restructuring after a polish pass wastes the polish.

Treat instructor feedback as diagnosis rather than as a task list. A comment on one paragraph is usually an instance of a pattern that shows up in several. Read the comment, name the underlying behavior, then search the whole artifact for that behavior and repair every occurrence. Correcting only the marked instance guarantees the same comment on the next artifact.

Reading the rubric row by row while revising

Revising against a rubric differs from drafting against one. Copy the rows out, then read the draft once per row, looking for that row alone. Reading for everything at once is how a writer sees the artifact they intended rather than the one on the page. For each row, mark the exact location that satisfies it. Rows with no location become the revision list, worked in weight order.

Then check the rows against the criterion-level feedback ledger the course has been building. If a row has lost points before, treat it as the first item regardless of weight, because a repeated loss is the most predictable one. Where a returned comment and the printed row appear to point in different directions, the instructor's reading governs the work in this section, and a short clarifying question is more efficient than guessing. Your classroom rubric decides the standard that is finally applied.

Repairing citation-claim mismatch and retiring idle sources

A late-course revision is the last practical chance to confirm that the reference list and the argument describe the same document. Work through the draft citation by citation and ask what each source is being asked to prove in that sentence. Three failures are common: a source that supports a narrower claim than the sentence makes, a source that supports a related but different claim, and a source inherited from an earlier Week whose relevance quietly expired as the argument moved.

Fix the first by narrowing the sentence, the second by finding support that matches or softening to what the source actually shows, and the third by removing both the citation and the entry. Then check for the opposite problem, an important claim carrying no citation at all, which tends to appear in paragraphs revised heavily enough to lose their attribution along the way. Finish by reconciling the reference list in both directions again, since revision breaks the match that was verified before revision began.

Three revision traps, and the correction for each

The first is revision that only adds. When a comment says a section is weak, the instinct is to make it longer, and length rarely repairs a reasoning gap. The fix is to name the missing element, whether warrant, evidence, implication, or structure, and add only that.

The second is fixing the instance instead of the pattern, which produces a clean artifact and an unchanged method. The fix is the pattern search described above, plus a note in the feedback ledger naming the behavior so the next artifact is checked for it before submission.

The third is format breakage during restructuring. Moving sections corrupts heading levels, numbering, cross-references, and citation placement more often than writers expect. The fix is a final format pass run after the last structural change, checking headings, style, reference list, file type, and successful file opening, in that order.

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 10 activities. The registered syllabus, classroom, rubric, announcements, instructor directions, and official policies remain controlling.

Week 10 questions