NURS 6800 Week 3 planning manual

1. Capture the live Week 3

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: making a developmental inference visible

By Week 3 an accurate definition is the floor rather than the answer. The scoreable move is the chain between definition and conclusion, written where a reader can follow it. For a developmental claim that chain has four visible links: the observation or description the prompt supplies, the expected pattern for the stage it names, the comparison between them, and the interpretation that follows. A fifth link, what would revise the interpretation, is what separates reasoning from assertion.

For behavior, the same discipline means writing in observable terms before writing in interpretive ones. Describe what occurs, how often, for how long, at what intensity, and in which settings, and keep that description separate from what it is taken to mean. Then say what preceded it and what followed it, because context carries much of the explanatory work in this subject. Keeping interpretation in its own sentence lets description and inference be scored separately, which is usually how the rows are built. The live rubric decides how much of the chain has to be on the page.

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: where the reasoning points sit

Rubrics for reasoning-heavy Weeks separate rows that reward accurate content from rows that reward analysis, and the two are scored independently. Read each row for its verb. Rows built on identify, define, or summarize are satisfied by correct content. Rows built on analyze, compare, differentiate, justify, or evaluate are satisfied only by a visible operation, and a paragraph that is factually flawless can still score low against them.

Mark every analysis row in the checklist and write beside it the single sentence in the draft where that operation happens. If no such sentence exists, the row is unmet no matter how long the section runs. Signpost those sentences so they are findable on a fast read, using plain connective language rather than decorative headings. Wording and level descriptions differ by section and term, so the row that governs is always the one attached to the live activity in the registered classroom.

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.

Sources that carry an argument, not just a definition

A Week that asks for visible reasoning needs sources chosen for what their design can support, not only for topical match. Current professional guidance can anchor a recommendation. A systematic review can support a general pattern. A single cohort or cross-sectional study can support a narrower claim about the population it studied. A measurement or instrument study speaks to how a tool behaves, not to how common something is. Matching source type to the strength of the claim is itself part of the reasoning being scored.

Work each source in by writing the claim sentence first, attaching the citation second, then reading the sentence back and asking whether the cited work actually tested that. Where a source only partly supports the point, say so inside the sentence rather than leaving the gap for the reader to find. Assigned readings come first when the live instructions require them, and older foundational developmental work can still be appropriate when it is used for a concept rather than for a current practice claim.

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 3 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 3 pitfalls and the fix for each

The first pitfall is definition stacking, where paragraph after paragraph explains terms and the analysis never arrives. It happens because defining is comfortable and comparing is not. The fix is to cap definitional material at the shortest form the prompt allows and to draft the comparison or application paragraph before anything else.

The second is asserting a conclusion the cited source never tested. An association gets written as a cause, a finding from one stage gets stretched to another, and the citation makes the whole sentence look supported. The fix is a single audit pass in which each cited sentence is checked against the use note for that source, with the claim narrowed until the two agree.

The third is burying a good inference inside a long paragraph with no signal. The reasoning exists, the reader does not find it, and the analysis row scores as though it were absent. The fix is to give the inference its own sentence at the start or the end of the paragraph and to name the operation being performed in it.

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 4. 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 3, 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 4.

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 3 activities. The registered syllabus, classroom, rubric, announcements, instructor directions, and official policies remain controlling.

Week 3 questions