NURS 8720 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 Doctoral Seminar II, the durable class question is: What claim, question, method, evidence, or approval gate is this work advancing? 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

Keep problem, evidence, method, finding, limit, and implication aligned. Distinguish a course exercise from original research and never imply approval before the relevant reviewer grants it.

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 re-argument rather than editing

Revision at this stage is not a read-through. Start from the criterion-level ledger built across the term and pick the two rows that have cost the most points. For each, write the diagnosis in one sentence, then the smallest change that would move that row, then the exact place in the document where the change has to appear. A revision plan of four or five such entries accomplishes more than a full pass over the prose, because a full pass repairs whatever the eye happens to catch and leaves the structural faults untouched.

Then test whether the argument still holds. Read the claim column from the reverse outline and ask, for each claim, what evidence now supports it and whether anything found since has weakened it. If the evidence has moved, the honest revision changes the claim and says so, rather than defending the original with additional qualifiers. A draft that quietly retains a claim the evidence no longer supports is the failure mode that survives every proofreading pass, because proofreading never looks at claims.

Rewrite rather than patch wherever a section is failing. Inserting new sentences into a paragraph built around a different point produces prose that reads as though it is arguing with itself, and graders describe that as unclear or unfocused without always being able to say why. Take the point, the evidence, and the warrant, and write the paragraph again from those three items.

4. Use evidence deliberately

Build a traceable evidence table with purpose, design, population or setting, result, limitation, and the exact sentence each source can support.

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: verification and replacement

Take the reconciliation one level deeper than assembly required. For every quotation and every paraphrase that carries weight, open the original and confirm the wording, the finding, and the context the author gave it. Paraphrases drift most in passages that have been revised several times, and the drift reliably moves toward what the writer wants the source to say. Checking against the original is the only reliable correction, and it is quick when the evidence table already records where each item came from.

Replace what does not hold. A source that turns out to be a secondary description, an older version of a superseded document, or a study whose population sits further from the target than the draft implies should be swapped rather than defended with extra qualifiers. Record the replacement in the evidence table with a short note on why it was made, because that note is the beginning of the answer if the choice is ever questioned by a reader or in a later course.

Finish with a date and rule check. Confirm that any recency requirement in the live instructions is met, that older sources appear only where they are genuinely foundational, and that the reference list contains no entry left behind by a section that was cut during revision.

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

Audit alignment across the problem, question, method, analysis, conclusion, rubric, and current institutional milestone.

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 a checklist against the draft

The registered classroom rubric decides, and in a revision Week it should be read as a checklist against the actual document rather than as a plan for one. Take a row at a time, find the passage in the draft that satisfies it, and write the page or section beside the row. Any row without a location is a gap, and gaps found this way are specific enough to close in a single sitting, which is exactly what a revision Week has time for.

Where a row is satisfied only partly, write what the next level's language would require and compare it against what is on the page. The difference is nearly always one of three things: something present but not explained, something explained but not supported, or something supported in one place and left unsupported in the others. Each has a different repair, and diagnosing which one applies takes less time than a general rewrite of the section.

Do not convert the rubric into headings. Copying criterion names as section titles produces a document organized for the grading grid rather than for the argument, and it tends to leave the connective reasoning unwritten because each heading looks answered on its own. Keep the argument's structure and let each row be satisfied inside 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 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.

Three Week 10 pitfalls and the fix for each

First pitfall: revising only what was commented on. Instructor comments are samples rather than an exhaustive list, and a note on an early page usually describes a habit that recurs several times later in the same document. The fix is to treat every comment as a category rather than a location, search the whole draft for other instances, and mark the comment resolved only when the pattern has been addressed everywhere it appears.

Second pitfall: new material without new evidence. Revision adds paragraphs to close a gap, and the additions arrive uncited because the reading was finished Weeks ago and reopening it feels like a detour. The fix is to route every added claim through the evidence table exactly as the original claims were routed, writing the use sentence before the paragraph rather than after it.

Third pitfall: version confusion. Several files with similar names exist, feedback was applied to one and formatting to another, and the wrong file is the one that gets uploaded. The fix is a single working file with dated copies kept in an archive folder, plus the habit of opening the exact file to be submitted and reading its first and last pages before it goes anywhere.

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