NRNP 6590 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 Role Transition for Advanced Practice, 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.

Worked reasoning for a repeatable cadence

Week 2 turns the reasoning chain from an idea into a drill with fixed slots. Build one reusable paragraph skeleton for judgment writing and practice it until it is boring: an opening claim that commits, a because-clause that cites the mechanism or standard, an alternatives clause that names what else was considered and why it ranks lower, and an authority clause that says what stays inside the writer's scope and what would be escalated. The skeleton is reusable for the whole term; the sentences inside it never are.

Watch the distance between the weakest and strongest versions of the same thought. A sentence such as "thorough assessment is important" commits to nothing: no cue, no standard, no consequence. The upgraded sentence binds a specific cue from the authorized context to a named standard, states the judgment, and adds the condition that would change it. Practicing that upgrade on two or three sentences early in the week costs minutes; discovering the weakness in returned feedback costs a graded activity. Pace the assigned readings into the same cadence, with notes taken in the shape of the skeleton and cues kept separate from standards, so drafting starts from structured material instead of highlights.

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 bench for the whole term

The searches that served the opening week will repeat, so stop treating them as disposable. Save the exact search strings that worked, note which databases they ran in, and start a bench: the guideline families, journals, and reference works that answered this course's kind of question. For each bench entry, record currency, authority tier, and the sort of claim it can support, so the next activity starts from a shortlist instead of a blank search box.

Working sources into a draft now follows a once-then-specific rule: introduce a source one time with its full analytic weight, then cite it afterward only for the particular claims it supports. Avoid the serial-summary pattern of one paragraph per source, which reads as a book report; organize paragraphs around claims and let sources appear where each claim needs them. The scholarly standard has not moved since orientation. Current guidelines and peer-reviewed evidence lead, assigned readings stay mandatory where the live activity requires them, and anything below that tier needs explicit permission from the current instructions before it earns a citation.

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.

Reading the rubric row by row against first results

Once the first graded work returns, the rubric stops being theoretical. Lay the returned result beside the rubric and read row by row: where the score landed, what the instructor's comment attached to, and which quality words in the row the comment echoes. This is the first real evidence of how this section's grader reads the rows, and no third-party example can substitute for it.

Annotate a private copy of the rubric with what each row rewarded or flagged, then convert the two or three rows that cost the most into standing checklist items inside the weekly cadence. Keep the annotation dated and tied to the rubric version it came from; a later activity may carry different rows, and the registered version in the live classroom always decides. The habit worth building this early is small and specific: nothing gets submitted until the previously flagged rows have been re-checked on purpose.

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: building the cadence around drafting alone, so discussion replies get squeezed into the final minutes of the window. Replies carry their own deadlines and their own credit. Fix: give replies first-class slots in the weekly schedule, with enough time to read peers' work well enough to compare, apply, or qualify rather than agree.

Pitfall: reading the instructions once when the week opens and never again. Announcements can adjust an activity midweek, and a routine built on the stale version delivers the wrong artifact on time. Fix: add a short midweek re-check of announcements and the activity page to the cadence, before drafting closes.

Pitfall: letting a strong first paragraph quietly become a template, pasted forward and lightly edited each week. That habit produces recycled language and stale reasoning, and both get noticed. Fix: reuse the skeleton and retire the sentences; every week's cues, evidence, and judgments must be built fresh from the live material.

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