How to Run a Silent Auction: A Step-by-Step Checklist for Event Teams

Most silent auctions underperform for the same handful of reasons, and none of them are about the items. They are about pricing, timing and checkout. This is a practical checklist built around fixing those.

Timings assume a twelve-week runway, which is comfortable. Eight weeks is doable. Four is stressful and it shows in the total.

GiveSmart homepage screenshot
Platform setup should happen weeks before the event, not the week of it.

Twelve to eight weeks out: procurement

The goal is fewer, better items. Forty desirable lots will outperform a hundred mediocre ones, because thin bidding across a large catalogue depresses everything.

  • Set a target number of lots based on expected guests — roughly one lot per two to three attendees is a reasonable starting point
  • Prioritise experiences over objects. Things people cannot simply buy online consistently outperform retail goods, which bidders will price against Amazon.
  • Ask your board and major donors first. They know people, and personal asks convert far better than letters.
  • Record fair market value for every item at the point of donation — you need it for pricing, for tax receipting and for the item description.
  • Get donation forms signed. Chasing paperwork after the event is miserable.

Eight to six weeks: pricing and descriptions

This is where most of the money is won or lost.

  • Starting bids at roughly 30-40% of fair market value. Too high and nothing starts; too low and bidding never recovers.
  • Set increments proportionally. A $50 item with $25 increments is broken. Aim for roughly 5-10% of the starting bid.
  • Write real descriptions. “Spa basket” raises less than a specific list of what is inside, its value and why someone would want it. Describe the experience, not the inventory.
  • Photograph everything properly. One good photo per lot, consistent style, decent light. Bidders scroll on phones.
  • Consider buy-it-now prices on items with a clear retail value, set at roughly 150% of fair market value.

Six to four weeks: platform setup

  • Choose and configure your platform — see the best silent auction software for nonprofits if you are still deciding
  • Enter every item with images, descriptions, values and starting bids
  • Configure soft close — extending an item by two minutes when a late bid lands. This reliably lifts final prices and eliminates end-of-night disputes.
  • Stagger closing times by section rather than closing everything at once
  • Set up card-on-file capture at registration. This is the single most important configuration decision.
  • Test the full flow yourself on a phone, on the venue’s wifi if you can

Four to two weeks: promotion and pre-bidding

Open the auction online before the event. An auction that goes live five to seven days early accumulates bids and arrives at the event with competitive momentum already established.

  • Email your full list, not just attendees — remote supporters can bid too, and often do
  • Feature three or four headline lots rather than the whole catalogue
  • Send a reminder when bidding opens and again 48 hours before closing
  • Brief volunteers, and specifically assign people to circulate with tablets for guests who are not comfortable with the app
Handbid homepage screenshot
Opening bidding several days early builds momentum before anyone walks in.

Event night

  • Check-in captures cards. Every guest, no exceptions. This is what makes checkout painless later.
  • Display items attractively with clear signage showing how to bid
  • Announce closing times from the stage, repeatedly. Guests forget.
  • Show a leaderboard if your platform supports it — visible competition drives bidding
  • Run fund-a-need separately from the auction, ideally after dinner when the room is warm. It frequently raises more than the auction itself.
  • Close sections in waves, ten or fifteen minutes apart, to create several moments of urgency rather than one crush

Checkout: where events succeed or fail

With cards on file, the auction closes and every winner is charged automatically. They receive a receipt, they collect their items, they leave happy. Without it, you have 200 people queuing at a table while volunteers reconcile bid sheets — and a meaningful number simply leave, which turns won lots into uncollected revenue.

Have item collection organised by lot number with volunteers who know where things are. Arrange delivery or later pickup for anything bulky.

Greater Giving homepage screenshot
Card-on-file at registration turns a checkout queue into an automatic charge.

After the event

  • Send receipts with the correct tax language for your jurisdiction — for auction wins, the deductible amount is generally the excess over fair market value
  • Thank every donor of an item, individually, with what it raised
  • Thank every bidder, including those who did not win
  • Export your data into your CRM while it is fresh
  • Record what worked: which categories drew bidding, where starting bids were wrong, which lots died. Next year’s auction is built on this.

The five most common mistakes

  1. Too many items, diluting bidding across the catalogue
  2. Starting bids set too high because someone felt the item deserved it
  3. Vague item descriptions that fail to convey why anyone should want it
  4. No card on file, producing a checkout queue and lost revenue
  5. Closing everything simultaneously, creating chaos instead of urgency

Background reading: what a silent auction is, silent auction payment processing, and silent auction software if you are running enough events to justify owning the platform.

Frequently asked questions

How many items should a silent auction have?

Roughly one lot per two to three expected guests. Fewer, better items consistently outperform a larger catalogue.

Should the auction open before the event?

Yes. Five to seven days of pre-bidding builds momentum and lets remote supporters participate.

What if guests are not comfortable with mobile bidding?

Assign volunteers with tablets to circulate and place bids on request. Handled well, this is a non-issue.

Featured on Aura++