NRNP 6811 Week 10 planning manual

1. Capture the live Week 10

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.

Repairing causes instead of symptoms

Revision at this stage is targeted repair, not general polishing. Rank the defects your feedback ledger shows by two measures, cost in points and frequency of recurrence, and spend the Week where the two rankings overlap. Classify each defect honestly before touching it: a reasoning defect, an evidence defect, a task-interpretation defect, or a mechanical defect, because each class has a different repair and applying the wrong one wastes the little time this stage of the quarter has left.

Repair at the level of cause. A thin middle is not fixed by smoother sentences; it is fixed by re-deriving the chain from context through principle to implication and writing the links that were missing. A mismatched source is not fixed by a better signal phrase; it is fixed by finding support whose population and ages actually fit the claim about children being made. Where a repair matters, verify it on parallel practice material first: rework a similar problem from the course materials, explain the corrected reasoning aloud in your own words, and only then apply the fix to live work. Sentence polish comes last, after the causes are gone, and takes a fraction of the time once it has nothing to hide.

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.

Source work during revision

Revision is when the reference layer gets honest. Replace the weakest sources instead of defending them: anything outdated where currency matters, anything whose studied population never matched the claim it supports, anything that only ever decorated a sentence. Update entries where newer statements of the same guidance exist, and note each change in the ledger so the correction propagates into any remaining work instead of resurfacing as the same penalty twice.

Then sweep for orphans in both directions: claims whose supporting citation vanished during rewriting, and references whose claims no longer exist in the revised text. Reconcile in-text citations against the reference list line by line, and re-read each revised sentence against what its source actually found, because rewriting drifts meaning in small ways that only a verification read catches. A revised draft with an unrevised evidence layer is half repaired, and the unrepaired half is the one evidence rows score.

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 10 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

Make the row-by-row self-score the final gate of every revision this Week. Take the live rubric of the current activity and score your own revised draft against each row in writing, naming the exact sentences that satisfy it. Score the way your returned feedback suggests your section scores, which the ledger now documents in detail, not the way hope scores. Any row without a nameable sentence goes back to drafting ahead of any further polish, because presence beats shine in every rubric this method has ever been checked against. Rows you have historically lost get scored twice: once by you, and once against the standing instructions you wrote at midcourse. The wording of this activity's rubric, in this term, remains the only standard; the self-score simply refuses to let the draft leave until every row has an answer you can point at.

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 11. 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 10, 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 11.

Week 10 pitfalls and their fixes

The first pitfall is polishing prose while a rubric row sits unaddressed. Fluency improves, the reading experience improves, and the score does not, because rows are earned by presence first. The fix is order: rows first, sentences second, always, with the self-score deciding when polishing is allowed to begin.

The second pitfall is version chaos. Heavy revision multiplies files until the wrong one gets submitted, an error no amount of revision skill undoes after the fact. The fix is one working copy, dated snapshot filenames when a milestone is worth keeping, and a final check that the file being uploaded is the file that was finished.

The third pitfall is revising into new scope: adding sections, angles, or ambitions the prompt never requested, which spends scarce late-quarter hours and can push the work off task entirely. The fix is to test every substantive addition against the live task list and rubric; if nothing asked for it, it goes into your notes for the future, not into the submission.

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

Week 10 questions