NURS 6710 Week 10 planning manual

1. Capture the live Week 10

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 Theory and Practice, 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.

Revising by diagnosis rather than by rereading

Rereading a draft from the top rarely finds structural problems, because the writer supplies the missing links from memory. Revise in separate passes with a different question in each, and do not mix them. The first pass is a reverse outline: write, in the margin or a separate file, the one claim each paragraph actually makes, then read only that list. Gaps, repetitions, and paragraphs that make no claim become visible immediately, and the list can be checked against the rubric far faster than the prose can.

The second pass follows the course chain through the draft with a single question at each link: is the cue stated, is the mechanism or standard named, is the judgment committed to, is the action specific enough to monitor, and is escalation addressed where the activity asks for it? Mark the first link that fails and repair it before reading further, since a break early in the chain usually explains the weakness in everything after it. The third pass is the reader's pass, taken after a break, reading for whether someone who does not already know the argument could follow it. Only after those three does line editing earn its time. What the finished work must contain is set by the current rubric, and a revision plan built from a previous activity's instrument will polish the wrong things.

Reading the rubric row by row with a finished draft in hand

A rubric read against a complete draft answers a different question than a rubric read during planning. Go row by row and, for each one, find the exact sentence or section where the row is satisfied and note its location. Rows that take a minute to locate are rows a reader may not find at all, and the usual repair is not more writing but a heading, a topic sentence, or a signpost that makes the existing work visible.

Then read the performance-level descriptions rather than the row titles and be honest about which level the current draft supports. Where the draft sits below the level above it, the difference is usually one identifiable thing that level names, such as an applied criterion, a considered alternative, a stated limitation, or evidence tied to a claim. Add that one thing rather than rewriting the section. Finally, check the rows that are easiest to fix and cheapest to lose, which are almost always formatting, citation accuracy, and mechanics, and give them a dedicated pass with the content settled. Accumulated feedback from earlier Weeks belongs in this reading too: any criterion that has lost ground twice should be checked here first. The rubric loaded with the live activity remains the only authority on all of it.

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.

Reconciling the reference list with the argument

Late revision is where a source layer either becomes coherent or stays a collection. Work in both directions. Read the text and confirm every citation appears in the reference list, then read the list and confirm every entry appears in the text doing analytical work. Entries that survive only because they were interesting are padding, and a reader who knows the field recognizes them quickly. Removing them usually improves the response.

Then reconcile the source set against the claims one more time. Load-bearing claims should rest on the strongest available support rather than on the source that happened to be found first, and where a stronger or more current source exists, swapping it in late is usually a short edit to one sentence. Check the categories again, since revision tends to blur them: recommendations from authoritative guidance, findings from research with a design attached, and the reported situation from official data for a defined place and period should each still be recognizable as what they are. Confirm currency and version once more for anything carrying weight, keep quotation rare and accurate, and apply the citation style the live activity requires rather than the one used most recently.

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 10 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 11. 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 10, 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 11.

Three revision pitfalls and the fix for each

The first pitfall is editing when rewriting is required. A paragraph built on the wrong claim cannot be repaired by better sentences, and hours spent smoothing it feel productive while changing nothing a rubric row can see. The fix is to decide, at the reverse-outline stage, which paragraphs are sound and which need rebuilding from their claim, then rebuild those before any sentence-level work begins.

The second pitfall is fixing the symptom an instructor named rather than the cause behind it. A comment about one weak transition often marks a section whose claims do not follow from each other, and inserting a connective word leaves the real problem in place for the next activity. The fix is to ask, of every piece of feedback, what would have had to be true earlier in the process for this comment not to exist, and to correct that.

The third pitfall is the late change that breaks agreement elsewhere. Adjusting a conclusion, a definition, or a figure after the rest is finished leaves an introduction, a summary, or a table stating the previous version. The fix is a rule for the final hours: after any change to a claim, a figure, or a term, search the whole document for the earlier version before moving on, then run one last read from the top with no editing allowed.

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

Week 10 questions