PRAC 6549 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 Advanced Primary Care of Adolescents and Children 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.

Build the close-out inventory and find the writing critical path

Week 9 is a logistics Week disguised as a content Week. List every remaining item across the final Weeks and, for each, record four fields: what must be produced, what it depends on, how long it needs after that dependency clears, and who owns the dependency. Then order the list by the date work must start rather than the date it is due, and the critical path becomes visible. In a practicum course the path usually runs through items with an external dependency, since anything waiting on a step the student does not control carries the least slack. Mark those first and begin the parts that can proceed without them, because a draft can be built around a placeholder for a dependency but cannot be built in the hours after it clears. Confirm each dependency's real status through the official channel rather than assuming; an assumed approval is the most expensive item on any close-out list.

Reading the rubric row by row

The rubric for the final work should be read now, in Week 9, and read differently from a weekly rubric. Sort the rows by lead time rather than by order of appearance. Some rows can be satisfied in a final editing pass, such as format, citation style, and length. Others need weeks, because they depend on evidence that must be located, a structure that must be designed, or material that must be gathered through a process the student does not control. Those long-lead rows determine what starts this Week. Write the section plan directly from the rows so no criterion gets discovered late, and note beside each row what proof will show it was met. Read the rubric version currently posted in your registered classroom, since a copy saved earlier in the term may have been revised, and the live classroom rubric is what decides.

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.

Freeze the source set and plan the citation check

There is a point in every course where collecting sources becomes a way of avoiding writing, and Week 9 is usually past it. Declare the source set closed except for gaps the plan actually names, and spend the search time instead on verifying what is already in hand. Build the citation check now rather than in the final hours: a list of every claim that carries a source, the source's current version and date, the population it covers, and the exact statement it supports. Reserve a slot in the schedule to work that list, because it is mechanical and reliably takes longer than expected. Where a gap is genuinely open, define the search narrowly and give it a deadline, after which the draft is written with the best available evidence and its limitation stated plainly. A late source that reshapes the argument is a Week 9 problem and a Week 11 disaster.

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.

The placement close-out is a separate track with its own owner

Assembling the close is where the two tracks of a practicum course must stay clearly apart. The written track is planned here: deliverables, dependencies, sources, and sequencing. The placement track has its own requirements, its own system, and its own timing, and it belongs to the student and the university. Whatever must be completed, documented, signed, or submitted on that side is completed, documented, and verified by the student through the process Walden specifies. This page does not tally it, estimate it, model it, or state that any part of it is finished, and it offers no template for a log, a preceptor evaluation, or an attestation. If anything on that track looks uncertain with the term closing, the correct action is to raise it immediately through the official channel. A well-assembled written close cannot substitute for an incomplete institutional step, and it should never be allowed to hide one.

7. Run the Week 9 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 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.

Three Week 9 pitfalls and the fix for each

The first pitfall is the rubric row discovered late. A criterion that needed lead time is read for the first time near the deadline, and the only remaining response is a thin paragraph. The fix is the lead-time sort done this Week, with every long-lead row started now. The second pitfall is the contradicting source found last, which forces a choice between ignoring it and rebuilding the argument under time pressure. The fix is to close the source set early and run the verification list while there is still room to revise. The third pitfall is the assumed dependency, a step believed to be handled because nobody said otherwise. The fix is to confirm every dependency's status explicitly through its own official channel and to record the confirmation with its date, so the close-out list reflects what is true rather than what is hoped.

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