Freeze the eligibility roster for a one-time recognition event; use a controlled, regularly refreshed roster for an ongoing program such as new-hire gifting. In either case, separate the decision that someone qualifies from the invitation, the selection deadline and the order. A current employee directory should not silently rewrite a gift that was approved against an earlier date.
The distinction becomes important when a holiday selection window stays open for several weeks. People join, change departments, leave or have records corrected during that time. Without a declared rule, two equally eligible employees can receive different treatment simply because one orders earlier.
This guide helps HR and program owners choose the rule before sending invitations. It is not a recommendation about who legally must receive a benefit. Your policy owner determines the eligible population; the company-store process should implement that decision consistently.
Publisher perspective: Brand Sauce publishes this guide from an employee-choice program perspective. The roster designs and acceptance checks below are editorial recommendations, not claims of built-in HR integrations or automated eligibility features. Confirm the actual workflow with your provider. Primary sources checked November 9, 2026. The hero is a conceptual illustration, not a live system.
Choose between three roster models
A frozen roster is an approved population evaluated against a defined date and rule. A live roster is evaluated repeatedly against changing records. A hybrid freezes the original population but admits documented corrections or additions through a separate approval process.
| Model | Best operational fit | Main tradeoff | Required control |
|---|---|---|---|
| Frozen event roster | A named annual recognition event with an eligibility cutoff | Predictable scope, but omitted people need an explicit correction route | Approved version, cutoff and exception owner |
| Live program roster | An ongoing program in which people qualify as events occur | Timely enrollment depends on reliable updates and clear repeated-event rules | Refresh monitoring and one approved gift per defined occasion |
| Frozen roster plus approved changes | A time-limited campaign expecting late HR corrections or a small supplemental cohort | Preserves the original decision, but requires someone to review changes | Change record distinguishing corrections from policy expansion |
“Hybrid” should not mean managers can add names informally. It means the original roster remains explainable while approved amendments are visible. An extra employee added because their start date was entered incorrectly is a correction. Adding everyone hired after the cutoff is a policy expansion. Those changes may both be reasonable, but they are not the same decision.
Write down four dates, not one
Start with a short program statement containing four separate time references:
- Eligibility effective time: when the person must satisfy the approved rule.
- Source extraction time: when HR produced the records used to evaluate that rule.
- Approval time: when the policy owner accepted the resulting roster or amendment.
- Selection closing time: when the recipient must submit the gift choice.
Include the time zone when a boundary matters. An extraction performed after the eligibility cutoff is not necessarily wrong, but the data must support the intended historical decision. A report containing today's department and status does not automatically tell you what those values were at last month's cutoff.
If the source cannot reconstruct the earlier state, ask HR to approve an appropriate historical report or documented correction. Do not label a current export “as of November 1” merely by changing its filename. The approval should say what the data actually establishes.
Illustrative policy wording: “This recognition campaign covers the population approved under rule R1 at the stated cutoff. The approved roster is version 1. Corrections require the HR program owner's approval. The selection deadline is a separate date. Any ongoing employment condition is defined in the campaign policy.” Replace those placeholders with decisions before launch.
Treat a changed HR record as a review signal
An automated update is evidence that data changed, not necessarily evidence that someone newly qualifies. For example, BambooHR's changed-employee endpoint returns employees whose records changed after a supplied timestamp. Its documentation says changes to any individual field, and changes to employment-status, job-information or compensation tables, can cause a record to appear.
The operational implication is ours: do not translate every changed record into a fresh gift invitation. Read the relevant approved fields, apply the campaign rule and check whether the person already has the corresponding allocation. A phone-number correction should not create another holiday gift.
For an ongoing welcome program, define the qualifying occasion—such as an approved employment start—and decide how rehires are handled. For a frozen campaign, route changes to a review queue unless the approved design explicitly allows an automatic correction. The separate guide to preventing duplicate gifts from HR imports explains how identity and occasion records can support that control.
“Live” still needs an update timetable
Do not promise immediate enrollment simply because membership is automated. Microsoft's dynamic-group processing guidance says Entra membership changes are typically processed within a few hours, but can take more than 24 hours under some conditions. That is a documented example of asynchronous processing, not a timing claim about every HR or company-store platform.
Ask your provider to identify each handoff: HR approval, source export or event, eligibility evaluation, store update and invitation release. Agree how the team sees the last successful update and how it detects a stalled handoff. “The integration is enabled” is not a freshness check.
When an employee says they should be included but the roster has not caught up, give support a review route. Avoid both extremes: rejecting the person solely because a sync is late, or issuing an unrestricted replacement code without checking the underlying allocation. If a manual grant is approved, reconcile it before the delayed automated update arrives.
Worked example: distinguish a correction from a new cohort
Illustrative scenario—not a client story or measured result: a company approves 240 recipients for an annual gift using a November 1 eligibility cutoff. Invitations open November 5 and choices close November 20.
On November 8, HR identifies three different changes:
| Change | What the program owner decides | What the operator records |
|---|---|---|
| A person met the November 1 rule but was omitted | Approve a correction to the original population | Original cutoff, correction approval and existing-gift check |
| A person started November 6 | Apply the stated cutoff, or approve an explicit expansion | Reason for inclusion or exclusion; no disguised data correction |
| A recipient transferred departments after invitation | Determine whether the transfer affects funding, eligibility or neither | Any approved cost-center change without issuing a second gift |
If the omitted person is added and the later starter is not, the approved population becomes 241. If leadership also expands the program to that starter, it becomes 242. The extra approval matters even if the price of one gift seems small: it changes the rule other similarly situated people may expect the program to follow.
For budgeting, use the approved population and a clearly defined per-recipient planning ceiling. At an illustrative $80 all-in allowance, 240 recipients imply $19,200 and 242 imply $19,360. This is allocation arithmetic, not a supplier quote, forecast of actual redemption or promise that any particular gift can be delivered for $80.
Keep eligibility separate from access and fulfillment
A frozen recognition roster is not permission to keep a former employee's corporate account active. Access removal must follow the organization's controls. Conversely, removal of an account does not by itself document what should happen to an already accepted order or an approved exception.
Define whether the program requires eligibility only at the cutoff or also at another stage, such as order acceptance. If there is an ongoing condition, state it before invitations go out and assign an owner to apply it. Do not let an undocumented nightly sync decide the question after a recipient has made a selection.
Use the company-store offboarding guide for access controls and outstanding-order handling. Here, the key record is the eligibility decision: its rule, effective time, approval and any later amendment. Fulfillment should receive the resulting instruction, not be asked to interpret an HR status code.
Keep a compact decision record
The FTC's business information-security guide recommends collecting and retaining sensitive information only for a legitimate business need and limiting access. Apply that principle by keeping the merchandise roster narrower than the HR record.
A practical minimum is the program reference, stable recipient reference, approved eligibility outcome, rule version, relevant effective date, approval reference and current invitation or order reference. The HR owner can retain supporting employment details in the appropriate restricted system. The gift vendor generally needs the approved result and the fields required to deliver the service—not salary, medical context or the full employment history.
Set a retention owner and period appropriate to the program's needs. Preserve enough controlled evidence to reconcile disputes and spending; do not distribute permanent copies of the roster across managers' personal spreadsheets. For the broader transfer design, see our employee gifting data-handoff guide.
The roster model does not dictate bulk or on-demand
A frozen population can support bulk purchasing when quantities, products and delivery destinations are sufficiently settled. That may be sensible for an identical item distributed at one event. But a headcount snapshot alone does not establish the size mix for apparel or reserve stock for employees who choose later.
On-demand production can suit a live program with uneven arrivals and varied selections, provided the exact product, decoration, destination and timing work. It does not remove the need for funding approval or a dependable eligibility record.
A hybrid can reserve a predictable core quantity while fulfilling approved late additions separately. Before buying, ask whether those later orders will use the same product and decoration, an approved equivalent or a different delivery promise. Obtain quotes for the actual volumes and destinations rather than assuming either route is cheaper.
Run six acceptance cases before invitations
Use synthetic records, not real employee data, to demonstrate these proposed checks with the operator or provider. This article reports no vendor test results.
- Corrected historical record: someone omitted at the cutoff receives a reviewed correction without moving the cutoff.
- Later starter: a person outside the frozen population does not silently gain eligibility; any expansion has approval.
- Unrelated update: changing a contact field does not issue another gift.
- Delayed update: a stale feed is visible, and a manual resolution is reconciled before automated processing resumes.
- Department transfer: a funding reassignment does not erase the original decision or create a duplicate allocation.
- Access removal: corporate access ends as required while an outstanding gift or order is routed to the approved resolution owner.
Launch when the team can explain each outcome from the record, not merely show that an invitation email was sent. For a one-time campaign, a well-controlled roster can be simpler than a live integration. For a continuing program, reliable refresh and reconciliation can be worth the additional operating work.
Frequently asked questions
Does freezing the roster mean we can never add someone?
No. Preserve the original version and approve an amendment. State whether it corrects an error under the original rule or expands the eligible population.
Should every new employee receive an open holiday invitation?
Only if that matches the approved program rule. A welcome gift and a holiday gift are separate occasions; joining one program should not silently enroll someone in the other.
Can a small team manage this without an HR integration?
Yes. An approved roster, restricted change log and accountable owner can implement the same decision model manually. Verify how the store prevents duplicate grants and how corrections reach it.
What should employees be told?
Explain the applicable eligibility rule, the selection deadline and the review contact in plain language. Keep internal HR evidence private. Someone questioning an omission needs a clear review path, not access to the whole roster.
