Patron tiers and comp authority: governing comps by player value

A patron's tier says how much they may be comped. It never says who is allowed to grant it. Governing comps by player value takes both — and the authority model has to understand the player, not just the number.

Every casino segments its players by worth. A patron who turns over serious theoretical win sits in a higher tier and, quite reasonably, justifies larger comps than a casual visitor. That much is settled practice. What is far less settled is the second half of the sentence: a larger comp still has to be granted by someone authorised to grant it. Tier and authority are two different questions, and treating them as one is where value leaks.

CompWarden's AEGIS platform is gaming-literate by design: it understands theoretical win, patron tiers, exclusion lists, and gaming-specific comp types. That matters here, because governing comps by player value is impossible for a tool that cannot see the player.

What patron tiers actually are

A patron tier is a segment that ranks a player by worth. The usual driver is theoretical win — the mathematically expected value of a player's action over time — but tiers can fold in trip frequency, wallet, and history. The output is a bracket: a way of saying, in shorthand, how much this patron may reasonably be comped.

Tiers are useful precisely because they set a defensible ceiling. A host does not have to justify a suite for a top-tier whale from first principles every time; the tier already establishes that a comp of that size is proportionate to the player's worth. The tier is the ceiling. What it is not — and this is the part generic tooling misses — is permission.

Tier informs the ceiling; authority enforces it

A higher tier justifies a larger comp. It does not, by itself, hand anyone the power to grant it. Someone must still hold the delegated authority for that amount, that comp type, that patron. Worth sets the ceiling; authority decides whether this person, right now, may reach it.

AEGIS resolves its delegation-of-authority matrix at runtime, and the matrix can factor both role and patron tier. A host's limit for a mid-tier player and the same host's limit for a top-tier player need not be identical — authority can scale with worth while still being checked on every request. If a comp sits inside the requester's resolved limit, AEGIS approves it in real time, an authority decision under roughly five milliseconds. If it exceeds that limit, the request escalates automatically up the reporting line until it reaches someone whose authority covers it.

Cross-property recognition

Patron worth, tier, and wallet are tenant-wide in AEGIS, not siloed per venue. A patron recognised as top-tier at one property is recognised as top-tier across the enterprise. That is how it should be: a whale does not become a stranger by walking from the flagship to a sister property down the strip.

Authority honours that recognition consistently rather than resetting the patron to zero at every door. The same tenant-wide tier that raises the ceiling at one property raises it at the next, and the same matrix governs who may grant against it. The patron's standing follows them; so does the discipline around it.

Preventing tier abuse

Governing by player value creates an obvious temptation: inflate the tier, justify the comp. If tier sets the ceiling, mis-stating a patron's tier quietly raises that ceiling. The defence is not suspicion — it is proof.

Because AEGIS seals every decision to an immutable, cryptographically verifiable audit trail — hash-chained and immudb-anchored — the patron tier and worth used to justify a comp are recorded alongside the approval. An outsized comp granted on an inflated tier is not lost in a spreadsheet; it is a visible, queryable record that Finance, Audit, and regulators can interrogate directly. The behaviour that would otherwise hide inside "player value" becomes the most auditable part of the decision.

Why generic approval tools fall short

Corporate delegation-of-authority tools were built to approve invoices and purchase orders. They understand a vendor, an amount, and a cost centre. They do not understand a patron — not theoretical win, not tiers, not exclusion status, not the gaming-specific comp types that make up floor reinvestment. Bolt one onto a casino and it can enforce a flat dollar limit, but it cannot let that limit scale with a player's worth, because it has no concept of worth.

Governing comps by player value therefore needs an authority model that is gaming-literate from the ground up. AEGIS reads the patron's tier and worth as first-class inputs, runs exclusion and responsible-gaming checks before any incentive reaches a patron, and resolves the authority decision against a live org chart. It complements the casino management system rather than replacing it — the CMS still calculates worth and issues value; AEGIS governs whether the grant is authorised and proves it afterwards.

Tier meets authority

Read the columns together and the point is plain: neither question answers the other. A well-built approval matrix is what lets the two meet — worth raising the ceiling, authority guarding the grant, and every decision sealed so the whole thing holds up later.