Skip to content
Hypamoon

For teams that run on Tanda

Tanda employee leaving: future leave and shifts

When a staff member's end date passes, Tanda turns their future shifts into vacant ones. Future leave requests stay where they are. On Tanda's ideas board a manager calls declining every future request before adding the end date a pain, and another asks what to do with people who did not start.

How it goes today

  1. Search the leave screen for the leaver's future requests.
  2. Decline each request by hand before setting the end date.
  3. Find the shifts that turned vacant after the end date.
  4. Ask around who can cover each one and change the roster.

How it can go

When someone leaves, their future leave and open shifts are sorted in one go.

As soon as an end date is set in Tanda, the manager gets a list of the leaver's leave requests after that date and, once agreed, they are declined with the note "Employment ended". Next comes a list of the shifts that went vacant, each with a colleague from the same team who is available then. After the manager picks, the shifts are filled in Tanda and left for you to publish.

Say this in ChatGPT, Claude or Copilot

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

Your request

With Hypamoon, when an end date is set for someone in Tanda, send their manager a list of the leave requests after that date and decline them with the note "Employment ended" once the manager agrees. Then list the shifts that go vacant, suggest a colleague from the same team who is available for each, and fill them in once the manager picks, without publishing.

You create a personal access token yourself on the API page in Tanda and choose what it may see. It has the same access as the person who makes it, so make it from an account that sees the teams you need. It stays yours.