A better time-off flow for distributed teams

Start with the employee question

Most time-off flows begin with policy. Employees begin with a simpler question: can I take these dates? A useful product answers with balance, schedule, overlap, cover, and what will happen after submission.

Perelan Time Off connects the request to the people record, calendar, manager decision, and Slack where configured.

Show balance before submission

The employee should see allowance, used, pending, and available balance before they submit. If policy is complex, explain the specific calculation rather than hiding the number until after approval.

Give managers team context

A manager needs more than a yes or no button. They need to know who else is away, whether cover is named, what the employee's schedule looks like, and whether the request sits inside their scope.

Make cover explicit

Cover is not only a note. It is part of the operational handoff. Even when cover does not grant new data access, naming it helps the team plan.

Update calendar and record together

Approval should update the source request and the calendar. If a Slack button is used, Slack should call back into Perelan and the Perelan record should remain authoritative.

Handle year-end rules carefully

Carry-over and expiry rules vary. Avoid claiming jurisdictional compliance unless configuration and legal review support it. The product can show policy behavior without pretending it is local legal advice.