# How to choose an attendance system for several branches - Canonical: https://qrgate.az/en/blog/choosing-attendance-software-for-branches - Markdown: https://qrgate.az/en/blog/choosing-attendance-software-for-branches.md - Language: en - Date: 2026-08-12 When a company opens its second branch, attendance recording usually does not change - a second file simply appears. At the third branch, a third. The question of **choosing an attendance system for branches** tends to get asked at the fourth, after the first serious discrepancy. This piece covers six criteria for making that choice and why each one matters. ## What breaks first as branch count grows The answer is not, as you might expect, "data gets lost". The data stays - what gets lost is **comparability**. Each branch fills its own file its own way. One writes "09:05", another "9.05". In one, lateness counts after ten minutes, in another after fifteen. In one the break is inside working time, in another it is not. The numbers add up but do not measure the same thing. This is the most dangerous state: the report exists and looks correct - yet a decision based on it can be wrong. A notable detail: the problem depends not on headcount but on the *number of files*. For a single office of two hundred a spreadsheet stays bearable; for six branches totalling sixty people it does not. ## Criterion 1: structural support The first thing to require from the system is at least three levels: branch, department and section. It looks like a technical detail, but it directly determines whether the reporting is usable. Without structure the report is either too general - "42 late arrivals company-wide" - or too granular, a separate row per employee. Neither serves a decision. ## Criterion 2: permission levels A branch manager seeing company-wide data is usually neither necessary nor helpful. The working model: the branch manager sees their branch, the department head their team, HR the overall picture, and accounting only the approved final figures. In a system without permission levels one of two things happens: either everyone sees everything, or the data is distributed through files HR builds by hand. The second is a return to the original problem - manual work. ## Criterion 3: centralised rules To compare branches genuinely, the lateness threshold, break rule and schedule templates have to live in one place. Then the indicators are calculated by the same logic and the sentence "branch three has twice the lateness of branch four" carries meaning. When each branch keeps its own rules, the same sentence is meaningless. The practical test question: *are the lateness figures of two branches calculated by the same rule?* If the answer is "I don't know", comparison is not yet possible. ## Criterion 4: adding a new site This is the biggest practical difference between the models and often settles the decision on its own. In a device-based setup every new branch is a project of its own: order, wait, cabling, installation, testing, acceptance. Where the recording point attaches to the structure, a new branch is essentially a row to add. If two or three new sites are planned over three years, this difference becomes the most volatile line in the cost calculation - more on the [multi-branch attendance system](https://qrgate.az/en/multi-branch-attendance-system) page. ## Criterion 5: notification scope In a multi-branch company, notifications only work if they are built together with scope. Sending a branch manager every lateness in the company makes the notification useless from the first week. The same notification scoped to their own branch gets read every day. The test question: *when a new branch opens, do the notification rules have to be rebuilt?* If the answer is yes, the distribution is tied to people rather than the structure. ## Criterion 6: comparison form of the report The last criterion is the most overlooked: if the report only gives a list, it is not enough for managing branches. What is needed is a comparison cut - branches side by side, over the same period, on the same indicator. Without it, the question "which branch has a problem" is answered by hand every month. ## A worked example: the difference hidden across six branches A pharmacy chain had six branches and sixty-two employees. Each branch manager filled in their own spreadsheet and sent it to head office on the 2nd. At head office two people merged those files - a job that took up to three days. Every month the same question came back: why is lateness so low at branch three? The answer surfaced a year later: at that branch the manager recorded lateness after twenty minutes, while everywhere else it was ten. For a year the company had been looking at figures that were not comparable. In the new setup the rules were centralised, the structure was built and permission levels were set. The file-merging work disappeared - but more importantly, branch comparison became meaningful for the first time. ## What the branch manager needs In multi-branch setups the most overlooked party is the branch manager. The system is built for head office and the manager becomes just a data source - which is the most common reason such rollouts fall out of use. In practice the manager needs three things: a **daily picture** (who is in today and who is not), **notifications scoped to their branch** (a shift that has not opened, lateness) and **the ability to correct, leaving a trace**. The third causes the most argument. In practice, closing off correction entirely does not work: the manager asks HR for it by phone, and no trace is created anyway. A correction that leaves a trace is both fast and verifiable. ## Where to start In a multi-branch company the rollout starts with one branch - not the simplest, but the one whose rules change most. A month of parallel running exposes the gaps and creates a template for the rest: the second branch joins with rules that have already been tested. [Calculate the QRGate price](https://qrgate.az/en) for your branch count, or first [look at what it does](https://qrgate.az/en/advantages). ## FAQ ### What breaks first as branch count grows? Comparability. When each branch fills its own file its own way, columns, date formats and lateness thresholds differ - the numbers add up but do not measure the same thing. This is the most dangerous state, because the report exists and looks correct. ### What structure should be required? At least three levels: branch, department and section. Without them the report is either too general or too granular. With the structure in place every recording point attaches to its branch and the same report reads at three levels. ### Should a branch manager see the whole company? Usually not. The working model: the branch manager sees their branch, the department head their team, HR the overall picture. Without permission levels, data is either open to everyone or distributed through files HR builds by hand. ### What makes branches genuinely comparable? Centralised rules. If the lateness threshold, break rule and schedule templates live in one place, the indicators are calculated by the same logic. When each branch keeps its own rules, comparison becomes formal - the numbers sit side by side but measure different things. ## Related pages - Attendance system costs - [Markdown](https://qrgate.az/en/attendance-system-costs.md) | [HTML](https://qrgate.az/en/attendance-system-costs) - Multi-branch attendance system - [Markdown](https://qrgate.az/en/multi-branch-attendance-system.md) | [HTML](https://qrgate.az/en/multi-branch-attendance-system) - Attendance analysis - [Markdown](https://qrgate.az/en/analysing-attendance-indicators.md) | [HTML](https://qrgate.az/en/analysing-attendance-indicators) - Employee attendance system - [Markdown](https://qrgate.az/en/what-is-employee-attendance-system.md) | [HTML](https://qrgate.az/en/what-is-employee-attendance-system) - Attendance without hardware - [Markdown](https://qrgate.az/en/employee-attendance-without-hardware.md) | [HTML](https://qrgate.az/en/employee-attendance-without-hardware) - QR attendance advantages - [Markdown](https://qrgate.az/en/advantages-of-qr-attendance-system.md) | [HTML](https://qrgate.az/en/advantages-of-qr-attendance-system)