HLTH 6207 Week 9 planning manual

1. Capture the live Week 9

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: assembling a complete package on a real timeline

Applications fail on completeness more often than on quality, and Week 9 is the point at which a completeness plan is still useful rather than merely aspirational. Build the assembly checklist from the controlling instructions rather than from memory: the narrative sections in their required order, the length and formatting limits, and every separate item that has to travel with the narrative, such as a work plan or timeline, an evaluation plan, a budget with its justification, evidence of organizational capacity, and letters of commitment from named partners.

Then sort that checklist by who controls each item, because that ordering is what makes a timeline real. Items the student controls can be finished at any point. Items depending on other people, on approvals, or on a system converting or accepting a file cannot, and each of those needs an internal deadline set far enough ahead that a single non-response does not become a failure. Request the dependent items first, even when they are the smallest pieces of work in the package.

The remaining reasoning concerns order of assembly: build the parts that constrain others before the parts they constrain, so that a late change in one place does not force rework everywhere else. What is actually required, and in what order, comes from the live instructions in the registered classroom.

Reading the rubric row by row before assembly

Before anything is assembled, build a row-to-location index recording the rubric row, the section that answers it, and the heading a reader would reach for. The index has one purpose, which is to prove that no row is homeless. A criterion with no location is a criterion the artifact does not address, and discovering that now costs a revision session rather than a grade.

The index also exposes the opposite problem. When three rows all point at the same paragraph, that paragraph is carrying more than it can hold and a reader will find only one of the three. The repair is to give each row a visible place of its own, using headings that name the concept the row is about without copying the rubric wording as empty labels.

Build the index against the rubric attached to the live activity, and rebuild it if the rubric version changes 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 assembly

Assembly is where reference problems surface, so reconcile deliberately rather than trusting a tool. Read the draft and list every in-text citation in order; read the reference list and mark each entry as it is matched. Unmatched entries in either direction are errors, and the most common one by far is a source removed from the text during revision and left standing in the list.

Then verify retrievability. Open every link, confirm every document still resolves, and check whether data pages have been updated to a newer year since they were captured, because a figure quoted from a page that now shows a different number is a problem a reader can reproduce in seconds. Record the retrieval date wherever the citation style calls for one.

Style, required elements, and any locator conventions are set by the registered classroom.

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

Three Week 9 traps and the fix for each

The first trap is the attachment prepared and never attached. It is finished, it sits in the working folder, and it is not in the submission, which is indistinguishable from never having written it. The fix is a final upload checklist verified against the assembled submission rather than against the folder.

The second trap is meeting a length limit by cutting the section that argues. Under pressure the evaluation plan and the justification are the easiest passages to shorten, because they are the least narrative, and they are frequently among the most heavily weighted. The fix is to cut description and repetition first and to check the weights before removing anything.

The third trap is assembly scheduled for the due date. Conversion failures, upload errors, and missing signatures all appear at the end, and none of them can be solved in the final hour. The fix is to complete a full dry assembly at least one working day early and to treat the remaining time as margin. Deadlines, the controlling time zone, and the submission route are set by the registered classroom.

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

Week 9 questions