10.8 Final Week Score Repair Plan
Key Takeaways
- The final week consolidates high-yield rules and repairs error patterns; it is not the time to start broad new content.
- Convert each mock result into classified error-log entries with a one-sentence corrected rule.
- Plan test-day logistics: valid ID, on-time arrival, pacing checkpoints, answer every item, and change answers only with a rule-based reason.
Final Week Objective
The final week is for consolidation, not panic expansion. By now you should know the exam shape (180 questions, 150 scored, 3 hours, 200-500 scaled score with 390 to pass), have completed at least one full timed set, and hold an error log that shows repeated weak patterns. At this point, broad rereading is far less useful than targeted repair and timed mixed practice.
Seven-Day Repair Model
| Day | Main task | Output |
|---|---|---|
| 7 | Full timed mock or large mixed set | Domain scores and an error log |
| 6 | Repair the top two clinical weaknesses | 30 to 50 targeted questions |
| 5 | Repair lab, phlebotomy, EKG, infection, or medication misses | Procedure sequence sheets |
| 4 | Repair admin, communication, legal, and ethics misses | Scenario drill notes |
| 3 | Second timed mixed set | Confirm fewer repeat errors |
| 2 | Light recall: ranges, reportable findings, order of draw, EKG leads, HIPAA, scope | One-page recall sheet |
| 1 | Logistics: ID, appointment, system check, sleep, pacing plan | Test-day checklist |
Why Consolidation Beats Cramming
In the final days, your brain retains rules better through spaced retrieval than through marathon rereading. Quizzing yourself, explaining a rule aloud, and re-deriving an answer all strengthen recall under pressure, whereas highlighting and re-reading build false confidence. Keep new content to a minimum; a brand-new topic learned the night before is unlikely to stick and may crowd out a rule you already half-know. The objective is to make your existing knowledge reliably retrievable when a disguised, multi-domain stem appears, not to chase the few unfamiliar facts that might never be tested.
Error-Log Scoring
Do not just write "wrong." Classify the miss as knowledge, sequence, calculation, scope, safety, documentation, communication, or pacing. Then write the corrected rule in one sentence. A useful entry reads: "An underfilled light blue tube may invalidate coagulation testing because the blood-to-additive ratio is wrong." That beats "study blue tubes," because it captures the reason the error matters and is recallable under pressure.
Test-Day Execution And Logistics
Pacing
With 180 questions in 180 minutes, you average one minute per item, which is generous. Set checkpoints: aim to be near question 60 by the one-hour mark and question 120 by the two-hour mark. Answer every item because there is no penalty for guessing, and flag only those that genuinely benefit from a second look. Change an answer only when a specific rule supports the change, never on a hunch or because an option is the longest.
Logistics Checklist
- Confirm whether your session is at a PSI test center or online proctored, and the start time.
- Bring valid, government-issued photo ID; the name must match your NHA registration.
- For online proctoring, run the system/webcam check the day before and clear your workspace.
- Arrive early (or log in early); plan for traffic, parking, or connection issues.
- Sleep the night before matters more than one extra hour of cramming.
During Scenarios
For every clinical scenario ask three questions in order: What is the assistant allowed to do (scope)? What protects the patient first (safety and escalation)? What should be reported, clarified, or documented? This sequence resolves most "what is the first or next action" items because the safest in-scope step almost always outranks the fastest or most reassuring one. Read the full stem before the options, underline the key clue (an abnormal value, a missing identifier, a refusal, a privacy request), and answer that clue rather than the first plausible option.
Managing The Mental Game
A three-hour exam produces fatigue, and fatigue produces careless misses late in the session. Build in micro-resets: between checkpoints, take a slow breath, roll your shoulders, and re-read the next stem fully rather than skimming. If a question stalls you, flag it, choose your best current answer so nothing is left blank, and move on; returning with fresh eyes is more productive than grinding. Avoid the trap of letting one hard item shake your confidence for the next ten. Each question is scored independently, so a single tough stem has no power over the rest unless you let anxiety carry it forward.
The Night Before And Morning Of
Stop heavy studying the evening before. Review only your one-page recall sheet, pack your photo identification and confirmation, set two alarms, and get a full night of sleep, because rested recall beats one more cramming hour. Eat a normal meal, arrive or log in early, and treat the system or check-in process calmly. Walking in with a pacing plan and a default in-scope habit for scenarios converts your week of repair into points.
Exam Cue Table
| Cue in the question | Best decision habit |
|---|---|
| Repeated miss | Classify the cause and write the corrected rule. |
| Timing drift | Use checkpoints; flag only useful review targets. |
| Final 24 hours | Consolidate ranges, safety rules, scope, order of draw, EKG leads, and logistics. |
| Tempted to change an answer | Change only when a specific rule supports it. |
Last-Minute Self-Test
Cover the right column, explain each habit aloud, and add a missed-question example with the exact first action and documentation step. Walk into the exam with a one-page recall sheet, a pacing plan, and a calm, in-scope default for every scenario.
What is the best final-week use of a full mock exam?
Which error-log entry is most useful?
During the exam, what should control whether you change an answer on review?