What changes when attendance runs across more than one branch
With one office and one fingerprint device, attendance is mostly a hardware question. Once you have branches in different towns, the scanner becomes the easy part. The hard part is getting every branch's punches into one place, under the same employee codes, on a schedule head office can rely on, and keeping attendance going on the day a device or internet line fails.
This guide is for HR and admin managers who look after several locations: a head office in Ranchi with branches in Dhanbad, Hazaribagh and Jamshedpur, say, or a hospital with a main campus and two collection centres, or a school group with three campuses. These are illustrations; the same planning applies anywhere in India. By the end you should be able to decide where devices go at each branch, choose how each branch sends its logs, set a process for transfers, and write a one-page fallback plan.
Shift timings, grace periods and overtime rules are a separate subject, covered in our guide to setting up shift rules in attendance software. Here we stay with devices, data flow and branch operations.
Placing devices at each branch
Device placement decides whether staff actually punch, or whether they queue, give up and ask the branch manager to mark them present. Walk each branch before you buy or move a device, and look at it from the point of view of the person arriving at 9:55 for a 10:00 start.
Entry point and queues
Mount the device where every employee passes on the way in and out, not inside the manager's cabin. To decide how many devices a branch needs, count how many people arrive in the busiest ten minutes and time a few test punches, including a failed read and a retry. If that busy window cannot be cleared in a few minutes, add a second device rather than accept a daily queue.
Power, network and surroundings
A device needs steady power and, if it will sync over the network, a reliable LAN or Wi-Fi point nearby. Avoid spots in direct sunlight, near a rain-exposed shutter or beside a dusty loading bay, because these are common reasons for poor fingerprint reads. In a godown or workshop, a simple cover and a power backup point often matter more than the model you choose.
Check the device clock at every branch during installation. A clock running a few minutes fast will quietly generate late marks for punctual staff until someone notices.
Getting branch punches to head office
Every multi-branch setup needs an answer to one question: how do the logs stored in a branch device reach the central attendance system? There are two common routes, and you can use different routes for different branches depending on their connectivity.
| Method | What the branch needs | Works well when | Watch out for |
|---|---|---|---|
| Network sync | A device model that supports it, plus a stable LAN or Wi-Fi connection | The branch has dependable internet and you want logs to arrive without anyone handling files | Internet outages delay logs; someone must notice when a device has not synced |
| Log export and import (Excel/CSV) | A person at the branch who exports the log file and sends or uploads it on time | Connectivity is patchy, or the device does not support network sync | Missed or late uploads; files exported for the wrong date range |
Whichever route you use, fix a daily cut-off, for example logs for yesterday must be in by 11 am. Name one person per branch who owns that task and one backup for when they are on leave. Head office should be able to see, at a glance, which branches have sent logs and which have not.
Expect duplicate punches. Staff press their finger twice when the device is slow, or punch at a second device near the exit. The central system needs a rule for treating several punches within a short window as one, otherwise the reports will show strange in and out pairs.
One employee code across every branch
Each device identifies people by the user number they were enrolled under. The central system identifies them by employee ID. Mapping one to the other is where many multi-branch rollouts go wrong, usually because each branch enrolled people in its own way: one used 1, 2, 3, another used mobile numbers, a third reused the numbers of staff who had left.
Before enrolment begins at any branch, agree a single numbering scheme and keep an enrolment register. A simple sheet with employee ID, name, home branch, device user number and enrolment date is enough.
- Use the employee ID as the device user number wherever the device allows it, so mapping becomes one-to-one.
- Never reuse the number of an employee who has left; give every new joiner a fresh number.
- Enrol at least two fingers per person, so a cut or bandaged finger does not stop them punching.
- When a person is enrolled at a second branch, use the same number there as at their home branch.
Handling transfers, deputations and staff who visit several branches
Branches lend and move people all the time. A cashier moves permanently from one branch to another, a nurse covers a collection centre for two weeks, an area sales manager visits four branches a week. Each case needs a slightly different treatment, and all of them should be decided as policy rather than case by case.
- Permanent transfer: change the employee's home branch from a stated effective date, enrol them at the new branch's device, and remove them from the old device so the old branch's headcount stays accurate.
- Temporary deputation: enrol the person at the host branch for the period, but keep their home branch unchanged so their attendance still reports to their own manager.
- Roaming staff: enrol them at every branch they visit regularly and read their attendance by employee rather than by device, so a day split across two towns still shows as one working day.
- Field days with no device: decide in advance how a day at a client site or a bank is recorded, either through a mobile method or a manager-approved regularisation.
The common mistake is to transfer someone in the HR file but forget the device, or the reverse. Make the device step part of the transfer form so both happen together.
When a branch device fails or the network goes down
Sooner or later a device will stop reading, a power surge will damage it, or a branch will lose internet for a few days. Many devices keep logs in their own memory until they are fetched, so a network outage is usually a delay rather than a loss, but a dead device is different. Write your fallback plan before you need it.
- Manual sheet: the branch manager records names with in and out times on a printed sheet and signs each day.
- Regularisation, not direct edits: HR enters those times as regularisation requests with the reason and approver, so the record shows they came from a fallback.
- Mobile or kiosk QR as a stand-by method, if your software supports it, so staff can keep marking attendance while the device is repaired.
- A spare device at head office that can be sent to a branch, already set to the correct date and time.
- A time limit: if a device is not fixed within an agreed number of days, it is escalated to the operations head.
Fallback entries are the easiest place for proxy attendance to creep back in. Review them separately each month instead of mixing them into the normal register.
Central reports head office should read every week
The point of collecting all branches in one system is that head office stops waiting for emailed Excel sheets and starts reading the same reports every week. Keep the list short and assign each report to someone who will act on it.
| Report | Who reads it | What to act on |
|---|---|---|
| Branch-wise present and absent summary | Operations head | Branches running short-staffed on particular days |
| Missing or single punches | HR and branch managers | People forgetting to punch out, or a device not reading properly |
| Late and early-out list | Branch managers | Repeated patterns, not one-off delays |
| Branches with logs not received | HR administrator | Sync or upload problems before they build up into a month-end rush |
| Department-wise attendance | Department heads | Cover planning and leave clashes |
At month end these reports feed salary processing. The steps for closing the month, approving exceptions and handing data to payroll are in our month-end attendance to payroll checklist.
How MATROP's attendance software handles branches, and when you may not need it
Our attendance and biometric software is built for organisations with more than one location. It supports multiple devices at head office and branches, takes logs either by Excel/CSV import or by network sync over LAN or Wi-Fi where the device supports it, and maps each device ID to an employee ID. It handles duplicate punches and works out in time, out time, late arrival, early exit and overtime from the logs.
Access is role-based, with separate logins for admin, HR, managers and employees, manager approvals and an employee self portal. Reports include daily and monthly registers, late lists, absent lists and department-wise reports, with Excel and PDF export. QR code attendance by mobile or kiosk is also available, which some organisations use as a stand-by when a device is down. Desktop (offline) and cloud (online) versions are offered; for branches in different towns, discuss with us which one suits how your branches connect.
Implementation starts with your rules, branches and device methods, followed by employee import and device mapping, a short pilot to check reports, and then full go-live with training. If you are in Jharkhand, you can visit our Ranchi office to go through your branch list with us.
You may not need this yet if you have a single small branch and the device's own report already gives you what payroll needs. It is also worth waiting if your branches have not yet agreed common timings and leave rules, because software will only make an inconsistent policy more visible. If you are still choosing hardware, read our comparison of RFID, fingerprint, face and mobile attendance first, or contact us with your device models.
Questions people ask
Do all our branches need the same brand of biometric device?
Not necessarily, but each model exports its logs in its own way, so one model across branches makes support and log imports simpler. Share the model numbers you already own before a demo so compatibility can be checked.
How often should punches from branch devices be pulled into the central system?
At least once a day, before head office reads the morning report. Where a device can sync over the network you can pull more often, but a fixed daily cut-off that every branch knows matters more than frequency.
What happens to attendance on a day when a branch device is out of order?
The branch manager keeps a signed manual sheet with in and out times, and HR enters those times as regularisations with an approval note. The device should be repaired or swapped quickly so manual sheets do not become a habit.
Should an employee be enrolled on devices at more than one branch?
Only if they regularly work at those branches, such as an area manager or a relief pharmacist. When they are enrolled on several devices, they must carry the same employee ID on every one of them.
