NURS 8100 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.

Reading the rubric row by row against the first returned score

By Week 2 a first result may sit in the gradebook, and that changes how a rubric should be read. Put the returned criterion scores beside the current Week's rubric and look for rows that describe the same skill under different names, since a row about analysis in one activity and a row about supporting evidence in another can be scoring the same weakness. For each row that lost points, write in plain words what the grader could not find, then locate the place in this Week's rubric where the same thing is asked for again.

Read the level descriptors rather than the row titles alone, because the distance between adjacent levels is usually one concrete behavior: naming a limitation, quantifying a claim, attributing a position to a stakeholder. Mark the two rows where you intend to change behavior this Week and leave the rest alone, since trying to lift every row at once produces a longer response rather than a better one. The live rubric in your registered classroom decides which rows exist and what each level requires, and posted instructor comments override any general reading offered here.

2. State the Week's reasoning question

For Healthcare Policy and Analysis, 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.

Turning the method into a cadence you can repeat

Cadence in a policy analysis course means the same four moves happen in the same order every Week, so that only the content changes. Fix the order now: population and baseline first, determinants and constraints second, intervention comparison third, implementation and evaluation last. The order matters because each move constrains the next. If the population is still vague when you reach determinants, you will list every social factor in the literature instead of the two or three that plausibly operate on your counted group. If constraints are unwritten when you reach the comparison, the options you weigh will include some that nobody in the system has the authority to choose.

Give each move a stopping rule rather than a time limit. Population is done when a number and a source sit beside it. Determinants are done when each one has a proposed pathway to the outcome. The comparison is done when every option carries a cost note, a feasibility note, and an equity note. Implementation is done when a first measure and a review point exist. A cadence built on stopping rules survives a heavy Week, because you can see exactly where you stopped and resume there instead of rereading everything to find your place.

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 at a sustainable rate

Two sources read properly beat eight skimmed, and Week 2 is where that habit forms or does not. Set a fixed weekly intake, then spend the reading time on the parts that will appear in your writing: the methods paragraph that says who was studied, the table that carries the effect, and the limitations section that says what the finding cannot support. Record each source in the register the same day you read it, while you still remember why it mattered.

When a source enters a draft it should do one of four jobs: establish the baseline, explain a mechanism, quantify an effect, or authorize an action. Write which job it is doing in your notes, and if it is doing none of them, it is background reading rather than a citation. Watch whatever currency rule your activity states, confirm publication dates before building on a finding, and treat an older foundational work as usable only where nothing newer has superseded its claim. Paraphrase from understanding rather than from the sentence in front of you, and reserve quotation for language whose exact wording carries legal or definitional weight.

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.

Three Week 2 pitfalls and the fix for each

The first pitfall is a cadence built around due times rather than around the work. A student who plans to write on the evening a piece is due will keep submitting first drafts. The fix is to schedule the moves instead of the deadline: place population and determinants on days well ahead of whatever your classroom calendar shows, and leave the last available day for checking rather than composing.

The second pitfall is carrying Week 1 language into Week 2 output. Reusing your own earlier sentences feels efficient and reads as unresponsive, because the new prompt is asking a different question. The fix is to reuse the method and the source register while writing the prose fresh, and to test any repeated phrasing against the current prompt before it stays.

The third pitfall is letting a discussion reply become agreement with a citation attached. A reply that endorses a peer and then adds a study has advanced nothing. The fix is to give each reply one specific job: apply the peer's claim to a different population, name a constraint their option would have to meet, compare their evidence with a source at a different level, or ask a question whose answer would change their conclusion.

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