The "exception log" no one wants to keep

The exception log is the running record of every comp, every escalation, every deviation from standard procedure. Nobody likes keeping it. Every property needs it. The properties that keep one well discover patterns that save 4-6 points of departmental margin per year; the properties that do not are flying blind.

What goes in the log

Each entry: date, time, type (comp / escalation / SOP deviation), who initiated, what happened, what was done, dollar impact, follow-up required. A typical 240-key property generates 40-90 entries per week. A 4-month archive has 700-1500 entries — enough to start seeing patterns.

What patterns the log reveals

Why nobody wants to keep it

Three reasons. First, it is administrative work in a department where everyone is already managing live operations. Second, it surfaces uncomfortable patterns — including patterns about specific staff, specific departments, or specific managers. Third, the value compounds slowly — the first 60 days of logging produces no obvious insight, and managers give up before the pattern reveals itself.

How to make it stick

Two practices. First: the log is a shared digital artifact, not a paper notebook. A simple spreadsheet (one row per entry, dropdown columns for type, department, severity) is enough. Front-line staff add entries during their shift; the duty manager reviews weekly.

Second: the weekly review of the log is a named meeting (15-20 minutes, Thursday morning) with a written outcome (3-5 actions for the week based on the patterns). Without the named meeting and the written outcome, the log becomes a data graveyard. With them, it becomes the most useful diagnostic tool in the department.

The exception log is the cheapest diagnostic instrument a hotel has. Properties that keep one well discover the structural issues they would otherwise blame on individual staff for years.