HLTH 6280 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 Policy and Politics in American Political Institutions, the durable class question is: Which authority, duty, conflict, stakeholder, and consequence control the decision? 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

Name the governing rule accurately, separate law from policy and ethics, apply it to the facts, compare defensible options, and commit to a justified recommendation.

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: revise the argument, not the sentences

Revision at this stage should start above the sentence. Export the draft and mark only three things: the claim of each section, the warrant connecting the evidence to that claim, and every place the reader is asked to accept a step that was never shown. The third mark is where the points are. Most policy analysis that reads well and scores poorly is missing warrants: the source is present, the conclusion is present, and the sentence explaining why the source supports the conclusion is not.

Then check the direction of the argument. Does the conclusion follow from the criteria you set, or was it decided first and the criteria arranged around it afterward. A recommendation that would survive unchanged if two of your criteria were reversed is not actually resting on those criteria. Check whether the counterargument is answered or merely acknowledged, and whether the limitation section quietly withdraws the recommendation the draft just made.

Only after those repairs should you work on sentences. Reordering paragraphs and tightening prose inside a draft whose warrants are missing is expensive work that moves no reasoning row. Which rows exist and how they are weighted is decided by the registered classroom.

Reading the rubric row by row as a revision log

Turn the rubric into a revision log rather than a checklist. Give each row three fields: the current state of the draft against it, the specific change that would move it, and the time that change will take. Then sort by weight multiplied by gap. The largest product is your first revision, and it is often not the row you find most interesting.

Bring the criterion-level feedback ledger from earlier Weeks into the same table. A row you have lost points on before deserves a dedicated pass even when this draft feels fine on it, because the pattern is more reliable than the impression. Do one pass per row, reading for that row alone, and record what you changed. A written log lets you confirm at the end that every planned revision actually happened, which a mental list never does.

Stop adding sources as a substitute for revision. A new citation rarely repairs a reasoning row and frequently costs an integration row. Re-copy the live rubric in the registered classroom before this pass rather than working from the file you saved in Week 1, because that live version is the one that decides the score.

4. Use evidence deliberately

Use primary authority where the task permits, then current scholarly or professional interpretation; never cite a summary as if it were the controlling rule.

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.

Repairing sourcing that feedback has flagged

Feedback about sources usually names one of four problems, and each has a different repair. If the comment is about currency, either replace the item or justify why an older foundational source is still appropriate for that particular claim. If it is about authority, trace the summary back to the instrument and cite what actually governs. If it is about integration, the source is fine and the sentence is wrong, so rewrite until the claim depends on the source rather than sitting beside it. If it is about relevance, the source is answering a different question and should be removed rather than defended.

Do the tracing work rather than the swapping work. Replacing one summary with a different summary is the most common false repair, and it reads as effort without accuracy.

Then re-check the whole list for jurisdiction and population match, because revision routinely moves a claim into a new section where its original source no longer fits. Keep the use notes current as you go. A source whose job changed during revision is the one most likely to end up supporting a sentence it never supported.

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

Verify jurisdiction, date, definitions, exceptions, stakeholder effects, counterarguments, and whether the recommendation exceeds the evidence.

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

Revision Weeks fail in ways that feel like diligence.

The first is surface-only revision. Hours go into transitions, word choice, and paragraph order while the missing warrants stay missing. The fix is to run the warrant pass first and forbid sentence-level work until every section has a stated connection between its evidence and its claim.

The second is confidence creep. Revision adds clarity, clarity reads as certainty, and the conclusion ends up claiming more than the record supports. The fix is to re-run the over-claim check after revising rather than only before: read the recommendation against the strongest limitation in your own draft and see whether both can be true.

The third is version confusion. Two or three copies of the work exist, edits land in the wrong one, and the file that gets submitted is not the file that was revised. The fix is a single named working file with the date in its name, one archive folder for everything superseded, and a final check that the file you open before submission contains the last change you remember making.

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