PRAC 6587 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 Acute 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.

Turning the Week 1 inventory into a written plan

Orientation produces a pile of documents and no visible product, and the move that converts it into work is a single planning page the student writes for themselves. Use three columns of plain sentences: what the registered classroom actually asks for this Week, what has to happen outside the classroom before any of that writing can be done, and what must be true before a file can be uploaded. Acute Care Immersion II sits inside an adult-gerontology acute care specialization, so the middle column is where the dependency lane lives: group, field, clinical, residency, proctoring, feedback, or approval steps, each written as a verb with an owner and a date rather than as a reminder.

If a step depends on somebody other than the student, name that person and the request that has to go out, because those are the items with the longest lead time and the least tolerance for a late start. The first and third columns are the written layer, and they are what the rest of this manual addresses.

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.

Reading the rubric row by row in Week 1

A rubric is not a restatement of the assignment. It is the list of separate things a reader will look for and score independently, which means it should be read twice: once for the whole shape, then once row by row, slowly. After each row, write one sentence in the student's own words answering a single question: what would a reader have to see in this document to mark this row as fully met?

Two habits do most of the work at this stage. Underline the verb in every row, because a row that asks the writer to describe is satisfied by different sentences than a row that asks the writer to analyze, compare, or evaluate. Then write the row's weight beside it, because rows are rarely equal and the heaviest row deserves the first and the longest drafting session rather than whatever time is left. Whatever the rows turn out to be, the rubric posted in the registered classroom decides; a rubric saved from another section or another term is not the one being scored.

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.

What counts as a scholarly source here, and how it enters the draft

In a course positioned in acute care practice, source quality is judged less by where a citation came from than by whether it can carry the specific claim it has been attached to. Before a source goes near the draft, record the fields the class method names: the source, its date, its authority or design, its population or setting, the usable finding, the limitation, and the exact claim it supports. Assigned readings come first wherever the live activity requires them, and current authoritative or peer-reviewed support is added only where a claim needs it.

The aim in a first Week is a short working file of well-described entries rather than a long list of titles. A source enters the draft attached to a sentence that already exists, never the reverse; if no sentence in the plan needs it, the entry stays in the working file and out of the reference list. Any source whose usable finding cannot be written in one line has not been read closely enough to cite.

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.

The line between this manual and the student's own record

Immersion coursework has two layers and only one of them is written at a desk. The placement layer belongs to the student alone: the activity performed, the time it took, the encounters that occurred, the site, the preceptor, the evaluations, the signatures, and every entry in whatever tracking system the program requires. Nothing on this page reconstructs, estimates, drafts, or illustrates any part of that record, and no wording here should be read as a model of what such a record contains.

Where a Week's work depends on placement activity, the activity itself is the student's to perform, document, and verify with the people who own the process. This manual covers only the writing around it: how to plan a deliverable, how to organize notes the student took, how to read the rubric, and how to prepare for a conversation. Nothing written here indicates that any hour, encounter, or competency has been met.

7. Run the Week 1 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 1 pitfalls and the fix for each

The first pitfall is reading the syllabus as a schedule and stopping there. The syllabus, the calendar, the rubrics, the announcements, and the resource list form one control packet, and the detail that changes a plan often sits in an announcement rather than in the calendar. The fix is to capture all of them into a single ledger in one sitting, and only then to plan.

The second is assuming the Week repeats the structure of an earlier course in the specialization. Codes recur across programs and sections, and structures do not travel with them. The fix is to rebuild the control table from the registered classroom even when the layout looks familiar.

The third is letting program and placement steps sit unstarted because the writing feels more urgent. Those steps usually have the longest lead time and depend on other people's calendars. The fix is to send the first request during Week 1, log the date it went out, and keep that lane visible beside the writing lane for the rest of the quarter.

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.

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