Project overview
StaffGrid is an HRMS attendance and payroll platform that brings employee records, time tracking, leave decisions, salary slips and daily work coordination into one administrative workspace. This case study presents the web application, its recorded walkthrough and the supplied HRMS Attendance Android app.
The product is relevant to HR administrators and business teams evaluating custom HRMS development. Instead of describing an abstract feature list, the screenshots show the actual screens: an employee directory, attendance records, a salary workspace, leave approvals, company holidays, daily updates and task progress. A public demo provides separate Admin, Manager and Employee sign-in options.
The records shown are demonstration data. Employee counts, salaries and progress percentages illustrate the interface; they are not evidence of customer adoption, revenue or productivity gains.
The operational problem
An HR team needs to connect several everyday questions. Who works here? Who has checked in? Which leave requests need a decision? What salary record should be published? What is each employee working on? When these answers sit in unrelated tools, administrators have to switch context and reconcile records themselves.
StaffGrid's product approach is to put these workflows behind a consistent navigation system. Employee identity appears alongside attendance, leave, salary and task information, making each screen easier to interpret. The product brings people records and everyday decisions into a coherent HR workspace.
Users and workflow structure
The live sign-in page offers three demo roles: Admin, Manager and Employee. The reviewed admin workspace groups its navigation into Workspace, Time & Absences, and Activity & Collaboration. This creates a readable path from people records to operational decisions.
The dashboard summarises employee count, today's attendance, pending leave requests and active tasks. It also surfaces leave requests needing attention and recent team updates. Those links give an administrator a direct route from a summary to the underlying workflow.
The role-based entry points reflect the different jobs within an HR system: administering the workspace, coordinating a team and accessing employee workflows. This case study focuses on the administrator experience shown in the supplied materials.
Employee directory and attendance management
The employee directory combines names, employee IDs, job roles, joining dates, contact details and active status in a table. Add Employee, Edit and Delete actions are visible beside the records. Keeping identity and status together makes the directory a useful reference while reviewing attendance and salary records.
The attendance management screen displays the date, employee, in time, out time and working status. Search and date controls sit above filters for All Records, Today's Logs, Present / Working and Leaves. This supports two common review tasks: finding a particular employee's record and narrowing the list to a current operational state.
Company Settings exposes office start and end times, half-day late and early thresholds, a monthly late grace allowance and an excessive-lateness penalty option. Bringing these controls together gives the administrator a clear place to review the organisation's attendance policy.
Payroll and salary-slip workflow
The Payroll & Salary Slips screen organises records by month and year, employee, paid days, net salary and visibility. Draft and Published badges distinguish records being prepared from records marked for release. A Generate Salary action starts the preparation workflow, while View Details opens an individual salary-slip summary.
The supplied video shows a salary summary with basic monthly salary, paid attendance days, loss-of-pay or deduction days and net salary payout. These labels make the calculation context visible to an administrator reviewing an individual record.
The draft-to-published distinction is particularly useful in a payroll workflow: preparation and review can be understood separately from release. The demonstrated scope covers salary records and payslip review; statutory filings and bank disbursement are outside this case study's verified scope.
Leave approvals and holiday planning
The leave-management table shows filing dates, employee identity, requested dates, full-day information, paid or unpaid type, reason and decision status. Pending requests expose Approve and Reject actions; approved requests remain visible as records of the workflow.
The holiday directory maintains dates, holiday names, descriptions and a type label, with Add Holiday and Delete controls. Together, these screens give administrators a place to review time-off requests and maintain the organisation's working calendar.
Holiday entries can be reviewed alongside leave requests when planning team availability. The sample calendar illustrates how dates, names and descriptions are presented together.
Tasks and daily team updates
StaffGrid extends the HR workspace with task assignments and work updates. Task cards show an assignee, employee ID, status, percentage progress and last update date. Assign Task, Update, Edit and Delete controls are visible. Pending, in-progress and completed states are written as text as well as indicated visually.
The Daily Updates Directory provides employee and date filters with a clear reset action. The dashboard's recent activity includes Plan of Action and End of Day Update entries. This connects the question of who is available with what the team is working on, while keeping task progress separate from attendance status.
Interface and product design
The interface uses a light workspace, a persistent sidebar, purple navigation accents and rounded panels. Tables suit employee, attendance, salary and leave records; cards suit task assignments where progress is the main focus. Section headings and short descriptions explain the purpose of each screen before the user reaches the data.
Primary actions appear near the section heading. Row-level actions stay beside the affected record. Draft, Published, Pending, Approved and Working labels communicate state without requiring a user to understand colour alone. The live site also exposes a theme toggle and a compact-screen menu.
This layout provides a consistent foundation for a custom employee-management system. The same record identity, status treatment and action placement recur across modules, giving users a familiar pattern as they move between HR tasks.
Web delivery and Android companion
The live web application uses Next.js and is delivered through Vercel. HR administrators can open the browser-based workspace to review records and move between modules. The companion Android deliverable extends the project's delivery scope to a dedicated attendance application.
The Android deliverable is HRMS Attendance version 1.0, with a minimum SDK of 24, corresponding to Android 7.0. Its universal package includes ARM and x86 architectures. Package inspection identifies camera and internet permissions and bundled camera, face-detection and TensorFlow Lite components. Mobile attendance behaviour and recognition accuracy require a device test; they are not inferred from bundled libraries.
The original APK is available in Project downloads below, with its version, size and SHA-256 checksum. It is a direct download for Android evaluation. The web demo and recorded walkthrough provide a quick way to explore the HR interface before evaluating the mobile build.
Delivered scope and evaluation
The reviewed deliverables are a live web demo, a 43.4-second silent product video, six distinct desktop screenshot views and an Android APK. The web navigation covers nine areas, including the dashboard and settings. These are observable scope facts, not percentage improvement claims.
For a production rollout, useful acceptance checks include unique employee identifiers, employee access boundaries, attendance corrections, leave decisions affecting paid days, salary draft-to-published transitions and Android synchronisation. A team should also measure the time taken to prepare payroll and resolve attendance exceptions before and after adoption.
This review is based on the live demo, screenshots, video and static APK inspection. It does not establish the backend stack, production security, runtime Android integration or measured commercial results. The case study documents the demonstrated product so prospective buyers can discuss their own requirements with concrete examples.
Planning a custom HRMS project
Start with your employee lifecycle, attendance policy, approval responsibilities and salary rules. Then map the web and mobile workflows that each role needs. This keeps a custom HRMS attendance and payroll project tied to the organisation's actual working process.
Explore ShubhDigi's HRMS development services, review more case studies, or discuss an HRMS project. Share your team structure, existing tools and required integrations so the scope can be based on concrete workflows.
