NRNP 6547 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 The Aging Experience, the durable class question is: What does the prompt ask the student to understand, apply, compare, create, or evaluate? 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

Define the required concept precisely, apply it to the stated context, make the reasoning visible, and close with the implication the current rubric requests.

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 cadence Week

The second Week converts first impressions into a loop the student can run every week without re-deciding it. Write the loop out explicitly: capture the live activity, restate its question, pull the relevant concept from the running inventory, draft in proof order, verify against the rubric, submit, and log the feedback. For a course about the aging experience, the loop carries one extra beat: before drafting, ask what the concept looks like specifically in an older adult context rather than in adults generally, because that shift is usually where the points sit.

Practice the concept-to-application beat on whatever material the registered Week supplies. If the live prompt asks for application, resist spending most of the word count on definition. A workable ratio for a short graduate response is one move of definition, two or more moves of application and reasoning, and one move of implication, with the live rubric free to adjust that ratio. Wherever Week 1 feedback flagged a weakness, run this Week's draft through that exact lens before submission so the correction lands while it is still cheap.

Cadence also means calendar honesty. Fix the weekly rhythm now: the reading block, the drafting block, the reply block, and the verification block on named days at named hours. A stable rhythm is what the heavier later Weeks will borrow against, and it is far easier to build in Week 2 than to improvise in Week 9.

Reading the rubric row by row

In Week 2 the rubric read gains a comparison. Set the current live rubric beside the scored Week 1 rubric and read them row by row as a pair. Where the language repeats, the expectation repeats, and the Week 1 comment on that row is this Week's standing instruction. Where the language changes, the change names exactly what this Week adds. Any row that lost points in Week 1 gets drafted first this time, not last.

Read for weight movement too. If more points now sit on reasoning or evidence rows than the first activity carried, the grading is signaling the course's direction of travel. Match effort to weight: the row worth the most points earns the most drafting and verification time, whatever order the prompt happens to list its parts in. The registered rubric in front of the student, never a remembered one, decides.

4. Use evidence deliberately

Use the assigned readings first when required, then add current authoritative or peer-reviewed support matched to the claim.

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 while the routine sets

Week 2 is where a source ledger starts paying. Keep one running file that records, for every source touched so far: the full citation, the date, the type, whether assigned reading, peer-reviewed study, practice guideline, or statistical report, the claims it has supported, and the Weeks it has appeared in. The ledger prevents both gaps and overuse, and it makes visible the moment a convenient source starts being stretched across claims its design cannot carry.

When the live activity asks for support beyond the assigned readings, search deliberately instead of gathering. Name the claim first, then find the source that carries that claim for an older adult population, then read enough of it to paraphrase from understanding. One well-fitted peer-reviewed source doing real analytical work beats three decorative citations, and rubrics written for graduate work are usually built to notice the difference between the two.

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 task completion, reasoning, evidence fit, examples, organization, citations, file rules, and the student's own explanation of the result.

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: cloning the Week 1 submission's structure onto the new prompt because it scored acceptably. The fix is to restate this Week's question in one sentence before opening any old file; if the sentence differs, the structure must differ, and the live rubric rows, not last week's habit, set the outline.

Pitfall: letting discussion replies drift to the closing minutes of the response window, where they shrink into agreement. The fix is to schedule replies as their own calendar item the day after the initial post, and to build each reply around one move: compare evidence, extend the peer's idea into a different aging context, or raise a supported boundary question.

Pitfall: quoting the readings instead of paraphrasing them, which hides whether understanding exists. The fix is mechanical: close the source, write the idea from understanding, reopen the source to verify accuracy, then cite. If the sentence cannot be written with the source closed, the material is not yet learned, and that gap caught in Week 2 is the cheapest it will ever be to close.

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