Ten Common Mistakes During First-Time Setup

The ten mistakes below account for most support calls in the first month of rollout. Reading them in advance will save you several days.

The ten mistakes below account for most support calls in the first month of rollout. Reading them in advance will save you several days.

1. Turning on every module on day one

When employees open the app and see fourteen items, they don't know where to start and go back to the old way of doing things. Turn modules on in four phases as described in A1-02.

2. Skipping the Region level because "the company only has one location"

When you open a second branch, you'll have to reorganize the entire structure and all the attendance data accumulated so far. Just create a default region.

3. Setting up job titles based on wishes rather than reality

The list swells to dozens of job titles that no one holds, diluting every report and competency framework later on. Only set up job titles that are currently filled or planned to be hired within 12 months.

4. Changing Branch, Department, or Job Title codes after importing employees

All your old import files break, and exported data can no longer be cross-referenced. Finalize the codes in steps 2–3 and keep them unchanged.

5. Importing the entire employee list on the first try

The template file has 74 columns in English, and getting one convention wrong breaks hundreds of rows. Import 5 people as a test, check the results, then import everyone.

6. Misreading the "Disable clock-in by phone" toggle

Turning this toggle on blocks clocking in through the app. Many people turn it on thinking it means "allow", and then the whole company can't clock in the next morning.

7. Not creating shift templates before scheduling

The shift template list starts out empty. Without shifts you can't schedule anyone, and without shifts the timesheet can't calculate late arrivals and early departures.

8. Forgetting to set up backup approvers

When an approver goes on a week-long business trip, the whole department can't request leave, and pending requests will lead to an incorrect timesheet at the end of the month.

9. Editing payroll directly when you see a discrepancy

If you fix it by hand, the next month will be off in exactly the same place. A discrepancy is a signal: if working days are off, the time & attendance configuration is wrong; if leave is off, the requests configuration is wrong; if allowances are off, the payroll template is wrong.

10. Only one person knows the system configuration

If that person resigns or takes extended leave, the whole business stalls. Train at least two people within the first month.

Mistakes 4, 5, and 9 are the three that take the most time to fix. If you only remember three things from this article, remember those.

지원
데모 예약
Chat