PRAC 6831 Week 10 planning manual
A course-specific Week workflow for capture, reasoning, evidence, student authorship, quality control, and gradebook closure.
Use accumulated feedback to repair recurring reasoning, evidence, format, or submission weaknesses before the last registered work. This page verifies a position in the Course-Based quarter calendar, not a universal assignment identity.
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.
| Control field | What to verify now |
|---|---|
| Identity | Exact course, Week, activity, and current version |
| Task | Every required action, question, audience, and deliverable part |
| Grading | Rubric rows, points, weights, thresholds, and penalties |
| Evidence | Assigned readings, source rules, dates, authority, and citation style |
| Calendar | Initial post, replies, files, approvals, due time, and time zone |
| Dependencies | Group, field, clinical, residency, proctoring, feedback, or approval steps |
2. State the Week's reasoning question
For Pediatric Primary Care Immersion I, 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.
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.
Revision as a separate pass, not a slower draft
Revision and editing are different jobs and they fail when combined. Revision asks whether the document answers the task, whether the reasoning holds, and whether the parts are in the right order. Editing asks whether the sentences are clear and correct. Doing both at once produces a beautifully written document that answers the wrong question.
Start with a reverse outline. Read the draft and write, in the margin, the single claim each paragraph makes. Then read only the margins. The sequence of claims should read as an argument. Where it reads as a list, the order is wrong. Where two margins say the same thing, one paragraph is redundant. Where a margin cannot be written at all, the paragraph has no claim and must be rebuilt or removed.
Only after the structure is settled should the language passes begin. At this stage of the term, use the accumulated criterion ledger to decide which passes matter: the weaknesses that recurred across returned work are the ones most likely to recur again, and each deserves a dedicated read of its own.
Reading the rubric row by row during revision
Revision is the moment to read the rubric as a grader rather than as a writer. Copy the rows out, read the draft with the rows beside it, and record for each row the exact location that satisfies it, named by section and paragraph. A row with no location is unmet no matter how much related material exists nearby. A row with three locations is diffuse and usually needs one promoted and the others trimmed.
Then assess the draft against the performance levels rather than the row titles, since the levels contain the actual standard. Note honestly which level the current draft would sit at and what specific change would move it, and make that change before any cosmetic work.
Finish by re-reading the posted instructions independently of the rubric. Instructions often carry requirements the rubric does not restate, and your classroom rubric decides the scored rows while the live instructions decide everything else the submission must contain.
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.
Auditing citations line by line
A revision-stage citation audit is mechanical and should be run as one uninterrupted task. Work through the document one in-text citation at a time. Confirm the item exists in the reference list. Confirm the claim in the sentence is what the source actually says, returning to the source rather than to your notes whenever there is doubt. Confirm that a paraphrase is genuinely reworded and not a lightly altered sentence. Confirm the citation sits with the claim rather than drifting to the end of the paragraph.
Then work the reference list in the other direction and remove any entry that no longer has a use. Check formatting details last, since correct formatting attached to the wrong source is worth nothing.
If the audit reveals that a claim has drifted beyond its evidence, fix the claim rather than hunting for a stronger source. Weakening a sentence to match its support is a repair, not a retreat.
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 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 10 pitfalls and the fix for each
The first pitfall is revising only what feedback mentioned. Comments are samples rather than an inventory, and an unmentioned instance of the same weakness will still be sitting in the document. The fix is to treat each comment as a category and search the whole draft for other instances of it.
The second pitfall is defensive revision, where a criticized passage is padded with qualifiers until it says almost nothing. The fix is to identify what the criticism was actually about, usually a missing join or an unsupported claim, and to repair that specific thing.
The third pitfall is late structural change with no time to re-check. Moving a section after the citation audit invalidates the audit. The fix is a fixed order of passes: structure, then content, then citations, then language, then format, with no return to an earlier stage once the next has begun unless that earlier stage is run again in full.
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.
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
What is assigned in PRAC 6831 Week 10?
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 PRAC 6831 Week 10?
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.