Time Off Request Form in monday.com
Published on November 9, 2026
Leave requests tend to arrive as chat messages: “Can I take the 18th to the 22nd?” Someone has to copy the dates somewhere, check who else is out, and remember to answer. A month later, nobody can say what was approved.
A form gives every request the same shape and puts it on a board where managers can see overlaps. This post covers the fields to collect, how a manager records a decision, and how to keep an approved request from being edited afterward.
Quick answer
- Use an insert form mapped to a leave board: Employee (People), Leave Dates (Timeline), Leave Type (Status), Covering Colleague (People), and Notes (Long Text).
- Give the manager a per-item update form to set the decision, so the answer lands in the same item as the request.
- Turn on read-only form mode with rules so an approved request can no longer be changed through the form. The full setup is in Lock a monday.com Form After Approval.
- Install FormFlow and map the form to your leave board.
Start From What monday.com Provides
monday.com already publishes a time off request template built around a WorkForm, and a vacation tracker template with statuses and automations. Its community also has a Tip of the week on managing annual leave and time off requests .
If you already use one of those boards, you do not need to rebuild it. Keep the board and its columns, and attach the form to it. The rest of this post assumes a board with the columns listed below.
The Fields to Include
Map each field to a column on the leave board. The field types reference lists what each column type supports.
| Field | Column type | Why it is there |
|---|---|---|
| Employee | People | Ties the request to a person; see the note below |
| Leave dates | Timeline | One date-range picker instead of two separate date fields |
| Leave type | Status | Fixed labels such as Vacation, Sick, Unpaid, Other |
| Covering colleague | People | Names who handles the work while the employee is out |
| Notes | Long Text | Anything the manager needs to know |
| Decision | Status | Pending by default; managers change it, not the requester |
Keep the Decision field off the requester’s form. Set its default to Pending on the board, then let the manager change it through the second form described below.
A note on the People fields: whether a respondent can pick users depends on who is filling in the form and how the field is set up. Assign a Person Through a monday.com Form walks through the options. If it is a problem for your team, a dropdown of employee names mapped to a Dropdown column is a plain fallback.
Give the Manager an Update Form
Once a request exists, the manager’s job is to change one column and perhaps add a comment. A second form built for that step keeps them out of the board’s edit screens.
- Create an update form on the same board with Decision and Manager Comment editable.
- Mark the employee’s fields (dates, type, covering colleague) as read-only, so the manager sees the request but cannot rewrite it.
- Use a monday.com automation to store each item’s unique link in a column and send it to the right manager. The pattern is covered in 5 Ways to Automate Your Forms with monday.com Automations.
FormFlow does not send the email or message itself; the notification comes from a board automation, and each automation action counts against your monthly quota. Which person gets which link is a board rule you set up, not something the form decides.
Lock the Request After a Decision
After a manager approves leave, the employee should not be able to quietly move the dates. With read-only form mode, the whole form switches to view-only when a condition you define is true, such as Decision equals Approved.
If the employee needs to change approved leave later, they submit a new request. That leaves a record of the original approval on the board.
What a Form Does Not Do
A form collects and updates data. It does not calculate leave balances, count remaining days, or check a request against a company calendar. Those need board formulas, a dedicated leave-tracking app, or an automation. The monday.com community has threads from users asking for exactly that, such as automating a leave tracker , so decide up front where balances will live.
When WorkForms Is Enough
If every request is a one-off and the manager just reads the board, a native WorkForm on the time off template does the job. The gap shows up when the manager must record a decision through a form tied to the same item, or when you want the form locked after approval. A form that only creates items cannot do either.
Frequently Asked Questions
Can a time off request form capture a date range?
Yes. Map a form field to a Timeline column, which uses a date range picker. If you need two separate dates, you can use two Date fields instead.
Can managers approve leave from a form?
Yes. Build an update form on the same board where the Decision field is editable and the employee’s fields are read-only, then send each manager the link for the item.
Can the form check how many leave days an employee has left?
No. FormFlow’s documentation does not describe leave balances. Track balances with board formulas or a separate leave app.
Can I stop employees editing leave after it is approved?
Yes. Turn on read-only form mode with a rule tied to the Decision column. Once the value is Approved, the form shows the request but accepts no changes.
Next Steps
- Lock a monday.com form after approval →
- Assign a person through a monday.com form →
- Insert forms vs update forms →
- Update forms documentation →
- Install FormFlow and build your first time off request form.
Last reviewed: 2026-10-15. Template descriptions verified against monday.com’s time off request and vacation tracker pages via search summaries (the pages themselves could not be fetched). Features may change.