PRAC 6567 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 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: revise by criterion, not from the top

Reading a draft from the beginning is a comfortable way to spend an evening and a poor way to raise a score. Top-to-bottom reading finds sentence problems and misses structural ones, because familiarity smooths over the gaps the writer already believes are filled.

Revise in three separate passes instead. The task pass reads the prompt and the draft side by side and asks one question per required element: is it present, and is it where a scorer will look for it. Mark absences and fix nothing yet.

The reasoning pass reads only the claim sentences, skipping everything else. Pulled out of context, weak claims become obvious: the ones that are really topic announcements, the ones no source supports, the ones repeating an earlier claim in different words. Repair the claims before touching the prose around them.

The mechanics pass comes last and is purely a checklist: citations, headings, format, length, file type. Running it earlier wastes effort on sentences that are about to be rewritten.

Order matters because each pass changes what the next one should examine. Revising mechanics first is the most common way a revision consumes a full day and improves nothing that is actually scored.

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

Revision is where the rubric earns its keep, so drive the revision straight from it. Put the rubric in one column and the draft in another and walk the rows in order. For each row, find the exact text that satisfies it and mark that text. Rows with nothing to mark become the revision list, ordered by rubric rather than by the sequence in which the draft happens to raise them.

For any row that lost points on an earlier submission, do more than reread it. Write out the descriptor for the level above the one previously earned, in your own words, and then write what the current draft would have to add to reach it. Specificity is usually the difference, and specificity is addable.

Then verify the version. Confirm the rubric open on screen is the one attached to the live activity, not one saved in Week 5 and reused out of habit, and confirm that any announcement modifying it has been applied. A thorough revision performed against a superseded rubric is wasted work, and 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: replacing a source late without damaging the argument

Late revision sometimes reveals that a source cannot carry the claim resting on it. Replacing it carelessly breaks more than it repairs, so work in a fixed order.

Start from the claim rather than the citation. Write the claim as a standalone sentence and decide whether it is worth keeping at its current width. Often the honest move is to narrow the claim until the existing source supports it, which costs one sentence instead of an evening.

If replacement is genuinely needed, search the specific claim rather than the general topic, and prefer a source whose population and setting match the context the response addresses. Read enough of it to write a fresh appraisal note. A source dropped in on the strength of its title is the fastest route to a misattributed sentence.

Then repair the surroundings. Check that the sentence says what the new source actually found, that any figures match, that the reference entry is correct, and that no later sentence depends on a detail only the old source supplied. Finally, reread the paragraph aloud. A late substitution usually leaves a seam, and reading aloud finds it faster than rereading silently.

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 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 polishing over a hollow claim. Rewriting a sentence that has no support makes the weakness harder to see without repairing it. The fix is the claim-only reading pass: settle what the draft asserts before improving how it asserts it.

The second pitfall is revising to the wrong instructions. Late in a quarter, saved copies accumulate and announcements get missed. The fix is to reopen the live activity and its current rubric at the start of the revision session and to work from nothing else on screen.

The third pitfall is revising a reflective section into something stronger than the record can support. Tightening language is legitimate. Adding detail, certainty, or accomplishment that did not exist is not, and in a practicum context it edits a claim about the student's own activity. The fix is a firm separation: revise the writing for clarity, structure, and accuracy only, and leave every statement about hours, activity, documentation, supervision, and verification exactly as the student can personally attest and as the official Walden process records it. No revision should imply a requirement has been met.

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