NURS 6800 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 Pediatric Development and Behavior, 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.

Worked reasoning: a repeatable pass for a developmental claim

Week 2 is where method stops being improvised. Build one sequence and run every developmental or behavioral claim through it in the same order. Name the domain or behavior at issue in the prompt's own terms. Bound the claim to the age range or stage the activity supplies. State where the observation would come from, whether caregiver report, direct observation, or a standardized measure, since each carries a different strength and a different blind spot. State the interpretation in a full sentence. Then state what would change that interpretation.

Running the same five moves twice in one Week does two useful things. It makes the reasoning legible to a reader working quickly against rows, and it converts a vague sense that something is missing into a specific missing move. If the third step keeps coming out empty, the gap is in sourcing rather than in writing. If the fifth step keeps coming out empty, the work is claiming more certainty than the material supports. The live rubric decides how much of this sequence has to appear on the page; the sequence itself is a drafting tool, not a template to submit.

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.

Reading the rubric row by row: turning criteria into a weekly checklist

In Week 1 the rubric was a document to read. From Week 2 forward it should become a checklist that regenerates in the same shape every Week. Take the live rubric, list its rows in descending order of weight, and give each row two lines in the working file: what the row asks for in plain words, and the sentence or section that will satisfy it. Rows carrying the heaviest weight get drafted first, whatever order they occupy on the page.

Keep the checklist honest by marking a row as unmet until something specific can be pointed at. A row marked complete with nothing beside it is the most common source of quiet point loss. When a criterion appears to repeat from the previous Week, do not assume its wording repeated too, because criteria are edited between activities and level descriptions shift. Rebuild the checklist from the rubric attached to the current activity in the registered classroom every single time.

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.

Standing sources: a shelf you can reuse without recycling

A cadence needs a source routine rather than a fresh scramble each Week. Write down the search strings that worked, the databases and professional bodies that produced usable material, and the filters applied for date range and study type. Keep a standing entry for every source that earned its place: full citation, design or issuing authority, the population and setting studied, the finding, and the limitation. That shelf is the part of the work that carries across the quarter.

What must not carry across is language. One source can appear in three different Weeks and support three different claims, but each appearance requires new reasoning written for the current prompt, and previously submitted sentences are not available for reuse. In this subject, watch the population field hardest: a finding drawn from one age band or one setting does not transfer silently to another, and the sentence citing it has to say so. Assigned readings remain first whenever the live activity requires them.

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 building the Week around the final due date. Discussion work usually carries an internal deadline for the initial contribution and a separate window for responses, so a plan aimed only at the end of the Week arrives too late to satisfy either. The fix is to schedule backward from the earliest deadline inside the activity, not the latest.

The second is copying last Week's structure into a differently scored prompt. Reusing a shape that worked feels efficient and quietly drops the rows the new rubric added. The fix is to rebuild the outline from the current rubric checklist first, and only then to notice which parts happen to resemble last Week.

The third is a reference list that grows faster than the use notes. Sources collected without a one-line note about the claim they support turn into padding under deadline pressure. The fix is a hard rule: no citation enters the draft until its use note exists, and any source without one stays in the log where it can do no damage.

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