NURS 8705 Week 9 planning manual

1. Capture the live Week 9

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: assembling parts written Weeks apart

Assembly is a reasoning task, not a formatting one. Sections written in different Weeks carry different vocabulary, different scope, and sometimes different claims. Read the assembled draft once for a single purpose: whether the same terms mean the same thing throughout. Build a short term sheet with the definition you are using for each key construct, then correct every deviation to match. Read again for claim consistency, checking that the conclusion asserts exactly what the analysis supports, no more and no less, and that the opening promises exactly what the body delivers. Introductions written first are the most common source of broken promises, so rewrite the opening last. Transitions come after both passes, because a transition between two misaligned sections only disguises the seam. What must be assembled, and in what form, is set by the live instructions.

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: a dependency map for the final stretch

The closing Weeks concentrate obligations that depend on other people and systems, and those cannot be compressed. Build a map with one row per remaining obligation and four columns: what it requires, who or what controls it, the latest date it can start and still finish, and what it blocks. Rows controlled by others, such as group contributions, scheduled sessions, approvals, technical access, or feedback you have requested, get contacted first and confirmed in writing. Rows that block other rows get scheduled ahead of the rows they block, even when they are smaller. Then find the longest chain in the map, because that chain, not the largest single item, determines whether the close is comfortable. Anything already late gets its own conversation with the instructor this Week. Deadlines, late-work rules, and submission routes come from your registered classroom.

Reading the rubric row by row across the remaining activities

With several activities left, read the rubrics together rather than one at a time. Lay the remaining rows in a single sheet and mark which are unique to one activity and which recur. Recurring rows are where practice pays twice, so a correction made now returns on every remaining submission. Mark also which rows carry the heaviest weight in what remains, since attention should follow weight rather than order of appearance. Then identify rows that depend on work not yet started, because those are schedule items disguised as writing items. Keep each activity's own rubric authoritative for its own submission; the combined sheet is a planning tool only. Version differences between activities are common, so check the live rubric again before you submit against it.

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.

Consolidating the evidence base for a culminating piece

Assembly is the moment to build one evidence file rather than several. Merge the tables from earlier Weeks, remove duplicates, and mark each row with the section it now serves. Then check coverage rather than quantity: does every major claim in the assembled draft have at least one row behind it, and does any claim rest on a source that has since been superseded or that you now judge weak? Fill gaps by searching for the specific unsupported claim rather than for the topic. Verify every citation against the actual record at this stage, since reference errors accumulate quietly across a quarter and are cheap to fix now and expensive to explain later. Confirm that the reference list and the in-text citations match in both directions. Citation style and formatting requirements are set by the 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 9 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.

Three Week 9 pitfalls and the fix for each

The first pitfall is assembling early sections without re-reading them, so an outdated framing survives into the final piece. The fix is one full read of the assembled draft before any new writing, listing contradictions as you go. The second pitfall is leaving an institutional dependency for the last Week because it is not itself graded. The fix is the dependency map, with confirmations obtained in writing rather than assumed. The third pitfall is discovering a missing requirement late because the instructions were read once in Week 1. The fix is a fresh literal read of the current instructions this Week, treating every sentence containing a verb as a requirement to be checked off. Announcements can modify requirements mid-quarter, so read those alongside the instructions.

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 10. 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 9, 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 10.

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 9 activities. The registered syllabus, classroom, rubric, announcements, instructor directions, and official policies remain controlling.

Week 9 questions