Race week is for confirming systems, not inventing new ones. A useful checklist protects the decisions already made in training and surfaces logistical problems while there is still time to solve them. Work from official event information and update the plan when weather or rules change.
Seven days out: refresh the official information
Download the current runner guide, cutoff table, course alerts, required gear list, parking instructions, packet-pickup rules, and emergency contacts. Send the same version to crew and pacers. Old screenshots create avoidable conflicts.
Five days out: organize systems
Lay out worn-and-tested clothing, shoes, lights, charging cables, batteries, bottles, packs, foot-care supplies, food, and permitted medications. Test lights and electronics. Build drop bags by location and a separate start-line bag.
Three days out: confirm people and transport
Review crew access, pacer meeting points, vehicles, lodging, start transportation, estimated arrival windows, and the no-contact fallback. Everyone should know what happens if messages fail.
The day before: reduce decisions
Complete packet pickup and mandatory checks, review the latest forecast and event messages, eat familiar foods, charge devices, label bags, set alarms, and place the start kit where it cannot be repacked accidentally. Avoid unnecessary sightseeing on tired legs.
Race morning: run the short list
Eat and drink what was rehearsed, address known hot spots, carry required items, confirm timing, and arrive with enough buffer for toilets and check-in. Do not add gear, supplements, or a new pacing strategy because another runner appears confident.
The practical takeaway
Race-week preparation should make the start feel simpler. Verify rules, systems, and people; resist last-minute reinvention.