Skip to content
Hypamoon

For teams that run on Papershift

Papershift leave request and minimum staffing

When a leave request comes in, the absence overview in Papershift shows it with its status. Whether the shifts on those days are still covered, and who else asked for the same week, is something to check in the schedule before saying yes.

How it goes today

  1. Open the schedule for the requested days and count who is planned.
  2. Compare it with the number of people each shift needs.
  3. Look through the open requests for the same days.
  4. Approve the request and fill the gaps in the schedule afterwards.

How it can go

Each leave request with the staffing on those days next to it.

Each morning you get the new leave requests from Papershift, each with the shifts on those days, how many people they need, who is assigned and who else is off or has asked. Requests that would leave a shift below its number are at the top. You decide in Papershift as you do now.

Say this in ChatGPT, Claude or Copilot

Your chat gets connected to Hypamoon first, with this request filled in. Papershift first switches on access for your company when you ask them, which can take a few business days. After that you get the key, or create it yourself, and paste it in the portal, never in the chat.

Your request

With Hypamoon, every morning, look at the leave requests in Papershift that are not yet confirmed. For each one, show the shifts on those days, how many people each shift needs, who is assigned, and who else is off or has asked for leave. Put the requests that would leave a shift short at the top and email me the list.

Papershift first switches on the API add-on for your company, through their sales team or your customer success manager. After that an account admin creates the key under Account Settings, API. It stays yours.