Skip to content
Hypamoon

For teams that run on Shiftbase

Shiftbase contract hours over two or four weeks

Shiftbase works with contract hours per week. Teams whose contracts run over two or four weeks write that they have no overview of planned hours against the contract for the full cycle.

How it goes today

  1. Open the schedule for the first week and note each person's hours.
  2. Do the same for the next week or weeks of the cycle.
  3. Add leave and sick hours for those weeks.
  4. Compare the totals with the contract hours times the number of weeks.

How it can go

See who is under or over their contract hours for the whole cycle, before you publish.

Before you publish, a list per department with each employee's scheduled hours plus leave over the cycle you choose, next to the contract hours for that cycle, and who is under or over and by how much. You set the cycle once, for example two weeks starting on a given Monday.

Say this in ChatGPT, Claude or Copilot

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

Your request

With Hypamoon, before I publish the schedule in Shiftbase, give me a list per department of each employee's scheduled hours plus leave over our two week cycle, next to their contract hours for those two weeks, and show who is under or over and by how much. I will tell you the Monday our cycle starts.

You create the Shiftbase API token yourself under Settings, App center, Public API. Shiftbase asks for the App Center Plus add-on on your subscription for this. It stays yours.