PRAC 6841 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 II, 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.
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.
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.
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.
Revising by criterion rather than by feel
Revision at this stage should be targeted, because unfocused rereading finds sentence-level problems and misses structural ones. Work criterion by criterion. Take one rubric row, read your draft looking only for that row, and change only what that row requires. Then take the next. Reading for one thing at a time is slower per pass and much faster overall, and it surfaces the gaps that a general read glides over.
Distinguish revision from editing and do them in that order. Revision changes what the document argues and how it is organized: a claim that was never stated, a paragraph in the wrong place, a comparison that was implied but never made. Editing changes how sentences read. Editing a paragraph that revision was going to delete is the most common way to spend an evening without improving anything. Where a returned comment refers to placement documentation or evaluation, note that it belongs to the official process and act on it there, because a written draft is not where a record gets corrected.
Order the passes so the expensive changes happen first. Begin with the pass that checks whether the document answers the prompt at all, then the pass that checks whether each section earns its place, then the pass that checks evidence and attribution, then sentences, then format. Running them in reverse is the usual reason a revision week produces a tidier version of the same weaknesses. Keep a short log of what each pass changed, since the log tells you which passes are still finding problems and which have gone quiet, and a pass that finds nothing twice can be retired for this draft.
Reading the rubric row by row against accumulated feedback
Put every piece of feedback you have received this term next to the current rubric and match each comment to a row. Comments that map to the same row twice or more identify the habit to fix now, in the work still open. Comments you cannot map are usually about clarity, which belongs to whichever row governs scholarly writing in your section.
Then run a difference check. Compare the rubric attached to the current activity against the one you last worked from, since rows and weightings can differ between activities. Revising toward a remembered rubric is a quiet way to lose points on a draft that is otherwise sound. The rubric shown in your classroom for the activity in front of you is the one that decides.
Repairing a source list without breaking the argument
Late replacement of a weak source is common and usually done badly. Swapping a citation without revisiting the sentence leaves a claim supported by something that says something slightly different, which is a worse problem than the original weak source. Do it properly: read the replacement, write down what it actually supports, then rewrite the claim to match. Expect the claim to become narrower and the paragraph to become better.
While you are in the list, check consistency across the whole document. Sources should appear where their claims are rather than clustering in one section. Anything cited once in an introduction and never used again is decoration and can go. Anything you would struggle to summarize accurately should be reread or removed. Currency matters here too, since a recommendation revised while you were drafting needs the current version before submission.
Revision-stage pitfalls and their fixes
The first pitfall is cosmetic revision, where wording changes and the argument does not. The fix is to run structural passes first and to require that each pass produce at least one change a reader could point to as a difference in reasoning.
The second is over-revision, where repeated passes erode the through-line until sections no longer follow one another. The fix is to reread the opening and closing sentences of every paragraph in sequence after your last pass, checking that they still tell a coherent story on their own.
The third is adding new material late without rechecking the rubric rows it affects. New paragraphs can push a document past a length limit or unbalance a criterion. The fix is a final row-by-row pass after all additions, not before.
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 6841 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 6841 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.