Ways of checking in
Each branch decides for itself how its staff record their hours. A head office can use phones while a factory floor uses a machine on the wall, and the same company can do both.
- The Mini App on a phone. Staff open MekongHRM in Telegram and check in. What they have to send with it is yours to choose — see below.
- The office code. A tablet by the door shows a code that changes every few seconds. Staff scan it.
- A time clock. A ZKTeco machine on the wall, for companies that already have one.
Before you start
- The
attendance.configurepermission. The Owner and HR roles hold it.
Steps
Every setting on a branch's card waits for you: nothing changes until you press Save at the bottom of the card, and a message then says it was saved. Cancel puts the card back to what is saved.
Choose the ways a branch uses
- Open Shifts.
- Against each branch, switch on the ways you want. A branch can use more than one.
Choose what a phone check-in must carry
Under What a phone check-in must carry, four choices:
| Records where they were | Records who it was | |
|---|---|---|
| Phone only | no | no |
| Phone and location | yes, and refuses somebody outside the circle | no |
| Phone and photo | no | yes |
| Phone, location and photo | yes, and refuses somebody outside the circle | yes |
They are two switches rather than four methods, and it helps to know which problem each one solves. A circle around the branch catches somebody clocking in from home or from the wrong site; it cannot tell whether the person holding the phone is the person it belongs to. A photograph is the other way round. Most companies want both, an office where everybody knows everybody wants neither, and a site with agency labour usually wants the photograph first.
Every branch starts on Phone, location and photo, so nothing loosens unless you loosen it.
A position sent by a phone is always stored with the punch, even on a branch that does not ask for one. What the setting changes is whether it is measured against the circle, not whether it is kept — somebody with location switched on has done nothing wrong.
Set how early and how late people may clock in
Under Shifts, each shift carries two numbers: how many minutes before it starts somebody may clock in, and how many after. The default is two hours either side.
They apply around each end of each stretch, so the same pair also decides when people may clock out. A shift of 08:00–17:00 set to 120 and 60 can be clocked into between 06:00 and 09:00, and out of between 15:00 and 18:00.
On a shift of two stretches the windows may be open at the same time, and a punch goes to the first of them in order — clocking into the morning, out of it, into the afternoon, out of it — that is open and not yet done. With 08:00–12:00, 13:00–17:00 and two hours either side, the morning arrival is open until 10:00, the morning departure from 10:00 to 14:00, and the afternoon arrival from 11:00 to 15:00. At 11:53 with nothing punched yet, the button says clock out of the morning; pressed, it says clock into the afternoon. The attendance grid reads the punches the same way, so it always says what the button said.
Outside those windows the button in the app is off, and it says when it comes back on. Somebody who worked and missed the moment files a missed-scan request instead — which leaves a reason and an approver behind, where a punch at eleven recorded as an arrival leaves neither.
Two things worth knowing before you tighten it:
- The middle of a shift is not a window. That is the point of the setting,
and it is also the thing that generates missed-scan requests. If your staff routinely arrive more than an hour late for good reasons, a small number here makes more work, not less.
- A day nobody was rostered for has no window at all. Somebody clocking in
on a rest day is never refused by this, because there is no shift to be late for.
Set where the branch is
A phone check-in is measured against a circle around the branch, so a branch asking for the position needs one before anybody can use it.
- On the branch, set the position and how far from it a check-in still counts. The default is 150 metres. The position is one box, Google Map Lat,long: right-click the spot in Google Maps, click the numbers at the top of the menu to copy them, and paste them as they are,
latitude,longitude. Anything else is refused under the box and the old position is kept. - Somebody standing outside that circle is refused, and told how far away they are.
Put the code on a tablet
- Open Check in here on the tablet you want to leave by the door.
- Leave the page open. It fetches a new code by itself every half minute.
Check the face too
On the Business plan and above, a branch that asks for a photo can also compare it with the photo on the employee's record: Face check, under the photo option in Attendance. A face that does not match is refused and the employee takes the photo again. See Face check.
Reminders
The bot's clock-in and clock-out reminders are not set here. Each person chooses their own in the Mini App, under Me and settings → Notifications: whether to be reminded, how many minutes before a stretch starts (5 by default) and how many minutes after it ends (15 by default). A clock-out reminder never comes after the time allowed to clock out has closed — on an 08:00–12:00 / 13:00–17:00 shift the morning's departure closes at 13:00, so somebody who asked for an hour is told at 12:55. Nobody exempt from clocking in is reminded, nor anybody on leave for that stretch. Nobody is reminded on a weekly rest day or on a public holiday of their branch either.
What you should see
A check-in appears in Attendance straight away — there is no wait for anything to run overnight.
The photograph and the position are kept with the check-in for 90 days and are shown only to people who hold attendance.view_evidence. That is a separate permission from being able to see the hours themselves, so a manager can see who was late without seeing everybody's photograph.
A branch in more than one place
A shop and its warehouse two streets away are one branch: the same shifts, the same holidays, one report. They are two places on the ground, so a branch can have more than one location — up to 30.
In Attendance, or on the branch's own page, each location is a row with three boxes:
- Name of this location (optional) — "Shop", "Warehouse". It is shown to the employee when they are outside the area, and on the off-site report, so both say which place the distance is measured from.
- Google Map Lat,long — the point, pasted as Google Maps copies it.
- Radius — each location has its own. A warehouse yard needs more room than a shop front.
Add a location adds a row and Remove this location takes one away. Nothing changes until you save.
A check-in counts as at the branch when it is inside any of the branch's locations. Somebody outside all of them is told how far they are from the nearest one. The map on the check-in screen draws every location and opens on the nearest.
Check-ins already recorded keep the answer they were given: adding, moving or removing a location never turns an old check-in from inside to outside.
You do not have to type the coordinates
If you never set a point for a branch, the first person who checks in at it sets one — the branch is placed where they were standing. Most companies do not know their own latitude, and somebody standing at the door knows where the office is better than a pin dropped on a map does.
It happens once. After that the branch stays where it is, however far away the next punch comes from, and only Attendance moves it. Three kinds of check-in are ignored, so the branch is not placed somewhere wrong:
- A position the phone is unsure of. If the phone only knows where it is to within more than 150 metres, the radius a new location starts with, nothing is placed and the check-in is refused as before.
- Anybody allowed to work away from the branch. Their position is the one that says least about where the office is.
- Any check-in at a branch that already has a location.
The activity log records it, with the name of whoever's check-in placed it. If it landed somewhere wrong — somebody checked in from home on their first day — correct it in Attendance and it stays corrected.
If something goes wrong
You are {distance} m from {branch}. Move closer, or ask HR to record this for you. — the message says how far away they are, so they know whether to walk closer or to ask you to record it for them. The distance is measured from the branch position, not from wherever the phone was last.
Somebody genuinely works away from the branch. Sales and field engineers can be allowed to check in from anywhere. Their position and photograph are still recorded — what the setting skips is the refusal, not the evidence.
MekongHRM needs your location to check you in. Allow it in your phone settings and try again. — the employee refused MekongHRM permission to see their location, which is a phone setting rather than something you can change for them.
That code has expired. The tablet shows a new one every few seconds, so scan it again. — the tablet's code has moved on since they started scanning. Scanning again takes a moment. If it keeps happening, check the tablet is still connected: a tablet that has lost its connection shows This tablet has lost its connection. The code may be out of date — tell your HR team..
Your branch has no location set yet. Ask HR to set it before you check in. — the branch has no position yet, so there is no circle to be inside. This normally fixes itself: see below.
Last checked 18/09/2026