NRNP 6624 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 Foundations of Psychotherapy, 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.

Worked reasoning for a cadence Week

By the second Week the goal is a repeatable reasoning drill, not a heroic one-off effort. In a psychotherapy foundations course, most written work reduces to the same four-part paragraph engine: a position stated in the first sentence, a concept defined from an assigned source, an application of that concept to the exact situation the prompt names, and a closing sentence that states the implication. Run every draft through that engine until it becomes automatic. If the live activity asks the student to apply a foundational idea, such as how a given theoretical orientation frames a problem, the engine produces a post a grader can follow without rereading.

Recalibrate the engine with the first instructor signals. Announcements, early comments, and any returned feedback reveal how this specific section wants reasoning displayed: how formal, how heavily cited, how tightly tied to the readings. Write those observations into the working notes as instructions to self, then apply them in the current Week. A cadence built from the actual instructor's expectations is worth more than any generic template for the same course code.

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.

A source routine that can repeat every Week

Sustainable source work in this subject is a weekly loop, not a fresh scramble. The loop has three stops: the assigned readings for the current Week, one focused pass through the library's nursing and psychology databases for anything the prompt requires beyond them, and a short vetting check on every candidate source: peer review status, publication date, author authority, and fit with the claim it must support. Cap the loop in time. A discussion post rarely needs a deep literature hunt, and hours spent searching are hours taken from reasoning and revision.

Annotate each keeper the same way every time: source, date, design or authority, the usable finding in one line, its limitation, and the exact claim it will support in this Week's work. That format, kept in one running file, becomes a personal evidence bank for the quarter. The rule that keeps the bank honest: a source enters the draft only through its use note, so nothing gets cited that was never actually read and summarized by the student.

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.

Reading the rubric row by row

Week 2 is when rubric reading should become comparative. Put the current activity's rubric beside Week 1's and note what repeats: most Course-Based rubrics reuse an anatomy of content rows, evidence rows, and mechanics rows even when the wording shifts. Build a private checklist from that anatomy, one line per recurring row type, and run every draft against it before submission. The checklist never replaces the live rubric; it guarantees the live rubric gets read completely instead of skimmed.

When the first scored rubric returns, read it row by row against the top column's language. For any row scored below the top level, write one corrective line in the working notes: what the top column asked for, what the submission actually did, and the single change the next submission will show. This is the cheapest coaching available in the course, it arrives already personalized, and a student who applies it in Week 2 compounds the benefit for nine more Weeks.

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.

Week 2 pitfalls and the fix for each

Pitfall: reusing the structure of the first Week's post for the new prompt because it worked once. Fix: translate the new task from scratch into one sentence naming the decision, the evidence, the audience, and the output, then let that sentence, not last Week's shape, dictate the structure.

Pitfall: batching the entire Week into deadline day, which quietly breaks activities that carry separate initial-post and reply windows. Fix: split the Week into capture, drafting, evidence, and reply blocks on different days, and treat the reply window as its own deadline with its own calendar entry.

Pitfall: letting replies collapse into polite agreement now that the novelty of the course has worn off. Fix: hold every reply to one of four moves, comparing evidence, applying the peer's idea to a different context, naming a boundary or exception, or asking a question grounded in the readings, and delete any reply draft that does none of them.

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