Most attendance systems record what somebody typed, not who was standing there. Confrmo: I’m Here makes every shift start, break and clock-out a real scan, tied to a named worker and to the workplace they are actually in. No shared PINs. No cards passed down the line. No signing the book on someone else’s behalf.
A timesheet is read when there is a dispute, an invoice, an audit or an incident, which is weeks or months after the shift it describes. By then the only thing anyone has is the record. If that record was a four digit code anyone on site knew, it does not settle the question, and everybody in the room knows it does not.
A PIN, a fob or a card is a thing, and things get lent to a colleague running late. The system records a clock-in that is entirely genuine and entirely wrong.
Most systems record a missing entry, which looks identical whether someone never arrived, arrived and forgot, or arrived somewhere they should not have been.
A problem discovered at the end of the month is a payroll argument. The same problem seen at 07:15 is a phone call that gets someone to site.
Everything below is what the service does today, in the release that is running now.
Every clock-in and clock-out is a real Confrmo VCode scan from the worker’s own signed-in device, tied to a named person rather than to a code that can be handed over.
Scans are matched to the workplace they belong to, with a grace window you set for shift-start timing. A scan somewhere else is recorded and flagged, not quietly discarded.
Assign workers to workplaces, publish the schedule, and let the record be measured against what was actually planned instead of against nothing.
No-show, late, missed clock-out, scanned out of location. Each one is raised as its own thing with the reason attached, so a gap is never just a gap.
Corrections are requested and recorded rather than overwritten, so the history shows both what was captured at the time and what was changed afterwards.
On duty now, on-time rates, scan volume, device use and location patterns across every workplace, updated while the day is still running.
Leave is booked and approved alongside attendance, so an absence that was agreed does not come back as an exception somebody has to explain.
Shift reminders, clock-out reminders and no-show alerts run automatically, so a problem surfaces during the shift rather than at the end of the month.
There is no hardware to install, no terminal to mount on a wall and nothing to wire in. The workplace is a location you draw, and the reader is the phone the worker already carries.
Give the site a location and assign the people who work there. If you already hold a list of workers, import it rather than typing it in again.
At shift start, at breaks and at clock-out, using the Confrmo app on iOS or Android. It takes about as long as looking at the time.
The dashboard shows who is on duty now and flags anything that did not go to plan, with the reason. Nobody has to collect anything at the end of the week.
Illustrative preview. Sample data, not a live account.
I’m Here is not a standalone time clock with a login bolted on. It runs on Confrmo’s runtime identity and on the same VCode scanning used across the platform, which is the reason a scan means a person rather than a device. The verification methods underneath are the subject of Confrmo’s pending patent applications.
Attendance software is bought on promises and judged on the day something goes wrong, so it is worth saying plainly where the edges are.
Workplaces and schedules, verified clock-in, breaks and clock-out, exceptions with reasons, corrections, time off, audit history, reporting and analytics, on iOS, Android and the web.
Timesheets and payroll export, and scanning while a device is offline. Both are the next stage rather than quiet omissions.
Face checks are used as a supporting signal and are never treated as proof on their own, so nothing here should be wired to a door or a lock on that basis alone.
Every scan is a Confrmo VCode read by that worker’s own signed-in device, so it is tied to a named person rather than to a code, a card or a PIN that can be handed over. A colleague cannot produce a scan on someone else’s behalf without their account.
The scan still records, and it is flagged as out of location with that reason attached. Nothing is silently dropped, because a missing record and a record with a problem are two very different things when a shift is later disputed.
No. Location is used at the moment of a scan and nowhere else. Storing the coordinates of a scan is opt-in, the retention period is set by the organisation, and an hourly job deletes coordinates once that period has passed, so the promise is enforced rather than simply stated.
The Confrmo app on iOS and Android. The dashboard runs in any modern browser, with no plugin and nothing to install.
A missed clock-out is raised as its own exception rather than left as a gap, and a reminder goes out before it gets that far. A correction can then be requested against the record, so the history shows both what was captured at the time and what was changed.
Not in this release. Attendance, exceptions, reporting and analytics are what this stage covers. Timesheets and payroll export come next.
Access is scoped by role and by workplace, so a site manager sees their own sites and not the whole organisation. Exporting data out of the dashboard is restricted to administrators by default, deliberately, because an export leaves the system and can be forwarded to anyone.
Staff access only. Use your Confrmo account.
Loading…
Not signed up yet? Start at confrmo.com.