Short answer
Handle time-off requests by giving each employee one request form with dates, sending it through a fixed approval route and showing only approved absences in the shared calendar. The approver sees pending requests in one list, rejects with a reason, and a cancelled request leaves the calendar by itself.
- Who submits: every team member
- What the calendar shows: approved absences only
- Rejection: always with a reason
On this page
When do you need a request and approval process for time off?#
A request process pays off as soon as a plan depends on who is in the office. It belongs to the same discipline as measuring which clients and projects make money: hours and deadlines only mean something when the capacity behind them is known.
- A vacation is agreed in a chat message, and nobody remembers the dates a month later.
- The spreadsheet of absences is updated by one person and is a week behind.
- A project manager hands a task to an engineer who is on sick leave until Thursday.
- A purchase request, such as a laptop for a new hire, floats between the manager and finance with no clear owner.
- A cancelled vacation stays in the schedule, and the team plans around a person who is already back.
- Staff request
- A staff request is a dated or itemised ask from an employee, such as vacation, sick leave, a purchase or any other request, that goes to an approver and ends in a decision.
- Absence
- An absence is an approved vacation or sick-leave request that covers a period of days, and it is the only kind of request that appears in the team calendar.
How do you handle time-off requests and absences in six steps?#
Handling time-off requests means one form for the ask, one route for the decision and one calendar for the result. The steps below set up that chain in order.
Decide who approves which request
Write down the route before the first request arrives. A route is a list of steps, and each step belongs to a role or to a named person. Steps can follow each other or run in parallel, and a step can carry a threshold by amount.
A threshold matters only for purchases. A vacation has no amount, so it skips a step that starts from a sum, and the same route can send a laptop purchase to finance while a vacation stops at the manager.
Tip. Without a route, one step goes to an administrator. A request never stays with nobody, but one person then approves everything, so set a route as soon as you have more than one approver.
Let each employee submit the request
Every team member, including a viewer, can create a request. The form asks what the person requests and the first and last day. An empty last day means one day, and the last day cannot be earlier than the first.
A vacation and a sick leave need a first day. A purchase and any other request need a title, because the approver sees only that line, and a purchase can carry an amount that drives the threshold of the route.
Approve from one list
The approver opens the list of requests waiting for their decision. A notification “Request to approve a request” arrives with the subject, for example “Vacation 01.12–14.12”, and a click on the notification opens that list.
Each step is decided by its own role or person. When a step has several stages, the next stage opens after the previous one is approved, and the request becomes approved after the last stage.
Reject with a reason
A rejection needs a reason, and the form refuses an empty one: without it the author cannot tell what to change. A rejection at any step rejects the whole request and closes the remaining steps.
Nobody approves their own request. A person who submitted it can read the decision and the reason in their own list, and a notification tells them the result.
Read the absences in the calendar
Once a vacation or a sick leave is approved, the Calendar shows a quiet line such as “Olena — vacation” on every day of the period, in the month and the week view. Every member of the company sees this line, because it is the team schedule.
Pending, rejected and cancelled requests never appear there. A purchase or another request has no place in the calendar at all.
Cancel when the plans change
The author cancels their own request while it waits for a decision, and an approved absence until it starts. After the first day the absence is a fact, and only an administrator can change it. An administrator can cancel any open or approved request.
A cancelled request closes its open steps and disappears from the calendar by itself, because the calendar is read from the approved requests and there is no separate list to correct.

What does a request route look like on real cases?#
The table shows one route for a small integration team and what each request does. The route has a manager step for every request and a step for a named person, the head of finance, that starts from an amount.
| Request | Steps that apply | What the team sees |
|---|---|---|
| Vacation, 1–14 December | Manager | After approval: the name and “vacation” on each day of the period |
| Sick leave, 3 days | Manager | After approval: the name and “sick leave” on three days |
| Laptop purchase, 42,000 | Manager, then a named person (the head of finance), threshold from 20,000 | Nothing in the calendar; the requester gets the decision as a notification |
| Laptop purchase, 15,000 | Manager | Nothing in the calendar; the requester gets the decision as a notification |
Steps that apply = the route steps whose threshold is not above the amount of the request, and a request without an amount skips every step with a threshold. In the example the threshold of 20,000 adds the head of finance to the 42,000 purchase only.
Which mistakes break the absence calendar?#
- Keeping a parallel spreadsheet. The two lists drift apart on the first cancellation, so read absences from the approved requests only.
- Leaving the route empty. Every request then waits for one administrator, and a vacation approved late gets planned around too late, so name a manager step.
- Approving by chat message. The calendar shows nothing until the request is approved in the list, so ask people to submit the request first.
- Rejecting without saying why. The form requires a reason, and a specific one saves a second round of messages.
- Treating the calendar as a warning for task assignment. Krokul uses the absence when it distributes new deals from a funnel pool, and for tasks the check stays with the person who assigns them, so look at the calendar before handing out work.
What belongs in a weekly check of team absences?#
Run the check on Monday, together with the weekly look at tasks described in how to run follow-ups with tasks and a calendar.
- The list of requests waiting for a decision is empty or has a named approver for each item.
- Every approved absence of the next two weeks is visible in the calendar.
- Tasks and deadlines of people who are away have a new owner.
- Cancelled vacations are removed, so nobody plans around a person who is back.
- The route still names the right people after any change in the team.
How does it work in Krokul?#
Krokul CRM is a B2B CRM for contract-based companies: deals, projects and profit per client in one system, implemented by integration partners. Its Requests screen sits in the My section next to the Calendar, and the work described above runs on it.
The Requests screen has three tabs: Mine, For approval and All, and the last one is open to administrators only. A request can be a vacation, sick leave, purchase or other request. The route for requests is set in the same editor as the discount route, described in how to set up a discount approval workflow: it lives in the Pricing screen under Approval routes, under the subject “Staff requests”. Administrators save routes and managers can read them.
Approved vacations and sick leaves show up in the Calendar as a line in the day cell, where several names are separated by commas. The same absences keep a person out of automatic distribution of new deals from a funnel pool on the days they are away, and nothing is written to the person’s profile for that. For the people side of capacity, the hours the same team logs against projects are covered in how to get engineers to log time accurately, and a project that starts from a won deal in the sales-to-delivery handoff brief. Project hours and paid hours sit on the Krokul page about projects and logged hours.
Frequently asked questions#
Who can submit a time-off request?
Every team member can, including a viewer. Opening the form needs no right to edit deals, because a vacation does not depend on it.
Who sees a request?
The author, the administrator and the approvers of its steps. Administrators see all company requests, and other people see their own and the ones waiting for their decision.
Can an approved vacation be cancelled?
Yes. The author can cancel it until the day before it starts, and an administrator can cancel it at any time. The absence then disappears from the calendar.
What happens when the only administrator submits a request?
It is approved at once and marked as approved automatically, because nobody else could decide it. When another administrator exists, the request goes to a decision as usual.
Does an absence block assigning a task?
No. Krokul reads absences for the calendar and for automatic distribution of new deals from a funnel pool, so the person who assigns a task checks the calendar.