Updated：2026-09

How to Prepare a Lucky Draw List

Whether a lucky draw result is trusted is often decided before the draw takes place: an inaccurate, duplicated, or disputed list undermines credibility no matter how the winner is picked. Rather than patching things up afterwards, prepare the list up front as a clean, complete, and verifiable record. This article is a practical checklist for organizers, from defining prizes to publishing verifiable results, and explains why each step matters.

Step 1: define prizes and quotas

Before touching the list, decide the prize structure: which prizes exist, how many winners each has, whether prizes are drawn in separate rounds, and whether the same person may win more than once. These rules determine how the list fields are designed and how the draw is batched. Write the rules down where participants can see them — the clearer the rules, the fewer disputes after the draw.

Where the list comes from and its format

Lists typically come from sign-up forms, exported spreadsheets, social media threads, or offline registration. LE59 Luck supports two ways to import: paste plain text directly, or upload a CSV file. Either way, keep at least two columns: a participant identifier (e.g. registration ID or phone number) used for deduplication and verification, and a display name (e.g. a nickname or masked name) shown in public results. Keeping the two separate avoids leaking sensitive fields when results are published.

Note that the list limit is 50,000 rows, which is plenty for ordinary events; if your data is larger, split or filter it into batches before importing.

Clean and deduplicate

Do not draw immediately after importing. Clean the list first: remove headers, empty rows, and malformed lines; normalize case and whitespace in fields such as phone numbers and email addresses; and check that the columns are aligned. Then deduplicate: each participant should appear exactly once, because duplicates mean one person gets multiple chances to win — the most common source of disputes. After cleaning, verify the total row count against the expected number of participants.

Privacy red lines

Public results hide external IDs and sensitive fields, and participant lists can be published with names masked on demand — but this protection works best when the list itself contains as little sensitive data as possible. Import only the fields needed for the draw and its announcement. Do not include ID numbers, full addresses, financial details, or any data unrelated to the draw; remove unnecessary columns before importing.

Checks before the draw

Complete two checks before drawing. First, freeze the snapshot: once frozen, the list and rules cannot be changed, so the draw operates on exactly the list everyone saw. Second, confirm the seed commitment: when the draw is created, the server generates a seed and stores its SHA-256 commitment; the seed is revealed after the draw so anyone can verify the commitment matches — this is the basis of a verifiable result.

Publishing and verifying after the draw

Draws support multiple prize tiers drawn in batches, with partial and final public states; a supplementary draw forms a separate event and keeps the original winners. When announcing results, share the public results page along with the verification method: participants can check the commitment and result hashes at the public verification page to confirm the process was not tampered with. The more complete the announcement, the higher the trust.

Preparing the list is the organizer's job; the tool makes the drawing process verifiable. Open the LE59 Luck draw tool and run the whole flow from importing the list to public verification.