Somebody arrives
One button, and they look at their phone. The face confirms who it is and where they were standing is recorded with the punch. No card to lose, no register to sign, no queue at a machine on the wall.
They step out
Out for lunch, back in after. Nothing is filled in: the break is the gap between the two punches, worked out from the punches themselves — so it can never disagree with them.
They leave
The day closes. Two blocks with a gap in the middle is still one day, and the answer to "why was I here nine hours and paid for eight" is now on the screen instead of nowhere.
hour
At any hour, HR looks
Three numbers and a list, in the order people actually walked in. Anybody who has not come sinks to the bottom on its own, which is exactly where the next question is.
What is different about it
Every attendance system records a time. The differences are in what happens around that.
No hardware, and no app store
It runs on the phone already in the person's pocket, or one phone kept at the counter. Nothing to buy, nothing to mount on a wall, nothing to wait for an app store to approve — it installs to the home screen straight from the browser.
A day is blocks, not a total
Most systems store a first punch and a last punch. This one keeps every block and computes the breaks between them, so the hours on somebody's screen and the hours on their payslip come from the same place and cannot drift apart.
Four ways in, so nobody is stuck
Face, fingerprint, a code to their own number, or a password. A shift worker who has forgotten a password at 8am is not a support ticket.
A correction is a claim, not an edit
Staff raise a correction with a reason; only HR's approval moves a figure. A punch a camera witnessed cannot be nudged at all, by anybody, which is what keeps the one reliable time on the day reliable.
One face, one person
A face already enrolled under another name is refused rather than accepted, at enrolment and again at approval. Two people sharing one identity is the failure that makes every punch after it worthless.
Built on what a small business already has
PHP and MySQL on ordinary hosting. It sits on your own server with your own data, beside the rest of your system rather than in somebody else's cloud.
Besides the hours
Tasks, from every direction
Whatever a person has been asked to do — by a manager, by the kitchen, by HR — on one screen. A baker should not have to know which part of the system asked for a job to find out it is due today.
Their own month
Every day, block by block, in the employee's own hands. Fewer questions at the counter, and a correction raised with a reason instead of an argument.
HR on a phone
Who is in, right now, in the order they walked in. Faces waiting to be approved and corrections waiting to be decided, with counts on them.
The outlet phone
One phone kept at the counter, signed in once, showing only that outlet's staff. For anybody who does not carry a phone to work.
What it keeps, and what it does not
It asks for a camera and a location. Anybody being asked that is owed a plain answer about why.
A fingerprint never leaves the phone
The phone keeps it and only answers whether it is the right person. What is stored here is a public key, which cannot sign in as anybody and cannot be turned back into a fingerprint.
A face is stored as numbers
The reading taken at enrolment describes the shape of a face. It is not a photograph and one cannot be recreated from it.
A photo is taken at the punch
Kept with that punch so a disputed day can be checked later, and used for nothing else. The camera runs between the button being pressed and the face being read.
Location is read at the punch, and only then
Nobody is followed between punches. The position is read once, to confirm the person was at the outlet, and they see the distance before anything is saved.
A record belongs to the person and to HR
No other employee can open it, and none of it leaves the business.
Part of something larger
Talvio is the attendance and HR side of the Brown Sugar FMS Platform.
One system, one set of data
The platform connects the departments of a food business so the same numbers serve all of them: inventory, production, recipes, purchasing, warehouse, sales, live P&L, food cost and wastage — alongside the attendance Talvio records. Less manual work, and reports management can act on the same day.
Take the part you need
Talvio stands on its own. A business already happy with the rest of its systems can run attendance here and nothing else.
Built for restaurants, not adapted to them
Shift blocks, multiple outlets, staff without email addresses, kitchens where nobody has clean hands at 8am. Designed around those from the start, which is why the punch is one button and the sign-in has four routes.
For your own business
In daily use across a multi-outlet food business, every shift. If it would suit yours, the person who built it will tell you honestly.
Ganesh Jangir
Founder and lead developer of this food management platform, working on automation, data analytics and management systems for the food industry. The aim in this project has been to bring food operations, inventory, production, finance, analytics and management into a single platform.
+91 75683 08849Shahnawaz
Development and implementation support for the project, contributing to planning, testing, improvements and new features.
First time signing in
Choosing your own password, and putting your face on file so checking in becomes one button.
See how it works