NURS 8720 Week 3 planning manual

1. Capture the live Week 3

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 the inferential step visible

Showing reasoning means writing the step between a finding and a claim instead of leaving the reader to supply it. Use a three-line form on every load-bearing point. Line one reports what the source found, in its own terms, with the design and the population or setting attached. Line two is the warrant: why that report bears on this problem, this setting, and this question. Line three is the claim the student is willing to defend, pitched at the strength the warrant allows. Graded comments asking for depth are usually asking for line two, which writers skip because it feels obvious to the person who did the reading.

Calibrate strength against design, in general form. A cross-sectional report of an association supports a sentence about co-occurrence in that population, not a sentence about cause. A single-site interventional report supports a sentence about what happened at that site under those conditions, not a forecast for another site. A synthesis supports a sentence about the weight and consistency of a body of work, not about any one mechanism. Write the claim, read the design column of the evidence table beside it, then adjust the verb until the two match.

Apply the same discipline to comparisons and decision criteria. If the work compares options, state the criteria before naming a preferred option and keep the criteria identical across options. If it applies a decision rule, give the rule, then the inputs, then the output, in that order, so a reader can check the middle step rather than take the conclusion on trust.

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: reading the method section rather than the abstract

A claim that shows its reasoning has to be built from sources read at the method level. Abstracts report conclusions; methods report what was actually done, and the limits of any claim live there. For each source doing real work this Week, open the method and record six things: the design, the sampling and setting, the measure or instrument, the comparison if one exists, the analysis, and the authors' own stated limitations. Those six items are what let a paraphrase be accurate instead of approximate, and they populate the evidence table columns the course method already requires.

Separate primary from secondary with care. Citing a review for a particular study's result attributes the finding to the wrong document and hides the design from the reader, who then cannot judge the claim. If the review is genuinely the source of the point, cite the review and say what it is. If the underlying study is the point, retrieve the study. Trace the reference back whenever a specific number or effect is going to appear in the draft.

Then paraphrase from the record rather than from the page. Close the source, write the sentence from the six recorded items, and only then reopen the source to check it. The habit produces prose in the student's own voice and makes it immediately visible when a sentence has drifted past what the study can actually support.

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 3 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, where description and analysis split

The registered classroom rubric decides, and when a Week turns on reasoning the rows worth finding first are the ones that separate description from analysis, because they are scored differently and are the rows most often satisfied only halfway. A description row asks what. An analysis row asks why, how, or so what, and it is satisfied only by inference the reader can see on the page. A paragraph that reports three studies accurately can score well on the first row and poorly on the second at the same time.

Read the level language on the analysis row with particular care. Movement between levels typically runs from stated, to explained, to supported, to consistently applied throughout. Translate each into the artifact: stated is a claim sentence, explained is the warrant line, supported is the citation matched to that warrant, and consistently applied means every major point received the same treatment rather than only the first one. Most work that lands mid-scale has the treatment in its opening section and nowhere else.

Then plan placement. Reasoning that appears only in a concluding paragraph is easy to miss under a row that scores the body of the work. Put the warrant next to the evidence each time the evidence appears, and reserve the conclusion for implication rather than for the analysis that should have been visible earlier.

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 4. 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 3, 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 4.

Three Week 3 pitfalls and the fix for each

First pitfall: the summary chain. Paragraph after paragraph reports one study each, in the order they were read, with no sentence connecting them to one another or to the question. It reads as coverage and scores under description no matter how accurate each summary is. The fix is to write the section's claim first as a single sentence, bring in only the studies that support, qualify, or test that claim, and open each paragraph with the point rather than with an author's name.

Second pitfall: attribution drift. A finding is credited to whichever document the student happened to be holding when the sentence was written, so a review gets cited for a trial's result and the design disappears from view. The fix is the design column: no result enters the draft without its design and source type recorded, and any result taken from a synthesis is labeled as such inside the sentence.

Third pitfall: hedging that erases the claim. Layers of may, could, appears to suggest, and further research is needed leave a grader nothing to evaluate. The fix is one qualifier per claim, chosen to match the design, followed by a statement of what would raise confidence. Precision reads as caution. Vagueness reads as absence.

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

Week 3 questions