HLTH 6207 Week 3 planning manual

1. Capture the live Week 3

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: the difference between a goal and an objective a reader can score

Week 3 is where reasoning has to become visible, and in grant writing the clearest place to show it is the move from goal to objective. A goal states direction and is allowed to be broad. An objective is a testable claim about the future, and it has to name five things: who changes, what changes, by how much, by when, and how the change will be detected.

Work the transformation rather than asserting it. An objective phrased as improving awareness among community members fails on four of those five counts, since it names no bounded population, no baseline, no magnitude, and no measurement source. Rebuilding it forces the decisions the rest of the proposal depends on. Naming the population fixes the denominator. Naming a baseline requires a data source, which is a commitment the evaluation section then has to honor. Naming a magnitude requires a defensible reason for that particular number, usually drawn from what comparable programs reported. Naming a date binds the objective to the period the plan covers.

The mechanism a reader scores is traceability running in both directions. Each objective should point backward to a specific claim in the need statement and forward to an activity that could plausibly produce it and a measure that could plausibly detect it. When that trace is written out instead of assumed, the reasoning is on the page rather than in the author's head. Whether the live activity calls for objectives at all remains a decision of the registered prompt.

Reading the rubric row by row when reasoning is the criterion

Rows that reward analysis are not asking for more sentences on the same subject. They are asking for steps arranged in an order a reader can follow. Sort the rubric into two groups: rows that can be satisfied by presence, such as required elements, formatting, and citation mechanics, and rows that can only be satisfied by sequence, such as analysis, justification, and evaluation of alternatives.

Then test the draft against the second group with one question per row. If the concluding sentence were removed, could a reader reconstruct it from the sentences above it? If yes, the reasoning is genuinely on the page. If the conclusion is the only place the idea ever appears, the paragraph is asserting rather than analyzing, and the repair is to supply the missing step rather than to strengthen the adjective.

Map every reasoning row to the specific passage that carries it and keep that map beside the draft while revising. The criteria, their wording, and their weight come from the rubric attached to the live activity 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.

Choosing sources that can carry a mechanism

Not every credible source can support a claim about why something works. Prevalence data establishes that a problem exists and can never explain a mechanism. A program evaluation with a comparison condition can support a claim that an approach produced a change. A systematic review or a curated evidence registry entry can support a claim that the approach produces change across more than one setting. Descriptive articles and conference summaries can suggest feasibility and rarely support more than that.

Match the source to the load the sentence puts on it, then bring it in with three moves: what the source did, what it found, and what that changes for the plan being written. The third move is the one most drafts omit, and it is the move that turns a citation into an argument. Where a claim needs a design the available evidence cannot supply, say so plainly and lower the claim rather than borrowing authority from a study that never tested it.

Which readings are required and which source types are permitted for this activity 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 3 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 4. 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 3, 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 4.

Three Week 3 traps and the fix for each

The first trap is the activity dressed as an outcome. Delivering eight sessions, distributing materials, and holding a community event are outputs: they describe what the program does, not what becomes different for anyone. The fix is to finish the sentence. After the activity happens, who is different, and in what measurable way? If the sentence cannot be finished, the item belongs in the activity list rather than the outcome list.

The second trap is the objective that is measurable only in principle. A target percentage with no named instrument, data source, or collector cannot be evaluated by anyone. The fix is to attach the measurement clause to the objective at the moment it is written, naming what will be collected, from whom, and by which method.

The third trap is the paragraph-terminal citation. When several claims are made and one citation lands at the end, no individual claim is attributable and the reasoning cannot be checked. The fix is to place each citation on its own claim, and to split the paragraph when that proves impossible. Citation format itself follows the style named in 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 3 activities. The registered syllabus, classroom, rubric, announcements, instructor directions, and official policies remain controlling.

Week 3 questions