Skip to content
Hypamoon

For teams that run on RotaCloud

RotaCloud import shifts from a spreadsheet

RotaCloud imports employees, leave and budgets from a CSV file, and copies weeks and templates within one location. Shifts planned in a sheet, from head office or a care plan, are added by hand. Reviewers mention typing shifts in and copying single shifts across dates.

How it goes today

  1. Plan the weeks in a spreadsheet with the team.
  2. Open the rota for each location and week.
  3. Add each shift by hand with its role and break.
  4. Check the sheet and the rota against each other before you publish.

How it can go

Put a rota from your spreadsheet into RotaCloud without typing each shift.

You drop the spreadsheet in, with name, date, start, end, break, role and location per row. First you get a summary per location and week, with rows that do not match a person, role or location. After you approve, the shifts go into RotaCloud unpublished, and you publish them there when the rota looks right.

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, take the rota from the spreadsheet I send, with name, date, start, end, break, role and location per row, and add the shifts to RotaCloud unpublished. Show me a summary per location and week first, with rows that do not match a person, role or location, and wait for my approval.

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.