NURS 6800 · Week 9

NURS 6800 Week 9 planning manual

A course-specific Week workflow for capture, reasoning, evidence, student authorship, quality control, and gradebook closure.

Week 9: assemble the close

Map every remaining activity, dependency, reply, approval, and gradebook risk before the final Weeks concentrate the stakes. This page verifies a position in the Course-Based quarter calendar, not a universal assignment identity.

NURS 6800 grading scale at Walden, how the work is graded, from Walden Tutors
How Walden grades NURS 6800, visualized by Walden Tutors.

1. Capture the live Week 9

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.

Control fieldWhat to verify now
IdentityExact course, Week, activity, and current version
TaskEvery required action, question, audience, and deliverable part
GradingRubric rows, points, weights, thresholds, and penalties
EvidenceAssigned readings, source rules, dates, authority, and citation style
CalendarInitial post, replies, files, approvals, due time, and time zone
DependenciesGroup, field, clinical, residency, proctoring, feedback, or approval steps

2. State the Week's reasoning question

For Advanced Pediatric Development and Behavior, 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.

Worked reasoning: giving the closing work a single spine

Longer or culminating work fails structurally more often than it fails on content. Before drafting, write one sentence stating the whole argument: the concept at issue, the context it addresses, the position taken, and what follows from it. Every section then has to earn its place by supporting that sentence. If a planned section cannot be tied to it in a few words, either the sentence is wrong or the section is.

Build the outline as a repeating unit rather than as a list of topics. Each unit carries a claim, the support for it, and the implication for the context named in the spine sentence. In this subject that usually means each unit stays bounded to one stage, area of development, or setting rather than sliding between them, because a section that changes scope midway is difficult to score against any single row. Draft the heaviest unit first. Introductions written before the argument is settled almost always have to be written again.

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: mapping a long deliverable

For a substantial deliverable the rubric doubles as an architecture. Lay the rows out in order and assign each one a visible home: a section, a subsection, a table, or a named checkpoint in the drafting plan. Rows describing the whole work rather than a part, such as organization or communication, get a checkpoint in the final pass instead of a section of their own.

Do not turn the rubric into the heading structure. Copying criterion names as headings produces a document shaped like a form and usually leaves the connective reasoning unwritten. Write headings that describe content and keep the row-to-section map in a separate working file. Confirm the point weights and adjust the space plan accordingly, then confirm that nothing in the plan exists without a row behind it. The rubric version attached to the live activity is the one that governs this map.

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.

Freezing the source set before final assembly

Late sources are the main cause of disorder in a closing deliverable. Set a cutoff before the final drafting pass and treat the shelf as closed after it. Before that cutoff, verify each entry: retrieve it again, confirm the citation details against the source itself, confirm the date and the design, and confirm that the use note still matches what the draft claims.

Then check coverage rather than count. Every load-bearing claim needs support of matching strength, and every entry in the reference list needs a sentence that uses it analytically. Remove the orphans. Where a gap appears after the cutoff, close it by narrowing the claim instead of adding a hurried source, since an unread reference is worse than an absent one. Assigned readings remain first wherever the live activity requires 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 9 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.

Three Week 9 pitfalls and the fix for each

The first pitfall is starting with the introduction. It is the easiest section to begin and the only one that cannot be correct until everything else exists. The fix is to write a placeholder spine sentence, draft the heaviest section, and write the introduction last.

The second is a reference list that keeps growing after the argument is fixed. Additions made for reassurance rather than for a claim inflate the list and invite mismatches. The fix is the cutoff, actually enforced, with any post-cutoff need handled by narrowing the claim it would have supported.

The third is leaving an institutional dependency for the final day. Group coordination, approvals, format conversion, accessibility checks, and the submission route itself can each consume more time than the last edit. The fix is to open every dependency lane in the calendar ledger this Week and to complete anything that depends on another person before the writing is finished.

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

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

Week 9 questions

What is assigned in NURS 6800 Week 9?

Only the registered Course-Based classroom can answer that. This positional manual deliberately does not invent a discussion, paper, quiz, project, exam, practicum task, or rubric.

How should I start NURS 6800 Week 9?

Capture every live activity, instruction, rubric row, point value, deadline, reply rule, dependency, and submission route before researching or drafting.

Can a tutor perform the Week for the student?

No. Tutoring supports understanding, method, practice, and feedback; the student performs required activity, authors the response, verifies it, and submits it.

Online now