It starts with four columns
The first version is innocent: employee name, office, gift, status. Then somebody asks whether the hoodie comes in different sizes. Remote employees need addresses. The hamper supplier asks for dietary requirements. Finance wants cost centres. Someone adds a delivery tracking column. Before long, the Christmas gift spreadsheet has become a small internal system.
There is nothing inherently wrong with a spreadsheet. It is flexible, familiar and often the fastest way to coordinate a one-off task. The problem is what the spreadsheet reveals: HR is manually carrying data and workflow that the reward mechanism itself does not know how to handle.
Every extra column is a clue about an exception the programme has pushed back onto the people team.
The size column is really a choice problem
Clothing makes the issue obvious. If the company chooses a hoodie, HR now needs to know everyone's size. If there are colours, cuts or styles, the number of variables grows again. The spreadsheet exists because the employer selected the final item before asking the recipient.
The same logic applies beyond clothing. Dietary notes exist because the company selected food. Device preferences exist because the company selected technology. 'Can I swap this?' exists because the company selected something the employee would not have selected.
Sometimes that trade-off is worthwhile. But it should be recognised as a design decision, not an unavoidable feature of employee gifting.
Addresses become sensitive operational data
For distributed teams, home addresses can become the most awkward column. HR may already hold an address for employment purposes, but that does not automatically mean an old HRIS record is the best fulfilment address for a December parcel. Employees move. People may prefer office delivery. Some records are incomplete.
Collecting fresh addresses creates another mini-process, while sharing them with suppliers introduces privacy and data-handling considerations. The fewer third parties that need employee data to complete a reward, the cleaner the operating model becomes.
This is particularly important when the programme spans several markets. Our coverage approach is designed around local reward access rather than forcing one cross-border fulfilment method everywhere.
Status columns hide the real workload
Ordered. Packed. Dispatched. Delivered. Failed. Re-sent. Collected. Returned. Each status sounds harmless until HR is updating it across hundreds of rows. The spreadsheet is now doing the work of an order-management system without the automation of one.
This is the point where the apparent simplicity of a bulk gift becomes questionable. The company bought one thing, but it is managing hundreds of individual fulfilment outcomes.
The real cost of fixed Christmas gifts includes this labour even when nobody assigns an hourly cost to it.
The swap column is the most honest one
Few columns reveal the underlying problem as clearly as 'swap requested'. An employee asking to exchange a reward is not being difficult. They are telling you that the value the company intended to give has arrived in a form that does not work for them.
A flexible reward mechanism moves that decision earlier. Instead of HR choosing and the employee swapping afterwards, the employee chooses before fulfilment begins. The budget stays controlled; the correction loop disappears.
That is a better place for choice to happen.
What the spreadsheet should become
HR still needs programme data: who is eligible, what value was issued, when it was sent and whether it was used. Those are useful management fields. Size, flavour, colour and delivery-product exceptions are different; they exist because HR is operating the shopping decision on the employee's behalf.
A modern reward workflow should keep the first category and remove as much of the second as possible. See How PeopleCredits works for the model we use: HR controls the programme, while employees shop their own eligible reward.
If your Christmas spreadsheet is already growing, do not only ask how to make the spreadsheet better. Ask which columns should not need to exist at all.
Planning employee Christmas rewards?
See how PeopleCredits gives your team one branded store while each employee chooses the reward that works for them.
Explore Christmas rewards