NURS 6002 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 Perspectives on Graduate Study for Advanced Nursing Practice, the durable class question is: What evidence supports the judgment, what alternatives matter, and what remains outside the student's authority? 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

Move from cue to mechanism or standard, then to prioritized judgment, action, monitoring, and escalation. Use only de-identified authorized context.

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.

Worked reasoning: revision as diagnosis, not decoration

Week 10 revision starts from the accumulated record, and its logic runs opposite to proofreading. Proofreading asks what looks wrong on this page; revision asks what the whole quarter's feedback says goes wrong repeatedly, then hunts the current draft for exactly that. Work it in order. Reread the criterion-level ledger built across the returned work and name the single most expensive recurring weakness in one concrete sentence, such as: claims are stated but the connecting logic to the cited evidence is left implicit. Translate the weakness into a search procedure the student can run on the live draft: for that example, find every citation and check whether the sentence before or after it states why the source matters here. Repair only what the search finds, sentence by sentence, and log each repair. Then run one confirmation pass to be sure the repairs did not introduce new problems in structure or flow. This narrow loop feels less thorough than rewriting everything, and that is its virtue: in the last stretch of a quarter, effort spent on diagnosed weaknesses moves scored outcomes, while general rewriting mostly moves sentences. The perspectives this course teaches include this one: professional improvement is targeted or it is theater.

Reading the rubric row by row

By Week 10 the returned rubrics are a dataset, and the row-by-row read becomes longitudinal. For each criterion that has appeared across multiple activities, line up its scores in order and read the trajectory: rising, flat, or sawtooth. A rising row confirms the fix applied after the midpoint audit is working; leave it alone. A flat row below top level means the attempted fix missed the actual gap, so reread the row's level language against the most recent returned comment and form a different hypothesis about what the grader is not seeing. A sawtooth row, alternating strong and weak, usually tracks process rather than skill: the row scores well when time was protected and badly when it was not, which makes the repair a calendar repair, not a writing repair. Apply the same trajectory reading to the current activity's rubric before submission, asking of each row: which trajectory is this row on, and does the draft in hand continue it or break it? That question converts the rubric from a grading instrument into the steering instrument it was always meant to be.

4. Use evidence deliberately

Prefer current authoritative clinical guidance and peer-reviewed evidence appropriate to the question; distinguish guideline recommendations from patient-specific facts.

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: repairing the citation layer

Revision Week extends to the reference apparatus, where quiet damage accumulates over a quarter. Sweep the current draft's citation layer with four repairs in mind. Replace the placeholder: any citation the student marked to fix later, an incomplete entry or a half-remembered source, gets completed now from the original, not from memory. Retire the weak link: if any claim still leans on a source below the scholarly tier for this subject, peer-reviewed literature, current professional-body guidance, or assigned texts, find the graduate-weight source that carries the claim properly or soften the claim to what the available evidence supports. Reconcile the lists: every in-text citation must appear in the reference list and every reference-list entry must appear in the text, a mechanical check that catches the additions and deletions revision itself creates. Refresh the dated: any guidance document cited early in the quarter gets one final currency check before the close, since a revision cycle elsewhere may have overtaken it. None of these repairs requires new reading; all of them require the honesty to open the reference list and look, which is why they are so often skipped and so cheaply scored 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 safety, scope, differential logic, contraindications, documentation, confidentiality, and every student-performed clinical requirement.

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: revising the surface, where a session of font, spacing, and comma work substitutes for engagement with the diagnosed weakness. The fix is to sequence ruthlessly: the ledger's named weakness gets repaired first, the confirmation pass second, and formatting last, because format work done first has a way of consuming the whole session and calling itself revision.

Pitfall: rewriting the draft's strongest sections again, since improving good work is more comfortable than confronting weak work. The fix is to rank sections by their weakest rubric row rather than by personal attachment, and to forbid touching any section ranked in the top half until every section in the bottom half has received its targeted repair.

Pitfall: treating revision as an invitation to expand, so the repaired draft grows past the assignment's stated length and dilutes its own best paragraphs. The fix is to hold length constant during revision: for roughly every sentence added in repair, retire a sentence that was doing the least work, which forces each addition to out-argue an incumbent.

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