NURS 3022 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 Professional Nurses as Change Agents, the durable class question is: What evidence supports the judgment, what alternatives matter, and what remains outside the student's authority? 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

Move from cue to mechanism or standard, then to prioritized judgment, action, monitoring, and escalation. Use only de-identified authorized context.

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 one finished Week into a repeatable loop

Cadence is the course method run on repeat until it stops costing attention. Convert what Week 1 taught into a fixed weekly sequence with names and days: a capture pass the day the Week opens, the task sentence written the same sitting, evidence selection next, drafting in proof order, the quality gate the day before each deadline, and replies distributed across the response window instead of bunched at its close. Write the loop down; a routine that lives only in memory dissolves under a busy stretch. The reason to stabilize now is the class question itself. Judgment about evidence, alternatives, and authority is the part of change-agent work the rubric rewards and the part that needs unhurried thought, so the loop exists to spend logistics cheaply and reasoning generously. When the live Week carries a discussion, the loop runs twice at small scale: once for the initial contribution and once for the replies, each with its own capture, evidence, and gate. When the live Week carries a file submission, the loop stretches instead: the evidence day grows and the gate adds format and upload checks. Keep one flexible day in the plan. Instructor announcements can adjust instructions mid-Week, and a cadence with no slack turns a small adjustment into a scramble.

Reading the rubric row by row

Week 2 is the first chance to read a rubric against returned results instead of in the abstract. If Week 1 feedback has arrived, place every instructor comment under the rubric row it belongs to, then read the new Week's rubric with those placements in mind. Ask three questions of each row: did a similar row appear last Week, what level did the work earn there, and what exactly separates that level's wording from the one above it. Rows recur as families across Weeks even when point values shift, so a weakness visible in one Week's row is a forecast for the next. Mark the single row where the most points were lost and give its counterpart in the current rubric the first drafting session, while attention is highest. Where no feedback has been returned yet, note that fact in the ledger and grade the Week 1 artifact privately against its rubric; the calibration is imperfect but far better than none. Only the live rubric controls, so open the current one even when it looks unchanged from last Week.

4. Use evidence deliberately

Prefer current authoritative clinical guidance and peer-reviewed evidence appropriate to the question; distinguish guideline recommendations from patient-specific facts.

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.

Building a source bank that survives the term

Start a running source bank this Week: one entry per source with the full citation, the date it was checked, the authority type, the population or setting it covers, and the one-line use note. For change-agent subject matter, keep the authority types visibly separate, because current clinical practice guidelines and professional standards function differently in an argument than peer-reviewed studies, and official health data functions differently than either. A bank organized this way lets a future Week's claim find its support in minutes. Reuse across Weeks is legitimate only at the source level, never at the sentence level. A guideline read in Week 1 may support a Week 5 claim, but it must be re-read for the new claim, re-framed in new language, and re-cited under the new activity's rules. Recheck dates on anything that updates on its own cycle, and retire an entry the moment newer guidance supersedes it. The registered instructions still decide what any given activity accepts, so the bank supplements the live rules and never replaces them.

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

Check safety, scope, differential logic, contraindications, documentation, confidentiality, and every student-performed clinical requirement.

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

Week 2 pitfalls and the fix for each

Pitfall one: spending the whole effort on the initial post and starving the replies. Reply windows close on their own schedule, and thin replies surrender points that the strongest initial post cannot recover. The fix is to treat each required reply as a separate deliverable in the ledger with its own evidence and its own deadline, drafted while the exchange is still alive enough to engage with.

Pitfall two: building the Week around the wrong clock. A plan aligned to a personal time zone or an assumed midnight can sit hours away from the classroom's stated time. The fix is to verify the due time and time zone inside the classroom for every activity separately and to write both into the calendar entry, not just the date.

Pitfall three: letting early confidence loosen the capture step. The second Week tempts the student to assume the pattern simply repeats, but instructions, rubric versions, and announcements can change between Weeks in the same course. The fix is to run the full capture pass every Week as if it were the first, and to compare the new rubric against the saved copy so any change is noticed on the day it appears rather than in the returned grade.

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