NURS 4300 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 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: making the mechanism visible

Week 3 asks the work to show reasoning, and the difference between asserting and showing is a visible chain. For illustration only, take a familiar improvement claim: purposeful rounding reduces inpatient falls. Asserted, that sentence is a conclusion with nothing holding it up. Shown, it becomes a chain a reader can audit: the problem stated with its scope, the published evidence summarized with design and population attached, the mechanism explained, meaning why regular presence changes the conditions that produce falls, and the boundary named, meaning where the evidence is thin or the setting differs. Apply that skeleton to whatever the live Week actually assigns. After drafting each paragraph, run a because test: every claim sentence should be followed within a sentence or two by the reasoning or evidence a skeptical reader needs, and any claim left standing alone at the end of a paragraph is a gap. Reasoning made visible also means calculations shown where the activity involves them, comparison criteria stated before comparisons are made, and decision rules written down before the decision is announced. A grader cannot award what a draft only implied.

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

In a Week aimed at reasoning, sort the current rubric's rows by what they actually purchase. Rows built on verbs like identify, describe, or summarize pay for coverage; rows built on analyze, evaluate, justify, or compare pay for visible thinking, and they are usually where capstone points concentrate. Read each reasoning row and mark the exact place in the draft where that row will be satisfied, section by section, in the order the rubric lists them, so the grader finds the scored moves where the scoring instrument expects them. If a row asks for evaluation, the draft needs stated criteria and a judgment, not a summary with an adjective attached. If a row asks for comparison, the draft needs the dimensions of comparison named before the items are walked through. Where any row's demand is ambiguous, ask the instructor early in the Week rather than resolving the ambiguity privately, and record the answer beside the row, because only the classroom rubric and its author decide what a row means.

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.

Sources as premises, not decoration

A reasoning Week changes what a source is for: each citation is a premise the argument stands on, not a gesture toward the literature. Choose evidence by the analytical work it must do. A mechanism claim usually wants a primary study or a systematic review that examined the mechanism; a scope claim wants surveillance or agency data; a practice-standard claim wants a current guideline, all subject to the source rules the current prompt sets. Work each source in analytically: a signal phrase that states what the source establishes, the finding paraphrased from understanding with population and design visible when they matter, then a sentence that says what this premise contributes to the claim. Quote only when exact wording is itself the point. A dropped-in quotation with no analytic follow-through does nothing for a reasoning row, and a paragraph of consecutive citations with no student sentence between them displays reading effort while hiding the thinking the Week exists to show.

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.

Week 3 pitfalls and the fix for each

Pitfall one: definition stacking. A draft that defines terms, summarizes readings, and restates the prompt can fill the length requirement while never making a claim. The fix is to write each section's one-sentence claim first and delete any paragraph that does not advance it, then reinstate definitions only where the argument actually needs them.

Pitfall two: the problem-to-conclusion jump. Drafts under time pressure state a problem, skip the method, and land on a recommendation, leaving the middle invisible. The fix is to draft the middle first, the evidence, the mechanism, and the criteria, and let the conclusion be the last sentence written rather than the first.

Pitfall three: citation without connection. A source appears, the sentence ends, and the reader is left to guess the relevance. The fix is a standing rule that every citation is followed by a student-authored sentence naming what the source changes about the argument. If that sentence cannot be written, the source is decoration and belongs back in the table, not in the draft.

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.

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