NURS 6730 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 Public Health Nursing Leadership, 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.

Turn the reasoning chain into a two-pass weekly routine

By the second Week the goal is not to discover the method but to make it cheap to run. Split the chain into two passes separated by at least a day. The first pass is fast and private: read the live activity, write the cue in one line, name the mechanism or standard that makes the cue matter, and stop there. The second pass adds prioritized judgment, the population-level action, the monitoring indicator, and the escalation point, then checks whether the first pass still holds. Splitting the chain converts a single frantic session into a cadence, and it exposes a weak middle line while there is still time to read.

Attach the routine to the calendar rather than to motivation. What breaks people in a Course-Based quarter is rarely the volume of writing; it is the number of separate commitments a single Week can contain, since a contribution, a response window, a file, and a dependency in the practicum lane are four different clocks. Give each visible commitment its own slot, place the first pass before the earliest slot, and keep a standing block for the second pass. Log how long each pass actually took this Week. That measurement, not an estimate, is what you schedule against for the rest of the quarter, and the registered classroom remains the only source for what the Week contains.

Reading the rubric row by row as a weekly ritual

Read the rubric again this Week even if it looks like the one you read in Week 1. Criteria change between activities, and a row that carried a small share of the score in an orientation task can carry much more once analysis begins. The ritual is short: open the rubric the classroom shows for this activity, read each row aloud, and after each one say what a grader would have to see on the page. If you cannot say it, that row is not yet understood, and it will not be satisfied by generally good writing.

Keep a single running rubric sheet for the course with one column per Week so drift becomes visible. Note the row labels, the weights, and the wording of the top level. When a familiar row reappears with different wording, mark it, because the change is a signal about what the current activity wants. Read the mechanics and communication rows deliberately as well; they are usually the smallest numbers on the page and the easiest to lose without noticing. The sheet is a planning tool only. Your classroom rubric decides the score, and the version displayed with the live activity outranks anything you copied earlier.

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.

Building a source routine you can repeat every Week

Cadence applies to evidence as much as to drafting. Set a fixed search block early in the Week and use the university library rather than a general web search, because access, currency, and peer-review status are all resolved for you there. Search with the vocabulary the field actually uses: population, aggregate, community, prevalence, incidence, determinants, intervention, program evaluation, health equity, workforce, surveillance. Pair a subject-heading search with a keyword search, then follow reference lists backward and citations forward from the two strongest results. Twenty minutes of structured searching returns more usable material than an hour of browsing.

Capture every candidate the same way each time, in one file: author or agency, year, type, population or setting, the finding you can use, the limitation, and the claim it will support. That last field keeps the routine honest, because a source with no claim attached is a source you have not read for a purpose. When the drafting session starts, the file is already an outline of what can be defended. Assigned readings stay mandatory where the current activity requires them, and your classroom rubric decides how many sources are expected, of what age, and in which citation style.

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

The first is treating a Week as one deadline. Where an activity has a contribution deadline and a separate response window, that is two commitments, and the second is scored even when the first was strong. The fix is a two-column ledger for every Week: what is due, and what is due only after something else happens. Anything that depends on another person or another step gets its own line and its own earlier internal date.

The second is writing to volume instead of to criteria. Early in a course it feels safe to submit more, so posts and drafts fill with definitions no row asked for. The fix is to cut every sentence that does not serve a rubric row or the class question, then check whether the remaining text still meets any stated length rule. Length rules are met by adding reasoning, not by adding restatement.

The third is quoting a number without its denominator or its date. Population claims collapse quickly under that habit, because a reader cannot tell whether a count is alarming or ordinary. The fix is a small number card kept beside the draft: for each figure, record the source, the year, the population it describes, and whether it is a count, a rate, or a proportion. Then write the figure into the sentence with that context attached, every time.

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