Skip to content
Hypamoon

For teams that run on RotaCloud

RotaCloud labour cost report per location

RotaCloud's reports show hours and costs per location, and its help centre says the team does not build custom reports. One reviewer keeps wage percentage per site and week by hand, because a later pay change also moves older figures. Separate RotaCloud accounts keep separate reports.

How it goes today

  1. Run the location totals report for last week.
  2. Copy hours and costs into your own spreadsheet.
  3. Add the takings for each site from the till.
  4. Work out the wage percentage and save a copy, as later pay changes move the figures.

How it can go

Wage cost per location each week, kept as it was.

Every Monday a spreadsheet with a row per location: scheduled hours, clocked hours and wage cost worked out from the pay rates in RotaCloud, next to a column for takings that you fill in. Each week is saved as it was, so a later pay rise does not change last year's figures. More than one RotaCloud account can sit in the same sheet.

Say this in ChatGPT, Claude or Copilot

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

Your request

With Hypamoon, every Monday, take last week's scheduled and clocked hours for each of our RotaCloud locations and work out the wage cost from the pay rates in RotaCloud. Put them in one spreadsheet with a row per location and a column where I add the takings, show wage cost as a share of takings, and keep each week as it was. Email it to me and the site managers.

You create the RotaCloud API key yourself in your account settings, under API and Webhooks. It opens the whole account, so give it a name you will recognise. It stays yours.