NURS 8750 Week 1 planning manual

1. Capture the live Week 1

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 V, 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.

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.

Worked reasoning for a Week 1 alignment spine

Doctoral Seminar V rewards alignment before it rewards prose, so the first worked pass is deliberately mechanical. Write six short lines on one page: the problem as a documented gap, the purpose as the action the work takes on that gap, the question as a sentence a reader could answer with evidence, the method as the way that question can be answered, the evidence as the body of work that method can draw on, and the implication as what changes if the answer holds. Read the six lines in order. If line three asks about something line one never established as a gap, the misalignment is already visible, and it is far cheaper to repair now than after a draft exists.

Then run the same six lines backwards. Start at the implication and ask what the finding would have to be, what evidence would produce that finding, and whether the question as written can reach it. Week 1 is the only point in the quarter where both directions can be rewritten at no cost. Save the version and the date beside the ledger built in step one, because later weeks need to show which version of the spine a given draft was built against. Whether any of this appears as a graded artifact is a question only the registered classroom can answer.

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.

What counts as scholarly source work here

At the doctoral level the useful distinction is not scholarly versus popular but what a source can be asked to do. A peer-reviewed report of an original study can support a claim about a result. A systematic or integrative review can support a claim about the state of a body of work. A theoretical or methodological paper can support a claim about how something should be studied. A professional standard, position statement, or agency report can support a claim about expectation or context but rarely about effect. Commentary and editorial writing can identify a debate and almost never settle one.

Build the intake sheet in Week 1 so that this classification becomes automatic later. For each item record the retrieval date, the database or catalog, the design, the population or setting, the single usable finding, the limitation that matters, and the one sentence the source is permitted to support. A source with no sentence beside it is not yet part of the project. Assigned readings stay mandatory wherever the current activity requires them, and the citation style named in the registered classroom governs how any of this appears on the page.

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 1 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.

Reading the rubric row by row

Take the rubric as it appears in the registered classroom and read each row three times. First read only the criterion name, to learn what object is being scored: a claim, a method description, a synthesis, a format element, or a professional register. Second read the verb, because describe, explain, analyze, evaluate, and justify are scored at different depths, and a row asking for justification will not be satisfied by an accurate description. Third read the top level descriptor and translate it into a test you can run on your own file, phrased as a yes or no question.

Write those tests as a numbered list and keep the list beside the draft. Note the point value or weight next to each so that effort follows scoring rather than comfort. Where two rows appear to overlap, decide which one owns the content and put a marker at the place in the file that answers each. Rubric wording, row count, and weighting differ by section and by term, so your classroom rubric decides; nothing on this page overrides the version your instructor posted.

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 2. 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 1, 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 2.

Three Week 1 pitfalls and the fix for each

The first pitfall is treating the syllabus overview as the activity instructions. An overview describes the arc of the term; the activity page carries the verbs that will be scored. The fix is to open both, copy the activity text into the working file word for word, and highlight every imperative before any planning begins.

The second pitfall is opening a literature search before the question sentence exists. Searching without a question returns a large, defensible-looking pile that resists synthesis, and the pile then starts to dictate the question. The fix is to refuse to run a search until the six-line spine reads cleanly, then to record the search terms that follow directly from the question wording.

The third pitfall is importing an alignment table from an earlier course and filling it in. Reused scaffolding carries assumptions that do not survive the move, and it hides the reasoning the current activity is asking for. The fix is to rebuild the table from the current prompt and the current rubric rows, keeping the habit from the earlier course and none of its content.

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

Week 1 questions