Facebook Giveaway Winner Picker for Mixed Entry Lists

Bring your prepared list to the free Giveaway Winner Picker. Paste an entrant on each line, or import a UTF-8 CSV and choose its entrant and comment columns. The picker processes the supplied records in your browser; it does not open Facebook posts, retrieve comments, check Page followers, or contact winners. Collect and assess submissions separately, then use the review stage to confirm exactly which identities and entries will take part in the draw.

Start with the announcement and a map of accepted submissions

In our example, a ceramics studio offers two pottery kits during an open weekend. The announcement accepts an answer under one named Facebook post or a completed entry card at the studio desk. Before copying anything, the organizer records the post reference, the desk-card collection window, and whether someone using both routes receives one chance or two. The published entry arrangement determines that choice.

Make a small source map in the working sheet. A source value might be ‘announcement comment’ or ‘Saturday desk card.’ Give each source batch a reference, such as the collection date and the initials of the person who prepared it. These details do not need to be imported into the picker, because its calculation uses the entrant column and the selected comment column, not your extra administration fields.

Keep neighboring activity outside the map unless it was an accepted route. A visitor asking about opening hours is not automatically entering for a kit. A comment on a reminder post is not necessarily a submission to the original announcement. Likewise, a message thanking the studio for the weekend should not become an entry merely because it arrived during the campaign. Resolve the meaning against the invitation, rather than treating every interaction as participation.

Write the closing moment with its date and time zone, and distinguish it from the later collection time. A desk assistant may transcribe Saturday cards on Monday, but Monday is not their submission date. If a card has no dependable timing information, flag the uncertainty instead of inventing a timestamp. The picker cannot decide whether a handwritten card arrived before closing, so this evidence belongs in the preparation stage before the final sheet is approved.

Read the Facebook discussion beyond the first visible comments

Facebook’s displayed discussion is not simply a ready-made entrant file. Meta explains that public comments can be ranked using relevance and interaction signals, while Page moderation can also change visibility. Begin with the actual announcement and inspect the comment-order controls available there. Expand additional comments and relevant reply branches. A screen showing a few prominent answers is useful for reading the discussion, but it does not establish that you have captured every submission your campaign accepted.

Check moderation context with the person responsible for the Page. Facebook documents keyword blocking that can hide comments containing configured words. A hidden answer and a late answer are different preparation questions. Review accessible records under the same entry criteria rather than assuming visibility alone settles eligibility. Do not add records that you cannot actually inspect, and do not describe your prepared sheet as complete if the organizer knows part of the accepted submission route remains unresolved.

Keep the comment author separate from names mentioned inside their text. If Nia writes ‘I would make a blue bowl with Sam,’ Sam is not a second entrant unless Sam independently submitted through an accepted route. Put Nia’s chosen identifier in the entrant field and the answer in the comment field. Copying every visible name from a discussion can accidentally enter tagged friends, replying staff, and people merely discussed by other participants.

Use a second pass for omissions, not a fresh uncontrolled copy of the whole conversation. Compare the source references already logged, look for unreviewed branches, and add only records that have not been captured. Overlapping collection passes are a common source of identical rows. If two organizers divide the work, assign explicit portions and reconcile the boundary. This is easier to explain than importing two complete lists and hoping duplicate removal repairs every collection mistake.

Turn the studio sheet into a focused import

Build a master sheet with separate columns for entrant, comment, source, submitted time, and preparation decision. Keep the original transcription available while working on a draw copy. An entry card might contain a delivery address or telephone number, but neither is needed for random selection. Leave those details in the studio’s separate contact record. A minimal draw file reduces the amount of personal material that could later appear in an exported full record.

Choose the entrant value deliberately. Facebook display names can be shared by unrelated accounts, and offline names can be incomplete. Where the source allows you to distinguish them, assign stable labels such as ‘studio-014’ and ‘studio-015’ and retain the mapping privately. A label is an identifier supplied by the organizer, not a verified Facebook identity. Do not merge two people because their names look similar, or infer that an offline entrant matches a commenter from an email address.

