Skip to content
Hypamoon

For teams that run on awork

awork overtime: hours worked against target

awork knows the weekly hours of each person, their absences and the public holidays of their region, and it records the time they track. A running balance of hours worked against hours due is something teams put together themselves.

How it goes today

  1. Export the tracked time every month.
  2. Keep holidays and sick days in a separate spreadsheet.
  3. Book absences on a placeholder project so nobody ends up short.
  4. Work out the difference per person by hand.

How it can go

Everyone sees their overtime balance, with leave counted.

Each month you get, per person, the hours due from their weekly hours in awork, minus their absences and the public holidays of their region, next to the hours they tracked, and the difference. The balance carries over from month to month, starting from an opening figure you give. People see their own balance on a page of their own, and you get a note when someone goes past a limit you set.

Say this in ChatGPT, Claude or Copilot

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

Your request

With Hypamoon, work out overtime for our awork team. Per person and per month, take their weekly hours from awork, subtract their absences and the public holidays of their region, and compare that with the time they tracked. Keep a running balance that starts from a figure I give per person. Give each person a page with their own balance, send me the overview at month end, and tell me when someone goes over a limit I set.

An admin creates the awork key under Settings, Integrations: add an API client, then Manage API Keys. It stays yours.