InnerWeb
Skip to main content

Overdue training call-backs: how many coordinator hours automation saves

An HR or OHS coordinator who calls workers with overdue training every morning loses hours on it, and the outcome depends on whether the call reaches the person at the right time. An automatic call-back with a schedule and an attempt limit takes over the repetitive part of the work. Below is a sample calculation with explicit assumptions.

-93%
coordinator time per call-back cycle in the sample calculation
Source: sample calculation
420 h
yearly saving across 12 cycles
Source: sample calculation

How the automatic call-back works

The morning call-back of workers from external companies with overdue training can be set to a schedule, for example three attempts a day on working days. An attempt limit ends the calling after two weeks, so that automation does not become a nuisance for the worker or the company.

The call-back does not replace the company's responsibility for training, it only shortens the path to information. The training report shows people without valid training, and the status is counted at every moment of presence on the site, not only at the moment of entry. The call-back list therefore reflects the actual state, not the state from the day of registration.

How much work manual calling takes

Manual call-backs have one problem: they are repetitive, and the work has to be done every day until the person completes the training. The coordinator opens the list, calls, records the result of the conversation, returns to people who did not answer and records again. Each attempt costs several minutes, even when nobody picks up.

In a sample of 25 people with overdue training in one cycle, with a worst case in which every person is called throughout the whole limit period, the number of attempts grows quickly. That is why the calculation takes the worst case as the upper limit, not as an average.

Coordinator time per call-back cycle

Coordinator time per call-back cycleBar chart: 2,250 minutes manually and 150 minutes with automation per call-back cycle.05001000150020002500minManual: 2250 min2250 minManualWith automation: 150 min150 minWith automation
Source: Sample calculation based on the assumptions in the Sample calculation section

Sample calculation

Assumptions: 25 people with overdue training in one cycle, 3 attempts a day, 10 working days within the two week limit period, 3 minutes of coordinator time per manual attempt and 12 such cycles a year. With automation the coordinator spends 15 minutes a day on handling exceptions, that is people who answered and need a conversation.

Manual: 25 times 3 times 10 gives 750 attempts, at 3 minutes each this is 2,250 minutes per cycle, or 37.5 hours. With automation: 15 minutes times 10 days gives 150 minutes per cycle, or 2.5 hours. The saving per cycle is 2,100 minutes, or 35 hours. Across 12 cycles a year: 27,000 minutes manually, 1,800 minutes with automation, a difference of 25,200 minutes, or 420 hours.

  • manual per cycle: 2,250 minutes
  • with automation per cycle: 150 minutes
  • yearly saving: 420 hours under the sample assumptions

What this calculation does not say

It does not say that all workers will complete the training faster. It only says how much of the coordinator's work moves to a schedule. The effectiveness of the call-back depends on the quality of contact data, on whether the external company reacts to messages, and on the availability of the training in the worker's language.

It is also worth separating two concepts: the call-back of workers with overdue training and the grouped notification to the coordinator after a person is stopped at the gate. These are different mechanisms with different goals and different channels.

How to introduce the call-back without a burden

Before launch we set the hours of attempts, the limit and the content of the message in line with the plant's instruction. We treat the first two weeks as a pilot on one external company, to check how workers react and whether the numbers in the system are current.

It is worth reporting the number of unanswered calls weekly. If the rate is high, the problem usually lies in the quality of the numbers, not in the schedule.

Example calculation

Coordinator time for call-backs of overdue trainings

Assumptions
ParameterValue
People with overdue training in a cycle25 people
Attempts a day3 attempts
Working days in the limit period10 days
Time of one manual attempt3 min
Handling exceptions with automation15 min a day
Cycles a year12 cycles

Result: 2,250 minutes per cycle manually, 150 minutes with automation; yearly 27,000 versus 1,800 minutes, a difference of 420 hours.

Note: Sample calculation on illustrative assumptions; the worst case assumes every person is called throughout the whole limit period. Indicative ranges from 2025-2026 implementations; individual pricing.

Video

Frequently asked questions

How many attempts a day does the automation make?

The schedule can be set, for example, to three attempts a day on working days. The number and hours are agreed with the plant.

When does the automation stop calling?

The attempt limit ends the calling after two weeks. Further steps are taken by the coordinator in line with the plant's instruction.

Is the call-back list up to date?

The training report shows people without valid training, and the status is counted at every moment of presence on the site, not only at the moment of entry.

Let us set up the call-back for one external company

We will propose a schedule of attempts and a limit matched to your plant's instruction. Let us arrange a conversation with HR and OHS.

Let's talk