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

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.

Mapping the closing work before you write it

This stage rewards planning more than prose. Take whatever remains in the term and write it out as parts rather than as activities: for each remaining deliverable, the sections it needs, the reasoning each section must contain, the sources already in hand, the sources still missing, and the single element most likely to take longer than expected. That last column is the useful one, because closing weeks fail on the element nobody scheduled rather than on the writing nobody could do.

Then separate the map into two lanes and keep them separate. The writing lane is yours to schedule and is what this page supports. The other lane holds everything institutional: required placement activity, record entries, evaluations, approvals, and any step that another person has to complete. Those items have their own deadlines, live in official systems, and cannot be moved by working harder on a draft. Confirm their status where they actually live, and raise anything uncertain with faculty or your placement contact now rather than in the final week.

Reading the rubric row by row as an assembly checklist

Convert each row of the live rubric into a component with a location. One row becomes a section or a specific paragraph, another becomes the next, and a row about evidence becomes a set of citations distributed where the claims are. Write the list down before drafting and treat it as a build order rather than a grading sheet. Build the component that carries the most weight or the most difficulty first, while there is still time to discover that it needs a source you do not have.

Check the list for elements that are easy to overlook because they are not prose: required file formats, title and reference pages, headings in a required style, a required number of replies, an attachment, a template. These are the components that turn a strong draft into a late or incomplete submission. What is required for your activity is stated in your classroom, and that statement governs.

Closing the source shelf

Late-term sourcing should be finishing work, not discovery. Go through every source you intend to use in the remaining deliverables and confirm three things: that you have read enough of it to defend the claim you attached, that the version is current, and that the citation is complete enough to format without a second search. Anything failing one of those tests either gets fixed now or gets replaced by something already on your shelf.

Resist the pull to add unread sources for volume in the closing stretch. A reference list longer than the argument is a familiar pattern and a readable one. Where a claim genuinely needs support you do not have, the efficient move is usually to narrow the claim to what your existing evidence supports, which improves the paragraph as well as the citation. Depth in the final weeks comes from what the sources are doing, not from how many appear.

Assembly-stage pitfalls and their fixes

The first pitfall is saving the hardest component for last on the theory that the easy parts will build momentum. They build a document with a hole in it. The fix is the build order above, hardest first.

The second is discovering a required element late, usually a format, a template, or a posting rule. The fix is a components pass on the live instructions at the start of this stage, listing every requirement that is not writing.

The third is a collision between placement obligations and writing deadlines that neither calendar predicted. The fix is a single view of both lanes maintained from here onward, with the institutional lane treated as fixed and the writing lane scheduled around 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 9 activities. The registered syllabus, classroom, rubric, announcements, instructor directions, and official policies remain controlling.

Week 9 questions