Home What's new Instructions Use cases Modules Bosanski Languages

Hours from the field now land on the right site by themselves

Added

For companies running several sites at once — owners, site managers and the HR admins who close the month. When a worker clocks in on their phone, InSync 365 can now recognise which site they are standing on and book those hours to it automatically.

Nobody on the crew does anything differently. There is no site to pick, no extra tap, and no app update to wait for. You outline a site on a map once, and from then on the hours arrive already sorted.

Overview: the same clock-in before and after, the map with site zones and the order the system applies, and a month of hours split across sites.
The same clock-in, sorted · how the zones are read · what the month looks like afterwards

The same clock-in, with the site column filled in

The same four workers before and after: previously every row showed no site, now each row carries the site the worker stood on, while the one who clocked in from the yard is deliberately left blank.
① nothing changes for the crew · ② the record follows reality · ③ blank stays blank when it should

Until now, every hour that came in from a phone arrived without a site. The hours were correct and the times were correct, but which crew had been on which site was something you reconstructed afterwards — from memory, from a foreman's note, or not at all.

Now the site is written on the hours at the moment work starts. Your people open the app and clock in exactly as before; the difference shows up later, in the record.

And when there is genuinely no site to name — someone clocking in from the yard or the office — the column is left empty on purpose. The system never invents a site to fill a gap.

You outline the site once, on a map

A map showing a wide company zone with two smaller site zones drawn inside it and a worker standing in one of them, next to the order the system applies: site zone, then the worker's own zone, then the company zone, then refusal.
① a site zone wins over the company zone · ② the site is decided when work starts

On the site's own page there is a map where you draw the area that belongs to it. That drawing already existed — what is new is that it now actually does something.

When someone clocks in, the zones are read in a fixed order:

The order matters in a very ordinary situation: many companies draw one wide company zone covering the whole town, with every site inside it. Standing on a site still books the hours to that site — the wider zone does not swallow it.

One more thing worth knowing: the site is decided when the shift starts. Walking back to the yard and clocking out there does not move the hours. If a worker switches to a different type of hours partway through the day, that starts a new stretch — and that stretch gets the site of wherever they are standing at that moment.

The in-app map that shows your crew where they are allowed to clock in now draws the site zones as well, so what they see on the screen matches what actually happens.

What it changes at the end of the month

A monthly hours-by-site report where the same 1,430 hours that used to sit in one unassigned block are now split across three sites with a small unassigned remainder, next to what that unlocks.
Labour cost per site · invoicing you can defend · planned against actual · and nobody types it in

The reports were always there — timesheets and site reports could already group by site. What was missing was the site itself on hours coming from the field, which is why a month of work sat in one undivided block.

Labour cost per site stops being a guess. Hours attach to a site, so the wage cost of that site can simply be read.

Invoicing gets something behind it. When a client asks what those hours were, the answer is in the record rather than in someone's recollection.

An overrun shows up while you can still act on it. A site burning through more labour than planned is visible during the month, not at the end of it.

Nobody types any of it in. No forms for the foreman, no evening spreadsheet, nothing to forget.

Even the leftover is informative: hours that stay unassigned came from outside every site zone, which usually means the yard or the office. That is a real answer, not a gap in the data.

A site only starts collecting hours once someone outlines it on the map, on that site's own page — so you can switch this on one site at a time, and sites without an outline behave exactly as they did before. The zones are read only for companies that require location for phone clock-in. Hours recorded before this was switched on stay as they were — nothing is reassigned backwards. Drawing a site zone is done by someone with the right to edit sites. Related guide: Setting up phone clock-in for your company.