HLTH 6207 Week 1 planning manual

1. Capture the live Week 1

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: reading a funding call the way a reviewer reads it

Grant writing has a second controlling document standing behind the syllabus: the funder's own published guidance. If the live Week 1 activity places a funding announcement, request for proposals, or program guideline in front of the student, read it the way a review panel does, in two columns rather than in one pass. The left column collects what the funder requires: who may apply, which activities are allowable, the funding ceiling and the period of performance, the required attachments, the page and formatting limits, and the submission route. The right column collects what the funder rewards: the review criteria, their weights, and the exact language those criteria use.

The reasoning worth making visible is that the two columns do different jobs. The required column decides whether an application is read at all, because a missed eligibility condition or a missing attachment is normally a screening failure rather than a scoring deduction. The rewarded column decides how well it scores once it is read. A proposal can satisfy every requirement and still finish low, simply because nothing in it was written toward a weighted criterion. Orientation is the cheapest possible moment to notice that gap, since no prose has yet been drafted against the wrong target.

Practice the extraction on a publicly posted announcement before applying it to any graded artifact, then check the extraction against the classroom prompt. Which of these elements the graded work must actually contain is decided by the rubric attached to the live activity in the registered classroom, not by the guidance document and not by this page.

Reading the rubric row by row in Week 1

Open the rubric before planning anything, and read it one row at a time from left to right instead of skimming the top performance column. For each row, rewrite the criterion as a question the finished work must answer, mark the controlling verb, and note where in the planned artifact that answer will appear. Rows built on verbs such as identify or describe are asking for coverage. Rows built on analyze, justify, evaluate, or apply are asking for a visible chain of reasoning, and coverage alone will not satisfy them.

Two uses of the rubric belong specifically to orientation. First, the rows disclose the vocabulary the course expects: when a row names a construct, that construct should appear in the student's own working notes from the first week onward rather than being translated into looser language. Second, the distance between the strongest and weakest performance descriptions inside a single row shows precisely what this course counts as depth in that criterion. Read that distance and write it down while the term is still open.

Row names, point values, weights, and thresholds come only from the rubric attached to the live activity in the registered classroom. Save that rubric version beside the working file so that a later revision is checked against the same document rather than a remembered one.

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.

What counts as source material in a grant writing course, and how to shelve it in Week 1

Scholarly support in this subject is wider than a single journal database and much narrower than a general web search. Four families do most of the work: peer-reviewed program evaluation and health promotion literature; public surveillance data and vital statistics published by health agencies; official agency guidance, program announcements, and technical assistance material; and organizational records such as service counts, capacity descriptions, and prior reports. Popular commentary, vendor marketing, and undated web pages carry no evidentiary weight even when they address the right topic.

Week 1 builds the shelf rather than the argument. For every item recorded, capture the publisher, the publication or data year, the geography, the population definition, and how the measure itself is defined, because one rate is comparable only to another rate that counts the same people in the same way. Then write the one-line use note the course method already requires: the single claim this source will later be asked to support.

Working a source into a draft is far easier when the shelf was built this way, because the use note becomes the sentence that introduces the source. Which readings are mandatory, which source types are permitted, and which citation style governs are all set by the registered classroom rather than by general practice in the field.

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 1 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 2. 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 1, 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 2.

Three Week 1 traps and the fix for each

The first trap is working from a summary. Announcement landing pages, synopsis blocks, and third-party roundups compress guidance and drop the conditions that decide eligibility. The fix is to obtain the complete guidance document, record its version and date, and check whether amendments, addenda, or published question and answer sets have changed it since. A proposal argued from a summary is argued from somebody else's abstraction.

The second trap is drafting need before confirming fit. Writing a persuasive problem statement is the most enjoyable part of the work and the easiest to begin, so it often starts before anyone has confirmed that the applicant type is eligible, that the proposed activities are allowable, and that the requested amount sits inside the stated range. The fix is a short eligibility and allowability pass that finishes before the first narrative sentence is written.

The third trap is a calendar built only from posted due dates. Grant work depends on other people and on file conversions, and those dependencies carry their own lead times. The fix is to give every dependency its own row in the Week 1 ledger with an internal date earlier than the item it feeds. What is actually due in this Week, and at what hour, is governed by the live classroom calendar and the instructor's announcements.

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

Week 1 questions