Platform
Every hour on site, on the record.
The hour is the unit everything else is built on — payroll, the invoice, the report. If the hour is retyped from a paper timesheet on Friday night, everything downstream inherits the error. Moonfoos captures the hour where it happens: a tap on an NFC tag or a clock-in in the app, on site.
Clock-in & hours
Why teams trust the hours
From the site, not the memory
Hours come from the clock-in that actually happened, on site. No “I think I was there till six.”
No disputes at month-end
When the worker, the manager and the payroll all read the same time-stamped record, the argument about hours mostly disappears.
The timesheet writes itself
Assigned tasks and clock-ins generate the timesheet automatically. There is nothing to add up.
Two ways to clock in
NFC tag at the site
A tap on the tag at the door marks the shift start and end. It works offline, it works with gloves on, and it is hard to fake from the van.
Mobile clock-in
No tag? The app clocks in by location and time. The worker sees their own hours as they happen.
Shift check-in and check-out
NFC tags track the whole shift — start, breaks, end — so the record is the shift, not just a single tap.
The timesheet that builds itself.
Assigned tasks and on-site clock-ins generate the timesheet automatically. Day, evening, weekend and public-holiday hours are tagged as they happen, so by month-end the timesheet is a review, not a rebuild.
Tagged by shift type
Every hour is already classified — day, evening, weekend, holiday — so the rates land where they belong.
The worker sees it too
The cleaner checks their own hours in the app, the same ones that feed payroll.
The worker’s view
Their hours, live
The cleaner sees the hours as they accrue, not a month later on a payslip they have to trust.
Their schedule, in their language
Shifts and site notes in the worker’s own language, so a new starter is not reading a rota they are still learning.
FAQ
Questions we get asked
Do workers need special hardware?
No. The only thing that goes on site is the NFC tag, and any phone with NFC reads it. A worker whose phone cannot read tags, or a site without one, can clock in from the app by location and time instead — the shift is still recorded from the site, just by a different route.
What happens if the NFC tag is damaged?
The shift falls back to a mobile clock-in, so the hours are still captured at the site while the tag is replaced. The record shows which method each clock-in used, so a run of mobile clock-ins at one site is something you can see and act on rather than something you find out about at month-end.
Can hours be edited after the fact?
A manager can correct a clock-in that was wrong, and the correction is logged against the original rather than replacing it — the record keeps the change and who made it. The worker sees the corrected hours in their own app, which is what keeps a correction a conversation instead of a dispute. Nothing about the hours is invisible to the person who worked them.
How does this work across sites and shifts?
A worker who moves between sites in a day clocks in at each one, and each shift carries its own site, task and shift type. The timesheet is assembled from all of them, so a split day or a two-site round is one record rather than two sheets stapled together. The rates follow the shift type, not the site.
Goes well with
See the clock-in on your sites.
Thirty minutes, live product, no slides. Bring your least favourite site and we will show you what the hours look like from it.