NRNP 6590 Week 10 planning manual

1. Capture the live Week 10

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: revising the method, not just the artifact

Revision in this course's sense means changing the process that produced the error, and the feedback ledger says where. Pull the highest-frequency gap category from the term's ledger, using the classification the class guide describes, and design one short drill for it on parallel, ungraded material. A recurring reasoning gap means rebuilding a flawed chain end to end. A recurring evidence gap means re-attaching citations at claim granularity until the habit resets. A recurring calculation gap means re-deriving with units and interpretation until the sanity check is automatic. A recurring task-interpretation gap means translating prompts into one-sentence tasks and checking them back against the original wording.

The drill is practice, not product: nothing rebuilt inside it is submitted anywhere. Its output is a repaired habit, which is then applied inside whatever the live Week 10 activity actually is. One deliberate rep against the real weakness, this close to the end, changes the final work more than three generic polish passes, because it aims at the thing the record says keeps going wrong.

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.

Repairing evidence habits before the last work

Read the term's evidence feedback as one pattern rather than as isolated notes. The recurring failures usually reduce to three: stale sources where currency mattered, authority mismatches where a heavy claim rested on a light source, and citation drift where the sentence slid away from what the source actually established. Identify which pattern the record shows, then correct it inside the current draft: re-verify the currency of anything carried forward, upgrade the authority under the claims that carry weight, and re-read each paraphrase against its source for population and strength.

Finish with a deletion pass over the reference list. Any entry that performs no analytic work in the current artifact comes out, however long it has traveled with the course. The reference lists of the final stretch should read as a defensible evidence portfolio: current where currency matters, weighted where weight matters, and with every entry attached to a claim that needed it.

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 10 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 as a revision map

Where the live classroom actually offers a revision or resubmission mechanism, the returned rubric is the revision map: address every criterion comment explicitly, row by row, and verify the reworked artifact against the current rubric version before resubmitting, since versions can differ even within a term. Keep a short note of what changed per row, so the revision can be defended as responsive rather than cosmetic if the question ever comes up.

Never assume a revision opportunity the classroom does not state. Whether one exists is a fact of the registered section, not a general policy, and hours spent on an assumed mechanism are hours taken from work that will definitely count. Where no mechanism exists, the same row-by-row reading still pays, applied forward: the flagged rows from returned work become explicit checkpoints inside the remaining activities, which is revision in the only form the calendar still allows.

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 11. 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 10, 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 11.

Week 10 pitfalls and the fix for each

Pitfall: cosmetic revision, correcting typos and spacing while the flagged reasoning gap stands untouched. The artifact improves; the cause of the loss does not. Fix: revise the flagged criterion first, in substance, and let mechanics wait for the final pass.

Pitfall: overcorrecting into a new error, most commonly stuffing citations everywhere after evidence-related feedback. Indiscriminate support reads as padding under the course's own rules. Fix: add evidence only where a specific claim lacks it, and make every added source survive the deletion test.

Pitfall: rebuilding everything in the last weeks out of anxiety, which spends scarce hours flattening strengths and weaknesses alike. Fix: rank the repairs by criterion weight and recurrence, fix the ones the record shows keep recurring, and leave the working habits alone.

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 10 activities. The registered syllabus, classroom, rubric, announcements, instructor directions, and official policies remain controlling.

Week 10 questions