Help guide
How to manage staff attendance, leave and shifts
Who was present, for how long, and who was awayKiske liye: Whoever marks attendance — a supervisor, a store manager, an office admin, or the owner.
Where the screens are
Attendance & Leave is a module of its own, and Payroll reads from it — payment days come from here and nowhere else.
| Tab | What it does | When you open it |
|---|---|---|
| Attendance register | The day register — one status chip per person, with undo | Every day |
| Today | Who is in right now, by shift and line | Through the day |
| Punch pad | Tap IN/OUT for a person, import the device export, run auto-attendance | Daily, if you use a device |
| Punches | Every punch as its own row — the machine it came from, whether it was outside the location, and the day it counted into | When a punch is missing or questioned |
| Leave | Apply, approve, balances, the leave ledger and policy setup | When someone asks for leave |
| Shifts | Shift assignment, roster, shift and WFH requests, weekly-off generator, holiday year | When a shift changes |
| Shift swaps | Every swap request — asked, agreed, approved, refused — with both people and both shifts on one row | When a swap is asked or to be approved |
Attendance — the day entry
Each person has five chips: P (present), A (absent), H (half day), L (leave), W (on duty or working from home). Every row also shows the shift and hours the person is expected for, and what they were yesterday — so you mark with the day's context, not five bare buttons.
App me: Attendance & Leave › Attendance register
- Pick the date (today by default) — month and day sit in one compact toolbar with the counts and the mark-all button beside them.
- Tap the right chip for each person. The mark is saved at once and the toast offers UNDO — tap it and the day returns exactly as it was. Tapping the same chip again clears it.
- Enter overtime hours in the OT box on a P or H row.
- Use "Mark all present (N)" — the button names how many people it will change before you tap it. People on approved leave and people on their weekly off are never touched; one tap of Undo takes the whole batch back.
- W chip
- Out on work or working from home — counts as a full day for pay, exactly like P.
- "X unmarked" pill
- How many PEOPLE have no status today — the only count payroll cannot see. Holidays and weekly offs are not in it, because those days nobody works. On a holiday or the shop's weekly off the pill names the day instead, and the count is zero.
- Approved leave on a row
- The day already belongs to an approved leave. The register will not overwrite it; it links to the leave, and the chip row's "Apply leave" opens the real application form with the person already picked.
- Month closed banner
- When a payroll run has closed a month, every screen says so in the header and marks are refused before you type — with the arrear/LWP path named in the refusal.
- auto pill
- This day came from punches. Tapping a chip makes it manual, and who changed it and when stays on the record.
Punch pad — let the device do the marking
Attendance from timestamps rather than taps. A biometric device or a phone sends punches, and the day builds itself.
App me: Attendance & Leave › Punch pad
- Both actions are in the Actions rail on the right (behind "Open actions" on a phone).
- Open "Import from device" and paste the device export (CSV). A device ID that matches nobody shows in red — fill that person's device ID in their employee record first, then save the punches.
- Or punch from a phone: pick the person, tap IN or OUT. Location is captured on its own.
- Open "Run auto-attendance", pick a date and run it — the day's punches pair up into P, H or A.
- Shift rules
- Each shift sets the hours below which a day is half or absent, how late counts as late, and whether overtime is counted.
- Geo-fence
- When a shift is tied to a location, a punch outside it is flagged. The attendance still counts; the flag is for a person to look at.
- Skip in auto
- Keep a wrong punch out of the calculation without deleting it.
Punches — every punch, and the day it counted into
The punch register. Where the punch pad is for the person standing at the gate, this is for the day afterwards: who is missing, which machine sent a punch, who punched from outside the location, and which punches no day has counted into yet.
App me: Attendance & Leave › Punches
- Machine
- The device a punch came from, by its name. A punch typed by hand reads Manual, a phone punch reads Mobile.
- Location
- Marked when the punch landed outside the shift's location fence. The attendance still counts — the flag is what a person looks at.
- Merged taps
- A double-tap inside two minutes is absorbed into one punch. This shows how many taps went into the row, so a person who swears they punched twice can be answered.
- Counted into
- The day's attendance row this punch was rolled into — the date and its status, linking straight to that day in the attendance register. "No day claimed it" means no run has used the punch yet; it is the list to work through before closing a month.
- Skip in auto
- Keeps a wrong punch out of the auto-attendance calculation without deleting it — the row stays as evidence.
- It opens on today. Widen the date range, or pick a person, a side (IN/OUT), a source, or the location flag, to narrow it.
- The rail counts what is in, what is out, what is outside the location and what absorbed a double-tap — tap a count to filter by it.
- The list under the table is over the rows you filtered, so a narrowed register never quotes the whole month's totals.
Leave — from request to balance
Every leave type has its own rules, and a balance is the sum of a ledger — never a number somebody typed.
App me: Attendance & Leave › Leave
| Type | Meaning | Worth knowing |
|---|---|---|
| CL | Casual leave | Up to 3 days at a stretch |
| SL | Sick leave | — |
| EL | Earned leave | Accrues monthly, carries forward, can be encashed |
| LWP | Leave without pay | The day's pay is deducted |
| COFF | Compensatory off | Earned by working a holiday or weekly off |
| OPT | Optional holiday | A few a year, chosen by the employee |
- On Requests, the button is "Apply leave". Pick the person, type and dates — the balance shows in the same dialog — then save.
- If the app refuses, the dialog stays open and says why: no balance, probation, overlap, a blocked date, or backdated.
- Approving writes the ledger entry and marks the days L in attendance.
- A comp-off for working a holiday is in the Requests rail: "Comp-off request".
- On Balances, the button is encashment, and the rail has "Adjust balance".
- Leave balances has its own page, laid out as a register: one row per person per leave type with opening, credit, used and closing for a date range — exportable, and every figure a sum of the same ledger rows the balance chip reads.
- Comp-off has its own page too ("Comp-off (worked a holiday)"): every request — pending, approved, rejected — in one table, with the form on the page. A day already paid at overtime rates is refused as a comp-off, and the refusal names the day.
- On Setup, the button is "Assign policy" — person, policy and leave year. The rail has "Block dates" and "Create leave year".
- After assigning, "Allocate" on that row writes the quota to the ledger in one tap.
- "Run accrual" and "Run expiry" sit on the policy card. Run accrual once a month and earned leave builds up on its own.
Shifts — who works which hours
Three segments: Roster, Requests and Setup. A shift decides what counts as late, half day and absent, so attendance is only as right as the shift behind it.
App me: Attendance & Leave › Shifts
- On Roster, "Assign shift" — pick the people, the shift and the dates. A rotating team gets one assignment per period. Two people holding the same day twice reads RED in the assignment list — fix it before payroll pays the day twice.
- The roster's count line under the grid says how many people each shift holds on each of the next 7 days. A shift with a minimum set (edit the shift, "minimum people") shows its shortfall as a pill on the day it falls short.
- On Requests, "Shift change request" — the employee or a manager asks, an approver decides. The rail has "WFH / on-duty request".
- Shift swaps have their own page (Attendance & Leave › Shift swaps): both people and both exchanged shifts on one row, saved views for what is waiting to be agreed and what is waiting for approval, and every decision checked by the app — approving an already-decided swap does nothing and says so. Open a swap to see its ribbon: Asked → Both agreed → Approved. Approve here or on the Today board; the roster changes the same way either way.
- On Setup, "Weekly off generator" writes the weekly offs for a period, so nobody is marked absent on their day off.
- On Setup, "Holiday year at a glance" shows all twelve months as strips with the year's totals. In November it warns if the NEXT year has no holidays yet — copy the calendar before January, or every day becomes a working day.
Closing the month
Payroll reads payment days from here. Close attendance first and the salary run has nothing to argue with.
- On Attendance, bring "X remaining" to zero for every day of the month.
- On Check-ins, run auto-attendance for any day punches arrived late, and look at flagged punches.
- On Leave, decide every pending request for the month — a pending request is not leave, and the day counts as absent.
- Then open Payroll › Run. Its readiness check stops on anyone with an unmarked day.
Reports
Sixteen reports behind one picker. Pick the report, pick the period, and export it as CSV or Excel.
App me: Attendance & Leave › Reports
- Pick a report. The date box changes with it — a period for most, a number of days for missed punches, a month for the team calendar.
- Read it on screen; a row opens the record it is about.
- Export to CSV for a spreadsheet, or to Excel when somebody wants it formatted.
| Report | What it answers | When it is asked for |
|---|---|---|
| Late and early exit | Who came late or left early, and how often | When a pattern is suspected |
| Missed punch | A day with an IN and no OUT | Before closing the month |
| Shift-wise | How each shift attended | When a shift looks short |
| Roster | Who is on which shift over a period | While planning the week |
| Working hours | Hours worked against shift hours | For overtime and billing questions |
| Absenteeism | Absence rate, by month and by weekday | When absence is being discussed |
| Leave applications | Every application: pending, approved, rejected, cancelled | At any audit of leave |
| Employees on leave | Who is away in a date range | When planning cover |
| Leave encashment | Leave turned into money | At settlement time |
| Comp-off | Earned against a worked holiday, and what was used | When a comp-off is claimed |
| Requests | Attendance and shift requests across statuses | When somebody says they asked |
| LWP summary | Unpaid days per person per month | Before the salary run |
| Statutory leave register | Opening, availed and closing per leave type for a year | For an inspection |
| Team calendar | A month grid showing who is away when | While approving leave |
Put one real day through it.
Not a sandbox with sample data — your own bills, your own items, your own customers. By evening you will know whether this runs your business.