Save the draw copy as UTF-8 CSV with a header row, then select the actual entrant and comment columns during import. Extra fields do not become conditions. In particular, a column saying ‘eligible: no’ will not silently exclude that row, and a submitted-time column will not enforce your deadline. Remove out-of-scope records from the import copy or use supported entrant exclusions where appropriate, while preserving the explanation in the master sheet.

Check quoted text and line breaks after import. An answer such as ‘Blue, with a white rim’ belongs in one comment cell, not two separate fields. Let the spreadsheet’s CSV export handle commas and quotes instead of manually joining cells. For a very simple list, paste one identifier per line instead. The tool accepts up to 10,000 rows within two megabytes; entrant identifiers allow 100 Unicode code points and comments allow 1,000. These are picker limits, not Facebook limits.

Reconcile 128 collected rows before choosing a chance model

Here is a fictional reconciliation you can reproduce in your own notes. The studio collects 96 comment records and 32 desk-card records, giving 128 raw rows. Five rows lack a usable entrant identifier, seven arrived after closing, and six belong to excluded staff identities. In this example those groups do not overlap. Removing them leaves 110 rows. Eight further rows are accidental exact copies from overlapping collection, so the reviewed pool contains 102 eligible entries across 90 distinct supplied identities.

The count of 90 is not a claim that the tool has discovered 90 real people. It means the prepared identifiers resolve to 90 identities under the chosen normalization settings. Resolve known transcription differences before the draw, and avoid collapsing genuinely different sources just to get a tidy number. Trimming surrounding spaces and applying Unicode NFC makes equivalent text forms consistent. Optional case folding and leading-at-sign removal should reflect how you prepared identifiers, not serve as guesses about ownership.

An exact duplicate combines the same normalized entrant with the same trimmed, NFC-normalized comment. Two different answers from the same identifier are therefore not exact duplicate rows. With duplicate removal enabled, repeated copies of one answer can disappear while distinct accepted answers remain. With it disabled, identical eligible rows can count repeatedly in entry-weighted mode. Check why the copies exist: eight transcription copies should not become eight extra chances simply because a setting permits repeated rows.

Excluding an entrant removes all rows that match that normalized identity. If a staff member commented twice and also left a desk card under the same prepared identifier, one identity exclusion covers all three. It does not exclude another spelling or a separate account automatically. The guide to duplicates and entry rules helps separate row cleanup from the more important decision about what earns a chance. Record both decisions beside the reconciliation.

Keep one-person chances separate from repeated accepted answers

Choose unique-identity mode if the studio promised one chance for each accepted identifier, regardless of how many eligible records it supplied. In the example, every one of the 90 identities has an initial chance of one in 90. Rae’s three accepted answers do not improve that initial chance. This mode is useful when Facebook comments and desk cards are merely alternative ways to join, provided the organizer has already resolved any known cross-route identity matches outside the picker.

Choose entry-weighted mode only when each remaining eligible row is intended to earn a chance. Rae’s three rows then give an initial chance of three in 102, while an identity with one row starts at one in 102. These fractions describe the first selection only. Once Rae is selected, all three of Rae’s rows leave the pool, leaving 99 rows belonging to 89 identities. The same identity cannot take the second kit or occupy a reserve position.

Avoid using the comment keyword as a substitute for judging the invitation. A filter for ‘clay’ is a literal case-insensitive substring check, so it can match ‘claymore’ as well as ‘clay.’ It cannot understand that ‘I do not want the clay kit’ declines participation. Nor does it verify a correct answer, a tag, or a follow. Read ambiguous wording before import; use the filter only when its simple text behavior matches the prepared rule.

Mixed sources deserve a specific filter check. If valid desk cards have blank comment cells, applying a comment keyword can remove them even though the campaign accepted that route. Either prepare the necessary accepted text accurately or leave the keyword unused and complete the eligibility assessment in the sheet. Do not fabricate comments merely to pass a filter. The draw should represent the accepted submissions, rather than whichever source happened to contain the easiest searchable wording.

Review the exact pool the two kits will use

Set two winners and, for example, three ordered reserves after checking the accepted pool. Those five positions require at least five eligible unique identities, even in entry-weighted mode. The picker supports one to 50 winners and zero to 50 reserves, with the combined total limited by the number of available identities. More rows do not create more distinct recipients when many rows belong to the same entrant. Match the settings to the actual number of prizes and replacement needs.

