NRNP 6549 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 Advanced Primary Care of Adolescents and 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.

Diagnosing before revising

Revision without diagnosis is redecorating. The reconciliation Week starts by merging every piece of accumulated feedback into one defect ledger and classifying each entry: task misreading, a broken reasoning chain, evidence that did not fit its claim, imprecision about ages and quantities, format and mechanics, or process failures such as timing. Classification changes behavior because each class has its own repair. A task-reading defect is repaired by re-deriving the one-sentence task statement before every remaining draft. A reasoning defect is repaired with the because test applied line by line. An evidence defect is repaired at the bench and at the point of citation. A precision defect is repaired with dedicated exactness passes.

Suppose the ledger shows a comment pattern such as responses reading as general rather than specific to the population. The revision rule that falls out is concrete: name the age band and its implications in every major claim, and apply the rule to every remaining piece of work, not just the submission that drew the comment. That is the real distinction of this stage: revising the habit rather than the artifact, so the correction compounds across everything still to be submitted in the closing Weeks.

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.

Verifying sources after the drafts have moved

Late revision quietly breaks citation integrity, so the reconciliation Week includes a verification pass over the evidence layer as it now stands. Reread each citation in its current sentence and confirm the source still supports the claim the sentence now makes, because moved and edited sentences drift away from the notes that once matched them. Remove orphan references that no longer correspond to anything in the text, and add entries for anything cited in revision haste. Recheck the aging of everything versioned: guidance that revises may have done so since the early Weeks, and a final submission citing a superseded edition reads as a currency failure in exactly the subject where currency matters most.

Then strengthen selectively rather than broadly: identify the two or three claims that carry the most weight in the remaining work and make sure each rests on the best available, population-matched support, upgrading a stretched or secondary citation where a stronger one exists. Leave working citations alone; a verification pass improves fit, it does not churn the list. The classroom's citation style and source rules remain the standard the pass is run against.

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 as reconciliation

The reconciliation version of the rubric read lines up two documents: every returned rubric from the quarter and the rubric of whatever remains. Go through the remaining rubric row by row, and for each row search the returned set for the places the same criterion cost points before. Where a match exists, write a one-line fix into the revision plan in behavioral terms: what the draft will visibly do differently so this row cannot repeat its deduction. Where a remaining row is new, with no history, plan it from its top-band language instead, underlining the words that separate the highest band from the next. The output is a short, concrete reconciliation sheet: each remaining row, its history, and its planned proof. This turns a pile of feedback into targeted work and replaces the vague resolve to do better with named, checkable changes. It also surfaces the rows that were never a problem, which get deliberately left alone, protecting working systems from late-quarter meddling. The live rubric for each remaining activity is the reconciliation baseline, and rereading it after the revisions are made, one final row-by-row confirmation, closes the loop the Week is named for.

Week 10 pitfalls and the fix for each

Revision-stage failures waste the quarter's best information. The first is rereading the work start to finish and fixing whatever surfaces, which finds surface problems and misses systemic ones because attention goes where the prose snags, not where the points went. The fix is defect-class revision: one targeted pass per diagnosed class from the ledger, each with its own narrow checklist.

The second is treating instructor comments as stylistic opinion to be weathered rather than scoring information to be used. The fix is mapping every comment to the rubric row it affects; once a comment has a row and a point value, it stops being a matter of taste and becomes an instruction.

The third is late-edit breakage: revising confidently into sections that already scored well and introducing new errors where none existed. The fix is a freeze rule, changing only what the diagnosis named, plus a final integrity read of any section a late edit touched, confirming that references, numbering, and cross-mentions still agree. The stage rewards restraint as much as effort: the best reconciliation changes exactly what the evidence says to change and nothing else.

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.

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