PRAC 6587 Week 10 planning manual

1. Capture the live Week 10

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.

Turning feedback into a revision plan

Revision without a plan degenerates into rereading, and rereading mostly repairs commas. Build the plan from the returned criterion rows: one line for each row that lost points, containing the comment as it was written, the student's own diagnosis of what the reader was missing, the specific change that will address it, and the exact location in the document where the change goes.

Sort those lines by weight, work from the top down, and stop when the remaining lines are cosmetic. Diagnosis is the step most often skipped and the step that decides whether the revision works, because one comment can describe several different problems and each has a different repair. Where a comment is ambiguous, the honest route is to ask the instructor rather than guess, in writing and early enough to act on the answer. What each criterion requires is settled by the live rubric, not by memory of it.

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 10

Read the rubric this Week as an instruction set rather than as a description. Take each row and rewrite it as an imperative addressed to the draft: this row wants this to be visible in this place. That rewriting exposes rows that were understood in the abstract and never located anywhere, which is the most common reason a well-written response settles in the middle.

Then check the two versions against one another: the rubric the draft was written under and the rubric it will be scored under, because a document revised against the wrong version can lose ground while genuinely improving. Where a row was already satisfied, confirm the revision has not damaged it, since a change made for one row routinely breaks another, particularly length, structure, and coverage rows. The rubric currently posted in the registered classroom governs every one of these judgements.

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.

Repairing the evidence weaknesses feedback named

Evidence comments usually describe one of four failures, and each has its own repair. Insufficient support means claims are standing alone: locate them and either support or soften each one. Weak support means the source cannot carry the claim: check the recorded design and setting, then replace the source or narrow the claim. Misused support means the citation does not say what the sentence says: reread the source at the point cited and correct the sentence rather than the citation. A currency comment means the date does not meet the activity's requirement: find current support, or explain why an older foundational source remains appropriate if the activity allows it.

Work from the recorded fields rather than from memory of the reading, since memory is what produced the misuse. Assigned readings come first where the live activity requires them, and adding more sources without addressing the named failure will not move the row.

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.

A gap named in feedback is never filled by invention

This is the Week when the boundary is under the most pressure, because feedback can name something missing that the student cannot now go back and obtain. If the missing element concerns the student's own placement activity, it cannot be supplied by writing.

Hours, encounters, logs, site and preceptor detail, evaluations, supervisor comments, and signatures are records of what actually happened, produced and verified through the program's own process by the student and the people authorized to confirm them, and nothing on this page reconstructs, estimates, or illustrates any of it. The correct response to a gap of that kind is a prompt written approach to the instructor or the program office, describing the situation accurately and asking what the process allows. A revision that closes such a gap with invented material is a far more serious problem than the points originally lost.

7. Run the Week 10 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 10 pitfalls and the fix for each

The first pitfall is surface revision. Sentences are smoothed, the structural problem the comment described is untouched, and the result does not move. The fix is to require every revision line to change the structure, the reasoning, or the evidence, and to treat wording changes as a separate final pass.

The second is revising against the wrong rubric version. The document improves against a saved copy while drifting away from the live one. The fix is to open the rubric in the classroom at the start of the revision session and to work only from that window.

The third is revision that breaks the limits. Added material pushes the response past a length or format rule and costs points somewhere else. The fix is to check length, format, and structure rules after every substantive addition rather than once at the end.

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

Week 10 questions