HLTH 1015 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 Exploring Your Path: Foundations Across Fields, 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.

Revise by diagnosis, not by sentence

Revision at this stage should begin with classification rather than with the keyboard. Take every piece of feedback you have received and label it with one of seven causes: understanding, task interpretation, reasoning, evidence, communication, format, or process. The label determines the repair, and the repairs are genuinely different. An understanding gap is repaired by rereading and re-explaining a concept, not by rewriting a paragraph. A task interpretation gap is repaired by reading the prompt against the rubric again. A process gap is repaired by changing a calendar, not a draft.

The evidence category deserves a worked rule, because it is the one most often mishandled. When a claim and its source do not match, there are exactly two honest repairs: change the claim so the existing evidence supports it, or change the evidence so it supports the existing claim. What is not available is leaving the mismatch and adding emphasis, yet adding adjectives to an unsupported sentence is the most common thing done instead. Decide which side moves, make the move, then reread the surrounding sentences, because a changed claim usually orphans the sentence that followed it.

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.

Replacing a source that did not hold

When feedback marks a source as weak, dated, or not on point, the repair is a like-for-like replacement at the same level as the claim, followed by a rewritten sentence. Swapping the citation and leaving the sentence untouched almost never works, because the new source says something slightly different and the sentence was built around the old one. Find the replacement first, read it properly, then write the sentence again from what the new source actually establishes.

Use the same pass to catch the quieter version of the problem: a source that was never flagged but does no work. Read each paragraph and ask what would be lost if the citation vanished. If the answer is nothing, either write the sentence that makes the source matter or remove it and let the paragraph stand on the reasoning it already has. In a course surveying several fields, a lean list of sources you can each describe from memory is a stronger position than a long list assembled for appearance, and it is far easier to verify in the final hours.

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.

Reading the rubric row by row during revision

Revise against the rubric governing the work you are submitting now, not the one attached to the feedback you are responding to. They may be identical and they may not be, and assuming is how a careful revision misses a row that changed. Put the current rubric beside the draft and do a pointing exercise: for each row, point at the text that answers it and read that text aloud. Rows you cannot point at become the revision list, worked in weight order.

Then read the returned rubric once more as a separate document, this time looking only at the wording of the level above the one you received. That wording is the most precise description available of what a reader was looking for and did not find, and it usually names a specific behavior rather than a quality. Turn it into an instruction you can execute in this draft. How the current work is scored, your classroom rubric decides, and instructor direction outranks any general method.

Keep a record of what you repaired. For each row you worked on, write one line naming the defect, the change you made, and where in the draft the change now lives. That record is useful twice. It keeps the revision honest, because a defect you cannot describe in one line was probably reworded rather than repaired, and it gives you a short list to verify in the final pass instead of a whole document to reread anxiously. It also carries into the next course, where the same rows tend to reappear under different topic names. Revision earns its hours only when the lesson survives the file, and one line per row is the cheapest way to make that happen.

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

The first pitfall is editing the surface of a paragraph whose claim was the problem. Feedback about weak analysis gets answered with tighter sentences, and the same row comes back marked the same way. The fix is the diagnosis step above: identify whether the defect lives in the claim, the evidence, or the presentation, and reach for sentence-level editing only when the answer is presentation.

The second pitfall is accepting every comment literally without interpreting it. A brief marginal note is a symptom, and treating it as a complete instruction produces a narrow fix that leaves the underlying pattern intact. The fix is to ask what the comment implies about your method, look for the same defect in two other places the reader did not mark, and repair all three.

The third pitfall is revising past the point of improvement. Late passes with tired eyes introduce new errors, break citations, and disturb paragraphs that were already working. The fix is a stopping rule set in advance: a fixed number of passes with a stated purpose each, then a verification pass only, then submission. Revision without a stopping rule is how a good draft arrives late and slightly broken.

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