PRAC 6831 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 Pediatric Primary 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.

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.

Building a repeatable writing week

By the second Week the instructor's phrasing, response habits, and posted expectations are visible, and that is enough information to fix a shape for the rest of the term. A workable shape has five blocks: capture, read, draft, check, and reply. Capture happens the day the Week opens. Reading ends with written definitions rather than highlighted paragraphs. Drafting starts with the heaviest rubric row. Checking is a separate sitting on a different day, because nobody proofreads a sentence written twenty minutes earlier. Replies are scheduled against the response window rather than squeezed in behind the initial post.

Immersion coursework adds a scheduling complication a lecture course does not have. Placement activity moves on a calendar the student does not fully control, and its record is maintained and verified by the student under Walden's own process. The writing week is therefore planned around the hours that remain, not the hours the student wishes existed. Keep the two calendars in separate columns so a written deliverable is never drafted as though an activity had already happened.

Notes the student has already taken can be organized for study without ever entering a draft. Sort them by concept rather than by day, remove anything that identifies a person, a family, or a place, and keep only the general question or principle the note raised. What travels into coursework is a concept to research, never a described encounter.

Reading the rubric row by row in the second Week

The second Week is the first chance to read a rubric comparatively. Put the current rubric beside any returned criterion feedback and look for rows that repeat. Recurring rows are the course's real spine, and improving on them pays in every remaining Week. Rows that appear once are local and should be handled locally rather than turned into a habit.

Sort the rows into two kinds. Product rows describe something that must exist in the finished text: a stated purpose, a defined scope, a supported claim, a correctly formatted reference list. Process rows describe how the work was done: timeliness, participation, engagement with peers, adherence to a stated procedure. Product rows are repaired by rewriting. Process rows can only be satisfied by scheduling, which means they have to be handled at the start of the Week rather than in the final edit.

Record each row in a criterion ledger using the rubric's own wording, then add a column for the evidence that will satisfy it and a column for who has to act. Weights, levels, and wording differ by section and term, so your classroom rubric decides what belongs in that ledger.

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.

Turning reading into a source shelf you can reuse

A term of writing goes faster when sources are collected onto a shelf rather than hunted again each Week. For each item record the full citation, the publication or revision date, the type, the population and setting studied, the one finding that is usable, the stated limitation, and the claim it is allowed to support. Type matters because the categories behave differently inside an argument. A primary study reports what was observed under stated conditions. A systematic review reports what the accumulated studies say together. Professional guidance states what a body recommends and usually names the strength behind the recommendation. A background text defines.

Write the use note before drafting, not afterwards. If a source cannot be given a single sentence describing the work it will do, it is not ready to be cited, and citing it anyway produces a reference list longer than the reasoning it supports. Assigned readings stay mandatory wherever the live activity requires them, and a shelf item never displaces a required reading.

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 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 reusing the previous Week's structure because it came back without complaint. A structure that fit one prompt can quietly ignore a new requirement, and the writing will read as fluent while missing a scored row. The fix is to rebuild the outline from the current instructions each Week and to test the new outline against the criterion ledger before a paragraph is written.

The second pitfall is writing replies that agree. Agreement adds nothing a grader can score. The fix is to give every reply one job before it is written: extend the peer's point to a different age band or setting, name a condition under which it would not hold, bring a source the peer did not use, or ask a question the course material makes answerable. Write the job at the top of the draft reply and delete the line before posting.

The third pitfall is a shelf that grows without use notes, which turns into a folder of files nobody can act on. The fix is a standing rule that nothing joins the shelf until its use note is written.

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