What is the best way to manage attendance across multiple branches?

Run one central system in which head office owns the policies, code list and shift templates, each branch has its own geofence or kiosk and a branch admin scoped to their own staff, and payroll reads one consolidated dataset after a company-wide cutoff. Standardise codes and templates before migrating, and pilot at two branches first.

How do we handle different state holidays in a centralized attendance system?

Maintain one holiday calendar per state, including the three national holidays plus the state's list under its Shops and Establishments or National and Festival Holidays Act, and map each branch to its state's calendar. Head office publishes all calendars at the start of the year so branches cannot mark holidays inconsistently.

Should branch managers be able to change attendance rules?

No. Branch managers should roster their staff onto head-office shift templates and approve corrections and leave for their own people, but should not create shifts or alter grace periods and half-day rules. Any state-specific variation should be defined centrally and documented in the policy, not improvised at the branch.

How is professional tax handled for employees in different states?

Professional tax is a state levy with slabs that differ by state, and some states such as Delhi, Haryana and Uttar Pradesh do not levy it. Assign each employee a PT state based on their work location, apply that state's slab in payroll, and confirm current slabs with the state's commercial tax department when they revise.

How long does it take to centralize attendance for 20 branches?

Typically three to five months: two weeks of head-office configuration and employee import, a one-month pilot at two branches alongside the existing registers, then waves of five to ten branches, each going live after the previous wave's first payroll reconciles. The pace depends on branch readiness and manager training more than on the software.

Multi-Location Attendance Management: Centralize Branches

Symptoms of Decentralized Attendance

Most companies do not decide to run attendance branch by branch; it happens as they grow. The first branch keeps a register. The second gets a fingerprint machine from a different vendor. The third branch manager photographs the register and sends it on WhatsApp on the 1st. By the tenth branch, head office HR spends the first week of every month typing, chasing and reconciling, and payroll goes out on the 10th with corrections the following month.

You will recognise the symptoms. Every branch uses its own abbreviations, so 'HD', 'H' and '1/2' all mean half day. Late marks are defined differently in Pune and Lucknow because each manager set the rule. A national holiday is marked as present in one branch and as holiday in another. Overtime is paid in cash at some sites and not recorded at all. Nobody at head office can say how many people are at work right now across the company, and the auditor's request for the March attendance of branch 7 takes two days to satisfy.

The cost is not only HR time. Inconsistent attendance means inconsistent pay for identical roles, which employees notice and which becomes a grievance. It means professional tax and Shops and Establishments compliance handled by whoever remembers, and it means the business cannot compare branches on absenteeism or overtime because the data is not comparable.

Month-end consolidation takes days and payroll slips past the 7th
Codes, grace rules and holiday treatment differ by branch
No live view of company-wide presence; audit requests take days
Branch comparisons are impossible because the data is not standardised

Designing the Central Model

The target model is simple to describe: one company account, one set of policies owned by head office, one geofence or kiosk per branch, one branch admin per location with rights limited to their own people, and one consolidated dataset that payroll and management read from. Everything below is about making that model fit a real business with branches in several states.

Start with the structure. Create branches (or sites) that map to physical locations, and departments that cut across them. Assign every employee to exactly one home branch and one department. Give each branch its own geofence with a radius that reflects the site (a standalone showroom needs 50 to 100 metres; a factory compound may need 300), or a kiosk tablet where staff share devices. Employees who travel between branches should be allowed to check in at any company geofence, with the record showing which one.

Then decide the ownership rule: head office defines policies (shift templates, grace, half-day, leave types, holiday calendars, overtime rules); branches apply them (roster their people onto HQ templates, approve corrections and leave for their own staff). Branches should not be able to invent a new shift or change a grace period. Attend Mitra's multi-location attendance setup follows this pattern with company-level policies, branch-level geofences and role-based access per branch.

One company account; branches as sites, departments across them; one home branch per employee
Per-branch geofence or kiosk; travelling staff may check in at any company site
Head office owns policy definitions; branches apply them to their people
Branch admins see and act on their own branch only

Standardizing Codes, Shift Templates and Policies

Before you migrate a single branch, publish a company attendance code list and freeze it: P (present), A (absent), HD (half day), WO (weekly off), PH (paid holiday), CL, SL, EL (leave types), LOP (loss of pay), OD (on duty or outdoor), and WFH if you allow it. Every report, register and payroll input uses these codes and nothing else. This one document eliminates most consolidation work.

Next, define shift templates centrally. A retail chain may need 'Showroom General 10:00 to 19:00', 'Showroom Late 12:00 to 21:00' and 'Warehouse Morning 07:00 to 15:00'; a clinic chain needs OPD and rotational patterns. Each template carries its in-time, out-time, grace period, half-day threshold, break rules and overtime eligibility. Branch managers pick templates for their roster; they do not edit them. The roster management glossary entry explains how templates, rosters and presets relate.

Finally, write the company attendance policy: how late marks accumulate, when a half day is deducted, how corrections are requested and approved, how overtime is authorised, and what evidence is needed for on-duty days. Our attendance policy template gives you a starting draft to adapt. The policy should allow for state variations in working hours and weekly offs without letting branches change the underlying rules.

Publish and freeze one attendance code list for the company
Define shift templates centrally with grace, half-day, break and OT rules
Branch managers roster onto templates; they cannot create or edit them
One written attendance policy with a section for state-specific variations

Roles and Permissions: Who Can See and Change What

