InnerWeb
Skip to main content

Temp agency coordinator leaves: a scenario for the administrator

The agency coordinator ends the cooperation on Wednesday, and on Thursday morning ten new workers from his list are due on the hall floor. This scenario describes how the plant administrator moves the external company's contact person without losing accounts or training results, and which server-side safeguards make sure nobody outside the company can be named.

2
roles of external company accounts: employee and coordinator
Source: feature card
20 min
time to change the coordinator in the scenario
Source: sample calculation

Situation: the contact disappears, the contract goes on

We describe a concept for a production plant that has a contract with a temporary staffing agency for several dozen people a year. On the agency side, the coordinator is the only addressee of messages about changes, training and expiring documents. When they leave, their mailbox stops being read, yet the warnings keep arriving there.

The worst case is silence: nobody learns that the training of one of the workers expires in two weeks. In the external companies module, a company has a contact person chosen from that company's accounts, so changing this person is an ordinary administrative task, not a project.

Step 1: a new person from the company's accounts, including those awaiting activation

The contact person is chosen from the accounts of the same company, including those still awaiting activation. This solves a common problem: the agency sends a new coordinator who has not yet set a password, and the first message has to reach them today.

External company accounts have two roles: an external company employee and a coordinator, meaning the technical contact of the external company. The new coordinator must hold the second role, otherwise the system will not accept them.

Safeguard on the server side

The server rejects a contact person who belongs to another company or does not have the external company coordinator role, regardless of what the form sends. An administrator's mistake or a modified request will not add to the company's data a person who does not belong to the agency.

Scenario: time to handle a coordinator change

Scenario: time to handle a coordinator changeBefore and after chart: the time to handle a coordinator change falls from 135 to 20 minutes in the scenario.020406080100minWithout switching the contact person (Clarifying who is responsible): 90 min90 minWith switching in the system (Clarifying who is responsible): 10 min10 minClarifying who is responsibleWithout switching the contact person (Sending lists by hand): 45 min45 minWith switching in the system (Sending lists by hand): 10 min10 minSending lists by hand
  • Without switching the contact person
  • With switching in the system
Source: Sample calculation: our own assumptions, no data from a specific plant

Step 2: checking who is waiting for activation

When the coordinator changes, the administrator reviews the company's employees and invitations tab. A person who entered the site or holds a valid training, but did not set a password, stays on the invitation list with the No password label. This is the working list for the new coordinator: for each person they should send a reminder or help set a password.

If the agency wants to move some people to another of its companies in the system, for example when its legal entity changes, moving a guest to an external company keeps the same account. Training results, the badge and the gate history stay with the person.

Step 3: warnings about expiring documents

When a permit is created, the system checks whether the assigned workers have the required qualifications and warns about documents that are about to expire. After a coordinator change it is important that these warnings reach the person who will act on them, not an inactive mailbox.

Good practice: on the day of the change, the plant administrator sends the new coordinator a list of agency workers with training expiry dates and agrees who renews them. This step takes a dozen minutes or so, and it prevents a permit from being blocked on the day someone from the group is needed on the line.

  • naming the new contact person from the company's accounts
  • checking the external company coordinator role
  • list of people with the No password label
  • list of documents expiring in the coming weeks
  • confirmation from the agency of who is responsible for renewals

Outcome in the scenario

In the sample calculation, the administrator closes the coordinator change in about 20 minutes, most of which is the conversation with the agency. Accounts, training results and gate history stay unchanged, so Thursday's group enters the site as planned.

The practical conclusion for the plant: the contact person is not an attribute of a human being but a function. As long as the company's data contains a current person with the coordinator role, the departure of a particular individual does not stop the contract.

Video

Frequently asked questions

Can we name a person from another company as the contact?

No. The server rejects a person from another company or without the coordinator role, regardless of the data in the form.

Can an account that is awaiting activation be the contact person?

Yes. The selection list includes the company's accounts, including those awaiting activation.

Do we lose training results after a coordinator change?

No. The change concerns the company's contact person. The workers' accounts and their history stay unchanged.

Let us put order into the contact persons of external companies

We will go through your list of external companies with you, agree who the coordinator of each one is and how to change them without a break in work.

Let's talk