PRAC 6587 Week 3 planning manual

1. Capture the live Week 3

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.

Making the reasoning visible on the page

Reasoning is invisible until the sentences carrying it exist. The practical test is whether a reader can follow the movement from the stated concept, to the context the prompt supplies, to the claim, to the implication the rubric asks for, without supplying a step themselves. Draft that movement as four labelled sentences before writing any paragraphs, then expand each one in place.

Two failures dominate this stage. The first is a paragraph that names a concept and jumps to a conclusion, leaving the connecting step in the writer's head where no reader can score it. The second is a paragraph that does contain the step but buries it mid-sentence, where a reader scanning for the reasoning will pass over it. In work positioned in acute care practice, the connecting step is usually the graded part, so give it its own sentence and write it with the verb the rubric row uses.

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 3

This is the Week to read a rubric for its verbs and its levels rather than its topics. Copy each row into a working document, strip it down to the verb and its object, and ask what a reader would need to see for that row to move from a middle level to the top level as the current rubric words those levels.

Most rubrics separate levels by three qualities: coverage, depth of reasoning, and strength of support. Work out which of the three a given row is actually measuring, because a row measuring depth is not improved by adding another item, and a row measuring coverage is not improved by explaining one item further. Then mark beside each row the paragraph or section where it will be visible in the draft. Rows with no location yet are the drafting queue. The registered classroom rubric, in its current version, remains the authority on all of it.

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.

Choosing sources that license a step rather than decorate a claim

When the aim is visible reasoning, a citation earns its place by permitting a step the writer could not otherwise take. Before attaching a source, name the step it is doing: establishing that a concept means what the draft says it means, showing that a relationship holds, supplying a standard against which something is judged, or marking the boundary where the claim stops.

Different steps want different support, and the fields already recorded in the working file make the match testable. Authority or design indicates whether the source can carry a general claim. Population or setting indicates whether it reaches the context the prompt names. The recorded limitation indicates where the step has to stop. A citation sitting at the end of a paragraph that would read identically without it is decoration; move it to the sentence it actually licenses or take it out. Assigned readings still come first where the live activity requires them.

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.

Reasoning about practice without importing the student's record

Making reasoning visible does not mean being supplied with material to reason about. Where a live activity asks for written reasoning connected to the student's own placement experience, that content comes only from what the student personally observed and recorded, handled under the confidentiality rules the program and the site impose.

This page will not invent a scenario, a case, an encounter, or a detail, not even as an illustration, because an illustration in this subject is indistinguishable from a template and invites a student to write toward a situation that never occurred. What this page can describe is the shape of the writing: how to define a concept precisely, how to sequence a comparison, how to state a limitation, and how to keep identifying detail out of a document. The experience itself, its documentation, and every hour or competency claim attached to it remain the student's alone.

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

The first pitfall is summary presented as analysis. The paragraph is accurate, properly cited, and answers no question. The fix is to write, after each paragraph, the question that paragraph answers; if the question turns out to be what the source says, rebuild the paragraph around what follows from it.

The second is reasoning that lives in a table while the prose merely repeats it. Graders read prose first, and a table cannot argue. The fix is to keep the table for structured detail and to write the interpretation in sentences beneath it.

The third is an unsupported bridge sentence carrying the whole argument. The pivotal claim is stated as though it were obvious, and the row scoring support finds nothing beneath it. The fix is to identify the single sentence the argument turns on and give it either a source or an explicit line of reasoning a reader can check.

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 4. 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 3, 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 4.

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

Week 3 questions