Skip to content
Hypamoon

For teams that run on Deputy

Deputy averaging hours over a roster cycle

Some awards and agreements let you average ordinary hours over a few weeks or a roster cycle. Deputy's award guides say it does not take averaging into account, so the average is kept somewhere else and overtime is put right when the cycle closes.

How it goes today

  1. Export each employee's hours at the end of every week.
  2. Add them up in a sheet per roster cycle.
  3. Compare the running total with the agreed hours for the cycle.
  4. Correct overtime in the pay run when the cycle closes.

How it can go

See who is heading over their average before the roster cycle ends.

Each week you get a list per location of the employees on an averaging arrangement: hours worked so far in the cycle, hours still rostered, and what that adds up to against the average you set, such as 38 hours a week over four weeks. People who will go over are at the top while there is still time to change the roster. You choose the cycle and who is on it; pay stays in Deputy.

Say this in ChatGPT, Claude or Copilot

Your chat gets connected to Hypamoon first, with this request filled in. You paste your Deputy key in the portal, never in the chat.

Your request

With Hypamoon, every Monday, for the employees I put on an averaging arrangement, add up the hours they worked in Deputy so far in the current roster cycle and the hours still rostered. Compare that with an average of 38 hours a week over four weeks, put the people heading over at the top, and email the list per location to me and the managers.

You make the Deputy access token yourself under Business Settings, Developer, OAuth Clients, with Get an Access Token. It stays yours.