NURS 8705 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, 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.

Worked reasoning: revision that changes structure, not just sentences

Revision at this stage should be triaged by cost and effect. Level one is structural: does the response answer the question asked, in an order a reader can follow, with each section doing distinct work? Level two is evidentiary: is every claim supported by a source that can support it, and is every source doing analytical work? Level three is sentence level, and level four is mechanics. Work strictly downward, because a sentence polished inside a section that will be cut is wasted effort, and most drafts arrive at Week 10 with a level one problem hiding underneath level three anxiety. Diagnose by reading only the first sentence of every paragraph in order. If that sequence does not tell a coherent story, the problem is structural and no amount of word choice will repair it. What the response must contain is decided by the live prompt and rubric.

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: reconciling feedback that appears to conflict

Late in a quarter you may hold comments that pull in different directions, for example to add depth and to shorten. These are usually not in conflict once translated. Depth normally means more reasoning per claim; shortening normally means fewer claims. Together they say make fewer points and support each one properly. Translate every comment into a structural instruction of that kind before acting on any of it, and write the translation down. Where two comments genuinely conflict, the more recent one and the one attached to the higher-weighted rubric row take precedence, and if the conflict matters, ask the instructor rather than guessing. Record what you changed and why in the feedback ledger, because the reconciliation itself is a lesson worth keeping for the next course. The instructor's direction governs wherever it differs from general guidance.

Reading the rubric row by row with the feedback ledger open

This is the read where the two records finally meet. Put the current rubric on one side and the accumulated criterion-level feedback on the other, and for each row note the level you have earned historically and the specific comment that explains it. Revise in order of the largest gap between weight and past performance, which is rarely the order the rubric lists. For each targeted row, write the observable test that would prove the row is now satisfied, then check the revised draft against that test rather than against a general sense of improvement. Rows you have consistently satisfied need only a verification pass. Nothing here predicts an outcome: the classroom rubric and the instructor decide what the work earns.

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.

Auditing every source before the final submissions

Reconciliation includes the sources. Open each reference and verify author, year, title, and outlet against the record, then confirm the in-text claim still matches what the source says, since claims drift during revision and a citation attached to a rewritten sentence may no longer fit. Remove sources that survived only because they were cited early. Check that any date rule the activities state is still met after replacements. Confirm that every source in the list appears in the text and every source in the text appears in the list. If a claim now rests on a source you would struggle to defend if asked, either strengthen it with better evidence or soften the claim to what the source supports. Style and source requirements come from the live activity.

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.

Two Week 10 pitfalls and the fix for each

The first pitfall is revising only where feedback was written, treating comments as an exhaustive list rather than as samples of a pattern. Instructors mark examples, not every instance. The fix is to read each comment as a category and search the whole draft for other cases of it. The second pitfall is late scope creep, adding a new idea or a new source in the final revision without re-checking alignment, which can break a chain that was previously sound. The fix is to run the alignment read once more after any late addition, and to refuse additions that cannot be integrated properly in the time available. A smaller, coherent response is more defensible than a larger one with a broken link. Submission rules and any resubmission policy come from your classroom.

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