NURS 8720 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 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: making earlier units do work in the current problem

Integration is not review. It is using something established earlier to change what the current work says. Build a two-column map. On the left, the concepts, methods, and frameworks the course has covered so far. On the right, the specific decision in the current problem that each one could inform: how the question is bounded, which population or setting is compared, which measure is defensible, which limitation must be stated, which rival explanation must be addressed. Any concept that cannot be attached to a decision stays off the page this Week, however well it was learned.

Where a theoretical or conceptual framework is in play, make it constrain something. A framework earns its place when it explains why these elements and not others, why a relationship is expected to run in a particular direction, or why a given kind of evidence counts as relevant at all. Write one sentence in the body that would be false if the framework were removed. If no such sentence exists, the framework is being named rather than used, and naming without using is among the most reliably marked weaknesses in doctoral writing.

Integration also runs forward. Note which decisions the current Week is locking in, because later Weeks inherit them: the definition of the central term, the population boundary, the outcome of interest, the comparison. Recording them keeps the eventual whole coherent and prevents the drift that appears when every Week is drafted as a standalone answer to its own prompt.

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: pairing the foundational source with the current one

Integration usually needs two kinds of citation on the same point. The foundational source is where a concept, framework, or measure was established. The current source is where it is being used, tested, or challenged now. Cite both when the point depends on what the concept means and on how it presently stands, and make clear in the sentence what each one is doing. That pairing is much of what separates a synthesized paragraph from a dated one, and it is visible to any reader who knows the literature.

Trace lineage before citing a framework. Find who originated it, what it was built to explain, and whether later work has modified or narrowed it. Citing a secondary description of a framework as though it were the origin is a common attribution error at this level, and it tends to surface at exactly the moment when the framework is carrying the most weight in the argument.

Never reuse previously submitted language to demonstrate integration. Preserve the lesson and the method, not the sentences. A later activity requires new reasoning, new evidence, and new authorship even when the underlying concept returns, and the safest habit is to draft the integrated paragraph from the concept map rather than from an earlier file, so the words come from the current argument.

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, on rows that ask for synthesis

Whatever the posted grid contains, the registered classroom rubric decides, and on integrative work the distinction to watch is between rows that say uses and rows that say integrates, connects, or synthesizes. Uses can be satisfied by an accurate mention. The others are satisfied only when a reader can see two things joined and something following from the join, which means the paragraph needs a sentence that exists because both elements are present. Writing that treats each concept in its own paragraph will satisfy the first wording and miss the second entirely.

Look for cross-criterion dependencies. Rubrics on synthesis-heavy work often score the same passage twice, once under content and once under analysis or scholarly writing, so a weak paragraph loses points in two places and a repaired one gains in two. Identify those passages during outlining and give them the largest share of the drafting time, since the return per hour there is roughly double.

Then check for any row about the course's own materials. When a row requires engagement with assigned readings or with concepts from earlier units, that requirement is read literally, and a well-argued section built entirely from outside sources can still miss it. Keep the assigned material in the evidence table so it is available when such a row appears.

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

First pitfall: reusing submitted text. An earlier post or paper covered the concept well, so it reappears with light edits. That is an authorship problem before it is anything else, and it also produces prose that answers the earlier prompt rather than this one. The fix is to work from notes and the concept map only, never from the earlier submission, and to draft the paragraph before rereading anything previously turned in.

Second pitfall: the named framework. It appears in the opening, is defined accurately, and then never touches the analysis again, so it functions as ornament. The fix is the falsifiable sentence test: find the sentence in the body that would be wrong if the framework were removed. If no such sentence exists, either put the framework to work on a real decision or take it out.

Third pitfall: the literature tour. Integration turns into a survey of everything covered so far, one paragraph per topic, with no argument running through it. The fix is the two-column map: a concept enters only where it changes a decision in the current problem, and the section is organized by those decisions rather than by the order the course covered the material.

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