Skip to content
Zenocta Solutions

Mobile App Development16 Jun 2026 · 8 min read

How We Built EmployHub: HR and Attendance Rules for Real Work

A behind-the-build look at EmployHub: why rigid attendance breaks, how a configurable rules engine works, and what we would advise anyone building an HR and attendance app.

ZEBy , Editorial Team

EmployHub, the HR, attendance and payroll app from Zenocta, shown on its social card

Most attendance tools assume that a working day is one punch in and one punch out. Real work does not behave like that. People step out, come back, work across shifts and run into grace periods and overtime rules. We built EmployHub because a rigid system produces inaccurate hours and manual payroll sums. This is the story of how that hr attendance app was shaped: the problem, the decisions, how the pieces fit, and what we would tell anyone building something similar.

What problem did EmployHub set out to solve?

The case study frames it in one sentence. Small and mid-sized organisations were tracking attendance manually or with rigid systems that did not support real-world work patterns like multiple check-ins, breaks and varying shift rules, leading to inaccurate hours and manual payroll calculations.

The key word is rigid. A system that insists on one clean punch pair forces everyone to work around it, usually with a register, a spreadsheet and a lot of corrections at month end. The result is a payroll that depends on someone recalculating hours by hand. Fixing that means building software that bends to each company's rules, rather than asking each company to bend to the software.

If you want the buyer's view of the same problem, our guides on attendance management software for small business teams and payroll and attendance software for small business in India cover how to evaluate a product. This article covers how one was built.

4roles: admin, HR, manager and employee
3future-scope ideas in the case study
11menu categories in a listed release

Who is EmployHub for?

The case study describes an all-in-one employee management and attendance tracking application for small to mid-sized organisations that want to digitise daily workforce operations, reduce manual HR work and gain clear visibility into employee activity. The Play listing names the kinds of businesses: offices, shops, clinics, agencies and multi-branch businesses that want one HR app instead of registers and spreadsheets.

It also names four roles, admin, HR, manager and employee, each seeing only what they need. That is the first design decision to notice. An HR product is used by people with very different jobs, and the same screen cannot suit all of them. The employee wants to punch in and download a payslip. The manager wants to approve. HR wants the whole picture.

How did we approach the design?

Zenocta built EmployHub as a configurable attendance and workforce management platform. According to the case study, employees can check in and out multiple times a day, and the system automatically applies each company's shift rules, grace periods, break deductions and overtime policies to calculate accurate hours without manual work.

The technology stack in the case study is Flutter for the employee and admin experience, Firebase for authentication, Firestore and Cloud Storage, a configurable shift and overtime calculation engine, and real-time attendance sync across devices. For a view on choosing frameworks, our post on Flutter versus native app development sets out the trade-offs.

The central idea: rules as configuration

The technical challenge the case study names is building a configurable rules engine that correctly calculates hours across varied shift patterns, grace periods and overtime policies. The design choice is to treat each of those as a setting. Working hours, shift windows, grace periods, break deductions and overtime policy belong to the company, not to the code. When a new customer arrives with a different pattern, the product is configured rather than rewritten.

The user experience challenge sits on the other side of the same coin: keep multi-check-in attendance simple for employees while giving admins clear visibility into workforce activity. A flexible engine is only useful if the person tapping a button on a phone is not asked to understand it.

How do the features fit together?

The case study centres on attendance. The Play listing shows how the product widened around that core, in a clear order: attendance, leave, payroll and approvals, then people, engagement and assistants.

Attendance and trust

The listing describes punching in and out on the phone, on the web or on a shared kiosk, with a GPS geofence for the office and branch sites and an optional selfie at check-in and check-out. It also lists GPS spoof and shared-phone checks, with an attendance anomalies list for HR, plus biometric device punches, an attendance calendar and a Who's in today view. Shift rosters and swaps, overtime and comp-off, work-from-home and on-duty requests, missed attendance requests and timesheets round it out.

Note the pairing. When attendance feeds pay, people have a reason to game it, so a product needs both convenience and checks. The anomalies list is the part that lets HR review the unusual cases instead of auditing everyone.

Leave, approvals and delegation

Leave covers applying and approving with balances and history, a company's own leave policy, a holiday calendar, a team leave calendar, cancellations and leave encashment. A single approvals inbox gathers leave, attendance, overtime, expenses and more, with approval workflows and delegation when a manager is away. The release notes mention a live pending count on the Approvals tab and bulk approval of leave requests.

Payroll and payslips

The listing describes a monthly payroll run with PF, ESI, Professional Tax and TDS, a pre-publish check that flags unusual salaries and missing bank details before payslips go out, payslips for every employee, a payroll register, a bank transfer file and an accounting journal. A payroll tool should prepare the figures, while you confirm the current rules with a qualified professional.

People, engagement and assistants

Beyond the core, the listing mentions employee records, departments, branches, org chart, onboarding checklists, documents, goals and reviews, announcements and polls, recruitment and learning courses. It also lists AI assistants: an HR assistant that answers from the company's own data, writing help, receipt scanning and an attrition watchlist. It states that everything AI suggests is shown for review first and nothing is saved until you confirm it.

