The one-page or it dies rule

Most hotel SOPs are 8-14 pages long, written in Word, kept in a binder behind the front desk, and consulted by exactly nobody. The reason is simple: a front-office agent dealing with a check-in queue does not have 4 minutes to find the right SOP, scan three columns of process language, and act. A one-page SOP gets read. A multi-page SOP becomes a wall ornament.

The rule

If an SOP cannot fit on a single page — 11pt font, half-inch margins — it is two SOPs that have been glued together and should be split. There is no exception to this rule. Every property I have worked at had multi-page SOPs that nobody used; every property I have rebuilt SOPs at moved to one-page versions and watched compliance jump from 35% to 80% in 90 days.

What goes on the page

That is the entire structure. Nothing else. No "background context," no "history of the procedure," no "company values." Those belong in onboarding documents, not at the moment of action.

Why the rule works

A one-page SOP can be scanned in 18 seconds. A 14-page SOP requires 4 minutes to navigate. At the front desk during a 16:00 arrival peak, you have 18 seconds. The SOP that fits in 18 seconds is the SOP that gets followed.

A second-order effect: writing a one-page SOP forces the author to identify what actually matters. The 14-page version was long because nobody was willing to say "this step is more important than that one." The one-page discipline makes the decision visible — and produces a sharper procedure for it.

One page or it dies. The discipline is in the rewrite, not the original draft.