InnerWeb
Skip to main content

Bulk Account Entry Without Import: Recommendations for the Administrator

The system has no bulk import of accounts, so entering several hundred people means a loop that creates an account and sends an invitation. On average it takes about 2 seconds per account. The recommendations below help plan the time window, the order and the control of the result.

approx. 2 s
average time to handle one account in the loop
Source: feature documentation
approx. 1000 s
loop for 500 accounts
Source: calculation: 500 x 2 s

Who this is for and why there is no import

These recommendations are for the IT administrator or implementation coordinator who has to create several hundred accounts before the pilot starts: own employees, people from external companies, managers. The system has no bulk import of accounts. Each person goes through the same path as an invitation from the panel, and account activation is an action of the person, not of the administrator.

Bulk entry is therefore a loop: for each row of the list an account is created and an invitation is sent. This approach has an advantage: each account goes through the same check, including the duplicate check for invitations from the panel.

Recommendation 1: calculate the machine time of the loop

The average time to handle one account in the invitation loop is about 2 seconds. For 500 accounts this gives about 1000 seconds, that is a dozen or so minutes of machine time (calculation: 500 x 2 s). For 1500 accounts it will be about 3000 seconds, roughly 50 minutes.

The figure is an approximation, because it depends on the load of the mail server and the network. We recommend planning a reserve, for example by doubling the result when planning the window.

Machine time of the invitation loop

Machine time of the invitation loopBar chart of loop time: 500 s for 250 accounts, 1000 s for 500, 2000 s for 1000.0500100015002000s250 accounts: 500 s500 s250 accounts500 accounts: 1000 s1000 s500 accounts1000 accounts: 2000 s2000 s1000 accounts
Source: Example calculation: number of accounts x 2 s

Recommendation 2: choose a window outside peak time

The invitation loop puts load on mail sending and the application server. Run it outside hours when the gate is handling badge swipes or the plant has its peak of guest registrations. For batches of several hundred accounts an evening or early morning is usually enough, not a whole day.

Recommendation 3: split the list into batches

Instead of one loop for the whole list, prepare batches of 100 to 200 people by company or department. After each batch check the result: the number of accounts created, errors, rejections because of duplicates. An error in the first batch then costs dozens of rows, not the whole list.

Splitting by company also makes later checking easier: the company coordinator checks their batch and confirms that everyone received an invitation.

Recommendation 4: tidy up the input data

Before the loop, tidy up the spreadsheet: an e-mail or a phone number in E.164 format for each person, unified spelling of names, no repetitions in the file. Rows with strong data will be matched automatically, rows based only on a name will go to a decision by a person.

The duplicate check covers the invitation from the panel and registration from a QR code. Choose a path covered by the check for the loop if the list may contain people already known to the system.

Recommendation 5: plan the queue after the loop

After the loop ends, some matters remain that cannot be closed automatically: weak matches for a human decision (at most 3 candidates, decision token valid for 780 seconds) and phone-only registrations waiting for administrator approval. Reserve the time of the person who will handle them before training starts.

At the end compare the number of active and pending accounts with the number of rows in the spreadsheet. Explain the difference row by row.

  • calculate the window: number of accounts x 2 s, with a reserve,
  • split the list into batches by company or department,
  • check the result of each batch before the next one,
  • reserve time for the decision queue,
  • compare the numbers: rows, active accounts, pending accounts.
Example calculation

Loop time for different list sizes

Assumptions
ParameterValue
Time per account2 s
Number of accounts250, 500, 1000 accounts

Result: 250 accounts: approx. 500 s, 500 accounts: approx. 1000 s, 1000 accounts: approx. 2000 s (approx. 33 minutes).

Note: Example calculation on an average of about 2 seconds per account; actual time depends on mail and network load.

Video

Frequently asked questions

Can the loop be run on the whole list at once?

It can, but it is better to split it into batches of 100 to 200 people. An error in the input data then costs one batch, and you check the result as you go.

Does the person have to activate the account themselves?

Yes. The invitation leads to activation by the person, so after the loop some accounts will be waiting for activation.

How long does entering 500 accounts take?

About 1000 seconds of machine time, that is a dozen or so minutes. This is a calculation of 500 x 2 s; plan a reserve.

Let's plan the account entry window

We will work out with you the batches, the loop time and the decision queue for your list. Book a talk.

Let's talk