Skip to content
Hypamoon

For teams that run on Tanda

Tanda cancel leave request, kept as cancelled

Tanda knows three states for a leave request: pending, approved and declined. On Tanda's own ideas board, the most voted open idea since 2020 asks for a way to cancel leave, because a request that is called off ends up as declined. Staff can withdraw their own pending request, but an approved one goes back through a manager.

How it goes today

  1. A staff member messages their manager that the leave is off.
  2. The manager declines the approved request in Tanda.
  3. The real reason is written down somewhere else, if at that.
  4. Later, nobody can tell a refusal from a cancellation without asking around.

How it can go

Cancelled leave shows as cancelled, with the reason.

Staff ask to cancel through a short form and give a reason. Once their manager agrees, the request is closed in Tanda the way a manager closes it today, with "Cancelled" and the reason in its note. Your own leave overview then has four groups: pending, approved, cancelled and declined, with who asked and when.

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, give our staff a short form to ask for their Tanda leave to be cancelled, with a reason. Send it to their manager to agree. Once agreed, close the request in Tanda with "Cancelled" and the reason in its note, and keep a leave overview with pending, approved, cancelled and declined as separate groups.

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.