HLTH 6207 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 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: revising from criterion-level feedback

Revision works only if feedback is sorted before anything is rewritten, because different comments require different repairs and applying the wrong one wastes the Week. Sort every comment into one of five bins: the task was misread, the reasoning was incomplete, the evidence did not fit, the writing obscured a sound argument, or a process requirement was missed. A misread task requires a new draft of the section, not a better sentence. Incomplete reasoning requires the missing step to be written. Evidence that did not fit requires a different source, not a stronger verb.

Then revise in that order, from the largest unit downward. Task-level repairs come first, because they can delete work that would otherwise be polished. Reasoning next, then evidence, then paragraph structure, then sentences, then mechanics. Working upward from mechanics is the most common way a revision session ends with a cleaner draft that scores exactly the same.

Treat cutting as a revision method rather than a last resort. In grant writing especially, a proposal comfortably inside its limit with every claim defended reads as more disciplined than one pushed to the limit with restatement. Which rubric governs the revised work, and whether a revision is permitted at all, is decided by the registered classroom and the instructor.

Reading the rubric row by row during revision

Put the returned rubric and the rubric for the current work side by side before revising anything. They are frequently not identical, and revising toward the older one is a way of losing the same points twice. Where the wording differs, the current version governs; where a weight has changed, effort should follow the new weight rather than the old habit.

Then work the rows in score order, weakest first, and give the weakest row a full working session of its own rather than a pass mixed in with everything else. Record what was changed for that row, so the next return can be read as evidence about whether the repair worked instead of as a fresh surprise.

A rubric saved from another section or another term is not a substitute for the one attached to the live activity in the registered classroom.

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

Revision is the right moment to remove sources rather than add them. Go through the list and identify every source surviving only because it was read: if no sentence depends on it, it is occupying attention the weakest section needs. Then look for places where a claim is carrying more weight than its support, and upgrade the source rather than softening the claim, where a stronger one exists.

Heavy editing also breaks paraphrases. When a passage has been restructured several times, compare it against the original source once more, because meaning drifts through successive rewrites even when nobody intended it. Re-verify any figure that was moved, combined, or rounded during revision, and confirm its citation moved with it.

Required readings and the citation style remain whatever the registered classroom specifies for this activity.

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.

Three Week 10 traps and the fix for each

The first trap is revising only what was commented on. Feedback is a sample rather than an inventory, and an instructor who noted one unsupported claim rarely listed every instance of the same pattern. The fix is to treat each comment as a category and to search the whole draft for other members of that category.

The second trap is answering a weakness with volume. A section marked as thin receives three more paragraphs and two more citations and scores the same, because the missing element was a connection rather than material. The fix is to identify what the row asked for before adding anything, and then to add only that.

The third trap is revising a superseded file. Versions accumulate across a course, and a session spent improving the wrong one is a session lost entirely. The fix is a strict naming convention with dates, one working file at a time, and a check of the file's own timestamp against the last submission before revision begins.

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