PRAC 6587 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 Acute Care Immersion II, 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.

Building the closing map

Assembly begins with one document listing everything still owed, whether or not it feels imminent. Give each item a row: what it is, what it depends on, who else is involved, how long the writing will take based on how long comparable work actually took this quarter, and the last date it could start and still finish.

Sort by last possible start date rather than by due date, because the two orders diverge whenever an item has a long dependency in front of it, and that divergence is where students lose Weeks. Mark every row that cannot begin until somebody else acts and send those requests immediately. Then look for collisions: two heavy items landing within the same few days is a scheduling fact rather than bad luck, and it is still fixable while there is room ahead of it. Only the registered calendar supplies the real dates and the real windows.

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.

Reading the rubric row by row in Week 9

Read the rubrics for everything that remains in one sitting, side by side, before planning any of it. Reading them together shows which criteria repeat across the closing work, and a criterion appearing in several places is worth preparing once and deliberately rather than improvising it separately each time.

It also shows the total weight still available, which tells the student where effort belongs: a heavy row inside a heavy item outranks another careful pass over something almost finished. Mark any row whose evidence or preparation carries a lead time, because those rows have to start now regardless of when their item is due, and mark the rows that depend on something outside the writing so they stay in the dependency lane. Every one of these readings stays provisional until it is checked against the live rubric versions in the classroom, which decide.

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.

Choosing the evidence that will carry the closing work

Closing work rarely rewards a fresh search. Go into the working file, select the small set of load bearing sources the remaining deliverables will rest on, and verify each properly: the finding as recorded, the date, the design or authority, the setting, and the limitation. Verification matters more here than at any earlier point, because a single misremembered finding will propagate through several closing sections at once.

Then identify deliberately the one or two claims for which nothing in the file reaches. Those are the only searches worth scheduling, and they belong in a bounded block before drafting rather than inside it. Assigned readings still come first where the live activities require them. Anything that has been decorative all quarter should be dropped now rather than carried into a final reference list where it will draw comment.

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.

Closing artifacts that reference placement are built only from the student's own record

Where any remaining deliverable draws on the student's placement, the assembly step is gathering, not composing. The student collects what they themselves recorded, confirms it against the program's system, and requests whatever confirmations, approvals, or documentation the process requires from the people authorized to provide them. That request usually has the longest lead time of anything in this Week and should be the first thing sent.

This page contributes nothing to the content of that record. It does not supply or model hours, counts, encounters, logs, site or preceptor detail, evaluation text, supervisor comments, or signatures, and nothing written here means that any requirement has been satisfied. What this page can help with is the writing that surrounds the record: the structure of a reflective or analytical document, the order of its sections, and the preparation for a conversation about work the student performed.

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.

Three Week 9 pitfalls and the fix for each

The first pitfall is sequencing by due date. The largest item is left until last because its deadline is last, and it then inherits every delay ahead of it. The fix is to sequence by last possible start date and to begin the largest item now.

The second is an assembly built on unfinished parts. Sections drafted in earlier Weeks are pulled in without being reread against the rows they will now be scored under. The fix is to check each imported section against its new rubric, since the criteria may differ from the ones it was originally written for.

The third is dependencies discovered rather than mapped. A required approval or confirmation surfaces late and the writing waits on it. The fix is to give every non-writing step its own lane in the closing map, with a named owner and a date the request goes out.

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