NURS 8710 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 I, 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: making the inference visible instead of implied

Showing reasoning means writing the step that most drafts skip. Consider a sentence of the common form "the literature supports early mobility." It states a conclusion and hides everything that would let a reader evaluate it. Break it into the four moves a doctoral reader expects to see: the premise being relied on, the evidence that establishes the premise, the inference that carries the premise to the claim, and the boundary where the inference stops holding. Written out, the same idea names what the studies actually measured, in which population or setting, what follows from that, and where it does not follow.

The fastest test for a hidden inference is the word "because." Insert it after every analytical claim in the draft and see whether a real reason follows or only a restatement. A second test is to ask what would have to be true for the claim to fail; if nothing could falsify it, the sentence is decoration rather than reasoning. Neither test adds length for its own sake, since making the inference visible usually replaces two vague sentences with one precise one. How that reasoning must be organized on the page is decided by your classroom rubric.

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 to separate description from analysis

Most rubric rows that students lose points on are analysis rows answered with description. Go through the live rubric and mark each row with the highest verb it contains. Rows topping out at identify, describe, or summarize are satisfied by accurate reporting. Rows reaching compare, analyze, evaluate, or justify are not satisfied by any amount of accurate reporting, however well written. That single mark next to each row is the most useful annotation available in a reasoning-heavy Week.

Now audit the draft against the marks. For every analysis row, find the sentence that does the analytical work and check that it contains a relationship rather than a fact: a contrast, a mechanism, a condition, a trade-off, or a judgment with grounds. If the only candidate sentence reports what an author said, the row is unmet no matter how many sources surround it. Keep the description that sets up the analysis, but make sure it occupies less space than the reasoning it supports. Which rows demand which verb level is settled by your classroom rubric, not by this page.

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.

Reading a study for what it can and cannot support

In a Week built on visible reasoning, source work means reading past the discussion section. Open the methods first and record the design in plain terms: whether the study observed or intervened, whether groups were compared, whether measurement happened once or over time, and who was actually enrolled or examined. Then open the results and note the effect the authors report and how precise it is. Only then read the discussion, treating the authors' interpretation as their argument rather than as a finding. Papers routinely claim more in the discussion than the design earns.

Working that source into a draft is a matter of matching verbs to designs. Observational work supports language about association, patterns, and correlation. Controlled comparison supports stronger language about effect. Qualitative work supports language about meaning, experience, and process, and it supports transferability rather than generalization. Choose the verb the design licenses and the sentence will survive review; choose a stronger verb and one careful reader can dismantle the paragraph. Which sources are required or permitted for this activity, and how they must be cited, is decided by your classroom rubric.

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.

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 traps and the repair for each

The first trap is a summary chain wearing the costume of synthesis. Each paragraph opens with an author's name, reports what that author found, and moves on. The repair is to reorganize by idea: give the paragraph a claim as its first sentence, then bring two or three sources under it, and state explicitly where they agree, where they diverge, and what the divergence means. If a paragraph cannot hold more than one source, its idea is probably too narrow to be a paragraph.

The second trap is the unstated leap, where a finding in one population is used to justify a claim about a different one without any sentence acknowledging the move. The repair is a boundary clause attached to the claim itself rather than parked in a limitations section at the end. One clause naming the population or setting the evidence came from does more for a reasoning row than a paragraph of hedging later.

The third trap is citation stacking, where several references are piled behind a sentence to make it look supported. A reader who opens two of them and finds they measured different things loses confidence in the whole draft. The repair is to cite the source that actually tested the claim, and to write a separate sentence for any source that tested something adjacent. Fewer citations doing real work read as stronger than many doing none. How much reasoning must be shown, and where it must appear, is decided by your classroom rubric.

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