Time-Out Zone

One request form, every kind of time off

A time off request here is one modal, three modes. Single days, recurring patterns, or a batch of date ranges, each checked against balance and policy before anyone hits submit. No paper form, no guessing.

Get startedView pricing
  • Lab Test Analyzer logo
  • Promics Edge logo
  • SelfHacked logo
  • SelfDecode logo
  • OmicsEdge logo

Recurring time off, planned once

Every-other-Friday off, a monthly appointment, a weekly class: set the pattern once and it becomes a series of individual requests, each one visible and decided on its own.

  • Daily, weekly, monthly, or yearly patterns with any interval, ending after a count or a date.
  • National holidays are skipped automatically; any single occurrence can be skipped by hand with a reason.
  • Up to 120 occurrences per series, all grouped under one batch you can withdraw together.

Bulk requests, one submit

When someone knows their year ahead, they don't file it one request at a time. Add up to 20 date ranges in one form, each with its own leave type, duration, and coverage person.

  • Every row is validated against balance and policy before anything is submitted.
  • Overlapping rows are caught inside the form, before they reach an approver.
  • Approvers still see and decide each range individually, so nothing hides in a bundle.

Three modes, one form

Single, Recurring, and Bulk live in the same modal, with the same leave types, checks, and approval routing behind each.

Recurring as a series

A pattern expands into individual requests that stay grouped, so a series is easy to submit and honest to approve.

Bulk without the blur

Up to 20 ranges in one submit, each row carrying its own type, duration, coverage, and reason.

The answer before the ask

Balance impact, approval route, advance notice, and duration rules are shown in the form, before submit.

The fine print, built in

Half days and hours

A half day counts as 0.5 day, four hours; hourly requests go from 15 minutes to a full day, where the leave type allows it.

Drafts that wait

Any request can be saved as a draft and submitted later; editing a pending request restarts its approval from step one.

Past dates, by policy

Leave types can allow past-dated requests, so forgotten days get recorded instead of lost.

Coverage named up front

Each request can name a backup person, and team coverage rules can block a submit that would leave a gap.

Every rule here is set per leave type, so vacation, appointments, and special leave can each behave differently in the same company.

Single flow

A request that answers back

Pick a leave type, choose full day, half day, or hours, and pick the days. The form fills in the rest before you commit.

  • The exact approval route is shown before submitting, not discovered after.
  • Multi-day requests can get a per-day breakdown: full day, morning, afternoon, or skip, day by day.
  • Reasons, supporting documents, and a coverage person attach right on the request.

Checks

Policy runs before the approver does

Every submit, in every mode, passes the same server-side checks, so approvers never see a request that breaks the rules.

  • Balance impact is simulated up front, including borrowing limits where negative balances are allowed.
  • Blackout periods, advance notice, minimum and maximum duration, and waiting periods all block at submit, not after.
  • Overlaps with existing pending or approved requests are rejected before they happen.

After submit

Plans change, records keep up

A submitted request isn't carved in stone, and none of the changes lose history.

  • Pending requests can be edited; the change keeps them pending and restarts approval from step one.
  • Pending requests can be withdrawn, one at a time or a whole batch at once.
  • Approved time off that hasn't started yet can still be cancelled.

Working days

Only real days are charged

The math behind every request charges working days, not calendar days.

  • Non-working weekdays and national holidays are skipped automatically in the day count.
  • Recurring series skip holidays on their own; weekends follow the pattern you chose.
  • Timezones are detected per request, so a distributed team's dates stay honest.

More resources

Feature

Balance tracking

Feature

Sick leave

Feature

Negative balances & unlimited leave

Ready to get started?

Give us a call. We'll show you how a single form covers one-off days, standing patterns, and a whole year of plans.

Balance Tracking

One PTO balance every role can trust.

Explore

Sick Leave

Sick days separate from PTO, with proof rules.

Explore

Frequently asked questions

How do employees request time off?
From the dashboard, one button opens the request form. They pick a leave type, choose full day, half day, or hours, select the days, and see the balance impact and approval route before submitting. Recurring patterns and bulk date ranges live in the same form.
Can employees request a half day?
Yes, where the leave type allows it. A half day counts as 0.5 day, four hours. On multi-day requests, a per-day breakdown can mark individual days as morning, afternoon, full, or skipped.
What is a recurring time-off request?
A pattern, like every other Friday, that expands into a series of individual one-day requests. Holidays are skipped automatically, single occurrences can be skipped by hand, and the whole series stays grouped so it can be withdrawn together.
Can multiple date ranges go in one request?
Yes. Bulk mode takes up to 20 date ranges in one submit, each with its own leave type, duration, coverage person, and reason. Overlapping rows are caught in the form before submission.
What does the approver see?
Each request individually, even from a recurring or bulk series, with the dates, balance impact, and policy signals attached. Nothing is approved as an opaque bundle; every day stays a visible decision.