PRAC 6587 Week 2 planning manual

1. Capture the live Week 2

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 the first instructor signals into a written cadence

A cadence is a written schedule of when each kind of work happens, not a resolution to keep up. Build it from what the opening Week actually taught: how long the reading took, how long a first draft took, and where the unplanned time went. Write the week as named blocks with start times, one block per activity type, and place the block that produces text ahead of the block that collects more reading, because collecting is comfortable and drafting is not.

In a course carrying an immersion structure, the cadence also has to accommodate steps other people schedule, which means the writing blocks are arranged around fixed commitments rather than the other way around. Test the cadence against one real week before trusting it. If two blocks routinely collapse into one, the cadence is wrong and should be rewritten rather than attempted again with more determination.

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 2

By the second Week there is usually more than one rubric available, and the useful reading is comparative. Put this Week's rubric beside the earlier one and mark which rows are identical, which are worded differently, and which are new. Rows that recur are the course's standing expectations and deserve a permanent checklist the student reuses every Week. Rows that change are the ones that catch a student running on habit.

For each recurring row, write down the sentence pattern that satisfied it last time, then test whether the current wording still accepts that pattern. Keep the weights visible while doing it, because a criterion that carried little weight in one activity can carry much more in another, and effort should follow the weight. None of this replaces the live document: the rubric in the registered classroom, in the version currently posted, decides what is scored and how.

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.

Building a source file the cadence can actually use

A cadence collapses when every drafting session has to begin with a search. The repair is a source file written once and read many times. For each entry keep the same fields the class method names, and add one line no database supplies: the sentence this source is allowed to support. That permission line is what makes an entry reusable across the quarter without becoming a crutch, because it stops the source from drifting under a claim it does not fit.

Assigned readings stay first wherever the activity requires them. When new searching is needed, run it inside a scheduled block and cap it, since an unbounded search will quietly absorb the writing time it was meant to protect. Close each reading block by writing the usable finding in one line; anything that cannot be stated in one line is not yet understood well enough to cite.

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.

Two ledgers, kept apart

A working cadence contains two ledgers that never merge. The first is the coursework ledger this page describes throughout: activities, rubrics, drafts, deadlines, submissions, and receipts. The second is whatever record the program requires of the student's own placement activity, and it is filled in only by the student, only from what the student personally did, and only in the system the program specifies.

This manual has nothing to add to the second ledger. It does not model entries, propose plausible figures, describe typical encounters, or supply language for evaluations, signatures, or supervisor comments, and any outside source offering those things should be treated as a hazard rather than a shortcut. Scheduling both ledgers in the same weekly plan is sensible. Letting the drafting habits of the first leak into the second is not. Verification of the second belongs to the student and the people authorized to confirm it.

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

The first pitfall is a cadence built on the best week the student ever had. It survives contact with one busy week and then dies. The fix is to design the schedule against a realistic week and to write a fallback version for the week that goes wrong, so the fallback is a plan rather than an improvisation.

The second is notes that cannot be written from. Highlighting a reading feels productive and produces nothing draftable. The fix is to end every reading block with three sentences in the student's own words, one of which names a claim the reading could support.

The third is treating replies as an afterthought when a discussion is live. A reply written against the deadline usually agrees with something and adds nothing the rubric can credit. The fix is to schedule reply blocks as their own appointments and to enter each one already holding a specific comparison, application, boundary, or question drawn from the course material.

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

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

Week 2 questions