NURS 5051 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 Transforming Nursing and Healthcare Through Technology, 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.

Worked reasoning for Week 2: one full pass through the loop

Suppose the live Week 2 activity asks the student to examine how a technology changes a nursing workflow; only the registered classroom decides whether it does, but the shape fits this subject well enough to rehearse. Run the course loop once, in order. Cue: what a nurse notices at the point of care, and what the system surfaces or hides at that moment. Mechanism: what the technology does with information, and where it can delay, distort, or duplicate it. Judgment: what the nurse decides with that information, stated in priority order. Action and monitoring: what is done, and what is watched to confirm it worked. Escalation: who owns the fix when the tool misleads, which is an authority question rather than a technical one.

Draft the answers in that order first, then reorganize to match the structure the prompt requests. The same loop covers a reading response: find the cue the author begins from, the mechanism claimed, the evidence offered, and the boundary of nursing authority in the author's account. Running the identical loop every week, whatever the task type, is what turns cadence from a calendar concept into a thinking habit.

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.

Reading the Week 2 rubric row by row

The second rubric reading is comparative. If Week 1 results have posted, put that returned feedback beside the Week 2 rubric and map every instructor comment to the row it belongs to; rows that carried deductions become the rows drafted first this week. Then read each Week 2 row across its levels and mark any verb that moved since last week. A row that said describe and now says analyze or evaluate is asking for new depth, and answering it with longer description is the most common early-term miss.

Confirm points and weights from the live rubric instead of assuming they repeat, and look specifically for rows that grade replies separately from the initial post, because reply rows run on their own calendar. Finish by revising the Week 1 checklist into a Week 2 version and dating it. An undated checklist quietly audits the wrong week, and the ledger only earns trust when every entry names the version it checked.

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.

Source work in Week 2: build a bank, not a pile

Promote whatever Week 1 used into a reusable bank: every source gets its use note completed, its date confirmed, and its claim named. Then extend the bank deliberately for the live Week 2 activity instead of searching from zero. Search by concept, such as safety, workflow, documentation, or communication technology, rather than by pasting prompt sentences into a search box, and pair each new candidate with something already banked: does it confirm, extend, or contradict? A contradiction is not a problem to hide; it is analytical material, so log it.

In the draft, let each paragraph carry only the sources doing work in that paragraph, and move context citations to wherever their claim actually appears. Recheck whether the activity requires current evidence before locking the list. The bank also upgrades replies: bringing one banked source a peer has not used, applied directly to the peer's point, advances the thread further than agreement ever does.

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.

Week 2 pitfalls and the fix for each

Pitfall one: cloning the Week 1 structure because it was accepted, while the verbs underneath have escalated. The fix is to re-derive the one-sentence reasoning question from the live Week 2 instructions; if the sentence differs from last week's, the structure must differ too.

Pitfall two: back-loading discussion replies into the deadline hour, which produces agreement notes that reply rows score poorly. The fix is to calendar replies as deliverables of their own, with working time attached, using the reply windows already captured in the control table.

Pitfall three: source dumping, meaning a long reference list in which no source performs analytical work. The fix is a one-pass test before submission: for each citation, say aloud which claim it supports; any citation without an answer is deleted or given a job. These three corrections, made now, are what the midpoint audit in Week 5 would otherwise have to force under worse time pressure.

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