NURS 8750 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 V, 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 for integration without recycling

Integration is a reasoning move, not a retrieval move. Build a concept ledger with one row per idea the course has already established, and for each row record the idea in your own words, the place it first became useful, and what it lets you do that you could not do before. Then take the current activity and ask, idea by idea, whether it changes the claim, changes the method, changes what counts as evidence, or changes nothing at all. Most rows will change nothing, and marking them so is part of the work.

The rows that do change something get a written sentence explaining the change, and that sentence is new prose about the current problem. This is the line between integration and recycling. Reusing a lesson is expected; reusing submitted language is not, and a later prompt asks for new reasoning, new evidence, and new authorship even when the underlying concept returns. Where an earlier framework genuinely applies, name it, state which part of it applies, and show it doing work inside this week's argument rather than listing it among things you have studied.

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.

Re-using a source for a new claim

A source already sitting in the reference list is not automatically available for a new claim. Open the entry, read the permitted sentence, and ask whether the new claim is that same sentence in different words or a different sentence entirely. If it is different, go back to the source itself and read the section that would support it. Citing from memory of an earlier reading is where quiet misattribution starts, and it survives every proofread because the citation looks correct.

Add a second permitted sentence to the entry when the source genuinely supports one, and note which activity each sentence was written for. That turns the intake sheet into a record of how the evidence base grew rather than a static list. Where a foundational work sits beside current evidence, state the division of labor in the prose: the older source establishes the frame or the definition, the current source establishes what is known now. That single sentence often satisfies a synthesis expectation that a longer paragraph of parallel citations does not.

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.

Reading the rubric row by row

Integration rows are usually worded almost exactly like the analysis rows from earlier weeks, which is why they get answered the same way and land differently. Read each row and ask what it wants connected: two concepts, a concept and a case, evidence and a decision, or this activity and the course question. Write the connection type in the margin, then find the sentence in your draft that actually performs it.

A connection is performed by a sentence that would break if either side were removed. If a paragraph mentions an earlier concept and would read identically with the mention deleted, no connection has been made. Check every claimed link that way. Watch also for rows that quietly require breadth, such as language about the course as a whole or about multiple perspectives, and make sure the draft covers the range rather than going deep in a single place. Row wording shifts between sections and terms, so your classroom rubric decides what breadth and connection mean in your class.

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 Week 6 pitfalls and the fix for each

The first pitfall is reusing submitted language from an earlier activity in this same course. It feels efficient and it is a real risk to the integrity of the work; the concept may return, but the response has to be newly reasoned and newly written. The fix is to work from the concept ledger, which holds ideas rather than sentences, and to draft the paragraph before opening anything previously submitted.

The second pitfall is name-dropping an earlier framework. A framework named in one sentence and abandoned in the next adds length without adding integration. The fix is the deletion test: remove the name and see whether the paragraph changes. If it does not, either put the framework to work or take it out.

The third pitfall is a reference list that has not moved since early in the term. Integration weeks tend to look backward, and the evidence base stops growing exactly when the argument is becoming more demanding. The fix is a small quota of new retrieval this week, aimed at the structural gap the argument has developed rather than at the topic in general.

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