Back to Blog Home

Time off request for a small firm: name the cover for every recurring job

A wall calendar with a week marked for vacation next to a handover list naming a person for each task

A time off request at a small firm should name a cover for every recurring job the person owns, and you should approve it only when each of those covers is in that week. A dates-and-signature form does not do this: Indeed's time off request form lists company, employee, department, dates, leave type and manager and employee signatures, and it has no field for who does the work while the person is away.

A typical failure: someone asks in a DM, you say yes in the hallway, and nobody writes down who runs the Friday invoice run, the client check-ins or the weekly report. Two people end up out the same week, and the job nobody covers is found when a client asks about it. The fix costs a few minutes per request: five fields on every ask, one approval rule, a notice table you set once, and a Friday check in Slack that looks at the next 30 days for gaps.

What should a time off request include?

A time off request needs five fields: the dates, the type, the recurring jobs the person owns in those dates, a named cover for each job, and how to reach them. The second and third fields are the ones most forms skip.

Copy this as the line a teammate sends:

#FieldExample
1Dates4 to 8 August
2TypeTime off
3Recurring jobs I own in these datesFriday invoice run; Tuesday client check-ins
4Cover for each job, already agreedInvoice run: Priya. Check-ins: Dana
5Reachable?No, back on the 11th. Urgent items go to Dana

The template in Tiny Team's PTO policy guide comes closest: its form has a coverage plan line that asks who will handle the employee's responsibilities, and its email version lists each task or project with the colleague who has agreed to cover it. That is a good start, but a single free-text box still lets a person write "Priya will help" without naming which jobs. Field 3 forces the list, and field 4 forces one name per job.

Where does the list of jobs come from? From a cover list the firm keeps once: each recurring job, who owns it, and who normally covers it. If you have not written down which jobs only one person can run, start with the bus factor list for a small firm; that article produces exactly this list.

Try Kipwise Agent free in Slack: mention it once in a thread and it does the repetitive work, with your permissions.

Why does a yes in the hallway cause gaps?

An informal yes leaves no record, so nothing can be checked against it later. Vendors and consultants who sell time off tooling describe this, and their accounts are author reports, not studies of firms like yours.

Rocketlane's guide to time off requests, from a software vendor, describes a manager who approves a week off verbally, forgets to log it, and schedules the same consultant for a client kickoff two days later; nobody catches it until the consultant is on a flight. SimplyPTO, which sells PTO software, says that at around twenty requests a month across email, chat and hallway conversations some never make it into the sheet. The McCary Group, a consultancy, says most PTO problems come from silence rather than denial: the person does not know whether the ask was seen.

All three point at the same weakness. The request lives in a place nobody reads back, and the approval is given without looking at what the person actually runs. A calendar entry for the absence does not fix it either, because a calendar shows who is out, not which jobs just lost their owner.

How should you decide yes or no?

Approve when every recurring job on the person's list has a named cover who is not also out that week; otherwise ask the person to fix the cover and send it again. That is the whole rule, and it fits on a sticky note.

A yes to a time off request is a statement about every recurring job the person owns, so approve only when each job has a named cover who is not also out that week. This is a recommendation, not something the sources above prescribe, and it follows from what they describe: Vacation Tracker, a vendor, says that without an overlap view half the team unknowingly books the same week. The rule makes the overlap check part of the decision itself, so it does not depend on the approver remembering who else asked.

Three practical points keep the rule honest:

  1. The cover must have said yes before the request is sent. The requester asks Priya, not the owner.
  2. A cover who is also out that week does not count, even if the person only asked for one day.
  3. A job with no possible cover is a real finding. It means you either move the job, pause it, or pay for outside help for that week, and the request has done its work by surfacing it.

When the answer is no, say it live. Tiny Team's advice is to deliver a denial in person or on a call, not by email, and it is also the cheapest way to turn a no into a different set of dates.

What notice should you ask for?

Ask for notice by length of absence: the longer the absence, the earlier the ask. Write the numbers down once, with one exception for emergencies, so a teammate can plan without negotiating each time.

The numbers below are examples from the guide above, not rules. Tiny Team's unlimited PTO guardrails suggest two weeks of notice for one to two days, four weeks for a full week and eight weeks for two weeks or more, and its general template uses 5 business days with 10 for three or more consecutive days. Pick your own.

Length of absenceExample noticeCover check
1 to 2 days2 weeksNamed cover for each recurring job that falls in those days
A full week4 weeksSame, plus a handoff note for each job
2 weeks or more8 weeksSame, plus a call on any job that cannot be covered for that long
Emergency or illnessAs soon as possibleCover is decided after the fact by the owner

Set notice by length of absence, with a written exception for emergencies, so the rule is a number a person can plan around instead of a judgment made request by request. Without the written number, the same person gets a yes at two weeks' notice and a no at three weeks' notice from a busy approver, and learns not to ask.

Two limits sit outside this process. The US Department of Labor says the Fair Labor Standards Act does not require pay for vacation or other time not worked and that these are matters of agreement between employer and employee, so your written policy is what counts. And state rules differ: Tiny Team notes that some states treat earned PTO as wages that must be paid out when someone leaves. Balances, accruals, pay and legal leave stay with payroll and the owner, not with this process.

How does the request run in Slack?

The request runs in a direct message with the Kipwise agent: the teammate says what they want, the agent files it as a numbered request, and a person approves. The agent does not decide.

