PRAC 6841 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 Pediatric Primary 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.

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.

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.

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

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.

Finishing the written work and verifying the rest separately

The final stage has two closures that must not be run together. The first is the written one, which this page supports: finish the last graded activity, check it against the live rubric, submit it through the required route, confirm the upload opened correctly, and keep the receipt. The second is institutional, and it is entirely yours. Whether every required placement activity is complete, whether every entry is recorded in the official system, whether evaluations and approvals have been submitted by the people responsible for submitting them, and whether anything remains outstanding are questions to answer inside those systems and with your faculty and placement contacts.

Nothing written in a paper can settle the second closure, and nothing on this page should be treated as evidence about it. Do not summarize your record into coursework, do not estimate anything that is meant to be counted, and do not assume a submitted paper implies a completed requirement. If any part of the institutional lane is unclear now, contacting the responsible office is the correct move, and doing it early in the week is better than late.

Reading the rubric row by row one last time

Run the final rubric pass on the finished document rather than on a near-final one, and run it slowly. For each row, find the sentences that answer it and read them out of context. If a row's supporting sentences do not make sense on their own, a reader working through the document quickly will not find them either. Fix by making the point explicit, not by adding volume.

Finish with the non-prose requirements, since they are where final submissions fail: format, file type, title and reference pages, required headings, reply counts, attachments, and the submission location itself. Confirm each against the live instructions for this activity rather than against how the term has usually worked. Your classroom rubric and instructions decide what complete means, and they are the last thing to check before you submit.

Retiring the source shelf with something worth keeping

Before the term closes, spend a short session converting your source work into something usable later. Keep a list of the professional bodies, agencies, and journals that consistently produced usable material in pediatric primary care, along with a note about what each is good for: definitions, recommendations, evidence strength, or population-specific detail. That list is the durable part. Individual citations age quickly and will need re-verification anyway.

Also record the searching habits that worked, including the filters that saved time and the phrasing that surfaced current guidance rather than commentary. Do not carry forward drafts or submitted text; carry forward the method. A later course will ask a different question, and the value of this term's sourcing is in how quickly you can build a defensible shelf again, not in reusing this one.

Closing pitfalls and their fixes

The first pitfall is treating submission as completion. A submitted file is one obligation discharged, not proof that everything the course required has been met. The fix is a written checklist that keeps the institutional lane visible until each item is confirmed at its own source.

The second is discarding your feedback ledger once results post. The recurring criticisms you collected are the most valuable thing produced this term and they will apply again. The fix is to save the ledger in criterion form and to reread it at the start of your next course.

The third is letting the last week's pressure erode the boundaries that held all term. Fatigue is when identifying detail slips into a reflection and when someone else's record starts to feel like reasonable material. The fix is to run the same de-identification pass on the final draft that you ran on the first, and to keep every part of the record with the person and the system that own it.

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