Tithi MondalBlog

Article5 min readUpdated

Attendance App Design: HR Screens Staff Will Trust

Attendance app design for small teams and factories: check in, leave request flow, payslip screen and employee self service that work on any phone.

Read inहिन्दीবাংলাमराठीதமிழ்తెలుగుગુજરાતી

Attendance App Design: HR Screens Staff Will Trust: cover illustration

A garment unit with 60 workers writes attendance in a register. At month end, the supervisor spends two evenings adding up days, and three workers argue about a missed Saturday. An attendance app replaces the register with a record that every person can see. The harder part is not the technology. The harder part is design: the same app must be easy for a floor worker and clear for an HR manager.

Who uses an HR and attendance app, and in what conditions?

There are three groups: employees, supervisors or team leads, and the HR or accounts person. Each needs a different home screen.

  • Employees use a low-cost Android phone, sometimes shared with family, often with a limited data plan. They open the app twice a day.
  • Supervisors approve leave and correct mistakes. They work on the shop floor or in the field.
  • HR or accounts closes the month, prepares salary data and answers questions. They work at a desk and need tables.

Language matters most for the first group. Many workers read Bengali or Hindi better than English. Labels such as "Punch In" may be unclear, while "Mark my attendance" is plain. My article on regional language app design in India goes deeper into this, and designing for low-end phones and slow networks covers performance.

What should the attendance check in screen do?

The check in screen has one job: record that the person is present, and tell them clearly that it worked. It should show the time, the location status if used, and one large button.

Design points:

  1. The button label changes with state: "Mark in" in the morning, "Mark out" after.
  2. After tapping, a full confirmation appears: "Marked in at 9:02 AM". Never leave doubt.
  3. If location or a selfie is required, say why in one sentence before asking permission.
  4. If the network fails, save the mark on the phone with its real time, and show "Saved, will upload soon".
  5. Below the button, show today's record and a link to the month.

Be careful with location and photo checks. They can feel like surveillance. Explain the rule, apply it fairly and give a fallback when GPS fails, such as a supervisor marking attendance with a reason. A workplace should decide its own policy. The design should make that policy visible, not hidden.

How should the leave request flow work?

A leave request flow should let an employee ask for leave in 4 fields, see the balance before sending, and know the status afterwards. Four fields are enough: type, from date, to date and a reason.

The steps:

  1. Employee taps Apply for leave.
  2. The screen shows balance first: "Casual leave: 3 days left".
  3. The employee picks dates on a simple calendar. Holidays and weekly offs are greyed, so they are not counted by mistake.
  4. The screen shows "This is 2 days" before sending.
  5. After submit, the request appears in a list with status: Pending, Approved or Rejected.

The supervisor gets a notification with the name, dates and balance in one view, plus Approve and Reject buttons. Reject requires a short reason, because a silent rejection creates arguments. Approval should also be possible from a WhatsApp or SMS link, since some supervisors will not open an app. See notification UX for push, SMS and WhatsApp for how to choose the channel.

Half day and short leave are common in Indian workplaces, so the date picker must offer them. Festival holidays vary by state and by company. The holiday calendar should be editable by HR.

What does a good payslip screen look like?

A payslip screen shows how the salary was calculated, in plain words, in a layout the employee can read in 20 seconds. The employee should see the money received first and the breakdown second.

Order of information:

  • Month and net pay in large type at the top.
  • Days worked, days of leave and days absent, shown beside the pay.
  • Earnings: basic pay, allowances, overtime.
  • Deductions: each item with a short explanation, such as "Provident fund" with a help icon.
  • A button to download the PDF or share it.

Keep money in a table with right-aligned numbers. If a deduction is unusual this month, such as unpaid leave for 2 days, explain it with a line of text. A worker who does not understand a deduction will go to HR or stop trusting the app.

Salary rules, deductions and statutory items are matters for the employer and its accountant. The designer lays out what the business provides. The business should confirm the required fields and wording of a payslip with its accountant before launch.

What does employee self service include?

Employee self service means staff handle routine HR tasks themselves, without waiting for HR. The useful set is small.

FeatureWhat the employee does
My attendanceViews the month, raises a correction
LeaveChecks balance, applies, tracks status
PayslipsOpens and downloads past months
DocumentsFinds the offer letter or ID card copy
ProfileUpdates phone number and address
HelpSends a question to HR

Attendance correction deserves special care. When someone forgets to mark out, they choose the date, enter the correct time and add a reason. The supervisor approves. Without this flow, HR receives corrections on WhatsApp and the record becomes messy. For profile screens, see profile and settings screen design.

What mistakes make staff avoid an HR app?

Staff avoid an HR app when it makes simple things slow or makes them feel watched. These are the patterns I would remove first.

  • Login that fails on shared or old phones. Use OTP login carefully and keep the session. See login and OTP screen design.
  • English-only technical words. Write "Mark attendance", not "Punch event".
  • No proof of action. Every mark, request and approval needs a visible confirmation.
  • A leave balance hidden in a menu. Show it on the home screen.
  • Admin screens crowded with every setting. HR needs filters, a month close flow and exports. For table patterns, read my article on data table design for web apps.
  • Ignoring the supervisor. If approvals are painful, they pile up and the whole system loses trust.

If you are planning an attendance or HR app for a factory, school, clinic or office, I can design the employee app and the HR panel as one connected system. See my mobile app design service or write to me through the contact section.

Frequently asked questions

What is employee self service in an HR app?

+

It is a set of screens where staff view attendance, apply for leave, open payslips and update basic details themselves, without asking HR each time.

Should an attendance app use selfie or GPS check in?

+

Only if the employer's policy needs it. Explain the reason on screen, allow a supervisor fallback when GPS fails, and keep the policy fair and visible.

How many fields should a leave request form have?

+

Four: leave type, start date, end date and reason. Show the leave balance and the number of days before the employee sends the request.

Can the payslip screen be designed without knowing salary rules?

+

Yes, the layout can be designed first, but the business must confirm the required fields and deductions wording with its accountant.

Working on something like this?

Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.

Your details go only to Tithi and are used only to reply to you. No newsletters, no sharing.