NURS 5050 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 Policy and Advocacy for Improving Population Health, 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: building a determinant chain you can repeat

Week 2 is where the course's reasoning should become a repeatable move rather than a one-time effort. The move is the determinant chain: start from the measurable outcome and walk backward. The outcome sits at the end; behind it sit behaviors and exposures; behind those sit living and working conditions; behind those sit the policies and budgets that shape the conditions. Practice on parallel material: take any population from the assigned readings and write the chain in four sentences, one link each, and give every link an actor who could plausibly move it. A chain link without an actor is an observation; a link with an actor is the beginning of advocacy.

The test of Week 2 is not brilliance but reproducibility. The student should be able to produce a defensible chain for a new population in a single sitting, because the cadence of a Course-Based quarter will keep asking for the same reasoning under new prompts. Keep the skeleton in the working notes: outcome, proximate factor, condition, policy context, actor per link. When the live discussion or written activity arrives, the skeleton fills with the week's actual materials instead of being reinvented under deadline pressure, and the saved time goes to evidence and replies, where the graded cadence usually concentrates.

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.

Turning the starter bench into a source log the quarter can trust

Week 1 produced a pile; Week 2 should produce a system. Give the source log fixed columns and fill them at capture time: citation, publication date, authority type, population and geographic level, usable finding, known limitation, and the claim it will support. The authority-type column earns its keep immediately, because policy and advocacy writing constantly mixes claim types: a prevalence claim wants surveillance data, an effectiveness claim wants peer-reviewed research, a what-the-rule-says claim wants the rule itself, and a professional-position claim wants the organization's own statement. Mismatches between claim and authority are among the easiest weaknesses for a grader to spot.

Working sources into the draft is a verb problem as much as a citation problem. Surveillance reports and estimates; studies find and demonstrate; statutes require and prohibit; organizations recommend and endorse. Choosing the verb that matches the authority keeps the writing honest and shows the reader that the student knows what kind of evidence is in hand. Before any source enters a paragraph, its date and level columns should already be filled; if they are blank, that is the log announcing the source was never actually vetted.

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.

Reading the rubric row by row

By Week 2 there may be a scored rubric from the first activity, and it is the most valuable document the course has produced so far. Set it beside the current week's rubric and read them as a pair. Rows that repeat verbatim across weeks describe the course's fixed expectations: participation, mechanics, citation practice, professional tone. Fold those into the weekly routine so they stop consuming fresh attention. Rows that changed carry the week's new demands, and any row where points were lost last time gets drafted first this time, deliberately, while energy is highest. Confirm the reply requirements in the live instructions as their own row-level obligation, because response windows are graded structure in this format, not courtesy. If a comment on the scored rubric reads ambiguously, write one sentence stating the interpretation and test it against this week's row wording before building on it. The current rubric remains the only authority on what any row means this week.

Three Week 2 pitfalls and the fix for each

Coasting on the Week 1 approach. The second week usually deepens the task while looking similar on the surface, and a student who assumes continuity answers last week's prompt with this week's materials. The fix is to re-run the capture pass from zero: open every activity fresh, record its verbs and parts again, and assume nothing carried over except the calendar.

Letting replies slip while polishing the initial post. The initial post has the visible deadline, so the response window quietly starves. The fix is to schedule replies as separate deliverables with their own calendar entries and their own short drafting time, and to hold back one strong idea from the initial post that can anchor a substantive reply.

Recency drift in the evidence. Under cadence pressure, the easiest source to cite is the one already open, whatever its date or level. The fix is mechanical: the log's date and geography columns are filled before a source may appear in a draft, and any statistic older than the newest available release at the same level needs a stated reason to stay.

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