NURS 6914 Week 2 planning manual

1. Capture the live Week 2

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 Advanced Palliative Concepts and Interdisciplinary Perspectives, the durable class question is: What does the prompt ask the student to understand, apply, compare, create, or evaluate? 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.

Turning the first instructor signals into a method

By Week 2 there is usually a comment, an announcement, or a returned result to read. Treat those as data about how this section scores rather than as general encouragement. Extract the three things a cadence needs: what the instructor rewards, what the instructor corrects, and how quickly responses arrive. In a palliative concepts course, one of the most common early corrections is register, meaning the work is written in clinical shorthand or in emotional language when the criterion wants disciplined analytic prose. Another is scope, where a broad concept question receives a narrow procedural answer.

Build the week's routine around those signals. A workable cadence for a five-credit Course-Based class separates reading, note-making, drafting, source checking, and posting into named blocks rather than one long session, because the checking blocks are the first to disappear under time pressure. Your classroom rubric decides the standard those blocks aim at, so re-read it at the start of each block rather than once at the end.

3. Build the work in proof order

Define the required concept precisely, apply it to the stated context, make the reasoning visible, and close with the implication the current rubric requests.

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

The Week 2 read of a rubric differs from the Week 1 read. You now have at least one result or one set of comments to hold against the criteria, so read each row twice: once for what it asks, and once for how this instructor appears to interpret it. Copy the rows into your working document as plain lines, then write under each one the specific sentence or section you intend to satisfy it with.

Rows that describe reasoning quality usually reward a visible chain: concept named, applied to the stated context, consequence stated. Rows that describe evidence usually reward matching rather than volume, so one well-placed source that supports the exact claim beats three that gesture at the topic. Rows about mechanics are inexpensive points and should never be lost. Mark any row whose language you cannot translate into an action and ask about it in the classroom channel. The posted version controls, and your classroom rubric decides.

4. Use evidence deliberately

Use the assigned readings first when required, then add current authoritative or peer-reviewed support matched to the claim.

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.

A weekly source routine you can repeat

Cadence applies to sources too. Set a fixed search block each week rather than hunting for citations while drafting. Start inside the assigned readings, because they come first when the activity says so and because their reference lists point to the literature this course treats as authoritative. Work outward from there to peer-reviewed palliative, hospice, oncology, geriatric, and nursing journals, then to guidelines and consensus statements from recognized professional bodies, then to national health agency reports.

Log every candidate in one table with author, year, design or document type, population or setting, the usable finding, and one limitation. Working a source into the draft is then a repeatable two-step move: the claim sentence in your own words, then the support sentence that names the source and its finding, followed where the criterion asks for it by an interpretation sentence saying what the finding changes. Do not let a source open a paragraph. Check the required style and any currency window in the live instructions, since your classroom rubric decides both.

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.

Building a note system that survives to Week 11

The point of a stable Week 2 is that later Weeks inherit something. Keep three files and only three. The concept file holds working definitions and boundary notes for palliative terms as they appear. The source file holds logged entries with their use notes. The feedback file holds criterion-level results and the corrective action you took. Every subsequent Week reads from these and writes back to them.

Name the files with the course code and Week so nothing is retrieved from the wrong section or term. Resist keeping whole submitted drafts as templates; preserve the method and the lesson instead, because a later prompt requires new reasoning, new evidence, and your own authorship even when the underlying concept returns. Keep all of it at the written and preparatory layer, with no protected information of any kind. Your classroom rubric decides what each activity requires, and these files exist to make satisfying it faster, not to pre-write it.

7. Run the Week 2 quality gate

Check task completion, reasoning, evidence fit, examples, organization, citations, file rules, and the student's own explanation of the result.

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 3. 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 2, 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 3.

Three Week 2 traps and how to clear them

The first trap is inheriting Week 1's rhythm without inheriting its correction, which produces a second submission that loses the same criterion. The fix is to open the feedback file before planning the Week and name one criterion you are deliberately testing this time. The second trap is front-loading, where the initial post lands early and the replies are written in the last hour against a closing window. The fix is to schedule replies as their own task with their own deadline, since a reply that compares evidence, applies a peer's idea to a different context, or marks a boundary takes real reading time.

The third trap is the growing tab pile, where sources are collected but never logged, so the same article is read three times and cited once. The fix is to write the source table entry at the moment of first reading, before the tab closes. Each of these is a working habit rather than a standard: the live instructions and your classroom rubric decide what the Week actually requires.

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

Week 2 questions