NURS 3022 Week 6 planning manual

1. Capture the live Week 6

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 Professional Nurses as Change Agents, 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.

Carrying earlier concepts into new sentences

Integration Weeks reward re-derivation and quietly punish re-pasting. Work from the ledger's concept list rather than from old files: write down, from memory and in the course's established vocabulary, each earlier idea the current prompt appears to touch, then check the wording against the original materials for accuracy. For every concept that survives the check, draft two fresh sentences: one stating the concept plainly, one stating precisely what it changes about the current problem. The second sentence is the integration; without it the concept is a name dropped for credit. Selection is the judgment step of the arc this Week: three earlier ideas doing visible work beat seven listed in passing, so choose the ones that genuinely alter the analysis and leave the rest unmentioned. Keep previously submitted files closed while drafting. Reusing language from earlier submissions raises originality questions that different sections resolve differently, and the version that is safe everywhere is new authorship over old learning. Where the current activity names assigned materials, they keep their mandatory place regardless of how much earlier learning the draft carries. The registered instructions still define what this Week's deliverable must contain; integration shapes how the thinking connects, not which requirements apply.

Reading the rubric row by row

Scan the live rubric for rows built on connective verbs: integrate, synthesize, connect, incorporate, build on. Rows of that kind grade a relationship, and a relationship can only earn credit if both of its ends are visible on the page in this submission. The grader reads what sits in front of them; earlier Weeks cannot testify on the draft's behalf. Convert each connective row into a planned bridge: a sentence that names the earlier concept, names the current problem, and states the link between them in one motion. Note also whether any row ties credit to course materials specifically, because a synthesis built entirely from outside sources can satisfy logic while missing a row that wanted the assigned readings in play. Weigh the connective rows against the rest and give them drafting time in proportion to their points, which is rarely what instinct allocates. As always, the row wording that counts is the wording attached to the current activity in the registered classroom, not a remembered pattern from earlier Weeks.

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.

Re-using sources without re-using sentences

This is the Week the source collection starts repaying its setup cost, and the rules of legitimate reuse are worth stating exactly. A source may serve again; a sentence may not. When an entry from an earlier Week fits a current claim, re-open the source and re-read the relevant part against the new claim, because a note written for one purpose can mislead when applied to another. Write a new use note for the new job, frame the finding in language built for this Week's argument, and cite it under the current activity's style and rules as if it had never been cited before. Then check the draft's balance: integration pulls attention backward, but most integrative prompts still concern a present problem, and whatever new evidence the live instructions require must anchor the draft in it. A response assembled only from familiar sources reads as a retrospective even when the prompt asked for analysis. Let old entries support, not substitute for, engagement with the current material. Counts, recency windows, and citation form stay wherever this Week's registered instructions put them.

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 6 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 7. 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 6, 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 7.

Week 6 pitfalls and the fix for each

Pitfall one: quiet self-copying. Lifting paragraphs from an earlier submission feels efficient and reads, to originality review, like recycled work; sections treat that differently and none treat it as a virtue. The fix is procedural: draft with earlier files closed, work from the ledger's concept list, and run whatever originality check the classroom itself provides before submitting.

Pitfall two: decorative integration. A sentence that announces a connection to earlier learning without showing what the connection changes is filler wearing a synthesis costume. The repair is the one-job rule: every earlier concept mentioned must demonstrably alter the current analysis, the weighed alternatives, or the proposed action, or it leaves the draft.

Pitfall three: outsourcing the connection to the reader. The writer sees the link because the writer lived both Weeks; the grader credits only what the page states. The fix is a reverse outline after drafting: for each claimed integration, point to the specific sentence that carries it, and where the pointing finds nothing, write the missing bridge. What integration is worth this Week, and where it must appear, is set by the live classroom rubric and nowhere else.

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

Week 6 questions