Deposits against uncertain licences: outfitter booking math

A Montana outfitter books a guided elk hunt for October. The client puts down a $4,000 non-refundable deposit in November when the hunt is twelve months away. In March, the state licence draw happens. The client doesn't draw a tag. The hunt can't happen, but the deposit is the outfitter's to keep — or is it? That depends on what the contract said, and whether the booking system tracked which hunts were conditional on a draw result.

Most outfitters operate in states where tags are limited and allocated by drawing — Colorado, Montana, Idaho, Utah, Nevada. The licensing calendar is fixed years in advance. The bookings start earlier. A deposit collected in November for an October hunt is flagged as conditional on a March draw. If the client doesn't draw, the deposit either gets forfeited, refunded, or rolled into a future hunt. That decision is a business choice, but it has to be tracked in the booking system from the moment of deposit, or you'll lose cash or goodwill in the settlement.

The deposit problem at scale

A small outfitter running five to eight guided hunts a year keeps this in a spreadsheet: one row per booking, a column for "draw result," maybe a note about whether the deposit was forfeited or rolled. An outfitter running 15 guided hunts and 40 pack-in trips across the season deals with hundreds of line items, client communication deadlines tied to draw dates, refunds or rollovers that have to happen in a narrow window before clients rebook elsewhere, and a bookkeeper who needs to reconcile actual cash against conditional promises.

The spreadsheet approach starts to fail when the answer to "what's our actual liquid balance?" depends on reading 60 rows and sorting by draw status. It fails harder when a client says they didn't receive the May refund email and you have to dig through three months of notes to find whether the refund was actually processed. It fails completely when draw results come in, you mark fifty bookings as "draw unsuccessful," and you don't have a workflow that says "send refund instructions" or "apply balance to 2027 hunt" without manual intervention per booking.

What the system has to track

A booking system built for outfitters with conditional deposits needs to capture and report on:

• Deposit date and amount, the hunt type (guided elk, rifle or archery, pack-in), the hunt dates, and the state licence draw date for that season.
• Draw contingency flag: is this booking conditional on a draw result, or is it a guaranteed hunt (private land, walk-up availability, standing appointment)?
• Draw result. When the draw happens, the booking records the client's tag status: drawn, not drawn, applied but waiting, or not applicable. This is often manual entry (the client tells you or you check the state website), but it's the keystone of the whole workflow.
• Deposit disposition. When the draw clears, the system needs to know the rule: forfeit, refund, or roll to a future hunt (and to which one). Some outfitters offer the client a choice at draw time — the system needs to capture that too.
• Reporting windows. Refunds (if owed) have to go out by a specific date. Cash that's rolled to a future booking shifts from liability to new revenue. The bookkeeper needs a report that says "these 12 bookings have drawn tags and are confirmed; these 8 were not drawn and refunds are due by June 1; these 3 are pending client decision." Without that, you're relying on memory.

The logic is straightforward, but the alternatives are not. A spreadsheet can hold this information, but it doesn't force workflow. A generic SaaS booking system built for restaurants or hotels treats "booking" as a transaction with a fixed date and outcome; it doesn't know about conditional draws or multi-season rollovers. An outfitter-specific tool like LodgeRunner or similar has some of this built in, but the cost and feature set may overshoot a small operation that really just needs deposits tracked against uncertain outcomes.

How different outfitters handle it

Some outfitters structure it as a non-refundable deposit plus a final payment due after a successful draw — that moves the risk clearly to the client and avoids the conditional-deposit problem entirely, at the cost of collecting less money upfront. Some collect a smaller deposit that rolls automatically to the next available hunt if the client doesn't draw, which keeps the client's cash in-house but requires you to track and manage that rollover. Some offer a refund if the client didn't draw, which means you need enough float to refund a block of deposits if draw season is bad across multiple hunts.

Each model has cash-flow implications and bookkeeping overhead. What matters is that whatever you choose, the system has to make it automatable. That's not a feature; it's a survival requirement. At 40 bookings a season across multiple draw dates, manual tracking is not only tedious, it's a liability — a forgotten refund or a double-application of a rollover is a customer service crisis you didn't need.

This is also why outfitter-specific appointment systems exist. A system built for outfitters treats the hunt booking, the deposit, the waiver, and the licence outcome as part of the same record. It knows which hunt dates are tied to which state draw dates. It can flag a block of bookings when draw results drop and force you through a settlement workflow. It doesn't do your business decision for you — forfeit or refund — but it makes sure that whatever you decide actually gets executed and recorded.

The SaaS vs. custom tradeoff

A commercial outfitter booking system charges a percentage of every booking or a monthly retainer — worth it if you're running dozens of hunts a year and the time savings and cash-flow clarity are real. If you're running 5-8 hunts and the draw-contingency logic is simple, a custom portal built on your own terms might cost less over time and give you the exact workflow your business needs without paying for restaurant scheduling or gear rental features you'll never use.

But whether you use a commercial system, a custom build, or a spreadsheet, the critical piece is knowing the rule and enforcing it consistently. A client who doesn't draw should either get a clear refund, a documented rollover, or a clear explanation of a forfeit policy — and the system should produce proof that you actually did it, because draw season is always chaotic and memory is the worst audit trail.

See the economics of booking commissions vs. flat retainers for guided hunts for a related conversation about how you price the work regardless of draw risk, and why spreadsheets break past 15 bookings a week for a deeper look at where manual systems stop working.