Measured Behaviour
Published
In every other area measured this pass the library's cautious default was the safe one. Here it is the cautious default that costs the money, and it does it without breaching a contract or failing a single check.
Fourteen blocks over a convention weekend
The measured settlement is fourteen group blocks at contracted rates well below what the house sells the same room for. Every group picked up fewer rooms than it contracted, which is normal: groups contract for the attendance they hope for.
Correct, 151 unclaimed rooms are released three weeks before arrival, the house sells all of them into a transient market that wanted 260, eight groups are billed for shrinking past their twenty per cent allowance, and the weekend totals 132,976.00 dollars.
Two options carry that: the cutoff, which decides when unclaimed rooms come back, and the attrition allowance, which decides what a group pays for rooms it never used.
A cautious default that costs forty thousand dollars
The library's default cutoff is zero, and zero does not mean release immediately. It means there is no cutoff, so every contracted room is held until the group arrives. That is the only default a library can reasonably pick: releasing a room the group still had a right to is a breach of contract, and no library should invent one.
Renaming cutoffDays alone is caught. The property's own block rule refuses a settlement in which unclaimed rooms were held past a cutoff, and the run stops.
Rename it together with the flag that enables that rule -- one adjacent line -- and the settlement completes. Measured: released 151 becomes 0, held-empty 0 becomes 151, transient demand turned away 109 becomes 260, and the weekend total falls from 132,976.00 to 92,508.00.
Forty thousand four hundred and sixty-eight dollars, and nothing anywhere reads as a violation. No contract was breached. No group was refused a room it held. The settlement foots. Every block was honoured to the letter, and a hundred and fifty-one rooms sat in it for people who were never coming.
Three names, one answer, and it is the invoice
The attrition clause is what a group pays for the gap between what it contracted and what it used. The library forgives any shrinkage by default, because charging a group that was never told is worse than charging nobody.
attritionPct, chargeAttrition and the pair of them all produce the identical result: ATTRITION-BILLED goes from 10,122.00 to 0.00 and the weekend total from 132,976.00 to 122,854.00. Eight invoices that should have gone out do not.
The property's own rule passes in every one of those arms, because it reports how many blocks were billed and zero is a number. The sentence it prints -- fourteen blocks settled, a hundred and fifty-one rooms released, no blocks billed for shrinkage -- is entirely true.
The forecast that trims the release
washPct is the shrinkage the revenue manager expects on top of the unclaimed rooms: five per cent of the claimed rooms are assumed to fall away too, so they are released with the rest.
Renaming it reverts to zero and releases 138 rooms rather than 151. The weekend total goes from 132,976.00 to 129,492.00 -- 3,484 dollars, thirteen rooms, no rule broken and no figure out of place. It is the smallest result in this file and the hardest to attribute to anything, which is roughly what makes it worth naming.
What refused, and what only moved a label
pickupRooms, contractedRooms and contractedRateUsd each make a block non-finite and the engine refuses before settling anything. That is the pattern this series has measured on every failure shape it has found: losing the value fails closed and loud, losing the meaning fails open and quiet.
groupName is the quiet one that costs nothing. The settlement is identical to the cent; the list of groups being invoiced simply reads undefined. An invoice nobody can address is not a rounding error, but it is the kind of defect a person catches on the first read.
releaseScope and the unit label were pinned equal to the library's defaults as controls and were inert as predicted, as were the enabling flag and the caller's rule on their own.
Why the safe-looking configuration is the dangerous one
It is worth being precise about what makes this area different. In the four other areas measured this pass the library default was permissive and the property's setting was the restrictive one, so losing a name loosened something. Here the library default is the restrictive one -- hold everything, breach nothing -- and losing a name tightens the property into an inventory position it did not choose.
That inverts every instinct about where to look. A reviewer scanning for loosened controls finds nothing, because nothing was loosened. The failure is a weekend of unsold rooms in a sold-out market, and there is no line on any report that says so: rooms held inside a block are not vacant, they are committed.
The nearest visible signal is the demand turned away, and a property that does not record refused transient requests has no signal at all.
What protection alone did, and what to do about it
Protection on its own changed nothing across five profiles and five areas. Everything above needed member renaming aimed at the block configuration or the block records.
Keep those names out of the regexp. If group sales runs through a marketplace listing or a partner add-in, the marketplace add-in guide covers distributing the bundle.
The design answer holds regardless of obfuscation, because a missing column in a contract import produces the same hold. Treat an absent cutoff as an error rather than as a hold to arrival, reconcile released rooms against the contracts rather than against the settlement's own totals, and record the demand you turned away -- it is the only number that moved against the property in the most expensive arm measured here. The same reasoning covers any inventory that is promised before it is delivered, as in inventory reservations.
Frequently asked questions
Does obfuscation stop group rooms being released?
Not on its own. Protection with default settings produced identical output on all five profiles. The behaviour below required member renaming aimed at the block configuration's option keys.
What was the most expensive result measured?
Renaming the cutoff option together with the flag that enables the property's own block rule. All 151 unclaimed rooms were held to arrival, transient demand turned away rose from 109 to 260, and the weekend total fell from 132,976.00 to 92,508.00.
Why does the library default to holding every room?
Because releasing a room the group still had a right to breaches the contract. A library that has not been told a cutoff cannot invent one, and holding is the only choice that cannot breach anything. It is the cautious default, and here it is the expensive one.
Does anything look like a violation when it happens?
No. No contract is breached, no group is refused a room it held, no check fails and the settlement foots. Rooms held inside a block are not reported as vacant -- they are committed. The nearest signal is refused transient demand, which many properties do not record at all.
What happens to the attrition billing?
Renaming the allowance, the charge flag, or both together produces the same result: billed attrition goes from 10,122.00 to 0.00 and eight invoices are not raised. The property's own rule passes, correctly reporting that no blocks were billed for shrinkage.
Which names failed loudly?
Three, each read individually. pickupRooms, contractedRooms and contractedRateUsd each make a block non-finite and the engine refuses before settling. Renaming the group name changed no money at all -- the list of groups to invoice just reads undefined.
What should we reconcile against?
The contracts, not the settlement. Released rooms should be checked against what each group contracted and picked up, and an absent cutoff should be an error rather than a hold to arrival. Also record turned-away transient demand: it was the only figure that moved against the property in the 40,468-dollar arm.
Related reading