NURS 4110 Week 2 planning manual

1. Capture the live Week 2

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 Leadership and Health Policy, 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.

Layering determinants without losing the cadence

Week 2 is where the reasoning deepens one layer while the schedule becomes a routine, and the two goals support each other. On the reasoning side, practice separating three tiers that beginning policy writing tends to blur: individual behavior, social and economic determinants, and system constraints. Work the separation on parallel material such as medication access for adults managing diabetes across a two-county area. A behavioral claim, missed refills, sits at the individual tier. The determinant tier holds the conditions that shape behavior: pharmacy deserts, work schedules that conflict with clinic hours, and cost exposure from coverage gaps. The system tier holds the structures that produce those conditions: formulary rules, transportation infrastructure, and clinic staffing models. Each tier needs evidence at its own level, and a draft earns credibility when it never supports a system claim with an anecdote or a behavioral claim with a national rate.

On the schedule side, convert last week's improvisation into fixed slots: a capture pass when the Week opens, a research window, a drafting block, the quality gate, and the submission step, each on its own day where the live deadlines allow. A stable cadence is what later, heavier weeks will borrow against. The registered classroom still decides what Week 2 actually contains; the cadence simply ensures the student meets it prepared.

Reading the rubric row by row

This week the rubric read gains a comparison point: the first returned scoresheet. Set the current activity's rubric beside whatever feedback Week 1 produced and work row by row through both. Identify the rows that repeat across activities, evidence quality, organization, mechanics, professional style, because recurring rows are the course's standing expectations and deserve permanent checklist entries. Map each instructor comment to the row it belongs to so the lesson attaches to a criterion instead of floating as general advice. Then allocate drafting time by row weight rather than by personal preference; a student who loves polishing prose but leaves the heaviest analytical row thin is spending effort where the points are not. Where this week's rubric differs from last week's, mark the difference explicitly in the matrix so the plan tracks the live document rather than memory of the old one.

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.

Source work on a weekly rhythm

Give source work its own recurring window early in each Week, before drafting begins and after the capture pass identifies what the activity requires. Start from the assigned readings, which remain mandatory where the current instructions require them, and extend outward only as far as the prompt needs. Log every candidate source in the running bibliography with its date, authority, level, and a one-line use note naming the claim it can support; a source without a use note does not enter the draft. Check currency deliberately: surveillance figures should be the most recent release, while a foundational policy document may be older and still authoritative. Resist the urge to re-research settled ground; the Week 1 log already covers the course's opening themes, and the weekly rhythm should add increments, not restarts. By the end of Week 2 the bibliography should show two layers of entries and no source that was read but never assessed for use.

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

Week 2 pitfalls and how to fix them

Three cadence-stage mistakes recur.

First: template drift, reusing Week 1's structure because it earned points, whether or not it fits the new prompt. Every activity gets its own one-sentence task translation before any outline is copied forward. If the sentence and the borrowed structure disagree, the structure loses.

Second: treating replies as an afterthought once the initial post lands. Reply windows are separate deliverables with their own deadlines and their own rubric presence where the live instructions score them. The fix is to calendar replies as independent items the moment the Week's capture pass records their dates, and to hold back reply material, a comparison, an application, a boundary case, so the replies advance reasoning instead of agreeing politely.

Third: collecting sources without deciding their job. A folder of saved articles feels like progress while leaving the draft unsupported. The fix is the use-note rule: each source earns its place by naming the specific claim it supports, and any source that cannot be attached to a claim stays in the log, out of the reference list. These are working habits, not official requirements; the registered classroom's instructions always override a private routine.

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

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

Week 2 questions