Events

The main concept of FaceTimer (attendance control system based on facial recognition).

Employees post events with photos ("I'm here"/"I'm out") to start continue and close a working period of time.

The need for confirmation events depends on a company setting (see Confirmations).

The system accumulates events, checks them with a face recognizer and builds reports.

Notifications about negative events can be received by mail or Telegram chat.

Confirmations

Confirmations are needed to stop time tracking when an employee forgets to post an event of type "I'm out". The system requests the employee to post a confirmation event and stops time tracking if the request is not confirmed (see Intervals).

The system has two confirmation modes: fixed and random.

The fixed request mode is designed for events at the beginning and at the end of the work shift. If the event "I'm out" is not made, the confirmation request is executed after the maximum possible employee's shift duration (see Intervals). As a rule, such a request occurs at night, the system closes the forgotten shift without the participation of an employee.

Random confirmation mode allows controlling the presence of employees during the working day. Requests are generated randomly according to a given algorithm (see Intervals).

It's also possible to initialize confirmation requests manually in the "Employees" section.

Scheduled events

In the "Scheduler" section, you can create scheduled events, they allow you to control the work schedule of employees. Usually, one scheduled event in the morning is enough to check whether an employee is working today.

Scheduled events check where, when and which employee should post an event. The check is considered successful if the employee posts events in within a certain time range from the scheduled time (see Intervals).

Also, scheduled events can be used to monitor presence at the workplace at a certain time or leaving time.

Intervals

There is a set of important parameters in the system that have the following default values:

time to confirm the request - 20 minutes;
maximum shift duration for fixed requests - 15 hours;
frequency of random requests - usually from 0 to 3 requests in 10 hours (recommended value);
the range of the scheduled events is 20 minutes before and after the scheduled time.

Optimal parameter values have been selected over the years of the service's existence. These values cannot be changed through the system interface, it requires to send a request for a change to technical support.