PRAC 6567 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 I, 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.

Worked reasoning: the closing sweep and the carry-forward brief

Week 11 has two jobs, and running them together produces a rushed version of each. Separate them.

The closing sweep is verification and nothing else. Confirm every registered activity has a submission the student can see, that each submitted file opens correctly from inside the classroom rather than from a local folder, that timestamps fall inside the required windows, and that receipts are saved. Confirm separately, with the responsible party, that every institutional step a practicum course depends on is complete and recorded. That confirmation is the student's to obtain, and nothing substitutes for it.

The carry-forward brief is written afterwards and is aimed at the next course. Keep it to one page under four headings. Method holds the working practices that produced the best results this quarter, such as the drafting order or the appraisal fields that proved useful. Weakness holds the recurring criterion gaps with a corrective practice for each. Sources holds the small number of references worth revisiting, with a note on why. Questions holds what remains genuinely unclear.

Write the brief from method and understanding rather than from submitted text, because a later course requires new work, new evidence, and new authorship even where the concepts return.

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

The rubric gets read twice in a closing Week, and the second reading is the one most students skip.

The first reading is the last check before submission. Walk the rows in order and, for each one, point at the specific text that satisfies it. Pointing is the test. If you find yourself explaining how a row is implied, that row is not yet satisfied. Give the heaviest rows a second look, and confirm the presence rows one final time, since those are the cheapest points on the page and the easiest to drop at the end.

The second reading happens after the result returns. Read the scored rubric criterion by criterion and record, for each one, what was said, what produced it, and what would change it next time. Move those entries into the carry-forward brief while the work is still fresh in memory. A returned rubric is the most specific feedback a quarter produces, and it stops being useful the moment the course closes and it goes unread. Grades, designations, and progression decisions rest with Walden and the instructor, and your classroom rubric decides what each row required.

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.

Source work: archive a shelf you will actually reuse

The reference shelf built across eleven Weeks is worth keeping, but only if it is trimmed and labelled now. Six months from now, an untidy folder of downloads is indistinguishable from no folder at all.

Keep three categories. Foundational sources shaped how you understand a central concept, and they stay regardless of age. Current guidance from recognized professional and specialty bodies stays with an explicit note that the edition must be re-verified before it is cited again, since such documents are periodically superseded. Recent primary studies and reviews stay only where they did real analytical work, with the use note attached to each.

Delete the rest. A source collected and never used will not become more useful later, and carrying it forward encourages the habit of citing what is nearby rather than what fits.

Store the shelf as a single table holding the full citation, the document type, the claim it supported, and the date it was appraised, in a file containing no placement material whatsoever. Keeping the study archive clean is the last practical step in holding the written layer and the student's own record permanently apart.

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.

Three Week 11 pitfalls and the fix for each

The first pitfall is closing the course on the strength of the gradebook alone. A visible grade for written work says nothing about whether the institutional steps a practicum course depends on have been received and recorded by the parties responsible for them. The fix is an explicit confirmation obtained by the student directly from each responsible party before treating anything as finished, and a refusal to infer completion from silence, from a planner, or from any page.

The second pitfall is carrying forward text instead of method. Saved paragraphs invite reuse, and reusing previously submitted work breaches originality expectations in a later course. The fix is the carry-forward brief: keep the practice, the diagnosis, and the source list, and delete the prose.

The third pitfall is reading a completed course as a completed capability. Finishing registered activities is an academic outcome. It is not the same as readiness, and it is not a determination anyone outside Walden can make. The fix is to write the open questions into the brief honestly, raise them with faculty in the next course, and remember that decisions about progression, competency, and readiness belong to Walden and the instructor 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