NRNP 6811 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.

Turning first signals into a weekly working cycle

Week 2 converts one week of lived experience into a cycle you can repeat for the rest of the quarter: capture the live activities, read with purpose, define the concepts, apply them to the stated context, check against the rubric, submit, and record the outcome. Give each step a standing time block matched to the deadline architecture you recorded in Week 1, so that research never collides with reply windows and checking never gets squeezed into upload hour. Write the cycle down as a checklist and revise it once, deliberately, when this week's results return, rather than improvising a new process every time something goes wrong.

Reading in this subject rewards a two-pass habit worth installing now. The concept pass asks what principle the material teaches. The application pass asks how that principle bends across childhood: what holds at every age, what changes as children grow and develop, and what depends on family and caregiver context. Annotate both answers into the scaffold you started, in your own words. Cadence matters here because prompts about children punish rushed generalization; a sentence that is safe as a broad statement often needs an age qualifier before it is true of a child, and qualifiers only get written when the schedule leaves room to think. By the end of Week 2 the cycle, not motivation, should decide when the work happens.

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 repeatable source pipeline

Stop searching from scratch every week. Build the pipeline once: the databases your program provides, saved searches for this course's recurring nouns, and filters for peer review, publication years, and child and adolescent populations wherever the tool offers them. Each new prompt then starts from its own key terms in an already-tuned instrument rather than from an empty search box, and the time saved goes into reading what you find instead of finding it.

Extend the Week 1 ledger into a running instrument with one line per source: citation, year, authority or design, the population and ages studied, the usable finding in your own words, its limitation, and the claim it supported. Write the use note at the moment of saving, not at drafting time, because a source you cannot summarize in one line is a source you have not yet read. When drafting, the ledger hands you the sentence: state the finding, cite it where it does work, and keep the assigned readings first wherever the live instructions require them. The pipeline is reusable structure; the content it carries must be found fresh for every new prompt.

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

In Week 2 the rubric stops being abstract, because the first scored results begin to return. Put each returned row next to your pre-submission reading of the same row and study the difference. Where your interpretation and the grader's application diverged, rewrite the row's requirement in your own words and record the sentence-level behavior that would have satisfied it. Then build a reusable row checklist for this course: every criterion phrased as a question, every question pointing at a specific place in the draft where the answer must live. Rubrics can vary by activity and can be updated midterm, so re-open the live version every single week instead of trusting last week's copy. The calibration you are building is yours to keep; the authority stays with the classroom's current rubric, exactly as it is written there.

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 their fixes

The first pitfall is reusing the shape of last week's answer on a task with different verbs. A response built to describe cannot satisfy a prompt that asks you to compare or evaluate, no matter how polished the paragraphs read. The fix is to re-derive the one-sentence reasoning question from the new prompt's own verbs and population words before any drafting begins, treating the previous week as method learned rather than template kept.

The second pitfall is source hoarding: downloading a folder of promising files and citing almost none of them. Collection feels like progress while doing no analytical work, and the unread pile becomes guilt by Friday. The fix is a working cap: for each source collected, write its one-line use note immediately, and discard whatever earns no note.

The third pitfall is posting discussion replies at the last permitted hour, which produces agreement instead of reasoning and risks missing the window entirely if anything technical goes wrong. The fix is to schedule replies as their own earlier block inside the response period, arriving with one course-material citation ready wherever the live instructions call for supported replies.

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