PRAC 6567 Week 5 planning manual

1. Capture the live Week 5

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: four ledgers, reconciled in one sitting

A midpoint audit only works if it is written down and done at once. Open four ledgers and reconcile them against each other in a single sitting rather than glancing at each across a week.

The first ledger is submitted work: every activity submitted so far, the date, the confirmation the student saw, and the current gradebook state. The second is feedback: every criterion-level comment received, grouped by the kind of gap it names rather than by the activity it came from. The third is the remaining calendar: every activity still visible, with its deadline and its reply, approval, or file steps.

The fourth is the placement dependency lane, and it is the one that most often breaks a practicum course late. It holds only institutional steps: approvals, forms, attestations, and any documentation the official Walden process requires. Reconciling it means the student personally confirms with the responsible party what has been received and recorded. Nothing in that lane can be checked from a planning page, inferred from memory, or completed by anyone else, and no entry in it may be drafted, estimated, or reconstructed on the student's behalf.

Read the four together and write one page naming the largest risk and the next action. That page is the output of the audit.

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 midpoint offers something Week 1 could not: rubrics that have already been scored. Read the returned ones with the same discipline used on blank ones. For each row that lost points, write three lines. The first restates the criterion in your own words. The second records what the submission actually did on that row. The third names the specific behavior that produced the gap, such as a claim left unsupported, a prompt part skipped, or a format rule missed.

Now group the third lines across every returned rubric. Two or more identical entries is the real finding of the audit, and it is worth more attention than any single lost point. Convert the pattern into one small corrective practice, and write down exactly where in the remaining calendar you will test it.

Then check something easy to overlook: that the blank rubric for the next activity is the same version you have been working from. Rubrics are sometimes revised mid-quarter and the announcement is not always noticed. Download the current copy fresh, compare it line by line against your saved one, and remember that your classroom rubric decides.

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: prune the shelf before it grows further

Half a course of research produces a shelf carrying dead weight. Audit it now, while replacing a source is still cheap.

Go row by row and mark each source with one of three verdicts. Keep means the source did analytical work in a submitted response or holds a use note tied to a remaining activity. Retire means it was collected and never used, in which case delete it rather than carrying it forward as a permanent candidate. Replace means it is still needed but weak: dated relative to what the activity asks, drawn from a population too distant to defend, or a tertiary summary standing where a primary source belongs.

For the replace list, search the specific claim rather than browsing the general topic. Write the claim down, then look for a recent peer-reviewed study, a systematic review, or current guidance from a recognized specialty body that addresses it directly. Check the currency expectation the live activity states before deciding what counts as recent.

Finish by confirming that every citation used so far resolves to a complete record. A midpoint hour spent on retrieval details prevents a scramble in the closing Weeks, when the same gap costs an entire evening.

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 5 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 5 pitfalls and the fix for each

The first pitfall is auditing the gradebook and stopping there. The gradebook reports written work; it says nothing about whether the institutional steps a practicum course depends on have been completed and recorded. The fix is to treat the dependency lane as a separate audit with its own confirmations, obtained by the student directly from the responsible party rather than inferred from silence.

The second pitfall is reading an ungraded item as an accepted item. An empty gradebook cell can mean a submission is queued for grading, or it can mean nothing arrived. The fix is to check the student's own submission confirmations against the activity list and to raise any mismatch with the instructor in writing immediately, while the timeline still supports a remedy.

The third pitfall is answering feedback by rewriting the criticized sentences. That repairs one artifact and leaves the habit intact. The fix is to correct the method instead. If the pattern is unsupported claims, change the drafting order so evidence attaches as each claim is written, then prove the change on the next activity rather than on the returned one.

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 6. 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 5, 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 6.

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 5 activities. The registered syllabus, classroom, rubric, announcements, instructor directions, and official policies remain controlling.

Week 5 questions