NURS 8750 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 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: making the inference chain visible

Showing reasoning in Doctoral Seminar V means putting the inference on the page, not the conclusion alone. Take one claim from the current activity and write it as a three-part chain. Line one is the evidence statement: what a specific source actually reports, in its own terms, with its design and population attached. Line two is the warrant: the reason that reported result bears on the question at hand rather than on an adjacent one. Line three is the claim: what you are asserting, scoped to exactly what lines one and two can carry.

Now test the chain by attacking line two, because that is where graduate reasoning usually fails. Ask whether the setting in the source matches the setting in your question, whether the outcome measured is the outcome you are claiming about, and whether the direction of the relationship is what you are asserting. If any answer is no, the repair is to narrow the claim, not to stack a second citation behind the same weak warrant. Write the surviving chain into prose as evidence, then warrant, then claim, in that order, and the paragraph will read as analysis rather than as report.

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 that produces synthesis instead of summary

A summary paragraph is organized by author; a synthesis paragraph is organized by finding. This week, take the intake sheet and re-sort it. Group entries by what they found rather than by who wrote them, and name each group in a short phrase that states the finding. Groups of one are a signal: either the finding is genuinely isolated, which is worth saying out loud, or the search has not yet reached the neighboring work.

Then write each group as a single paragraph that opens with the finding, cites the sources that share it, and states plainly where they disagree and why the designs might explain the disagreement. Convergence across different designs is stronger than repetition within one design, and saying so is itself analytical work a rubric row can see. After every cited sentence, add one line in your own voice naming what the citation just did for the argument. If that line cannot be written, the citation is decoration and should come out. Format the result in whatever citation style your registered classroom names.

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

At this stage, read the rubric for its depth verbs and treat everything else as secondary. Copy each row's verb into a list: identify, describe, explain, compare, analyze, evaluate. Beside each verb write what a reader would have to see on the page to accept it. Identify needs a named thing. Describe needs attributes. Explain needs a mechanism. Compare needs a stated basis of comparison. Analyze needs parts and the relationship between them. Evaluate needs criteria and a judgment made against them.

Now audit the draft against that list, marking the highest verb your prose actually performs in each mapped section. A row asking for analysis that receives a competent description is the most common gap in the middle of a seminar quarter, and it stays invisible unless the verbs are checked deliberately. Where the gap appears, the repair lives in the paragraph structure, not the vocabulary: add the parts, the relationship, or the criteria that the verb requires. Verb wording and level descriptors differ across sections and terms, so your classroom rubric decides what each row is scoring.

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

The first pitfall is the source-by-source paragraph. One paragraph per study produces a competent-looking review that never states a finding of its own, and rubric rows asking for analysis cannot be satisfied by it. The fix is the re-sort described above: one paragraph per finding, with the sources arranged inside it.

The second pitfall is a claim that outruns its design. A cross-sectional result does not support a causal sentence, and a single-site result does not support a general one. The fix is a scope pass in which every claim sentence is read next to the design column of the intake sheet and rewritten to the level that design supports, with the qualifier kept inside the sentence rather than exiled to a closing note.

The third pitfall is hedging until nothing is asserted. Stacked qualifiers read as caution but land as the absence of a position. The fix is one defensible claim per paragraph, stated plainly, carrying a single qualifier that names a specific condition rather than a general disclaimer.

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