The Point Where Spreadsheets Stop Working

Attendance in a spreadsheet works fine at eight people. At around twenty-five it starts consuming real time, and at fifty it becomes a monthly crisis. The transition is not gradual, and most small businesses go through it without noticing until a payroll cycle goes badly wrong.

The specific symptoms are recognisable. Someone spends the first two days of each month chasing attendance data. Leave balances live in a second sheet that only one person maintains and nobody else can interpret. An employee disputes a deduction and there is no way to reconstruct what happened on that date. A new joiner's details exist in four places with three versions.

The instinct at this stage is to look at full HR suites, which is usually the wrong move. A fifty-person company does not need performance management modules, org chart tooling, or engagement surveys. It needs attendance that is trustworthy, leave that has a balance nobody argues about, and salary that comes out of the same data — with nobody employed full-time to operate it.

• Spreadsheets fail around 25 people and become a crisis around 50
• Two days lost at the start of every month is the clearest signal
• Leave balances known to one person are a single point of failure
• You need attendance, leave, and payroll — not a full HR suite

What Actually Matters at This Size

Four things determine whether attendance software works for a small company, and none of them are on a typical feature comparison page.

First, setup that one person can complete in a few days without a consultant. Second, verification that fits how your staff actually work — if everyone is in one office, a network check is enough; if you have field staff or multiple sites, you need face verification and geo-fencing. Third, leave that carries a running balance so nobody maintains a parallel sheet. Fourth, a direct path from attendance to salary, because that is where the two days a month are going.

Attend Mitra covers these without requiring a dedicated administrator: Excel import for employees, shift templates that carry their own verification rules, leave policy templates assigned by department or set as the company default, and payroll runs that compute from the same attendance and leave records. The mobile apps mean employees check their own shifts, balances, and payslips instead of asking.

• Setup completable by one person in days, not a consultant-led project
• Verification matched to how staff actually work, configured per shift
• Leave with a running balance so no parallel spreadsheet exists
• A direct path from attendance to salary with no manual reconciliation
• Employee self-service so questions do not land on one person

What to Ignore for Now

Small companies lose more time to over-configuration than to missing features. A few things are safe to defer, and deferring them is what gets you live in a week instead of a quarter.

Complex approval chains rarely make sense at this size — if the founder or one manager approves everything, a single approval level is correct and multi-level routing is overhead. Elaborate department structures can wait until departments genuinely operate independently. Performance modules are premature when managers see everyone daily. Per-employee overrides should be avoided almost entirely: put the rule on the shift or the leave policy so it applies consistently, because bespoke exceptions become unmaintainable faster than anyone expects.

The one thing not to defer is the payroll connection. Companies that set up attendance and leave and postpone payroll integration keep the manual month-end they were trying to eliminate. If the reason you are buying is the two days lost every month, configure the payroll path in week one.

• Single approval level is correct when one person approves everything
• Defer elaborate department structures until teams operate independently
• Skip performance modules while managers see everyone daily
• Avoid per-employee overrides — put rules on shifts and policies
• Do not defer the payroll connection; it is the reason you are buying

A One-Week Rollout

The realistic sequence for a small company is short. Import employees from Excel using the provided template. Create your shift templates — usually one or two — with the verification rules each needs. Set up your leave types and one policy template as the company default so new joiners inherit it automatically. Add the year's public holidays to the company calendar.

Then enroll faces if you are using face verification, which takes under a minute per person and is the only step needing everyone present. Assign the week's roster. Have employees install the app and confirm they can see their shift, their balance, and mark attendance.

Run the first month deliberately. Watch for shifts where the geo-fence radius is too tight, leave types you did not think of, and employees whose situations do not fit the default policy. Fixing these in month one with forty people is straightforward. The free trial runs for 14 days without a credit card, which is enough to configure and test properly — the useful test is one complete month-end, not a week of check-ins.

• Import employees, create one or two shift templates, set a default leave policy
• Add the year's holidays to the company calendar in one sitting
• Enroll faces — under a minute each, the only step needing everyone present
• Assign the first roster and confirm employees can see it in the app
• Test through a complete month-end, not just a week of check-ins

Room to Grow Without Migrating Again

The cost of choosing badly at this size is not the subscription — it is migrating again in eighteen months when you have doubled and the tool has stopped fitting. It is worth checking that the things you do not need yet exist.

The ones that matter as you grow: multiple shift patterns including night shifts that cross midnight, different leave policies per department, delegated administrators scoped to a department or feature so approvals do not all funnel to one person, and geo-fencing for when you open a second location. Also worth having available: hiring with public job application pages, digital ID cards, announcements, and document sharing — none of which you need at fifteen people and all of which become useful at eighty.

Attend Mitra includes these in the platform rather than as separate products, so growing into them is a configuration change. Check how you are billed as you grow, though — headcount versus active employees per month makes a real difference for seasonal or contract-heavy businesses, and it is worth confirming before you scale rather than after.

• Multiple shift patterns including night shifts crossing midnight
• Department-specific leave policies as teams diverge
• Delegated admins scoped by department so approvals stop funnelling to one person
• Geo-fencing ready for when you open a second location
• Confirm headcount versus active-employee billing before you scale