PRAC 6537 Week 11 planning manual
A course-specific Week workflow for capture, reasoning, evidence, student authorship, quality control, and gradebook closure.
Complete the live final work, verify submissions and grades, and preserve the methods and feedback that belong in the next course. This page verifies a position in the Course-Based quarter calendar, not a universal assignment identity.
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.
| Control field | What to verify now |
|---|---|
| Identity | Exact course, Week, activity, and current version |
| Task | Every required action, question, audience, and deliverable part |
| Grading | Rubric rows, points, weights, thresholds, and penalties |
| Evidence | Assigned readings, source rules, dates, authority, and citation style |
| Calendar | Initial post, replies, files, approvals, due time, and time zone |
| Dependencies | Group, field, clinical, residency, proctoring, feedback, or approval steps |
2. State the Week's reasoning question
For Adult Acute Care: Comprehensive Patient Management I Practicum, 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.
Closing the written layer cleanly
Closure is a set of verifications, not a feeling. For every remaining activity, the student performs the submission themselves, then reopens the submitted artifact from inside the classroom to confirm that the correct file uploaded, that it opens, that it is the final version rather than a working copy, and that the timestamp falls inside the window. Saving the confirmation is part of the step. A submission that was made and cannot later be evidenced is a weak position to be in if anything is queried.
Then separate what is genuinely finished from what is merely off the student's desk. Written work submitted and receipted is finished. Anything awaiting a result, an approval, a confirmation, or another person's action is open, and open items need a named next contact and a date. The status of every placement requirement sits in the student's own documentation and with the responsible Walden contacts; the student confirms it directly with them, and nothing here can describe, estimate, or attest to it.
Close the written layer by writing the handover to the student's own future self: which methods worked, which checks caught real errors, which parts of the routine collapsed under pressure, and what should change next course. Ten minutes spent on that now is worth more than rereading a graded file later.
Reading the rubric row by row one last time
The final rubric walk answers a narrower question than earlier ones: not how could this be better, but is anything missing. Take each row and confirm there is a visible, locatable piece of the submission that answers it. Visible matters. A requirement satisfied implicitly across several paragraphs is easy for a grader working quickly to miss, and at this stage the cheap fix is a heading or a topic sentence that makes it findable rather than a rewrite.
Check the mechanical rows with particular care, because they are fully within the student's control and are the most annoying points to lose: file type, file naming, length, structure, citation style, and any required declaration or cover element. Confirm each against the live wording rather than against the convention used earlier in the quarter, since a final activity often specifies something different.
Then stop. Late in a final week, further changes are as likely to introduce an error as to remove one, and a draft that satisfies every row does not become better by being touched again. Record which rows felt hardest to satisfy and why, because that record is the most useful thing to carry into the next course. The live classroom rubric for the registered section decides here as it has all quarter.
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.
Turning the source shelf into something reusable
The annotated source log built over the quarter is the most durable asset the course produced, and it is usually discarded. Spend the closing hour making it reusable instead. Keep the entries that are genuinely foundational for adult acute care reasoning: current authoritative practice guidance, the syntheses that framed the major questions, and the professional standards documents that recur. Retire the entries that answered a single narrow prompt.
For each entry kept, make sure the annotation stands alone. It should record the date, the authority or design, the population or setting, the usable finding, the limitation, and what it was used to support, written clearly enough to be understood by someone who has not read it in months. An annotation that only makes sense while the source is open is worth very little later.
Add one closing note to the file: which kinds of sources this subject actually rewarded, and which searches turned out to be dead ends. That note shortens the first week of the next course considerably. Carry the shelf and the method forward; do not carry forward the sentences. Any later prompt requires new reasoning, new evidence, and new authorship, and previously submitted text belongs in the archive.
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 11 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.
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.
Three Week 11 pitfalls and the fix for each
The first pitfall is treating submission as completion. Written work can be fully submitted while an approval, a confirmation, or an administrative step remains open, and a course does not close on the strength of the visible half. The fix is a two-column closing list: submitted and receipted on one side, open with a named contact and a date on the other. Every item on the open side is the student's to pursue and verify directly with the responsible Walden office, and none of it can be assumed complete.
The second pitfall is discarding the feedback ledger once grades appear. The ledger is the only structured record of what actually went wrong and how it was repaired, and it is far more valuable than the returned files themselves. The fix is to write one closing summary naming the two recurring weaknesses, the corrections that worked, and the check that will be run from the first week of the next course.
The third pitfall is planning to reuse this quarter's writing. It feels like an efficiency and it is a risk, both academically and practically, since a document written for one prompt rarely fits another and the seams show. The fix is to keep the method, the outline patterns, the standing checklist, and the source shelf, and to archive the prose. Everything reusable from this course is a way of working, not a paragraph.
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
What is assigned in PRAC 6537 Week 11?
Only the registered Course-Based classroom can answer that. This positional manual deliberately does not invent a discussion, paper, quiz, project, exam, practicum task, or rubric.
How should I start PRAC 6537 Week 11?
Capture every live activity, instruction, rubric row, point value, deadline, reply rule, dependency, and submission route before researching or drafting.
Can a tutor perform the Week for the student?
No. Tutoring supports understanding, method, practice, and feedback; the student performs required activity, authors the response, verifies it, and submits it.