NURS 8730 Week 6 planning manual

1. Capture the live Week 6

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 III, 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: connecting earlier Weeks without repeating them

Integration means using a prior concept as an instrument on new material, not restating it. The test is blunt: if a passage could be lifted out of this Week and dropped back into the Week it came from without loss, it is repetition. Rewrite it so the earlier idea performs work here, by applying it to the current problem, by using it to explain a result that could not previously be explained, or by showing where it stops applying. The third move is the strongest available in a seminar, because a boundary condition demonstrates command of a concept in a way that a summary never does.

Build the connection in one direction at a time. Take the current material as the subject and the earlier concept as the lens, write the paragraph, then reverse the pass and ask whether the current material changes anything about how the earlier concept should now be understood. The reverse pass often produces the most original sentence in the draft. Preserve the lesson and the method from earlier work rather than the language, since previously submitted wording does not belong in a new response and a returning concept still requires new reasoning, new evidence, and fresh authorship.

Reading the rubric row by row for integration language

Look for rows whose wording reaches outside the current activity: synthesize, integrate, connect, build on, apply course concepts. These rows are usually scored on the presence of a visible link rather than on how many concepts appear. One well-developed connection, stated explicitly and carried through a paragraph, satisfies such a row better than a list of terms.

For each integration row, decide in advance which earlier concept will be used and where the link sentence will sit, then keep that sentence explicit rather than implied, because a reader should not have to reconstruct a connection held only in the writer's head. Where a row combines integration with a second demand in one sentence, split it into two checkpoints so neither half is lost. The registered classroom rubric decides what these rows require, and only its current version counts.

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.

Working earlier sources back into new writing

Integration puts pressure on the source base, because earlier citations return in a new argumentative position. Before reusing a source, re-read its use note and confirm that it can support the new sentence and not merely the old one. A study that established prevalence in an early Week cannot silently become evidence of effectiveness later. Where the new role exceeds what the source licenses, find evidence that fits the role rather than stretching the familiar article.

Mix the vintage deliberately. Foundational work can carry a concept or a framework, while current primary research should carry claims about the present state of the evidence, subject to any recency rule the classroom sets. When the same source is cited twice for different purposes, make the purposes visible in the prose so the repetition reads as economy rather than as a thin base. Follow the citation style the classroom names, and confirm that every reused entry is still accurate after edits move text around.

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 6 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.

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 7. 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 6, 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 7.

Three integration pitfalls and the repair

The first pitfall is self-recycling. Reaching for an already written paragraph is tempting when a concept returns, and the course names that error directly. The repair is to close the old file, write the new passage from the note rather than from the prose, and treat any sentence that arrives fully formed as a signal to check its origin.

The second pitfall is the name-drop chain, where three or four earlier concepts appear in one sentence to signal breadth. The repair is a hard limit: one concept per paragraph, developed until it changes something about the current material, and no concept mentioned that is not used.

The third pitfall is integration that drifts away from the live prompt. A connection is only valuable when the current activity asks for it and the rubric can see it. The repair is to check each link against the prompt's own verbs before the paragraph is kept.

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

Week 6 questions