HLTH 6031 Week 1 planning manual
A course-specific Week workflow for capture, reasoning, evidence, student authorship, quality control, and gradebook closure.
Read the syllabus, calendar, rubrics, announcements, and required resources as one control packet before planning the first visible activity. This page verifies a position in the Course-Based quarter calendar, not a universal assignment identity.
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.
| Control field | What to verify now |
|---|---|
| Identity | Exact course, Week, activity, and current version |
| Task | Every required action, question, audience, and deliverable part |
| Grading | Rubric rows, points, weights, thresholds, and penalties |
| Evidence | Assigned readings, source rules, dates, authority, and citation style |
| Calendar | Initial post, replies, files, approvals, due time, and time zone |
| Dependencies | Group, field, clinical, residency, proctoring, feedback, or approval steps |
2. State the Week's reasoning question
For Leadership and Advocacy in Health Education, the durable class question is: Which population, determinant, stakeholder, and measurable outcome define the problem? 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 population and baseline, trace determinants and system constraints, compare interventions, and connect the recommendation to implementation and evaluation.
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: name the population before naming the problem
In Leadership and Advocacy in Health Education the first analytical move is not choosing a topic but bounding a population. A population is defined by four coordinates that can be written down and defended: who is counted, where they live or receive services, over what period, and through which data source they become visible at all. "Adults with hypertension" is a topic. "Adults aged 45 to 64 enrolled in one county health system during two named years, counted in that system's own reporting" is a population a reader can check. Write those four coordinates as one sentence in the working file during Week 1, before any prose exists, and keep the sentence beside the drafting space so every later claim can be tested against it.
Baseline follows immediately. A baseline is a number with a denominator, a time stamp, and a source, not an adjective. If the only figure available is a raw count, say so and explain why a rate cannot be produced at this level; if the figure is a rate, state the denominator in the same sentence. Orientation work is cheap now and expensive later, because a population defined loosely in the first Week forces every determinant, stakeholder, and outcome statement in the rest of the class to stretch to cover it.
Build the first determinant and stakeholder inventory
With the population fixed, build two short inventories instead of an outline. The determinant inventory lists conditions that plausibly move the outcome, sorted by level: individual knowledge and behavior, interpersonal and household, organizational and program, community and environment, and policy or financing. The stakeholder inventory lists parties by what they control, which is usually budget, access, staff time, data, rules, or trust. Each stakeholder entry should carry one sentence on what that party gains or loses if the outcome changes, because advocacy arguments fail on interests far more often than on facts.
These inventories are working documents rather than deliverables unless the live activity asks for them. Their purpose during orientation is to prevent the most common early error, which is committing to an intervention idea before the problem has coordinates. Keep both inventories in the same file as the population sentence and attach a source to every line as it is added, because retrofitting sources onto a list built from memory takes longer than sourcing while you build.
4. Use evidence deliberately
Use current surveillance, policy, organizational, and peer-reviewed evidence at the same geographic and population level as 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 scholarly here, and how a source enters the draft
This subject accepts four evidence families and they do different jobs. Surveillance and vital statistics from a public health authority establish magnitude and distribution. Policy and regulatory documents establish what is permitted, required, or funded. Organizational reports, program evaluations, and needs assessments establish local feasibility and current practice. Peer-reviewed studies and systematic reviews establish whether an approach changed an outcome and under which conditions. A general encyclopedia entry, a consumer health page, an undated advocacy post, or a slide deck summarizing someone else's data cannot carry an analytical claim even when it happens to be accurate.
A source enters the draft only through a use note written before drafting: the claim it supports, the population and geography it covers, its date, its design or authority, and its limitation in one clause. During orientation, practice matching level to level. National prevalence supports a national statement and becomes background the moment the sentence names a county, a clinic, or a school district. Where the live activity requires assigned readings, read them first and cite them at the point where they actually do work rather than appending them to a list.
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
Test equity, feasibility, stakeholder effects, measurement validity, unintended consequences, and the boundary between association and causation.
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.
Reading the rubric row by row
Open the rubric in the registered classroom and read it as a scoring instrument rather than a topic list. For each row, isolate the controlling verb, the object of that verb, and any qualifier that sets a standard. Identify, describe, analyze, evaluate, justify, and apply are scored differently, and the qualifiers attached to them carry most of the difference. Then write, beside each row, the exact location in the draft where a reader will find that row satisfied. A row that cannot be pointed to marks a hole no amount of editing will close.
Read the performance-level columns across, not only the criterion names down. The distance between adjacent levels usually describes one specific addition: a named limitation, a comparison, a connection back to the population, a cited support. That distance is the instruction. Rubric wording, weighting, and level names vary by section, term, and instructor, so the registered classroom rubric decides in every case; this page explains how to read one, never what one says.
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 orientation pitfalls and their fixes
The first pitfall is treating the syllabus as the rubric. A syllabus states policy and sequence, a rubric states what earns credit, and the two often use different words for the same work. The fix is to keep both open in the same capture session and to store the rubric version beside the working file, so a later revision is checked against the same instrument that will score it.
The second pitfall is a population defined so broadly that no data source can measure it. When the population sentence cannot be attached to a real reporting unit, every later section inherits the vagueness. The fix is to narrow until a data source exists, then state the narrowing as a scope decision with a reason, which reads as judgment rather than as avoidance.
The third pitfall is collecting sources before the question exists. A folder of interesting reading built in the first days usually produces a draft organized by sources instead of by reasoning. The fix is to write the question for this activity first, in one sentence naming the decision or explanation, the required evidence, the audience, and the output, then search only against that sentence.
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
What is assigned in HLTH 6031 Week 1?
Only the registered Course-Based classroom can answer that. This positional manual deliberately does not invent a discussion, paper, quiz, project, exam, practicum task, or rubric.
How should I start HLTH 6031 Week 1?
Capture every live activity, instruction, rubric row, point value, deadline, reply rule, dependency, and submission route before researching or drafting.
Can a tutor perform the Week for the student?
No. Tutoring supports understanding, method, practice, and feedback; the student performs required activity, authors the response, verifies it, and submits it.