When a company undergoes a merger or rebrand, managing open employee gift claims becomes a complex logistical task. The transition requires coordinating between the outgoing and new HR portals, ensuring that employees receive their entitled rewards without duplication or loss of information. Success depends on maintaining clear records of which claims are fulfilled, pending, or awaiting action, and establishing who holds responsibility for each stage of the process. This guide outlines the steps for transitioning these claims, emphasizing the importance of distinguishing between open invitations, accepted selections, and shipped orders. It provides specific scenarios for keeping old claims active versus moving them to a new system, ensuring that privacy commitments and legal obligations are upheld throughout the handover. To begin the transition, identify the specific record the employee is inquiring about. Use the original program and claim number to link the invitation, employee selection, and warehouse records. Relying solely on an employee's name or work email is insufficient, as individuals may hold multiple valid awards or have changed contact information. A stable internal reference number is essential for accurate tracking. Document each claim with concrete facts: the offer details, deadlines, selection status, and the last known action by the fulfillment provider. This log should indicate when each data point was verified. Requests for updates from the provider should focus on activities occurring up to the handoff time, such as new acceptances or shipment updates, which can change an open invitation into a completed order. Investigate discrepancies by asking the warehouse for specific details: does the tracking number correspond to the correct award? Was the package merely printed or actually dispatched to a carrier? If dispatched, determine who can track its status post-merger. Discrepancies between shipping labels and warehouse reports require placement in an exception queue with a designated investigator and a follow-up schedule. At scale, assign clear ownership: HR manages original terms and eligibility, the provider confirms selections, and the warehouse confirms release and dispatch events. Procurement must identify who can access historical records after the contract ends, and finance must determine which cost center covers outstanding invoices. These roles dictate whether the help desk can resolve issues or only collect messages. In one scenario, a regional employer closes an anniversary gift program with 200 approved awards. Verification shows 123 are fulfilled, 42 invitations remain open, 29 selections are being processed, and six records have conflicts. During a cutover call, if the old provider agrees to keep the gift page active for six weeks, the team keeps open invitations and pending selections with them, moving only unresolved exceptions to the new help desk. Extending the old claim page requires precise definitions: the final date for accepting selections and the final date for investigating late deliveries. The agreement must specify who handles returns already in transit and provide finance with invoice contacts. If the provider cannot cover all obligations, narrow the population staying on the old route and decide who completes the rest. Program notices and service agreements often use different time zones and clocks. Record the specific time attached to each deadline and clarify how valid selections submitted between these windows are handled. If the agreement does not cover the entire promised claim window, inform HR and procurement immediately so they can negotiate extensions or complete affected claims before notifying employees. Before the new portal launches, test the old system from an approved account and contact support through the new channel. Ensure that HR verifies access paths for employees who have lost old mailbox privileges. This preparation allows the team to trace awards through branding changes and provide employees with specific follow-up timelines, keeping the process secure and efficient. In another case, an employer retires a co-branded site, having 71 grants to account for: 43 unclaimed, 21 accepted, and seven with conflicting states. Five of the accepted ones have shipped. The operations lead moves the 43 unclaimed records to the successor system, while the 16 accepted-but-unshipped orders continue with the original provider under a short service agreement. Before the domain goes dark, agree with the old provider on the stop time for accepting claims. Keep the claim history available for reconciliation and check for late submissions. If a late acceptance removes a record from the import list, it goes to fulfillment. The lead must compare references and confirm counts to ensure no duplicates or omissions occur during the migration. After importing the unclaimed records, the system may reject one due to unmatched contact information. The operator retains the response, disables the old claim, and corrects the contact via the employee directory. This corrected record is processed individually. If imports timeout without detailed responses, a manual lookup or provider review of the references is necessary before proceeding. Final reconciliation must account for all grants: those in the new system, those still being fulfilled, those available for lookup, and those in the exception queue. The sum serves as a check for missing groups. Matching individual references identifies specific duplicates or omissions that might cancel out in the total, ensuring each employee has exactly one live claim in the new system. Conduct a second check after the initial invitations are sent. An export marked 'unclaimed' before cutover might appear again afterward. The operator must distinguish the cutoff export from current records. Before repairing missing invitations, verify whether the claim was accepted, rejected, or deliberately excluded to maintain data integrity. Test the new path through an employee experience. Verify that the recipient can find the new page, that identity verification works, and that the offer reflects original terms. Check if support can locate confirmations using original references. Ensure that old invitations, if opened, provide a safe help route without allowing a second claim of the same gift. Use invented records to test various states: uninvited, selected-waiting-address, shipped, changed-email, and expired. Re-run the import under documented test conditions to ensure it leaves one open claim for an eligible employee and generates no new dispatch for shipped items. Save the counts and configuration details so the launch team can repeat these critical checks after the live change. Set a stop condition before recipients see the new page. If both routes accept the same claim, or if support cannot look up orders, halt new requests for that group. Keep evidence of accepted claims. If a package has left, it requires a fulfillment decision, and reverting the link does not recall the parcel. Reopening the old route requires actual release and shipment results. Document who can pause a group, confirm a shipment, or approve a replacement. Assign response times for individual exceptions that persist past the cutover. If an employee reports a broken link, the help desk should provide a reliable update timeline. This escalation plan also applies to later cases involving returned gifts or address changes. Determine how the help desk handles cases where the employee cannot use the old mailbox or the new portal. Provide agents with an approved method to check identity and retrieve original claims with limited access. Test this process for uncertainty, ensuring the agent can place cases on hold, name the reviewing team, and offer a way for the employee to check back. Maintain the handoff utility without forwarding personal details. The transition meeting requires a count and list of unresolved references. Provide each role only the information they need through appropriate systems, and plan when temporary access ends. Keep live claim links out of shared sheets to prevent unauthorized claiming or redirection of gifts. A merger may involve prior privacy promises, such as those addressed by the Federal Trade Commission in its 2014 letter regarding the Facebook-WhatsApp acquisition. For employee gift programs, provide privacy and legal owners with the original notice, vendor terms, and intended use so they can assess which information the successor will handle and what requires review. The FTC's guide on protecting personal information advises inventorying information, limiting access, and setting retention periods. Apply this by keeping full delivery details in the fulfillment system and using case references in cutover records. Close temporary exports after the transition according to retention requirements, and assign responsibility for any open returns or billing disputes. Notify employees of the change through trusted channels like the employee portal, explaining which invitations remain valid and how support changes. Advise recipients to use known websites or phone numbers to verify suspicious messages, as recommended by the FTC. Ensure these known channels function correctly before sending emails from the new domain to avoid confusing employees. Close the program only when someone can answer for every remaining gift. Upon receiving warehouse confirmation that the carrier took possession of a parcel, update the original award with the verified tracking result and direct the employee to the approved tracking channel. Keeping the employee from receiving a second invitation while the first was in transit prevents duplicate sends. The merger team can now report final counts: fulfilled awards, open invitations, pending selections with the old provider, dispatched orders under lookup, and unresolved cases. Each count must have a date and an owner. Weekly reconciliations will show state changes. When the provider finishes the last order, check the final invoice and ensure remaining returns have a contact. At closeout, have finance link any shipping, replacement, or return charges to the same claim. If an employee claims a gift never arrived, support needs the order and carrier evidence to investigate. Keep outcomes and support assignments in the restricted program record before removing temporary access, ensuring future inquiries can be resolved without searching departed colleagues' inboxes. Use the lessons learned from this transition in future Giftpack programs. When planning milestones or onboarding, consider how to identify awards after email changes, what shipping evidence support can see, and how long the provider assists after the last claim date. For ongoing gifts, confirm options with current and prospective providers before changing invitations. While this guide focuses on claims during mergers, other operational challenges exist, such as rotating API credentials to prevent duplicate orders. Both scenarios require strict controls to ensure promised rewards reach recipients without redundancy. Understanding the underlying systems—whether for tracking claims or managing digital credentials—is key to successful program execution. Physical logistics also present challenges, particularly for mobile field-service technicians. Delivery models must adapt to technicians who rarely return to base. Options include staffed depots for regular visits, truck distribution for shifting crews, vendor-packed cartons, local branch purchasing, carrier holds, and recipient-directed shipping. Carrier holds require careful management of service types and pickup hours, as packages are typically held for up to seven days. Recipient-directed shipping demands verified addresses and approved workflows to avoid misdelivery. Digital entitlements can simplify delivery but must be tested on devices actually used by technicians to ensure accessibility. Before rolling out handoff models broadly, pilot them to identify bottlenecks. Select depots with varying hours and technicians with different access levels. Test physical transfers, carrier hold retrieval, and digital link access to gather realistic timing data and reveal failure points. Defining exit criteria ensures flawed routes are discarded before widespread implementation. [1]
Transferring Employee Gift Claims After a Merger: A Step-by-Step Guide
A comprehensive guide on managing open employee gift claims during company mergers, covering record-keeping, provider handoffs, privacy compliance, and logistical challenges for…