NURS 9000 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 Dissertation, the durable class question is: What claim, question, method, evidence, or approval gate is this work advancing? 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.

Rewriting the alignment sentence after the first instructor signal

Week 2 usually brings the first real signal from the classroom: an announcement, a clarified expectation, or a comment on Week 1. Treat that signal as data and rewrite the alignment sentence instead of defending the first version. Work it in order. If the signal touched scope, narrow the population or setting slot until the sentence names a group you could actually describe. If it touched method, test whether the question you wrote can be answered by the reasoning you planned, since a question that asks why cannot be settled by a description and a question that asks how many cannot be settled by a discussion of meaning. If it touched evidence, count how many of your sources speak to the exact population in the sentence rather than to the topic in general. The rewritten sentence becomes the cadence anchor: every drafting session opens by reading it and closes by asking whether the new paragraphs served it. Nothing here overrides the live prompt, and your classroom rubric decides what the finished response must contain.

3. Build the work in proof order

Keep problem, evidence, method, finding, limit, and implication aligned. Distinguish a course exercise from original research and never imply approval before the relevant reviewer grants it.

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 against your working calendar

By the second Week the rubric should stop being a document you consult and become the shape of your working week. Take the criterion table and add a column for the day you will work each row. Rows that require reading and source retrieval belong early, because they depend on library access and turnaround you do not control. Rows that require your own reasoning belong in the middle, when you have evidence and still have revision time. Rows that require format, citation mechanics, and file handling belong last, because they are quick to do and expensive to forget. Then look for rows that describe process rather than product, such as participation windows, response counts, or documentation steps, since those are the rows most often lost by strong writers who concentrate on the paper. Re-read each row's highest performance level as an instruction rather than as praise, and write that instruction in your own words beside the row. If your paraphrase is vague, you have not understood the row yet. Your classroom rubric decides.

4. Use evidence deliberately

Build a traceable evidence table with purpose, design, population or setting, result, limitation, and the exact sentence each source can support.

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 literature search you can repeat and defend

A doctoral literature base is built by a documented search, not by whatever appears first. In Week 2, write down the databases you used, the exact search strings, the date limits, and the inclusion and exclusion rules you applied, because you will be asked to defend or repeat the search later and memory will not serve. Prefer primary research reports for anything you intend to call a finding, and read the methods section before the abstract's conclusion, since the design decides what a study can support. Record each source in the evidence table with purpose, design, population or setting, result, limitation, and the one sentence it can license. When you work a source into the draft, name what it studied before naming what it showed, then state your claim; that order keeps a single-site result from quietly becoming a general truth. Discard sources that never perform analytical work, however long they took to find. A reference list padded to look substantial reads as weak scholarship to any careful reviewer, and the classroom sets the style and recency rules that apply.

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

Audit alignment across the problem, question, method, analysis, conclusion, rubric, and current institutional milestone.

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 2 pitfalls and their fixes

The first pitfall is starting the week's work on the day it is due and letting the routine reset every seven days. The fix is a fixed weekly rhythm that separates capture, reading, drafting, checking, and submission into different sittings, so no single session carries the whole load and no step is skipped because time ran out.

The second pitfall is answering the prompt from memory of Week 1 rather than from the live Week 2 text. Prompts in a research sequence look similar and often differ in one decisive verb, and answering the previous verb produces a competent response to the wrong task. The fix is to paste the current prompt at the top of the working file and delete it only after the final check.

The third pitfall is collecting sources faster than you read them. A folder of thirty unread files feels like progress and produces citation errors, because unread sources get cited from their abstracts. The fix is a hard rule that no source enters the reference list until its row in the evidence table is complete, including the limitation column.

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.

Make the cadence survive a bad week

A routine is only real if it holds when something goes wrong, and across a multi-quarter research sequence something will. Decide now what the reduced version of your week looks like: which single activity is protected, which reading can be deferred, and which check can never be skipped no matter how little time remains. Write that rule down while you are calm. Decide also what triggers a message to the instructor or the official support channel, and send it early rather than after a deadline has passed, since a documented question before the due time reads very differently from an explanation afterward. Keep the working draft where it syncs, and keep one dated copy outside the classroom, because a lost file is a schedule problem rather than a writing problem. Finally, log the hours the week actually took against the hours you planned. Two or three honest logs will tell you whether the term plan you built in Week 1 is real, and correcting it now costs far less than discovering the gap at the midpoint.

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