---
title: 'Home office requests'
summary: 'The employee-initiated workflow for remote-work days. Holiday brings time off. Home office brings time out of the office at the same expected hours.'
section: features
tags:
  - tempus
  - home-office
  - requests
  - approvals
updated: '2026-07-21'
---

> A **home office request** is the employee-initiated workflow for remote-work days. Each company sets weekly and yearly home-office caps at the [company](tempus_companies.md) level, and approved days draw against those balances.

[Holiday requests](holiday_requests.md) bring time off. Home office requests bring time out of the office at the same expected hours. A home-office day still counts as a working day, so time-tracking and overtime proceed normally - only the location changes.

## Overview

This page is restricted to Admin and HR for the cross-cutting view, manual approvals, and overrides. Department managers approve their team's requests through the Voxbi app inbox. From here you browse, filter, approve, reject, or cancel pending requests, and see approved days on the [time point overview](tempus_time_point_overviews.md).

## What it does

The status flow matches holiday requests: Pending moves to Approved or Rejected with immediate effect. Each request has one of two sub-types:

- **Request** - a new home-office day or range. Approving adds the days and decrements the balance.
- **Removal** - a request to cancel an already-approved day. Approving drops the days and restores the balance.

> [!CAUTION]
> The Removal flow is easy to misread. The original request stays Approved and the days stay on the calendar while the Removal is Pending. Rejecting the Removal leaves the original untouched. Approving it removes the days and restores the balance. Check the sub-type before acting.

> [!IMPORTANT]
> The yearly cap is often regulatory - cross-border workers in Luxembourg are subject to an EU-mandated yearly limit. Configure caps carefully at the company level, since an incorrect value can create compliance exposure.

## See also

- [Holiday requests](holiday_requests.md) - the sibling workflow for actual leave.
- [Companies](tempus_companies.md) - where the weekly/yearly HO caps are configured.
- [Contracts](tempus_contracts.md) - where the ho_balance field lives.
- [Time point overviews](tempus_time_point_overviews.md) - where approved HO days appear in reports.
- [Validator rules](validator_rules.md) - custom approval routing.

```yaml fields
employee:
  label: Employee
  tab: General
  hint: 'The employee the home office days are recorded for. Only employees on this tenant appear in the list.'
status:
  label: Status
  tab: General
  hint: 'Whether the days are recorded straight away or sent for validation.'
  values:
    -
      value: approved
      label: Approved
      text: 'Records the days immediately with no validation step and no email.'
    -
      value: pending
      label: Pending
      text: 'Opens the validation workflow and emails the configured validators.'
home_office_dates:
  label: 'Home office days'
  tab: General
  hint: 'The individual days worked from home. Click days to select or unselect them. Weekends are not selectable, and days beyond one year ahead cannot be booked. Existing absences, home office, and public holidays are shown as colored tints so clashes are visible before booking.'
start_date:
  label: 'Start date/time'
  tab: General
  hint: 'When the home office period begins. Shown when editing an existing record.'
end_date:
  label: 'End date/time'
  tab: General
  hint: 'When the home office period ends. Shown when editing an existing record.'
note:
  label: Reason
  tab: General
  hint: 'Optional context for the validators, such as the reason or coverage arrangements.'
```