NRNP 6590 Week 1 planning manual

1. Capture the live Week 1

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 at orientation depth

Week 1 is the right time to practice the course's reasoning chain on low-stakes material, because the chain is easier to learn as a reading tool than under a deadline. Take any short piece of de-identified authorized context the live classroom supplies and label each sentence of a practice paragraph by its job. A cue sentence reports what is actually given and adds nothing to it. A mechanism or standard sentence explains why the cue matters and carries the citation. A judgment sentence commits: it ranks, chooses, or rules something out, and it names the evidence doing that work. An action sentence describes a verifiable step. A monitoring sentence states what would confirm or overturn the judgment. An escalation sentence names the point where the matter leaves the writer's authority and moves to consultation or referral.

Written this way, the chain exposes gaps that a plain reread hides. A paragraph with three cue sentences and one unsupported judgment is an inventory, not reasoning. A paragraph that jumps from cue to action has skipped the standard that justifies the action. In a role transition course, the escalation sentence deserves particular respect: showing exactly where authority ends is part of what the writing is expected to demonstrate, not an admission of weakness.

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.

What counts as scholarly for this subject

Build the source infrastructure before any activity demands it. For advanced practice work, the strong tiers are current clinical practice guidelines from recognized professional bodies, peer-reviewed journal articles, and systematic reviews; course texts and assigned readings orient the field and remain mandatory wherever the live activity requires them. Consumer health pages, patient handouts, and general reference sites do not carry scholarly weight unless the current instructions explicitly allow them. Week 1 is for verifying access rather than collecting papers: confirm the library databases open, the citation style resources are at hand, and a working bibliography file exists with columns for date, authority, population or setting, usable finding, and limitation.

Working a source into a draft starts with the one-line use note described in section 4: write what the source will do before writing prose around it. In an orientation week, most sources will define standards and role expectations rather than settle decisions; let them do exactly that and no more. A source that cannot be attached to a specific claim in the plan does not belong in the working list yet, however impressive it looks.

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 1 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 before anything is graded

Read every rubric visible in the Week 1 classroom as a set of questions the grader will answer, one row at a time. For each row, record the verb, the object, any count words such as how many sources or elements, the quality words, and the differences between adjacent performance levels. Those differences are the actual instruction: whatever separates the top cell from the next one down is what the row is really asking for. Rows about mechanics, citation format, and length are the cheapest rows to secure and the most careless to lose.

Where a row's wording is ambiguous, ask the instructor now, while the question costs nothing and the answer benefits the entire term. Keep a dated copy of each rubric beside the working file, because sections and terms vary and the registered rubric in the live classroom is the only version that decides anything.

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 2. 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 1, 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 2.

Week 1 pitfalls and the fix for each

Pitfall: reading the syllabus like a novel, once, start to finish, and calling orientation done. The material feels familiar while none of it is captured. Fix: convert every obligation into a ledger row with a date, an owner, and a verification step, exactly as section 1 describes, and treat that ledger as the real deliverable of orientation week.

Pitfall: importing assumptions from a previous course, including formats, source rules, and rubric expectations that felt universal there. Fix: zero-base the expectations; verify each one against the live Week 1 documents before relying on it, and mark anything unverified as unknown rather than assumed.

Pitfall: researching before the task sentence exists, which produces a folder of sources aimed at no particular question. Fix: write the one-sentence translation of the live activity described in section 2 first, then search to that sentence; every source gathered afterward will arrive with a job.

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

Week 1 questions