Centralisation fails when either extreme is chosen: head office approving every correction for 800 people (bottleneck), or branch managers with full admin rights (chaos returns). The workable middle is a small set of roles. Company admin at HQ: defines policies, sees everything, runs payroll. Branch admin or manager: rosters, approves corrections and leave, sees live status for their branch only. Department head: sees their department across branches, read-only, with approval rights for their direct reports. Employee: self-service to mark attendance, view records and request corrections or leave.

Approval workflows should mirror this. A missed punch is regularised by the branch manager; overtime above a threshold needs a department head; a change to a shift template needs the company admin. Every action is logged with who, when and why, so an HQ auditor can trace any change in a branch without asking the branch.

Role-based access also protects data: a branch manager in Kochi has no reason to see face descriptors or attendance history for staff in Indore. Attend Mitra provides role-based access with branch scoping and full audit logs, so the permission model above can be configured rather than improvised; the multi-branch attendance page describes the typical role set.

Company admin (HQ), branch admin, department head, employee: four roles cover most businesses
Approvals escalate by type: corrections at branch, large OT at department, policy at HQ
Audit log on every change; HQ can trace without asking the branch
Scope branch admins to their own branch's data only

Handling State-Specific Rules From One Console

The genuine complexity of multi-state operations is that some rules differ by state, and a central system must accommodate that without fragmenting. Three areas matter most: holidays, professional tax and working-hour rules.

Holidays: the three national holidays (26 January, 15 August, 2 October) apply everywhere, but the remaining paid holidays follow the state's list under its Shops and Establishments or National and Festival Holidays Act, and festivals differ (Onam in Kerala, Pongal in Tamil Nadu, Chhath in Bihar, Durga Puja in West Bengal). Maintain one holiday calendar per state, assign each branch to its state's calendar, and let HQ publish all calendars at the start of the year. Professional tax: it is a state levy with different slabs and some states levying none; assign each employee to a PT state based on their work location and apply that state's slab in payroll. Our state-wise professional tax slabs guide lists the current rates.

Working hours and weekly offs: state Shops and Establishments Acts differ on spread-over, closing hours and weekly off rules. Handle this by creating state-specific variants of shift templates only where genuinely required (for example, a state that limits closing time for shops) and by documenting the variation in the policy's state section. Labour welfare fund contributions, where the state levies them, follow the same per-state assignment. Keep the number of variants small; every extra variant is a future reconciliation problem.

One holiday calendar per state; each branch mapped to its state calendar; HQ publishes annually
PT state assigned per employee from work location; slabs applied in payroll
State-specific shift template variants only where the law forces it
LWF and other state levies follow the same per-state mapping

Consolidation, Payroll Cutoff and Branch Dashboards

With a central system, consolidation stops being a task and becomes a report. The remaining discipline is the cutoff: pick a company-wide attendance cutoff (the last calendar day, or the 25th if you pay on the 1st) and a regularisation deadline (two working days after cutoff) by which branch managers must have approved all corrections. After the deadline, records lock and payroll runs on what is there. Publish this calendar to every branch at the start of the year and enforce it; the first month a branch misses the deadline and payroll still goes out on time is the month the new discipline sticks.

Payroll then reads from one dataset: present days, LOP and overtime per employee, already standardised. State-specific PT and any LWF apply by mapping. EPF and ESIC apply uniformly with the current ceilings. The point is that the attendance input to payroll is no longer assembled from ten sources on the 3rd of the month.

Dashboards are the management dividend of centralisation. A live monitor showing present, late and absent counts per branch at 10:15; a monthly view comparing absenteeism rate, late-mark frequency and overtime hours by branch; and drill-down from a branch figure to the individual records. Attend Mitra's live monitor and analytics provide branch-wise views with CSV, PDF and XLSX exports, and the monthly attendance report guide shows what a consolidated management report should contain. Once branches are comparable, outliers become obvious and conversations with branch managers become factual.

Company-wide cutoff and regularisation deadline; records lock after the deadline
Payroll reads one standardised dataset with per-state PT and LWF mapping
Live monitor by branch; monthly comparison of absenteeism, late marks and overtime
Drill-down from branch totals to individual records for audit and HR follow-up

Migration Plan and Governance

Do not switch all branches on the same day. A workable plan runs in four phases. Phase one (two weeks): finalise the code list, shift templates, policy, holiday calendars and role model at HQ; import the employee master with branch and state assignments, using an Excel import rather than manual entry. Phase two (one month): pilot at two branches, one that is well run and one that is difficult, so you learn from both. Run the pilot alongside the existing register for one payroll cycle and compare.

Phase three (two to three months): roll out in waves of five to ten branches, each wave starting after the previous wave's first payroll has been reconciled. Each branch gets a short manager training, a one-page employee guide in the local language, and its geofence or kiosk set up before go-live. Phase four: retire the old registers and machines, and switch payroll to read exclusively from the central system. Our multiple location employee management page outlines the typical rollout support.

Governance keeps the model from fragmenting again. Hold a monthly attendance review at HQ that looks at the branch dashboard, regularisation counts (a branch with hundreds of manual corrections has a process problem), overtime outliers and policy exception requests. Review shift templates and the code list once a year, and version the policy. Assign a named owner at HQ for the attendance system; when nobody owns it, branches quietly go back to WhatsApp.

Phase 1: HQ configuration and employee import; Phase 2: pilot two contrasting branches for one payroll cycle
Phase 3: waves of 5 to 10 branches, each after the previous wave's payroll reconciles; Phase 4: retire old systems
Local-language one-page guide and manager training per branch before go-live
Monthly HQ review of dashboards, correction counts and overtime; annual policy and template review; a named owner

How Multi-Site Businesses Centralize Attendance Across Branches