PRAC 6587 Week 11 planning manual

1. Capture the live Week 11

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.

Writing the closing work and the carry-forward record together

The final Week produces two documents. The first is whatever the registered classroom requires, drafted with the same discipline as every earlier Week and finished early enough that verification is unhurried. The second is written for the student alone: a short record of what this course taught about method.

Include the criteria that repeatedly cost points and what actually fixed them, the sentence patterns that satisfied the reasoning rows, the sources that proved load bearing and why, the parts of the schedule that held and the parts that never did, and the steps whose lead time was underestimated. Keep methods and lessons, never previously submitted language, because a later course requires new reasoning, new evidence, and fresh authorship of its own. Written at the end of the quarter this takes under an hour; reconstructed at the start of the next course it is mostly gone.

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 11

The last rubric read is an audit rather than a plan. Take the final rubric and work row by row against the finished document, marking for each row the exact page, section, or paragraph where a reader will find what that row asks for. A row with no location is not finished, however complete the document feels while reading it.

Then read the level descriptions once more for the heaviest rows and check the draft against the wording rather than against the impression the draft makes. Finish on the mechanical rows, which are the cheapest points in the course and the ones most often lost at the end: length, format, headings, citation style, file type, and any submission rule the classroom states. This audit is only as good as the version it runs against, so run it against the rubric currently posted in the registered classroom.

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.

Closing the source file properly

Two things should happen to the working file at the end of a course. First, every entry appearing in a final reference list gets one last accuracy check against the recorded fields: the author or authority, the date, the design, the setting, the usable finding, and the claim it supports in this document. Errors here are cheap to fix now and expensive to explain later.

Second, the file is preserved rather than deleted, because a graduate specialization returns to the same territory repeatedly, and a well-annotated set of entries with findings and limitations already written down is the single most valuable thing carried out of a course. Mark which entries were load bearing and note the kind of claim each one supported. What the file must never become is a store of sentences to reuse; it is a record of sources and findings, and the writing is authored fresh every time.

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.

What leaves with the student, and what this page never touched

At closure the division stands exactly where it stood in the first Week. Everything concerning the student's own placement, the activity performed, its documentation, the hours, the encounters, the site, the preceptor, the evaluations, the signatures, and every confirmation attached to them, belongs to the student and to the program's process, and the student is the one who verifies that each piece is complete, accurate, and lodged where it needs to be.

This manual never drafted, reconstructed, estimated, or illustrated any part of that record, and nothing written across these eleven pages indicates that any hour, encounter, competency, or requirement has been met. Only the program, the faculty, and the official process determine that. What these pages have covered throughout is the written layer around it: planning a deliverable, organizing notes the student took, reading the rubric, and preparing for a conversation.

7. Run the Week 11 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 11 pitfalls and the fix for each

The first pitfall is closing on an assumption. The final upload is made, nothing is confirmed, and a failed submission is discovered after the window has shut. The fix is to reopen the submitted artifact from inside the classroom, confirm the timestamp and the file, and save the receipt before leaving the session.

The second is discarding the feedback ledger along with the course files. The most useful product of the quarter disappears in a tidy-up. The fix is to move the ledger and the annotated source file somewhere permanent before archiving anything else.

The third is letting the end of term erode the boundaries that held all quarter. Deadline pressure is exactly when confidentiality rules and record ownership matter most. The fix is to run the same protected-material check on the last document as on the first, and to route anything uncertain to the instructor or the program rather than deciding alone.

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

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

Week 11 questions