NURS 4300 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 BSN Capstone, 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: one claim served by the whole course

Integration means the current Week's work visibly uses what earlier Weeks built, without recycling a word of what was submitted. The reasoning move is architectural. First, restate the current problem in one sentence. Second, list the course assets that bear on it: the analysis habits from the early Weeks, the evidence-to-action discipline from the middle ones, the sources already tabled, the feedback lessons sitting in the ledger. Third, design the argument so each asset does named work. For illustration only, a draft might open by framing the problem, deploy the analysis skeleton to show why the problem persists, then use the evidence-to-action unit to justify a response, with the through-line stated in a sentence the reader cannot miss. What transfers is method and understanding; the language is authored fresh, because a later prompt requires new reasoning even when a concept returns. Integration done honestly also surfaces disagreement: where an earlier Week's simple version of a concept meets this Week's complication, name the tension and resolve it with evidence instead of quietly using whichever version is convenient.

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.

Reading the rubric row by row

Integration Weeks often carry rows whose verbs are connect, integrate, synthesize, or incorporate, and those rows cannot score a link the draft only implies. Read each such row in the current rubric and ask what visible artifact would satisfy it: usually a sentence that names the connection outright, stating that this concept from earlier material explains this feature of the current problem, placed where the row's position in the rubric suggests the grader will look for it. Then audit the draft's topic sentences: in synthesis work they should carry ideas, not source names and not Week numbers, and each should be a claim the following sentences bring material together to support. Watch for rows that quietly demand breadth, language like multiple concepts or across the course, and meet the stated breadth exactly rather than betting that one deep connection covers it. Where a row's scope is unclear, the classroom is the authority: ask, record the answer beside the row, and draft to the recorded answer rather than to a private reading of an ambiguous phrase.

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.

Synthesizing sources instead of listing them

Integration shows in how paragraphs treat sources. A paragraph organized by source, one study per stretch of prose, each summarized in turn, is a reading log. A paragraph organized by idea opens with a claim, then brings two or more sources into contact with it: one supplies the finding, another extends it, qualifies it, or contradicts it, and the student's sentences do the reconciling. Apply a two-source test to every substantive paragraph in this Week's draft: if no paragraph puts two sources in conversation, the synthesis is happening in the student's head but not on the page where rows can score it. Handle disagreement between sources explicitly: name the criteria, design strength, population fit, and recency, and let the criteria pick the stronger finding or justify holding both with a boundary drawn between them. Pulling forward sources tabled in earlier Weeks is good practice and fair use of the course's own assets; pulling forward previously submitted sentences about them is not, so re-enter old sources through new claims.

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.

Week 6 pitfalls and the fix for each

Pitfall one: recycling submitted language. Pasting paragraphs from an earlier Week into an integrative draft creates an originality problem inside the same course and skips the new reasoning the prompt exists to elicit. The fix is a strict carry rule: concepts, sources, and lessons transfer; sentences do not. Reopen the concept and write it fresh against the current problem.

Pitfall two: serial summary posing as synthesis. The draft walks through materials one by one and calls the walk-through integration. The fix is the idea-first rewrite: reorganize so every topic sentence is a claim, merge source material under the claims it serves, and delete whatever no claim needs.

Pitfall three: treating the Week as a detached prompt. Answering only the local question, as if the course had no arc, produces competent work that misses the integrative point. The fix is one explicit through-line sentence near the top of the draft stating how this Week's problem sits inside the course's larger question, then a body that actually honors it.

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.

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