NURS 8720 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 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: building the spine before the sections

Assembly starts with one sentence, not with an outline. Write the spine: the single sentence the finished work exists to establish, containing both the claim and the basis for it. Then write, in order, the questions a skeptical reader would have to see answered before accepting that sentence. Those questions become the section order, and each section's job is to answer exactly one of them. Work assembled this way survives compression and reordering, because every part has a stated reason to exist and the reason is written down.

Then test each existing piece against the spine. Material written earlier in the course was drafted to answer earlier prompts and will not automatically serve the whole. For each piece, decide whether it answers one of the reader's questions, answers a question nobody asked, or answers one of them only partly. Keep, cut, or rebuild accordingly, and rebuild by rewriting rather than pasting: previously submitted language cannot be recycled, and it would not fit the new argument even if it could.

Map the remaining calendar against the assembly rather than against a page target. List every remaining activity, reply, dependency, approval, and submission step with its own lead time, then mark which ones cannot begin until another finishes. The critical path decides what gets drafted this Week. A section that is easy to write and blocks nothing is the wrong place to spend the Week's best hours.

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: reconciling the evidence base against the whole

Run a two-way reconciliation. Every in-text citation must have a reference entry, and every entry must be cited somewhere it performs actual work. Then run the harder pass: for each load-bearing claim in the spine, name the strongest source supporting it and ask whether that source is genuinely the strongest available or simply the one found first. Load-bearing claims deserve the best evidence in the table, and at this stage there is still time to move one into position or to search for a better one.

Check coverage across the assembled whole rather than section by section. A source can look well used inside one paragraph while quietly carrying three unrelated claims across the piece, which is over-reliance that only a whole-document pass reveals. Confirm too that no major section rests on a single document, and that current and foundational sources are each sitting where they belong rather than where they were first pasted.

Then verify the mechanics of the list while the argument is still settling: complete details, consistent style, retrievable identifiers where the style requires them, and nothing left over from a section that has since been cut. Reference reconciliation is far faster now than in the final Week, when attention is needed for the argument and the submission route.

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.

Reading the rubric row by row, on a rubric that scores the whole

The registered classroom rubric decides, and the rubric for a culminating activity usually differs in shape from a weekly one: more rows, uneven weights, and rows that score the document as a whole rather than any single part. Read the weights first and sort the rows by points at risk. Then map each row onto a section of the spine and flag any row that has no home, because that is a requirement the current outline is ignoring and the cheapest moment to fix it is before assembly begins.

For rows that score the whole, such as coherence, alignment, organization, or scholarly voice, plan a dedicated pass instead of hoping they emerge from good sections. A row describing the document as a unit cannot be satisfied by any one paragraph, and it is often the row that separates a set of competent sections from a competent piece of work.

Note the mechanical rows and every submission requirement attached to them: file format, file naming, length, template use, and the exact place the artifact must be delivered. These are scored or penalized independently of the argument, and the due date is the worst possible time to discover one of them for the first time.

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.

Three Week 9 pitfalls and the fix for each

First pitfall: assembling before the argument settles. Sections get joined while the central claim is still moving, so every subsequent change ripples through a formatted document and each ripple costs an hour. The fix is the spine sentence: stabilize it, check it against the rubric and any guidance the instructor has actually provided, and only then begin joining sections together.

Second pitfall: leaving dependencies for the final Weeks. Approvals, group contributions, and technical steps get postponed because writing feels more urgent and more measurable, and then the calendar has no slack left when one of them takes longer than expected. The fix is the critical path list built this Week, with the longest lead item started immediately rather than scheduled.

Third pitfall: terminology drift across sections. The central term is defined one way in an early section and used differently later, because the two were written Weeks apart and neither was checked against the other. The fix is a terms sheet: one page listing each key term, its definition, and its source, applied in a single search pass across the assembled draft before anything else is edited.

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