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

Revision as diagnosis, not decoration

Week 10's stage is repair, and repair starts with a diagnosis rather than a thesaurus. Open the term's feedback ledger and name the recurring weakness in one sentence before touching any draft. Then revise in ordered passes. First, task fidelity: every part of the live prompt answered, in the required structure. Second, reasoning: chains visible, and the developmental or family-context modifier present wherever the prompt's stated context calls for it. Third, evidence: claims matched to sources, applicability stated, nothing cited that is not doing work. Only then mechanics: format, citations, length, file rules.

The strongest late-course tool is the reverse outline. Reduce each paragraph of the draft to one sentence describing what it actually does, then set that outline against the rubric and the prompt. Gaps and detours become obvious in outline form while they hide inside polished prose. In this subject, the highest-value late fix is usually specificity: replacing generic care language with the age-band and family-context reasoning the stated details support. Keep dated versions of every file so a late edit can never silently destroy an earlier correct answer.

Reading the rubric row by row

Before any revised work goes back in, score it row by row in the grader's reading order, and be hostile about it. For each row, decide which column the draft currently earns and write down the sentence that proves it. Where the proof sentence sits buried in the middle of a paragraph, move it to where the grader will look first: the section the instructions name, the topic sentence, the labeled heading. Graders read with the rubric beside them, and revision means placing answers on that path.

Then bring in the term's history. The rows that cost points in returned rubrics deserve a second, deliberately suspicious read now, because self-review has already proven generous exactly there. If self-scoring reveals a row that cannot honestly be placed in the top column, that row defines the remaining revision time. This is also the last comfortable week to ask the instructor about any rubric language that is still ambiguous, and the answer that comes back controls the work.

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.

Repairing citations so revision does not break them

Revision detaches citations from claims: sentences move, merge, and split, and the source that supported the original sentence stays behind. So Week 10's source work is verification. Walk every claim-source pairing in the revised draft and confirm the source still says what the moved or rewritten sentence now claims. Re-check each quotation against the original for exact wording. If revision created a new claim, source it or soften it; if it cut a claim, retire the orphaned entry from the reference list.

Finish the records while the volume is manageable: complete every reference entry to the current style requirement, confirm edition and version years, and reconcile the list against the text in both directions. Never leave a sentence citing a source it no longer represents; that mismatch reads as carelessness at best and misrepresentation at worst, and one verification pass prevents it entirely. A revised draft is only stronger than the original if its evidence still stands exactly where the new sentences need it.

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.

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

Pitfall one: rewording instead of re-reasoning. The revision changes vocabulary while the same flawed chain runs underneath. The fix is the reverse outline first: if a paragraph's one-sentence summary does not answer a rubric row or prompt part, rebuild the paragraph from its reasoning up, and only then improve its sentences.

Pitfall two: late-edit damage. Rushed changes introduce new errors into work that was previously correct: a dropped citation, a broken heading, a contradicted earlier sentence. The fix is version control plus a final in-context read of every edited paragraph, checking the paragraph before and after it as well.

Pitfall three: treating instructor comments as one-off corrections. Each comment gets patched where it was made and nowhere else. The fix is the ledger habit: classify the comments by category, then sweep the entire draft for that category, because a flagged weakness almost never occurred only once.

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