What really costs time with bulk invitations
There is no mass import function for invitations: mass entry of accounts is a loop of creating an account and sending the invitation, roughly 2 seconds per account. For 60 people this is about two minutes of system work. This component is negligible and should not influence the decision on the implementation date.
The real cost lies on the human side. HR must prepare a list of people with correct contact details, enter them into the loop, check which delivery channel the system reported, and hand over the link in person wherever there was no channel. Each of these steps is a separate cost item.
Structure of the cost: four items
The breakdown below lets HR estimate the time without guessing. The unit times are assumptions for a sample calculation and should be replaced with your own measurements after the first wave.
Preparing the list
Collecting first names, surnames, the account language and an e-mail address or phone number takes the most time, but it is usually done anyway, for the contract. The extra cost concerns only checking the language column, because the language decides whether the person goes to the induction training. When only the Polish training is active, an account with another language goes to the password without the induction training.
Entering the account and sending the invitation
This is the loop mentioned above: account and invitation one after another. The system time is about 2 seconds, but an operator who types the data by hand needs a few minutes per person. The calculation assumes 3 minutes per account, including a check of address correctness.
Checking the delivery channel
The invitation response gives the delivery channel: e-mail or SMS means confirmed sending, and no channel means the account was created but nothing arrived. Reading this information for each account costs in the order of half a minute, and it avoids phone calls on Friday evening.
Handing over the link in person
Where there was no channel, the operator hands over the link in person. The calculation assumes this applies to 6 of the 60 accounts, at 10 minutes each. E-mail sending is asynchronous through a queue, so the system only knows whether the message was queued, not whether it reached the inbox; this is why some people will report on their own that they received nothing.
HR time per wave of 60 accounts, by item (sample calculation)
Sample calculation for 60 accounts
Assumptions: 60 new accounts in one wave, 3 minutes of operator work per account, 30 seconds of channel checking, 6 accounts needing the link handed over in person at 10 minutes each. The labour cost rate is taken as 60 PLN per hour (illustrative assumption).
Entering: 60 times 3 minutes is 180 minutes, that is 3.0 hours. Channel checking: 60 times 0.5 minutes is 30 minutes, that is 0.5 hours. Handing over links: 6 times 10 minutes is 60 minutes, that is 1.0 hour. In total 4.5 hours, which at 60 PLN per hour gives 270 PLN per wave.
The system time of 60 times 2 seconds, that is 2 minutes, does not change the result. With four such waves in a month, the HR time costs about 18 hours, that is 1,080 PLN. This is an indicative result: if HR has a list template and performs the entry without breaks, the time will be lower, and with data collected from document scans it will be higher.
How to scale and what shortens the time
HR time grows linearly with the number of people, because there is no import. At an average of 4.5 minutes of HR time per account (4.5 hours for 60 accounts), 20 people is 1.5 hours, 40 people is 3.0 hours, and 100 people is 7.5 hours.
The biggest saving is not faster typing but fewer repeats. A correct account language, a current address and an earlier test opening of the link reduce the number of cases in which HR has to go back to the person. The activation token stays valid for 7 days, and simply opening the link does not use it up, so a test opening of the link before the wave costs nothing.
- Prepare the list with the account language before the wave, not during it.
- Open a test link before sending to the group.
- Read the delivery channel for every account and note accounts without a channel.
- Measure your own time during the first wave and use it in the calculation instead of the assumptions.
HR time by number of accounts (sample calculation)
HR time per wave of 60 accounts
| Parameter | Value |
|---|---|
| Number of accounts in the wave | 60 accounts |
| Operator work per account | 3 min |
| Channel check per account | 0.5 min |
| Accounts without a channel (link in person) | 6 accounts at 10 min each |
| System time per account | 2 s |
| Labour cost rate for HR | 60 PLN/h |
Result: 4.5 HR hours per wave, about 270 PLN; system time about 2 minutes.
Note: Sample calculation on illustrative assumptions. Replace the unit times and the rate with your own measurements; individual quotation.
Video
Frequently asked questions
Is there a mass import of invitations?
No. Mass entry of accounts is a loop of creating an account and sending an invitation, roughly 2 seconds per account on the system side.
How long does it take to send 60 invitations?
The system time is about 2 minutes. The main cost is HR work around the invitations: in the sample calculation 4.5 hours for 60 accounts.
How do we know which accounts need the link handed over in person?
From the invitation response: no channel means the account was created but not delivered. The operator then hands over the link in person.
Do these figures apply to our plant?
They are a sample calculation. The unit times and the rate should be replaced with your own measurements from the first wave.
Let's calculate a wave for your plant
Tell us the number of people and the account languages, and together we will estimate HR time and invitation channels. Pricing and assumptions are individual.
Let's talk