LayerWhat it handlesDesign idea
CapturePunches, GPS, optional selfie, kioskEasy for the employee, checked for the company
RulesShifts, grace, breaks, overtimeSettings per company, not code
DecideLeave and approvals inboxOne place for every request
PayPayroll run, pre-publish check, payslipsCatch problems before payslips go out
AssistAI help for reviewSuggest first, confirm before saving

What would we tell someone building something similar?

These lessons follow from the decisions above. They are advice, not results.

Advice

Write the rules down in plain words before you code them. If a manager cannot explain how grace periods, breaks and overtime work in their company, no engine will calculate them correctly.

  1. Collect real shift patterns first. Gather the rules of several real businesses, including the awkward ones, before designing settings.
  2. Make rules configurable by the customer. Grace periods, break deductions and overtime policy should be editable by an admin, not by a developer.
  3. Keep the employee screen almost empty. The more rules there are behind the scenes, the simpler the front should be.
  4. Pair convenience with checks. When attendance drives pay, add location checks, an optional selfie and a review list for unusual cases.
  5. Put every request in one inbox. Leave, overtime and expenses should not each have their own hunt for approval.
  6. Catch payroll problems before they go out. A pre-publish check that flags missing bank details is cheaper than correcting payslips later.
  7. Let AI suggest, never decide. Show every suggestion for review and save nothing until a person confirms.
  • What are your shift windows, grace periods, break rules and overtime policies?
  • Do staff work from one site, several branches or the field?
  • How will you verify location, and do you want a selfie at punch?
  • Who approves what, and who covers when they are away?
  • What must payroll prepare, and who checks it?
  • Which roles need which screens?

How did the roadmap compare to what is live?

The case study lists three future-scope ideas: payroll export tied to calculated attendance, a leave and time-off management module, and geofenced check-in for field or multi-site teams. The current Play listing describes a leave module, GPS geofencing for office and branch sites, and a payroll run with a bank transfer file and accounting journal. The listing is the authority on what the app does today.

The lesson for founders is that a product grows outward from its core. Attendance came first, and leave, payroll and approvals followed because each one depends on the one before it.

What is live today?

EmployHub is live on Android and the web. The listing states that HR and admins can open the web app with the same account to manage employees, attendance, approvals, payroll and reports on a large screen while staff use the phone app, and that Slack and Teams alerts and calendar sync are included. It also says every company's data is kept separate and only visible to its own members, with role-based access, Google Workspace sign-in and an audit log of admin changes.

On plans, the listing says you can start on the free plan with core attendance, leave and people tools, new companies get a 2-month free trial with every feature, and afterwards you can keep the free plan or choose the Value pack (every feature, with ads) or Premium (every feature, no ads). The listing adds that ads only show in the mobile apps, never on the web app. Our EmployHub app page has the current details.

How do you get a similar product built?

If your company has awkward shifts, several branches or field staff and you want attendance and HR shaped around your own rules, start by writing those rules down. Our guide to how to create payslips for employees is a useful companion, and our software development process from idea to launch explains how we move from a brief to a live app.

You can read the full EmployHub case study, browse our other apps, or talk to us about your own build. We return a scoped, fixed-price proposal, so you know the scope before work begins.

Try it live

Open the real thing: demos run in a new tab with sample data, apps link to their own page.

Frequently asked questions

  • 01Can an attendance app handle multiple check-ins and different shifts?

    Yes. The EmployHub case study says employees can check in and out several times a day and the system applies each company's shift rules, grace periods, break deductions and overtime policies automatically. These rules are configurable per organisation.

  • 02Which technologies were used to build EmployHub?

    The case study lists Flutter for the employee and admin experience, Firebase for authentication, Firestore and Cloud Storage, a configurable shift and overtime calculation engine, and real-time attendance sync across devices.

  • 03How do you prevent attendance from being gamed?

    The EmployHub listing describes GPS geofencing for office and branch sites, an optional selfie at check-in and check-out, GPS spoof and shared-phone checks, and an anomalies list for HR to review unusual cases instead of auditing everyone.

  • 04Can AI be used safely in an HR app?

    Yes, if suggestions are reviewed. The EmployHub listing says everything AI suggests is shown for review first and nothing is saved until you confirm it. We recommend that pattern for any AI feature in HR or payroll software.

  • 05Can Zenocta build a custom HR or workforce management app?

    Yes. Zenocta builds custom HR tech and workforce management platforms. Tell us your shifts, sites and approvals, and we will return a scoped, fixed-price proposal. EmployHub is live on Android and the web.

0% read ·

Get new guides in your inbox

Practical notes on billing, payroll, apps and AI for growing businesses, written from what we build. No spam.

We email occasional guides. Unsubscribe any time: reply to any email or write to info@zenocta.ie.

Ready to build something real?

Website and app development from ₹8,888. Book a free consultation and get a scoped, fixed-price proposal within 24 hours.