NURS 8710 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 Doctoral Seminar I, 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.

Worked reasoning: turning the question into a standing weekly routine

By Week 2 the reasoning question stops being a one-time exercise and becomes something you re-ask on a schedule. Work it as a loop with four named slots rather than as one long study block. The first slot is search and capture, where the live prompt is re-read and candidate sources are pulled. The second is appraisal, where each candidate is reduced to design, population or setting, result, and limitation. The third is drafting, where only appraised material is allowed on the page. The fourth is checking and replying, which is protected time rather than whatever is left.

The point of naming the slots is diagnostic. When a Week goes badly, one slot ate the others, and knowing which one is the difference between a real fix and a vague resolution to start earlier. Doctoral reading is slow, so the appraisal slot is usually the one that gets squeezed and the one that most needs a floor. Write the four slots into the calendar with the same seriousness as a deadline, then record after the Week which slot overran. Which activities exist in the Week, and when they close, is decided by your classroom rubric and the registered calendar.

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 as a recurring instrument

Rubrics in a seminar sequence tend to repeat their structure even when the prompts change, so the second Week is the right moment to build a reusable reading of them. Take the rubric attached to the current activity and sort its rows into three families: rows about substance, rows about reasoning and evidence, and rows about scholarly presentation. Note which family carries the most weight in this activity. That distribution, more than the topic, tells you where the hours should go.

Then convert each row into a question with a yes or no answer, written in your own words, and keep that question list where you draft. A row about evidence becomes a question such as "does every analytical claim in this draft carry a source that actually tested it." A row about organization becomes "can a reader find each required part without hunting." Yes or no questions are harder to fool yourself with than adjectives. Do not assume this Week's rows match last Week's; re-open the live rubric and confirm, because the wording, the weighting, and the row set are decided by your classroom rubric each time.

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 search record and a running evidence table

A cadence that holds up needs a search you can reproduce. Each time you go looking, record the database or index used, the exact terms and combinations, the filters applied, the date range, the number of results kept, and the reason for keeping them. That record costs a few minutes and repays them whenever an instructor asks how a source set was assembled, or whenever a later Week needs the same ground covered again without starting over. It also exposes a narrow search early, while there is still time to widen it.

Feed everything that survives into one running evidence table rather than a folder of downloads. Give each entry purpose, design, population or setting, result, limitation, and the exact sentence it can support. Sources that fail to yield that last column stay in the table marked unused rather than being deleted, because a later Week may find the analytical role they were missing. Peer-reviewed primary studies and reviews carry the analytical load; unsigned web summaries and undated pages do not belong in doctoral work at all. What citation style governs the final list is decided by your classroom rubric.

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.

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 the repair for each

The first trap is search sprawl. The topic is interesting, the database is generous, and two hours disappear into collecting rather than appraising. The repair is a hard stop expressed as a number rather than as a feeling: decide before searching how many sources this activity actually needs to satisfy its rubric rows, gather slightly more than that, then close the database and appraise what you have. If appraisal reveals a genuine gap, run one more targeted search against the named gap instead of browsing again.

The second trap is drafting from abstracts. Abstracts are written to attract readers and routinely omit the limitation that would disqualify the study for your purpose. The repair is a rule with no exceptions: nothing enters the draft until its methods and limitations sections have been opened and its evidence-table row is filled in. A source you have only read the abstract of is a candidate, not evidence.

The third trap is treating replies as an afterthought when the live Week contains a discussion. Contributions written at the deadline tend to agree pleasantly and add nothing. The repair is to draft replies in the checking slot, from the same evidence table used for the initial post, so a reply can compare designs, apply an idea to a different setting, or name a boundary. Reply counts, windows, and rules are set by your classroom rubric.

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