NRNP 6810 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 Primary Care Approaches for Children, 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.

A repeatable reasoning loop for pediatric prompts

Week 2 is where the method becomes a routine instead of a rescue. Fix the loop in writing: capture the live activity, state its reasoning question, plan in proof order, draft, audit against the rubric, submit, and record the result. Then give the loop its subject checkpoints. Every substantive paragraph in this course can be tested with four questions. Is the concept defined the way the assigned materials define it? Is it applied to the exact context and age band the prompt states? Is the developmental or family-context modifier written out rather than implied? Does the paragraph end with the implication the current rubric asks for?

Keep the loop as a template of questions, never a template of prose. Sentences must be rebuilt each week from the live prompt, or the answers drift away from what is actually being asked. Pin the loop to the Course-Based calendar: in a fixed-date week, the initial discussion post, the replies, and any file upload are separate deadlines with separate work behind them, so give each its own working session rather than one shared evening.

Reading the rubric row by row

By Week 2 the rubric should stop being something read after drafting. Turn the current week's rows into a pre-writing checklist: one line per row, phrased as the question the grader will answer. If Week 1 feedback has arrived, reconcile it row by row before writing anything new. Find the row that cost the most points, restate in one sentence what its top column demanded, and put that sentence at the head of this week's checklist.

Watch the small words that change scope: each, all, both, and at least are quantity commitments, and audience words such as colleagues or caregivers change the register a row expects. Where a discussion is present, note that replies are usually scored by their own row with their own expectations, so a strong initial post cannot carry weak replies. The checklist keeps the cadence honest: when a row is answered in the draft, mark where. A row with no marked location is a row not yet earned, and the live classroom rubric remains the deciding document.

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.

Growing a source bench instead of starting over

The second week decides whether evidence work compounds or restarts from zero every time. Keep one working bibliography for the course and grow it deliberately. Organize it by the broad lanes of children's primary care rather than by week number: development and growth, prevention and health supervision, acute concerns, ongoing management, and family communication. The lanes are an organizing habit for private notes, not a prediction of what any registered week assigns.

Each bench entry needs four parts: the full citation record in the required style, the date it was verified, its authority type, and a one-line use note naming the claim it can support. When the new week's task arrives, shop the bench first, then search for what the bench lacks. Re-verify anything date-sensitive before reusing it, because prevention and management guidance in this field revises on its own schedule. Assigned readings still come first whenever the live instructions require them, and every source that enters the draft must be re-matched to this week's actual claim, not carried on momentum.

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.

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 one: letting the initial post drift toward the file deadline. A Course-Based week usually stages its deadlines, and the earliest one arrives faster than the opening week suggested. The fix is to schedule the initial post as its own deliverable with its own working session, placed early enough that replies can still do real work afterward.

Pitfall two: reusing the Week 1 source list wholesale. Sources that served an orientation task rarely match a second week's claims, and a grader can see support that points at nothing. The fix is bench discipline: re-match every carried source to a sentence in this week's draft, and retire any source left without a claim to support.

Pitfall three: padding replies with agreement. Restating a peer's post with praise satisfies no reply expectation. The fix is one deliberate move per reply: compare evidence, apply the peer's idea to a different stated context, name a boundary where the idea stops working, or ask a focused question grounded in the course materials.

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