In a small company, changing how attendance works takes one meeting. In an organization with a head office, directorates and centers in more than one governorate, the system can be technically ready and weeks later half the staff still have not installed the app. Some check in from home because nobody made it clear that check-ins only count inside the work site. Most of the problems at this stage are administrative, and the software is only part of it.
Why do employees resist a new attendance system?
Because they see a deduction tool before they see any benefit. Any attendance system reads as surveillance at first, and more so when it lives on a personal phone and asks for location and a face scan.
Resistance usually shows up as delay: putting off the install, forgetting to check in again and again, or complaining that the app does not work on a certain phone. Some of those complaints are real, and you should take them seriously, because ignoring them hands the holdouts an argument.
What eases resistance is letting staff see what they gain. They can request leave or a short departure from their phone instead of filling in a paper form, check their own balance, and stop waiting for a signature from a manager who is out of the office.
Why roll out an attendance system in phases?
Because every site exposes a problem the others did not: weak internet, a particular phone model, a shift nobody defined. When you launch at one site, you fix the problem for dozens of people instead of thousands.
- Pilot siteOne department at headquarters, with support close by
- Rest of headquartersAfter fixing what the pilot revealed
- Directorates and branchesIn batches, with a coordinator at each site
- Remote sitesWhere internet and phones are harder
- Official go-liveThe numbers feed into leave and deductions
Give every phase a named person on site whom employees can turn to, someone who knows how to install the app, link a phone and explain the messages. Move to the next phase when complaints at the current one drop and the coordinator can solve the recurring issues without calling the developers.
What should management prepare before launch?
An official circular that sets the start date and states what is expected of each employee, plus short written instructions for installing the app and logging in. In government bodies especially, many employees will not act until the circular arrives, however ready the app is.
- Download links for each app store, with screenshots of the first screens.
- A clear sentence saying check-ins only count inside the work site boundary.
- The rules for lateness, departures and leave, written exactly as the system will apply them.
- The name and number of the person to contact when something goes wrong.
- What happens when someone changes or loses their phone.
What we learned launching Dawami
Dawami is an attendance app we built at Visual Innovate. It started as a solution for the Jordanian Ministry of Youth and was launched in phases across the ministry's headquarters, directorates and youth centers. These are the things we changed or added because of what came up in the field:
- People forget to check in and out, especially in the first weeks. We added an audible reminder and a visual notification at check-in and check-out times.
- Some newer Huawei phones do not have Google services, so anything that depends on them will not run. We published a version on Huawei AppGallery.
- Internet is weak at some sites, so the app works offline and warns the employee that the record will be sent later.
- GPS does not refresh properly on some phones, so the dashboard map now shows the point the employee checked in from, and the manager can judge the case directly.
- Anyone who forgets to check out has their record closed automatically at the end of the day, so open records do not distort the reports.
- On the administrative side, the rollout needed official circulars and clear instructions to download the app and to check in only within the site.
How do you handle mistakes in the first weeks?
Record violations without deducting them at first. Have management review lateness and absence and accept or cancel each penalty by hand, so you learn which cases are system errors and which are real lateness.
Watch for repeated complaints from a single site. Ten complaints from one center usually point to a problem with that site's boundary or its internet. Tips on drawing boundaries and dealing with GPS are in attendance across multiple sites.
When can you trust the system's numbers for leave and payroll?
When a full month passes with no unexplained gaps between the system and reality. Compare the automatically calculated leave and departure balances with what managers know, and fix the rules before the numbers reach payroll.
It is the same step we recommended in our HR and payroll system article: run both in parallel, then switch over. If you have not picked an attendance method yet, start with the comparison between an app and a fingerprint machine.
We build attendance and HR systems and support their phased launch as part of our custom software service. Tell us how many sites you have and how you record attendance today, and we will suggest a rollout plan that fits the size of your organization.
Questions our partners ask
How many phases does an attendance rollout need in a large organization?
There is no fixed number. A common path is one pilot site, then the rest of headquarters, then branches or directorates, and finally using the numbers for payroll once they are stable.
What do we do about employees who forget to check out?
Sound and on-screen reminders near the end of the shift help. The system also closes any open record automatically at the end of the day, and managers review the repeat cases.
Should deductions apply from day one?
It is better to record violations without deducting anything for the first few weeks, and have management accept or cancel each penalty by hand until staff get used to the system.