NRNP 6547 Week 9 planning manual

1. Capture the live Week 9

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 an assembly Week

Assembly is project reasoning applied to the course's endgame. Build the closing map in one sitting: every remaining activity visible in the registered classroom, its rubric weight, its dependencies, its earliest possible start, and its immovable dates. Then reason backward from the last deadline the way the course reasons forward from evidence: which item sits on the critical path, which items can run in parallel, and where a single delayed dependency, a reply window, an approval, a group contribution, a technical submission step, would cascade into the items behind it. The map is one page; the Weeks it protects are the most expensive of the quarter.

Begin the closing argument early at the thinking layer, even while earlier deliverables are still moving. Whatever form the final work takes this term, its spine can be drafted now from the concept inventory: the central concepts the course has built, the strongest evidence attached to each, and the connections between them that survived the integration Weeks. A spine drafted in Week 9 turns the final Weeks into execution instead of invention, and it presumes nothing the live instructions have not shown.

Hold capacity honestly. If the map shows more work than the calendar holds, the response is scope planning now rather than optimism: identify the highest-weight items, protect them first, and raise any genuine conflict through the official channels while options still exist.

Reading the rubric row by row

The most valuable rubric read of the quarter is reading the final work's live rubric the moment it becomes visible, well before drafting begins. Read it row by row twice: once to outline the deliverable, and once against the accumulated feedback ledger. Every row whose language matches a family that lost points earlier in the course gets flagged, because the final work is where recurring weaknesses compound and where fixing them pays the most.

Long rubrics for large deliverables hide structural requirements inside prose: named sections, minimum source counts, format specifics, and sequence expectations. Convert every such requirement into a checklist item on the closing map the day the rubric is first read. In the last Weeks of a course, discoveries should be small; anything structural discovered at upload time was readable in Week 9.

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.

Consolidating the evidence base

Assembly is when the ledger becomes the reference base for the close. Sweep it once, deliberately: confirm that every source likely to appear in the final work still earns its place with a current, claim-fitting use note; complete any citation data still missing; and check each retained source against whatever currency and type rules the live instructions set. A finished ledger means the final Weeks cite from a verified shelf instead of re-researching under pressure.

Fill the last gaps with intent. The spine drafted from the concept inventory shows exactly where support runs thin; run one focused search per gap, favoring current peer-reviewed work involving older adults and authoritative sources for scale, and stop when the claim is carried. Late-course research discipline is subtraction: fewer, stronger sources doing visible work inside the argument.

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 9 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 9 pitfalls and the fix for each

Pitfall: postponing the final rubric read until drafting feels imminent, then discovering a structural requirement late. The fix is the early double read the moment the rubric is visible, with every structural item converted immediately into a checklist entry on the closing map.

Pitfall: dependency blindness, planning as though writing time were the only constraint while replies, approvals, group steps, and technical submission stand between draft and grade. The fix is listing dependencies as first-class items on the closing map, each with its own owner, date, and verification step.

Pitfall: new-source panic, grabbing whatever loads fastest to plug late gaps. The fix is gap-first searching from the spine, with every candidate held to the same scholarly bar the earlier Weeks used, because the final deliverable is the worst possible home for the weakest citation of the quarter.

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

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

Week 9 questions