Refinar

Leave management system
with your leave types and your rules

People request leave from their phone, managers approve with the rota in view, and everyone sees their balance. Start from a working app with requests and approvals, and describe the leave rules your company actually uses.

Start your leave app

What it starts from

This page starts the Time clock starting point, a complete app for clocking in, leave and the weekly rota. Requests and approvals work on day one. Leave policies differ in every company, so the pre-filled request describes yours.

Already in the starting point

  • Leave requests with a type (vacation, sick, personal, unpaid, other), dates and a note.
  • Approve or reject by a manager, and cancel by the person who asked.
  • A yearly allowance for the whole workplace, changed per person where needed, and the days left.
  • Approved leave on the rota and on the who is in screen, and days someone cannot work.
  • Roles: employees see their own leave, managers decide, a viewer reads and exports.

What the first request asks Refinar to add

  • Your own leave types with their own yearly days, such as casual, sick and earned.
  • Carry-over of unused days into next year, up to a limit.
  • Half-day leave, and a public holiday list that is never counted.
  • Two-step approval: the team manager, then HR.
  • A month calendar of who is off, and each person's balance on their home page.

What leave looks like in the app

Request in a minute

Pick the type and the dates, add a note, send. The request shows its status until it is decided, and can be cancelled before it starts.

Approve with the team in view

Managers see pending requests next to the rota and other approved leave, so two people from the same shift are not off at once.

Balances people can trust

Each person's allowance, what they have taken and what is left, from approved requests only. Changing someone's allowance is one field.

Who is off, at a glance

Approved leave appears on the rota and on the screen of who is in today, so nobody chases an absent colleague.

A history for every person

Every request with its dates, type, decision and who decided, exported to CSV whenever HR or payroll asks.

Attendance in the same app

Clock in and monthly hours come with it, and a day on approved leave is never counted as missed.

The tables behind it

Real Postgres tables you own. The solid ones come with the starting point; the dashed ones are what the pre-filled request adds.

leave_requests

In the starting point
  • id
  • employee_id → employees
  • type
  • start_date, end_date, days
  • note
  • status: pending | approved | rejected | cancelled
  • decided_by, decided_at
  • half_day (added)

employees

In the starting point
  • id
  • name, email, position
  • annual_leave_days (overrides the workplace)
  • active

workplace_settings

In the starting point
  • annual_leave_days
  • work_days
  • time_zone

leave_types

Added by your first request
  • id
  • name
  • days_per_year
  • counts_against_balance
  • carry_over_max

holidays

Added by your first request
  • date
  • name

leave_approvals

Added by your first request
  • request_id → leave_requests
  • step: manager | hr
  • approver_id → user
  • decision, decided_at

How it works in 3 steps

  1. 01

    Start from this page

    Press Start your leave app. The Time clock starting point is picked and your leave rules are written into the first request, ready to edit.

  2. 02

    Your app runs in about a minute

    Refinar creates the app with sign-in, requests, approvals and a real database, then adds your leave types and rules in a live preview.

  3. 03

    Change it by describing it, then launch

    Ask for more in plain sentences: maternity leave, comp-off for weekend work, a yearly reset date. When it is ready, press Go live and the code and the database are yours.

What it does not do yet

The starting point does not accrue leave month by month, carry days over or know your public holidays: the pre-filled request asks for carry-over and a holiday list, and accrual is one more sentence if you need it.

It sends no email or push notifications; people see their requests in the app. It does not check your leave rules against labour law. You set the types and the days, and you stay responsible for them.

Questions

What is a leave management system?

Software where employees request time off, managers approve or reject it, and everyone sees how many days are left. It replaces leave forms, email threads and the spreadsheet HR keeps on the side.

How are leave balances calculated?

Each person has a yearly allowance, the workplace's default or their own. Approved requests of the types that count are taken off it. With the pre-filled request, each leave type gets its own yearly days and a carry-over limit.

Can it follow casual, sick and earned leave rules?

Yes, as types you define with their own days and carry-over. The app applies the numbers you give it; it does not decide what the law in your country requires.

Can employees see each other's leave?

Employees see their own requests, managers see everyone's. The pre-filled request adds a calendar of who is off; you decide in the request whether employees see it too.

Does it send email when a request is approved?

Not in the starting point. Email can be added by describing it, with an email provider you connect.

How much does it cost?

Building the app and changing it use credits from your Refinar plan, and hosting is part of going live. There is no fee per employee. The details are on the pricing page.

More starting points

Read next