Prepare a reliable list before drawing, grouping, or shuffling
A repeated line can be an accidental paste, a separate ticket, or two people with the same name. Decide what each line represents before cleaning it. This workflow uses registration and invitation lists to help you check membership and then move the reviewed list into a draw, team assignment, or running order.
1. Give each entrant a distinct label
Use one entrant or eligible ticket per line. If two people are both named Alex, use labels such as “R014 · Alex” and “R027 · Alex”. A duplicate remover compares text; it cannot tell an accidental repeat from two different people with identical names.
Keep registration IDs consistent across the invited and registered lists. Use IDs alone when that is sufficient, or use the exact same ID-and-name label in both lists. “R014 · Alex” and “R014” are different text entries. Do not merge people solely because their names match.
2. Remove accidental duplicates, with matching rules you can review
Duplicate Line Remover keeps the first occurrence of each distinct line in input order. Switch to the duplicate view to inspect repeated values before deciding what to remove. The result is a unique list, not a count of people or weighted draw entries.
By default, leading and trailing whitespace is trimmed and matching is case-sensitive. Blank or whitespace-only lines are always omitted, even when trimming is off. Internal spaces, accents, full-width forms, and Unicode composition are not normalized. “Alex” and “alex” differ unless you choose case-insensitive matching. When matching ignores case, the first retained spelling is used.
Turn trimming off when spaces are meaningful. Whitespace Trimmer is useful when you deliberately want to clean more of a text block, but review its settings before applying it to IDs or names. The two list tools each accept up to 20,000 items and 2 MiB per input.
3. Compare registrations with invitations as sets
Put the invited IDs in list A and registered IDs in list B. The intersection contains IDs in both lists. A only shows invited IDs absent from registrations; B only shows registered IDs absent from invitations. These are membership checks, not a decision about eligibility.
The symmetric difference combines entries found in only one list. The union combines both lists. All five outputs contain unique entries: repeated registration lines do not increase counts. Common and A-only entries follow A’s first-seen order, B-only entries follow B’s, and combined results keep A entries before new B entries. Shared entries use the first spelling from A.
Use the same trimming and case settings when cleaning and comparing. For example, invited A = R014, R027, R035 and registered B = R027, R035, R040 gives intersection R027/R035, A only R014, and B only R040. To review edited paragraphs or line-position changes in a document, use Text Diff instead of a set comparison.
4. Copy reviewed plain lines into the next tool
Copy the chosen result as plain lines, or export a text file and copy its contents. Open the next tool and paste those lines yourself. Links between tools do not automatically transfer participant data; review the pasted count and labels again.
Lottery Draw merges identical trimmed entries. Random Group Generator and List Randomizer preserve repeated nonblank lines as separate entries. If identical lines represent distinct people or tickets, label them uniquely before the draw; if they are accidental repeats, remove them before grouping or shuffling.
5. Keep the checked input and the agreed rules
Save the reviewed list together with the matching settings and a short note about whether one line represents a person or a ticket. For a registration check, save A-only and B-only separately so follow-up work does not confuse missing registrations with unexpected entries.
The list tools process input in your browser. Reloading or leaving the page can clear your work, so copy or export results first. Website analytics and advertising are separate services described in the privacy policy. Use participant IDs when names are unnecessary.