NURS 6370 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 Foundational Skills for Nurse Educators in Academic and Healthcare Environments, the durable class question is: What evidence supports the judgment, what alternatives matter, and what remains outside the student's authority? 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

Move from cue to mechanism or standard, then to prioritized judgment, action, monitoring, and escalation. Use only de-identified authorized context.

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 objective, strategy, and assessment chain visible

The third Week is where description stops paying. The chain that carries most nurse educator reasoning has four links, and the work of the Week is to put all four on the page instead of leaving three of them in your head. Name the learner group and the setting. State the objective at a stated level of learning. Choose the teaching strategy that reaches that level. Choose the assessment that can detect whether the objective was met.

The chain is testable, and testing it is the analysis a rubric can score. Read your objective and your assessment side by side and ask whether the assessment could tell a learner who met the objective from one who did not. An objective written at the level of application paired with a recall assessment fails that test, and writing that failure out is worth more than another paragraph describing either one. Where a link is weak, name the misalignment and repair it in view of the reader.

Do the same for the strategy link. A strategy justified only by preference is an assertion; a strategy justified by the level of the objective and by the constraints of the setting is reasoning. Two sentences carry it: this level of learning requires learners to do rather than to hear, and this setting allows that much practice time. That is the difference the Week is asking you to show.

Reading the rubric row by row

Read the verbs first and rank them. Rows built on identify, describe, and summarize are satisfied by accurate content. Rows built on analyze, compare, justify, evaluate, or align require a visible operation: two things set against each other, a criterion applied, a conclusion drawn. Mark every row in the second group, because those are the rows that fail quietly inside a paper that reads well.

Then decide where each higher-order row becomes visible. Give it a heading, a labeled sentence, or a short table if the format allows one, so the reader is not asked to locate your analysis inside a descriptive passage. Signposting is not padding; it is how a reader confirms a row was addressed.

If a row's language is ambiguous, resolve it against the live instructions and the posted announcements rather than against an example from another section, and remember that the rubric in your registered classroom decides how the row is applied.

4. Use evidence deliberately

Prefer current authoritative clinical guidance and peer-reviewed evidence appropriate to the question; distinguish guideline recommendations from patient-specific facts.

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 that carry mechanism, not just assertion

A Week built on visible reasoning needs sources that explain rather than sources that declare. Prefer studies reporting how an educational approach was implemented and what changed, and standards documents that state the reasoning behind a requirement. A secondary source asserting a best practice without a mechanism can name the practice, but it cannot support a claim about why the practice works, and why is what this Week is asking for.

Appraise before you cite. For each candidate, record the learner group, the setting, the design, the outcome that was measured, and the limitation the authors state themselves. A source whose outcome measure does not match the objective you are discussing is the wrong source, however recent it is.

In the draft, attach the source to the mechanism sentence rather than to the claim sentence. Placing it there tells the reader exactly which part of the reasoning the evidence holds up, and it lets the analysis rows and the evidence rows reinforce each other instead of competing.

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

Check safety, scope, differential logic, contraindications, documentation, confidentiality, and every student-performed clinical requirement.

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 pitfalls, and the fix for each

The first pitfall is the unmeasurable objective. Verbs such as understand, appreciate, or be familiar with cannot be observed, so any chain built on them breaks at the last link. The fix is to rewrite the objective around an observable action and then confirm that the assessment observes that same action.

The second pitfall is strategy shopping: a paragraph listing several teaching approaches and committing to none. It reads as coverage and scores as description. The fix is to choose one approach, justify it against the objective and the setting, and mention an alternative only to say why it was set aside.

The third pitfall is burying the reasoning in the final paragraph. Analysis written last usually arrives last, after the reader has already worked through the earlier rows. The fix is to draft the analytical section first and let the descriptive material shrink to whatever the analysis needs.

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