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

Running the midpoint audit as a written exercise

A midpoint audit performed mentally is worth nothing. Build one table with a row for every graded item released so far and columns for submitted, returned, criterion results, comments received, action taken, and action still open. Build a second table for everything with a deadline still ahead, including the steps that depend on other people. The value sits in the two totals at the bottom: how much of the course has already been scored and how much remains, because those figures decide which repairs are still worth attempting.

Then read the comment column as a set rather than one entry at a time. A single comment is a reader's response to one artifact. The same comment appearing three times is a pattern, and a pattern is the only thing worth changing method over. Write the pattern down as a sentence, then write the smallest change in practice that would test it during the next live activity.

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 in Week 5

The midpoint rubric read runs backwards. Instead of reading a rubric in order to plan, collect every returned rubric and read the rows across activities to find the one that consistently scores lowest. Line them up and mark each recurring row with its results in sequence.

A row that started low and has improved is a solved problem. A row that is stable and low is the target for the rest of the quarter, and it deserves a written definition of what a stronger response on that row would contain, in the student's own words, drawn from the wording the rubrics themselves use. Do not average the rows or convert them into a general impression, because the detail is the whole point. Then look forward and check whether the recurring row appears in the rubrics still to come, since a weakness that will not be scored again is not where the remaining effort belongs. The live rubrics decide what each row means.

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.

Auditing the reference list for sources that never worked

Half a quarter produces a reference list with passengers in it. Go through everything cited so far and mark each entry as load bearing, redundant, or decorative. Load bearing sources supported a claim that would fall without them; keep their full record and note where they might return. Redundant sources duplicated a stronger entry; keep one and drop the rest from the working file so future searches start smaller.

Decorative sources were cited because a citation seemed expected. Those are the entries that attract evidence comments, and the audit should record why each was reached for, since the reason usually points at a claim the student was unsure of. Where feedback has named an evidence weakness, translate it into a concrete source requirement for the remaining Weeks: a different design, a closer setting, a more current date, or the assigned reading that was skipped.

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.

Auditing the placement lane without writing in it

The midpoint is also when a student discovers that a program or placement step has fallen behind, and the temptation to close that gap on paper is at its strongest here. It does not close on paper. Whatever record the program requires of the student's own activity is completed only by the student, only from what actually occurred, only through the process the program specifies, and confirmed only by the people authorized to confirm it.

This page will not draft, reconstruct, estimate, or illustrate any part of that record, and it offers no figures, no sample entries, and no wording for evaluations, signatures, or supervisor feedback. The productive midpoint move is a written list of who must be contacted, what must be verified, and by when, sent early rather than late. Nothing on this page indicates that any hour, encounter, or requirement has been met; only the program's own process determines that.

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 an audit that only counts points. Points are the output; the criterion comments are the diagnosis. The fix is to build the audit around criterion rows and to treat the score column as secondary information.

The second is reading a comment about clarity as a comment about style. Comments about unclear writing frequently describe unclear thinking, and rewording a confused paragraph preserves the confusion in better sentences. The fix is to restate the underlying point in one plain sentence before touching the paragraph; if that restatement is hard to write, the problem was never the wording.

The third is an audit with no dates attached. A list of repairs with no scheduled slot is a list of regrets. The fix is to assign every open action to a specific block in the remaining calendar and to treat that block as fixed rather than as an intention.

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