Skip to content
Hypamoon

For teams that run on RotaCloud

RotaCloud deleted shifts when someone leaves

RotaCloud can restore shifts deleted on the rota. Its help centre says that shifts removed because an employee or location was deleted do not show there and are permanently lost, and that deleting an employee removes their future shifts.

How it goes today

  1. Look through the rota for the leaver's future shifts before you delete them.
  2. Note the dates and times somewhere else.
  3. Delete the employee in RotaCloud.
  4. Add the shifts again for colleagues, one at a time.

How it can go

A leaver's future shifts handed to a colleague, rather than gone with the profile.

Each night a copy of the coming eight weeks of the rota is saved. When someone is deleted, the location manager gets the list of their future shifts from that copy, with a suggested colleague who is free and works that role. After the manager picks a person per shift, the shifts are added again, unpublished.

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 night, keep a copy of our RotaCloud rota for the next eight weeks. When someone is deleted, email the location manager their future shifts from that copy with a suggested colleague who is free and has that role, and add the shifts again, unpublished, for the people the manager picks.

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.