Use review as a checkpoint with another organizer. Compare the eligible row total, identity total, duplicate treatment, exclusions, and chance model with the sheet. For the studio, inspect one desk card, one multi-answer commenter, one staff exclusion, and a pair of similarly named entrants. These spot checks test risky transformations; review all flagged records as well, rather than relying on samples to establish completeness.

Resolve a discrepancy before clicking Draw winners. If the tool reports 89 identities instead of the expected 90, look for a normalization collision or a missing identifier. If it reports too few entries, examine duplicate removal and the selected comment column. Do not change the expected total merely to match the screen. Changing an input or setting invalidates the previous review and any results or exports, so review the revised pool again before treating it as ready.

The actual selection uses the browser’s cryptographic random generator with rejection sampling for an unbiased index. There is no weaker random fallback if the secure facility is unavailable; the draw is refused instead. That selection method operates on your reviewed list. It does not repair an omitted desk-card batch or certify your collection decisions. Keep attention on both halves of the process: a well-defined pool first, followed by the explicit random draw.

Use reserves without quietly running the studio draw again

After drawing, treat the displayed reserve sequence as an ordered queue. Suppose the first kit winner cannot collect within the previously stated window. Record that outcome and approach reserve one according to the campaign arrangement. Do not select whichever reserve is easiest to reach, and do not run another draw just because a familiar customer did not win. A preset sequence makes the replacement decision understandable to the assistant handling collection the following day.

Keep selection and contact separate. The picker does not send Facebook messages, confirm receipt, check account ownership, or arrange delivery. Use the source mapping to find the intended recipient through your established contact route. A public reply from a similar display name is not enough to change the record. Confirm the connection to the submitted entry before collecting any delivery information, and keep addresses out of the public winner announcement and the general draw file.

Download the result before closing the page. A copied summary or CSV can support the short winner list; the JSON export contains the fuller draw record, and the PDF provides a readable record with guidance. Choose the audience first. The full record can include the eligible pool, comments, and exclusion reasons, so it should not be posted wholesale on the Page simply to demonstrate that a draw took place. Review exported content before sharing it.

The record includes a UTC timestamp, random draw ID, settings, counts, and the selected winners and reserves. It is an organizer-generated account of the draw, not tamper-proof evidence or a platform certificate. For a genuine mistake discovered afterward, preserve that record and explain the correction. The reserve and redraw record workflow covers how to distinguish routine replacement from a separately documented new draw.

Close the campaign with a useful studio handoff

Give the front-desk team a concise fulfillment sheet containing the approved recipient labels, prize allocation, contact status, and reserve order. Link it privately to the saved draw record rather than pasting every entrant’s answer into the handoff. If both pottery kits are identical, say so. If their contents differ, settle which rank receives which kit before drawing, because changing that allocation afterward can change what the announced selection actually means for the recipients.

Prepare the public announcement from the fulfillment outcome, not from the entire imported dataset. Thank participants, identify recipients in the agreed format, and explain any next contact step plainly. A photograph of the two prepared kits may communicate more than a screenshot containing dozens of unrelated names. Keep a private note of when winners were contacted and when a reserve was promoted so a different staff member can answer a later question consistently.

Archive the source map, approved import copy, and exported record together with a clear campaign name. The picker keeps entries in memory rather than saving them to browser storage, so refreshing or leaving is not an archive strategy. Download what the studio needs while the result is present. Store the private mapping separately where appropriate, and follow the organization’s normal retention practice rather than leaving contact details in a shared giveaway folder indefinitely.

For the next open weekend, reuse the preparation checklist, not the old entrant list. Improve whichever collection point caused uncertainty: clearer card timing, a better source reference, or a simpler repeated-entry rule. Return to the Giveaway Winner Picker with the next approved Facebook campaign list when it is ready. Other utilities remain available in the free tools directory; none replaces deciding what the new campaign accepts before collecting its entries.

Questions about Facebook Giveaway Winner Picker

Continue with another giveaway workflow

Return to the Giveaway Winner Picker to review your entries, or explore another guide below. Browse all free tools for other preparation tasks.