Here is a made-up example for a firm of 18. The Cover sheet lists three jobs: the Friday invoice run (owner Dana, cover Priya), the Tuesday client check-ins (owner Marcus, cover Dana) and the weekly report (owner Priya, cover Marcus).

  1. Marcus messages the agent: "I want 4 to 8 August off." The agent asks "Send this request?" and shows the type, the dates and a line for each recurring job he owns with its cover. Marcus presses send.
  2. The request type needs an approval first. The owner gets a private card from the agent with Approve and Reject. The first press decides, and Marcus sees the result under his request card. In the channel the team sees only "Request #31 was sent", never the dates or the reason.
  3. The owner checks the rule: the check-ins have a cover, Dana, who is in that week. Approve.
  4. After the approval, someone asks the agent to add one row to the shared Out sheet. An Approve card appears first, and the row is written only after it is pressed. If Marcus has connected his Google Calendar, he can also ask the agent to put the dates on his own calendar; that is a separate connection from Google Drive and Sheets, and the event has no other attendees unless he asks.

The agent reads a Google Sheet through your connected Google account and can read a range and add rows. Writing needs the separate Google Drive edit connection, and each write waits for an Approve card. For calendars, the agent lists and changes only a person's own primary calendar, so the Out sheet is your shared record of who is away, which is why step 4 matters.

Why a request instead of a DM thread? The request keeps a card with its number and state in the person's own chat, so nobody has to scroll to find out what happened. This is the opposite of what Rocketlane assumes: it says the formal path should be an HR system and not Slack or email, and that is fair for a firm that owns one. A firm of 18 without HR staff can get most of the benefit from a numbered request and a sheet. Slack's own request time off tutorial is a good measure of the alternative: it collects start and end dates and sends them to a manager, but it needs the Slack CLI, code and a paid plan.

For how an approval request works in general, see approval requests for a small team; for the same pattern on an IT ask, see the IT request desk for a small firm.

What does the Friday check catch?

The Friday check catches the weeks in the next 30 days where a recurring job has no named cover or the named cover is also out. It reads a range from the Out sheet and from the Cover sheet and posts only the gaps in the ops channel.

Check cover again every Friday for the next 30 days, because a cover who was free when you said yes can be approved out a week later. This is the case the approval rule alone cannot see. Marcus's request was fine on the day it was approved. If Dana later asks for the same week, the owner who approves Dana's request is looking at Dana's jobs, not at the fact that she is also Marcus's cover. A weekly look at the sheet finds it while there is still time to change something.

Set it up once in the ops channel by telling the agent, in plain words, what to do every Friday: read the Out sheet and the Cover sheet, and list any week in the next 30 days where a recurring job has no named cover or its cover is out. The agent creates a scheduled task and posts each result in that channel. You approve the task once; later runs do not ask again. A scheduled task runs with the same permissions as a live request from the person who created it.

A good Friday post is short:

> Weeks with a gap, next 30 days. Week of 4 August: Tuesday client check-ins, cover Dana is out 5 to 6 August. Week of 18 August: weekly report, no cover named.

The post prompts a look and a person decides what to do with each line. It is wrong when the sheet is wrong.

What goes wrong, and who handles it?

The sheet is only as good as the rows in it, so most failures are a missing row or a stale cover. Plan for these:

  • A request approved but never written to the Out sheet. The Friday check cannot see the absence. Make the row part of the approval: whoever approves asks the agent to add it the same day.
  • A cover who changes after the request. Ask people to update the Cover sheet when a job moves. Review the Cover sheet once a quarter with each owner.
  • A job nobody can cover. The post names it every week until a person decides. That is intended.
  • Last-minute and sick days. These skip the notice rule. The owner decides cover that day and adds the row afterwards.
  • A denied request. The requester is told under their request card, and the person who said no talks to them directly.
  • Confidential reasons. A confidential request type never appears in a channel; its alerts are private messages. Keep the reason out of the Out sheet, which the team can read.
  • Pay, balances and legal leave. These stay with payroll and the owner, outside the request.

How do you know it works?

Run it for one month and look at four things. If any of them fails, fix the sheet before blaming the people.

  1. Every approved absence has a row in the Out sheet. Compare the approved requests with the sheet at month end.
  2. The first Friday post matches a hand check. Read the Out and Cover sheets yourself for the next 30 days and compare your list of gaps with the post. If they differ, find out why before trusting the post.
  3. No client asked about a job nobody covered. This is the failure you started with, so it is the number that matters most.
  4. The number of requests sent with no named cover. If it stays high, the cover list is out of date or the jobs on it are wrong.

What to do next

Today, write the cover list: every recurring job the firm runs, its owner and its usual cover, in a Google Sheet, with an Out sheet for approved absences next to it. That takes under an hour for a firm of this size and is useful even before you automate a single step.

When the list exists, add the Kipwise agent to Slack and ask for a Time off request type that needs the owner's approval. The agent comes with the internal request desk, costs $10 per user a month with at least three users, and starts with a free trial when you add it to Slack; see the Slack ticketing system page for how the request desk is set up with your team.

Topics

Related posts

Put an AI teammate in your Slack

Free trial on install: $2 of AI credit for 7 days on the fast model, or $10 for 14 days with all models on a paid Slack plan or for existing Kipwise customers.