HLTH 6100 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 Critical Issues in Emergency Management, the durable class question is: What outcome is being chosen, for whom, under which constraints and trade-offs? 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

Convert theory into criteria, compare options against evidence and constraints, quantify material effects where possible, then state implementation, ownership, and measurement.

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.

Revising the argument rather than the sentences in Week 10

Revision at this stage should change what the work claims, not how it sounds. Take every piece of feedback received in the course and sort it into three bins: the reader did not believe the claim, the reader could not find the support, or the reader could not follow the path. Each bin has a different repair, and applying the wrong one is why some students revise repeatedly without moving.

For belief problems, the fix is evidence or a narrower claim, and narrowing is usually the better move, because a smaller claim that holds beats a large one that does not. For location problems, the fix is structural: headings, an explicit statement of the criteria, or a table that puts the comparison where a reader expects it. For path problems, the fix is sequence, which usually means moving the criteria earlier and the conclusion later than instinct suggests.

Then reconcile across the course. Your later analysis may contradict something you argued earlier, and that is normal and defensible when it is acknowledged. Write the reconciliation sentence: what you concluded before, what changed your assessment, and what you conclude now. Silent contradiction reads as carelessness, while a stated revision reads as judgment. Check that your criteria names, defined terms, and measurement rules are identical everywhere they appear, since inconsistency in those three places accounts for a large share of late-course confusion.

Reading the rubric row by row as a revision instruction

A rubric is a revision instrument as much as a scoring one. Convert each row into an imperative edit and put it on a checklist: state the basis of comparison in one place, attribute every number to a population, name the trade-off, give the metric an owner. Work the list against the draft one row at a time rather than rereading the whole document, because whole-document reads catch tone and miss criteria.

Where you have prior feedback on a row, place the instructor's exact words beside it, since a comment is usually more specific than the rubric text and is the closest thing to the scorer's own reading. Where a row has cost points more than once in the course, mark it and check it twice, with the second check performed after a break so you read what is there rather than what you intended. Your registered classroom rubric decides the final judgment, and the live version for this activity is the one to work from even where an earlier rubric in the same course looked similar.

4. Use evidence deliberately

Combine relevant scholarly literature with current market, organizational, or policy evidence while labeling assumptions and protecting confidential information.

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 source-level feedback in Week 10

Source feedback usually names one of four problems: a claim with no support, a citation attached to something the source does not say, quotation used where analysis was expected, or a source whose authority does not match the claim's weight. Diagnose which one applies before touching the reference list, because three of the four are fixed in the prose and only one is fixed by adding a source.

Work the fixes in order of cost. Unsupported claims either get a source or get narrowed until they are ordinary. Mismatched attributions require reopening the source and rewriting the sentence to what it actually supports. Over-quoting is repaired by paraphrasing from your notes and keeping the quotation only where the wording itself is the evidence. Authority mismatches are repaired by promoting the claim's support from general reference or news material to peer-reviewed research, standards, or authoritative agency documents. Then stop, because adding unfamiliar sources during a final revision is how new errors enter a draft that was nearly finished.

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

Stress-test feasibility, incentives, ethics, risk, counterarguments, implementation ownership, and the metric that would show the decision worked.

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.

Three Week 10 pitfalls and the fix for each

The first is polishing sentences a reader already understood while leaving the disputed claim untouched. The fix is to work the feedback bins first and to grant yourself a prose pass only after the argument-level repairs are done.

The second is applying a correction only to the file it came from. A criterion missed in one activity is usually missed as a pattern, and a fix that lives in one document does not carry. The fix is to update your working template and your criteria glossary at the same time you revise the draft, so the correction becomes structural.

The third is destabilizing a good draft in the last hours. Late structural rewrites, newly added sources, and format experiments introduce errors at the moment there is no time left to catch them. The fix is a stated cutoff hour after which only verification tasks are permitted, with the version saved and the submission route tested before that hour arrives.

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.

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