PRAC 6577 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 Advanced Primary Care Immersion Practicum II, the durable class question is: What evidence supports the judgment, what alternatives matter, and what remains outside the student's authority? 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.

3. Build the work in proof order

Move from cue to mechanism or standard, then to prioritized judgment, action, monitoring, and escalation. Use only de-identified authorized context.

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 with two rubrics open

By Week 2 you have a returned rubric as well as a live one, and reading them side by side is more informative than reading either alone. Mark every row that recurs word for word, every row whose verb has changed, and every row that is new. The recurring rows become a standing checklist you run before every submission for the rest of the quarter, because they will keep earning or costing points all term. The changed verbs are the real news: a row that moved from describe to justify is a different task wearing a familiar label, and answering it in last week's register loses points quietly. New rows get the full treatment of noun, verb, and location on the page. Keep the comparison in one file so it accumulates rather than restarting each week. Your classroom rubric decides what those rows say and what they are worth; nothing here predicts their content.

Turning the course method into a weekly production rhythm

A cadence is a schedule for thinking, not only for typing. Assign each stage of the cue-to-escalation chain a slot in your week: reading and cue identification early, the mechanism or standard next, judgment and alternatives in the middle, action and monitoring last. Then draft in two passes. The first pass writes the reasoning chain as bare sentences with no transitions, no citations, and no introduction, so you can see in a few minutes whether the argument actually holds together. The second pass adds evidence, qualifiers, and prose. Splitting the passes stops the common Week 2 problem of discovering a broken argument after the paragraphs are already polished and feel too expensive to cut. Protect a fixed slot for replies and for the mechanical work of formatting, conversion, and upload, because those expand to fill whatever is left.

A note habit that only you can run

The notes you take around your own placement activity are yours. You keep them in your own documentation system, under the rules your site and Walden set, and you are the only person who can create, correct, or confirm a single line of them. This page can describe the habit worth forming in Week 2: date every note as you make it, keep identifying detail out of anything that travels, and never let a note file and a coursework draft share a folder. It cannot supply an entry, estimate what a week of activity should contain, or tell you whether your record is adequate. Set the habit now so that the writing lane never has to wait on memory later, and so the boundary between what you performed and what you wrote stays obvious to you and to anyone reviewing the work.

4. Use evidence deliberately

Prefer current authoritative clinical guidance and peer-reviewed evidence appropriate to the question; distinguish guideline recommendations from patient-specific facts.

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 shelf you can reuse

A quarter of scattered downloads becomes a pile that nobody rereads. Build a shelf instead. At the moment of capture, before the source is closed, write the use note: the one claim this source can support in this course. Record the issuing body, the publication or revision year, and, for a guideline, whether the version you have is the current one, because professional guidance is reissued and a superseded edition can be embarrassing to cite. Tag each entry with the kind of claim it can carry, such as mechanism, recommended standard, prevalence, or communication practice, so that later weeks can search by need rather than by memory. A shelf built this way makes Week 6 integration and Week 9 assembly fast, and it keeps you from padding a reference list with sources that never do analytical work in the response.

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 2 quality gate

Check safety, scope, differential logic, contraindications, documentation, confidentiality, and every student-performed clinical requirement.

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 cadence failures and the repair for each

The first failure is the reply that agrees. It arrives on time, restates the peer's point in fresh words, and adds nothing a reader could score. The repair is a fixed reply pattern: compare the peer's reasoning with a different source, apply their claim to a different population or setting, name the boundary where their claim stops holding, or ask one focused question that a course reading could answer.

The second failure is a growing source pile with no use notes. Each item looked relevant when saved and none has an assigned job, so drafting stalls while you reopen files. The repair is the capture-time use note, and a rule that a source without one does not get cited.

The third failure is drafting coursework in the same file as your own placement notes. Copy and paste is unforgiving, and material that belongs only in your documentation system can end up in a shared draft. The repair is separation at the file level plus a habit of writing coursework from your own summarized understanding rather than from the note file itself.

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