HLTH 6207 Week 6 planning manual

1. Capture the live Week 6

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: making the planning table and the narrative agree

Integration Week has a natural test artifact in grant writing: the logic model, or whichever compressed planning table the live activity requires. Its value is that it forces the whole proposal onto one surface, where disagreements between sections become impossible to hide. Build it by reading across rows rather than down columns. A row runs inputs, activities, outputs, shorter-term outcomes, and longer-term outcomes for one strand of the program, and every cell in that row has to be about the same strand.

Two failures surface immediately when the table is read this way. An activity with no output means nobody will be able to demonstrate that the activity happened, which is a documentation problem as much as a design one. An outcome with no activity behind it is a wish, and it reads as one. Both are repairs to the plan, not to the table.

The integration step is the second pass: return to the narrative and confirm that every cell has at least one sentence, and that the sentence uses the same terms the cell uses. Earlier Weeks produced a need statement, a set of objectives, and an evidence rationale at different times and in different moods. This is where they are made to say the same thing in the same words. What the live activity actually requires remains the registered prompt's decision.

Reading the rubric row by row when integration is the criterion

Rows that reward synthesis are scored on connective tissue, which is the hardest thing to fake and the easiest thing to leave out. Read those rows and ask what two things each one wants joined: a concept and a case, evidence and a decision, an earlier unit and the current problem. Then locate the sentence in the draft where the join happens. If the join exists only in the student's head, the row is scored on what is visible.

A useful diagnostic is to read the artifact's section openings in sequence and ignore everything else. If they read as separate assignments placed end to end, the transitions are doing no work and the synthesis row will show it. The repair is one sentence at each seam stating what the previous section settled and what the next one therefore has to resolve.

Carry the method and the lesson forward from earlier Weeks, never the language: a later prompt requires new reasoning, new evidence, and fresh authorship even when the same concept returns. The rubric governing this activity is the one 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 when several units have to meet

Integration changes how a source is used more often than it changes which sources are used. One evaluation can legitimately appear in two places if it does different work in each: establishing that an approach has been tested in a comparable population, and later supplying the measurement interval its evaluators used. What is not legitimate is citing it twice for the same claim in order to create the appearance of two supports.

Keep a source-to-section map alongside the draft, recording the source, the section, and the job it performs there. The map exposes both problems at once, showing sections that carry no evidence and sources that carry too much. It also makes the final reference reconciliation mechanical instead of anxious.

Where an earlier Week's source has been superseded by something more current, replace it and record why, rather than keeping both because both were read. Required readings for the live activity come from 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 6 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 7. 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 6, 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 7.

Three Week 6 traps and the fix for each

The first trap is the planning table built last. A table assembled after the narrative is finished, purely because it was required, will contradict the narrative somewhere, and the contradiction is visible to any reader who reads both. The fix is to build the table first, reconcile the narrative to it, and change both together whenever a design decision changes.

The second trap is the recycled paragraph. Integration invites reuse of language that already scored well, which is not what integration means and not what the course permits. The fix is to carry the method and the finding forward and to write the passage again for the current prompt, from the current evidence.

The third trap is the outcome that restates the activity in different words. Participants will attend sessions is not an outcome, and rephrasing it as participants will engage with programming does not make it one. The fix is to name the change in knowledge, behavior, condition, or capacity that attendance is supposed to produce, and to confirm a measure could detect that change.

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

Week 6 questions