How to Build a Corporate Gift Recipient List

Ask anyone who has run a corporate gifting program what the hard part was, and almost nobody says choosing the gift. Choosing the gift is the fun part. It takes an afternoon.

The hard part is the list. Who is on it, who was left off, where everyone actually is, and what happens when three people have moved and one has left the company. The list is where gifting programs run late, run over, and generate the story that gets told afterwards.

Here is how to build one that holds together — for clients, for employees, or for both.

Who should get a corporate gift?

Start from the relationship, not the org chart. Include anyone whose working relationship you would notice losing over the next twelve months — inside the company as well as outside it.

Most programs cover two groups, and it is worth naming them separately because they behave differently.

External: active clients and the people inside those clients you actually deal with, not just whoever signs the contract. Partners, referrers, and the people who quietly send you work.

Internal: employees. This is the group most often left until last and then handled as an afterthought, which is a mistake — an employee list is usually larger, more complete and easier to build than a client list, because HR already holds it. New hires who joined mid-year, remote staff who never receive anything physical, and the teams who carried something difficult are all worth naming deliberately rather than letting a headcount export decide.

What it usually does not mean is every contact in the CRM, every prospect in an open deal, or the long tail of accounts that have not transacted in two years.

The most common list-building mistake is starting from an export. An export gives you every record that exists, and the whole exercise becomes deletion — which is slow, political, and produces a list nobody feels good about. Starting from “who would I notice losing” produces a shorter list faster, and it is defensible when somebody asks why a name is missing.

Should you tier the list?

It depends on whether you have the resources to run it. Tiering adds real layers of complexity — separate builds, separate budgets, separate shipping runs — which is entirely workable if someone owns it, and a problem if nobody does.

The instinct to send something better to your most important relationships is a reasonable one, and plenty of good programs are tiered. The question is not whether tiering is legitimate. It is whether the added administration has an owner, because that is what actually determines whether a tiered program ships on time.

There is a second thing worth knowing before you decide, and it applies most to employee gifting: people judge a gift against whatever else is sitting on the desks around them. The comparison is local and immediate — not against their own expectations, and not against some notional market rate. That is what makes an uneven gift noticeable in a way an inexpensive one is not.

Which points at a more useful lever than price. Personalization usually does more work than spend does. A lower-cost item with someone's name engraved on it reads as higher implied value than a more expensive generic one — and it holds up better in exactly that desk-to-desk comparison, because it is visibly meant for one person.

So if the budget will not stretch across everyone at the level you first had in mind, personalize down rather than cutting names. Choosing an expensive item that limits how many people you can include is usually the worse trade — you end up with a shorter list and a gift that still gets compared.

How do you collect recipient addresses?

Ask the recipient. Do not infer addresses from records you already hold.

This is the single biggest time saving available, and most programs skip it. The addresses in your CRM were captured for invoicing, and they are wrong more often than anyone expects — people have moved desks, changed offices, gone remote, or left. A short form sent to the recipient (“we're sending you something, where should it go?”) is faster than verifying records, and it doubles as a soft heads-up that something is coming.

It also solves the home-versus-office question, which you cannot answer on someone else's behalf. Let them tell you. This matters most for employees — a gift sent to an office that someone visits twice a month is a gift that arrives in three weeks.

What columns does the list actually need?

Fewer than you think — but the name and address fields have to be exact, because those are what get engraved and what get printed on a label.

Column	Why it matters
Full Name	One field, spelled the way the recipient actually uses it. Robert may be Bob. If you are personalizing the item, this is the text that gets engraved — get it wrong and the gift is worse than not sending one.
Street, Street 2	Street 2 is where the unit, suite or apartment number goes. A missing suite number is the most common single cause of a failed delivery.
Zip, City, State, Country	State as a two-letter abbreviation. Country written out.
Email and phone	Carriers need a contact for exceptions. Without one, a problem quietly becomes a return.
Quantity	Usually one per person, but not always — some recipients get two, and it is easier to say so here than in an email later.
Customization fields	One column per personalized element: the logo version, initials, the name as it should appear on the item, and any per-recipient note text. This is what makes variable-data personalization possible in a single production run.

If it is easier to start from the right columns than to reshape what you already have, download our recipient list template — it is the same format we load directly into production, so nothing gets re-typed.

What do you do about exceptions?

Decide the rule before the exceptions arrive, not after.

Every list generates them: the client in a country you do not normally ship to, the person on leave, the recipient whose employer does not permit gifts over a certain value, the address that comes back undeliverable. Handled individually and in the moment, each one costs a decision and a delay, and collectively they are what pushes a program past its deadline.

Write down four rules at the start and the whole category becomes administrative rather than deliberative:

• Value limits. What happens when a recipient's company caps gift value? Usually: send the note and skip the item, or substitute a lower-value build.
• Undeliverable addresses. How many attempts, then what? Usually: one re-ask by email, then hold.
• People who have left. Send to the successor, or drop? Decide once.
• Late additions. A cut-off date after which new names go into the next send. Without this, the list never closes.

Should "who gets what" and "where it goes" be the same job?

No, and separating them is the most useful structural change you can make.

They are different problems with different owners and different failure modes. "Who gets what" is a judgment call — relationship, budget, seniority — and it belongs to whoever owns those relationships. "Where it goes" is a data problem, and it belongs to whoever can chase addresses.

Programs that combine them into one spreadsheet owned by one person stall, because that person cannot finish the data half until the judgment half is settled, and the judgment half is always waiting on somebody senior. Split them and both halves can run at once.

When should you start?

Earlier than the production deadline suggests, because the list takes longer than the gift.

There are three holiday deadlines to work back from:

Deadline	Date	What it covers
Priority	September 15	The earliest window and the least crowded. Widest product selection and the most room for custom decoration.
Standard	November 1	All products, including custom-decorated programs. This is the date most holiday programs should be working towards.
Rush	December 1	In-stock products only. Custom decoration and custom packaging are not available this late.

List-building is the unpredictable part. Collecting a few hundred addresses from people who are not thinking about your gifting program takes two to three weeks of calendar time, most of it waiting. Start the list at the same time you start choosing the gift, not after the gift is decided.

Common ways the list goes wrong

• It starts as an export. Deletion is slower than selection.
• Addresses are inferred rather than asked. Invoicing addresses are not delivery addresses.
• Exceptions get decided one at a time. Each is small; together they are the delay.
• Tiers get added without an owner. The complexity is fine; the unowned complexity is what slips.
• Nobody owns the list either. It gets added to the workload of whoever is organized and kind, usually without being taken off anything else.
• It never closes. Without a cut-off date, names keep arriving until production has to start anyway.

No minimums. One box or one thousand. Budget planner · ROI calculator · All guides and tools