Most competition operators start out running draws from memory. It works fine for the first few. You know what needs doing, you’re doing all of it yourself, and the whole cycle fits comfortably in your head.

Then you’re running four competitions at once, you’ve hired someone part-time to help with customer service, and you realise nobody except you knows the order things happen in or what gets checked before a competition goes live. That’s usually the point where a missed step costs something real: a compliance detail skipped, a countdown email that never sent, a winner announced before the draw record was saved.

A competition is not one event. It’s a repeatable process with roughly forty discrete steps, and it runs identically every time. Which makes it close to a perfect candidate for documentation, and a good example of how process work translates directly into capacity.

Here’s the cycle, broken into the stages worth documenting separately.

Stage one: prize sourcing and verification

Before anything is listed, the prize needs sourcing, pricing and verifying. That means confirming availability, confirming the actual acquisition cost against your planned ticket revenue, and getting documentation together if it’s a vehicle or anything else with paperwork attached.

The step people skip is verifying that the prize is deliverable at the price they’ve assumed. Prizes sourced from a marketplace listing rather than a confirmed supplier have a habit of disappearing between planning and draw day.

Document: supplier contact, confirmed cost, lead time, delivery method, and who signs off on the margin before the competition is created.

Stage two: listing and pre-launch compliance check

This is the stage that most rewards a written checklist, because it’s where the legal exposure sits.

For UK operators, every competition needs a genuine skill question configured, a free entry route displayed at equal prominence to the paid route, a postal entry address with clear instructions, ticket allocation and per-customer caps set, the closing date and draw date published, and terms specific to that competition rather than generic.

Under Section 14 of the Gambling Act 2005 the skill question and free entry route are what keep the competition lawful, so this isn’t a quality checklist, it’s a compliance gate. Nothing goes live until every item is ticked and initialled.

Document: the full pre-launch checklist, with named sign-off. Include screenshots of what correct looks like, because “free entry route displayed correctly” means something specific and new staff won’t guess it.

Stage three: the launch sequence

Once the competition is live, a fixed sequence of marketing actions fires. Announcement email to the list. Announcement post across social channels. Paid campaign activated with creative already approved. SMS to the segment that opted in.

The value of documenting this is timing. There’s an optimal order and spacing, and it’s specific to your audience. Once you’ve found it, you want it repeated exactly rather than reinvented by whoever is on shift.

Document: the sequence, the timings relative to launch, the channel-by-channel copy templates, and who owns each send.

Stage four: the countdown

The final 48 hours generate a disproportionate share of entries, which means this stage is where a missed step costs the most money.

Reminder email at 48 hours. Social countdown content daily. Abandoned basket recovery running. Final call SMS in the last few hours. Someone monitoring site performance, because traffic in the closing hour can run at many times normal load and you want to know about a problem before your customers tell you.

Document: the countdown calendar, the monitoring checks and who’s watching them, and the escalation path if the site struggles.

Stage five: draw execution and verification

The draw itself needs to be transparent and evidenced, not just performed.

That means closing entries, reconciling postal and free entries into the pool alongside paid ones, running randomised selection through a verifiable method, capturing the draw record, and streaming or recording the draw if that’s part of your format.

Document: the exact draw procedure, where the record is saved, and what evidence is retained. If you’re ever asked to demonstrate a draw was fair, this documentation is the answer.

Stage six: winner contact and payout

Contact the winner privately first. Verify identity and age. Agree delivery or arrange payout. Publish the winner announcement once you have consent. Update the results page.

The order matters. Announcing before verification creates problems that are entirely avoidable.

Document: contact templates, verification requirements, consent wording, and the timeline you commit to publicly.

Stage seven: reconciliation and review

The stage almost nobody documents and everybody needs. Reconcile revenue against prize cost and ad spend for that specific competition. Log entry numbers, conversion rate, cost per entry and sell-through percentage. Note what worked in the creative and what didn’t.

Without this, you’re running competitions on instinct and won’t know which prize categories actually make money until much later than you should.

What the platform should own, and what stays a checklist

A well-built raffle platform automates a meaningful chunk of the above. Ticket caps and allocation, skill question enforcement, free and postal entry logging, randomised selection, draw records, winner announcement pages, entry confirmations by email and SMS, and the analytics for stage seven should all be functions of the software rather than tasks for a human.

That’s worth knowing when you’re choosing one. A raffle website builder that ships compliance structure, draw mechanics and marketing integrations as standard, as specialist UK providers like Nera Marketing do, removes a large number of steps from your SOP entirely rather than just making them faster.

What stays human is judgement: prize sourcing decisions, creative approval, compliance sign-off, winner verification, and the review at the end. Those are the steps worth documenting in detail, because they’re the ones where a person can get it wrong.

Why this compounds

The operators who scale in this sector are not the ones with the best prizes. They’re the ones running six competitions concurrently with the same headcount as an operator running two, because the process is written down and anyone on the team can execute it.

Document it once, at the point where you can still remember every step. It gets significantly harder to reconstruct later.