September 17, 2026

Running a State Draw Campaign Without the Two-Tab Spreadsheet

A state draw campaign doesn’t start with a hunter walking into camp — it starts months earlier, usually in the dead of winter, with an outfitter working a phone list of last year’s clients and this year’s leads, asking who wants in and for what unit. Most of that campaign still lives in a spreadsheet with two tabs: one for who’s applying and what they picked, one for who got drawn. The trouble isn’t the spreadsheet itself so much as what tends to collect inside it once a season or two goes by — card numbers sitting a couple of columns from state-portal passwords, next to a customer ID number that, more often than anyone realizes, embeds someone’s date of birth. None of that is what an outfitter set out to collect. It’s just where a phone-worked campaign’s paperwork ends up living when there’s nowhere better for it to go.

Draws, the tracker inside Hunt Outfitter built for exactly this campaign, gives that information a home that doesn’t ask an outfitter to hold data it has no business holding. It’s a Business-plan feature, and it’s marked Beta in the app today — new enough that some edges are still getting smoothed, not so new that outfitters aren’t already running real campaigns on it.

A campaign that starts before there’s anything to book

Draw hunts run backward from the rest of an outfitter’s calendar. The hunter has to be drawn before there’s a hunt to sell, so the campaigning happens months ahead of the season it’s for, and an outfitter is chasing applicants and deadlines while the rest of the operation is between seasons. Draws is built around that shape: a cycle is one campaign — one outfitter, one state, one license year — and it holds the pieces every campaign needs to reference, from the outfitter’s own registration number to the attach code hunters put on their applications to land in that outfitter’s pool. Because states commonly reissue the attach code every year, the cycle exists per license year rather than as a standing setting, so last year’s code can’t accidentally get reused.

The tracker covers two states today, New Mexico and South Dakota, reflecting where the outfitters running campaigns through Hunt Outfitter actually apply. If yours is elsewhere, the honest answer is that it isn’t covered yet.

Building the list and working it by phone

A draw campaign is, at its core, a list that gets worked one call at a time, and Draws treats it that way rather than pretending the process is more automated than it is. Applicants come from existing clients or from an import, and from there the tracker is built around the log-and-move rhythm that a phone-worked list actually runs on: call someone, note what happened, move their status, set a date to chase them again if they haven’t decided. Left alone, that list defaults to showing only the people who still need something from you, which is the difference between a tracker you open once a week and one that quietly becomes a second spreadsheet nobody trusts.

Each hunt code an outfitter is watching gets catalogued once per cycle, typed the way it’s said on the phone rather than however the state’s own system formats it, so the terms an outfitter’s staff already use are the terms that show up in the tracker.

What gets recorded — and what a hunter chose

Opening an applicant is where the actual application gets recorded: their ranked hunt-code choices (most states allow three, plus a fourth quadrant option for deer and elk), which party they applied as part of, their application and attach numbers, and the fee arrangement that was agreed. That last piece matters more than it sounds — a hunter might pay their own way, an outfitter might front the fee and reimburse it after the draw, or a client might be reading their card number over the phone once, which Draws records as a receipt (last-4 and card brand) rather than as anything resembling a stored payment method. Relationship labels — deposit holder, premium member, friends and family, whatever categories an outfitter already uses to think about its client list — carry over onto the applicant record and can filter the tracker, since those labels describe the relationship rather than the campaign and outlive any single draw year.

The part that isn’t a spreadsheet column: a hunter’s state-portal login

Some campaigns run through submitting on the hunter’s behalf, which means an outfitter sometimes ends up holding a hunter’s actual login to the state’s licensing website. That’s a different category of sensitive than an application number, and Draws treats it as one: a hunter’s state-portal credentials live in their own table, encrypted at rest under a dedicated key that isn’t shared with anything else in the system, and nothing about that table tolerates being read in plaintext by accident — there’s no legacy fallback to fall back on, because the table was built encrypted from day one.

Viewing a stored credential is restricted to owners and admins, and every reveal gets logged to the activity record before the value is decrypted, not after — so a reveal that somehow failed to get logged simply doesn’t happen. Reveals are also rate-limited, because a legitimate use of this feature looks like submitting one application at a time on the phone, not paging through a client list. Once revealed, the values sit on screen for a minute and then clear themselves, so a credential isn’t left displayed on a screen that’s already moved on to the next call.

What’s deliberately never stored

The clearest design choice in Draws is what it refuses to hold. There’s no card-number field anywhere in the feature — not because outfitters wouldn’t want one, but because the moment a full card number gets stored, an app is in a different, heavier compliance category than a booking tracker has any reason to be in, and storing a security code after a transaction is authorized isn’t something that’s allowed at all regardless of category. So the fee panel captures the receipt, not the payment method: last four digits and the card brand, enough to answer “which card was that?” without ever holding the card itself.

That same discipline extends to importing an existing spreadsheet into Draws. If a file still has the columns a hand-built tracker tends to accumulate — a login column, a customer ID column, a card or expiry or CVC column, a Social Security number — the whole upload gets refused rather than silently stripped, and every cell in every row is checked for something that looks like a card number or a Social Security number before any of it gets written. The point isn’t to catch a deliberate attempt to smuggle sensitive data in; it’s to catch the ordinary case, where a card column has been sitting two columns over from a password column for years and nobody thinks about it anymore until it’s asked to be imported somewhere new.

Neither the tracker nor Hunt Outfitter decides who applies

One thing Draws deliberately doesn’t do is take a position on whether an outfitter should be the one submitting an application on a hunter’s behalf, or whether the hunter should do it themselves. That’s a question between an outfitter and its own state wildlife agency, not something a booking platform is positioned to answer, so both paths are built as equally first-class options, and an application starts out undecided rather than defaulting to either one. If your outfit already has a policy on who submits, Draws tracks whichever one you use; if you’re still figuring it out, “undecided” is an honest place for a new applicant to sit until you do.

From a drawn name to a booking

When results come in, Draws records them applicant by applicant — drawn, unsuccessful, or not yet known for imported history where the outcome was never captured — and rolls them up into a matrix of who applied for what and who actually drew it, so an unmapped choice shows up as its own line instead of quietly disappearing from the view. A drawn applicant doesn’t turn into a booking automatically; the tracker prefills the normal booking form with what it already knows and links the two records once the booking is created the same way every other booking on the platform is. The draw campaign and the booking calendar stay connected without the tracker pretending it can skip the steps an outfitter would take anyway — the same discipline that runs through the rest of a pre-season setup, where a drawn name is just one more thing that has to land cleanly on the calendar before opening morning.

Where this lives

Draws is a Business-plan feature and is currently marked Beta — see pricing. It sits alongside the rest of what an outfitter has to have in order before a season starts, including the state-specific registration questions covered in our Colorado outfitter requirements guide — Colorado isn’t a supported draw state in Draws today, but the compliance instinct is the same one. For the full walkthrough, including the import rules and how the credential vault works in practice, see the Draw Applications help article. Start free or book a demo.

Start free on the Starter plan — or try a paid plan free for 14 days.