A checklist is only useful if it is finished before the test. Most December checklists are written as tasks the manager will perform in real time: answer this, confirm that, send the other. During the surge there is no time to perform tasks. The checklist has to describe rails that are already built and running, not chores waiting for your attention.

The leak is the verb. "Respond to inquiries promptly" is a hope, not a system. "Inquiry auto-response is live and tested across all channels" is a rail. The difference decides whether your checklist survives contact with December volume. Below, each item is written as a state to verify, not a task to do, because the surge does not leave room for doing.

Verify that platform messages, direct inquiries, texts, and emails all trigger an immediate, accurate first response. Test each channel yourself. An unanswered inquiry during the surge is a booking handed to a faster operator, and the gap is widest exactly when you are busiest.

Confirm holiday pricing, minimum-night rules, and gap-night logic are set in the calendar and enforced automatically. No manual overrides should be required during the window. The override you make under pressure is the revenue leak you find in January.

Walk a test booking through deposit, balance, and confirmation. Money is the step you cannot batch later, so it must run on its own. A stalled deposit during the surge is a booking quietly lost while you are looking elsewhere.

Confirm the full sequence, confirmation, pre-arrival, access, welcome, mid-stay, checkout, review, is loaded and keyed to booking dates. Staged communication is the work volume would otherwise destroy, so it must be staged before volume arrives.

Verify that anyone covering during the holidays has access to shared records and written procedures, not just your phone number. Coverage that ends at the founder is not coverage. Confirm a covering teammate can resolve a real issue without reaching you.

Confirm one view shows arrivals, outstanding payments, open issues, and unanswered inquiries pulling from every source. The dashboard's job is to surface the problem before the guest does, and that only works if it is built and tested before the surge.

Verify that double-bookings, failed payments, and cleaning misses route to a defined path with a named owner. Operators with a written exception path resolve incidents in minutes; those improvising lose hours they do not have.

A December checklist is not a list of things to do. It is a list of rails to confirm. If every item is a verified state rather than a pending task, the surge becomes execution instead of crisis. Own the rails before demand exposes the leaks, and the busiest month runs on systems, not adrenaline.

Not sure which rails are missing? The free STR Leak Scorecard scores your operation across seven categories and ranks your top three leaks, turning this checklist into a prioritized plan.