Enter Exam Week with a Checklist, Not Anxiety

Why this matters

Peaking means arriving with skills fresh and judgment calm. Cramming new domains in exam week adds fragile knowledge that fails under pressure while stealing sleep that steady hands need. The checklist replaces worry with verification: everything decided in advance gets decided well.

Concepts

Taper the final seven days: no new domains, only retiring drills plus one light mock early in the week for rhythm. Daily load drops while sleep, food and movement rise in priority: the brain is the test equipment and it needs maintenance. Logistics lock by mid-week: ID valid and at hand, connection tested with a backup (tethered phone), quiet room booked and interruption-proofed, exam rules re-read (breaks, ID checks, allowed resources).

Rituals rehearse until boring: the five-minute reading pass, the two-minute flag rule, the ten-minute closing sweep. Boring is the goal; novel decisions under pressure are where points leak. The night before ends early with the checklist ticked, not with one more mock.

Worked example

Exam Friday, the week that works:

Mon: light mock (rhythm only) + miss review, 2h max
Tue: retiring drills only (miss log), logistics lock: ID, connection + tether test
Wed: flag-rule + sweep rehearsal on old tasks, room booked, rules re-read
Thu: rest. One 30-minute command warmup, early night, checklist ticked
Fri: normal morning, early login, reading pass first, procedure carries you
Banned all week: new domains, all-nighters, environment changes

Every item is verifiable the night before: ticked boxes, tested tether, rehearsed rules. Nothing left to decide means nothing left to worry about.

Exam notes

A new mock the night before can only donate anxiety: scores wobble and wobbles stick. Environment changes (new keyboard, new chair, new room) in exam week add friction exactly when smoothness matters. And backup connection untested is no backup: test the tether Tuesday, not Friday.