How to Request Time Off: Three Emails and a Coverage Checklist

To request time off, check your workplace's process, choose clear dates, and send the request to the person or system that can approve it. State when you will be away, when you will return, and how time-sensitive work could be covered. Keep the status clear until the required approval is recorded.

You can be considerate without writing a defense of why you deserve rest. A useful request helps the team make arrangements. It does not promise that you will finish two weeks of work in the evening before you leave.

Table of contents

• What should you check before requesting time off?
• What should your time off request email say?
• How do you make a realistic coverage plan?
• What if the request is unanswered or declined?
• What should you do after approval?
• Frequently asked questions

What should you check before requesting time off?

Check the applicable leave category, request channel, available balance if relevant, notice expectations, and dates. Look for team coverage constraints before proposing a plan.

This guide concerns ordinary planned vacation or personal time. For illness, caregiving, or other leave categories, use the relevant workplace process rather than adapting a vacation email and assuming it covers everything.

There is no single notice period or approval workflow that applies to every employer. GitLab's published time-off policy, for example, includes its own planning, coverage, and Workday requirements. It illustrates why the actual workplace policy matters; it is not a rule for your job.

Write down these details before sending:

• First and last day away.
• First working day back.
• Full days, partial days, or particular shifts.
• The leave category and balance, when applicable.
• Important deadlines or meetings in the period.
• The person or system that records the decision.

If you work irregular shifts, state the affected shifts instead of relying on a calendar date alone. If teammates are in different time zones, name the zone for partial-day requests. Precision now prevents an awkward correction after the schedule has been arranged.

What should your time off request email say?

Use a short request with dates, a realistic coverage proposal, and a clear next step. The following original fictional examples show three common situations.

A planned vacation:

Subject: Vacation request — November 9–13

Hi Jordan, I would like to request vacation from November 9 through November 13, returning November 16. I have checked the team calendar and can finish the customer summary before I leave. Alex is open to covering the routine check-in, subject to your agreement on priorities. Could you confirm whether these dates work? I will submit the request through our leave system as required. Thank you.

A partial day:

Hi Jordan, I would like to request personal time on October 22 from 1 p.m. to the end of my shift, returning for my usual start the next day. The morning handoff will be complete before I leave. Please let me know whether I should record the hours in the leave system before or after your review.

A request soon after starting:

Hi Jordan, I would like to discuss a prior commitment on November 6. I realize I am still in onboarding and want to understand the applicable time-off process. Could we review whether that day is possible and how to handle any scheduled training? I have not assumed the request is approved.

Use only statements that are true. Do not claim a colleague has agreed to cover you before speaking with them, or say you checked a balance you have not checked.

If the official system is the required request channel, the email may simply provide context. Avoid creating two conflicting versions of the dates. GitLab's policy is one concrete example of a workplace where time away must also be logged in a designated system.

How do you make a realistic coverage plan?

Sort affected work into four actions: finish, hand over, defer, or escalate. Ask who has the capacity and authority to accept each essential task.

The purpose is to identify coverage needs, not personally solve every staffing problem before you are allowed to ask. Managers may need to adjust priorities or arrange resources.

This is our planning framework. A real-world example appears in GitLab's customer success coverage guidance, which separates work needing attention from standing context and specifies an escalation route.

Do not quietly transfer ten hours of work to someone who has no free time. Ask the manager which tasks take priority. The weekly focus capacity calculator can help you make the tradeoff visible before promising a compressed pre-vacation schedule.

For a short absence, a few clear lines may be enough. For a longer one, link the active documents and record the next action for each item. Confirm that the cover person can actually open the files.

What if the request is unanswered or declined?

Ask for the status and the practical constraint. Do not treat silence as approval, and do not turn a scheduling disagreement into a long argument by email.

A useful reminder says:

Hi Jordan, could you let me know the status of my November 9–13 vacation request? I need to finalize arrangements by October 23. If there is a coverage concern, I am happy to discuss the affected work and possible dates.

Only include a booking deadline if it is real. Where possible, wait for the required approval before making commitments that would be difficult to change.

If the answer is no, clarify what would make an alternative workable:

• Is the problem the dates, the duration, or a particular shift?
• Is there a specific delivery or staffing requirement?
• Would different dates or a shorter period address it?
• When can the request be reviewed again?

Keep the conversation factual. “Which deadline would be affected?” is more actionable than “Why does nobody want me to take a break?” If there is confusion about the policy or leave category, ask the appropriate HR contact for the process that applies.

An existing one-on-one meeting may be a better setting for a complicated discussion. Afterwards, record the dates and decision through the normal channel so neither person has to rely on memory.

What should you do after approval?

Record the approved dates, update the relevant calendars, and confirm the handoff. Prepare an out-of-office message only after the coverage contact and routing are agreed.

Use this departure check:

1. The official request shows the correct dates and status.
2. Your calendar reflects when you will actually be unavailable.
3. Each essential task has an accepted owner or an agreed pause.
4. The receiver has working access to the current files.
5. Your automatic reply gives the return date and agreed contact route.
6. Your return day has space to review what changed.

GitLab's engineering coverage process explicitly considers responsibility and communication before time away. The useful principle is that a colleague should know what they are taking over, not discover it in an automatic reply.

Use the separate out-of-office message guide for the reply itself. Keep private travel plans and internal handoff details out of an email that may reach strangers.

Do Only 3 Things a Day provides a broader system for choosing realistic priorities. It is useful before and after an absence because the answer to a crowded calendar is often deciding what can wait, rather than adding more promises.

Frequently asked questions

How far ahead should I ask?

Follow your workplace's notice expectations and request planned dates as early as reasonably possible. Longer absences or busy periods may require more coordination. Do not assume a number from another employer's handbook applies to yours.

Must I give a personal reason?

Provide the information required for the relevant leave process. An ordinary vacation request often needs clear dates more than a detailed personal story. If another category applies, use that category's process and appropriate private channel.

Is a verbal yes enough?

Confirm what your workplace requires. A conversation may settle the plan, but the official system or written record may still need updating. Send a brief confirmation and check that the dates match.

Can I ask soon after starting a job?

You can raise the request and ask about the applicable process. Explain any prior commitment honestly and discuss onboarding or schedule conflicts. Avoid assuming either automatic approval or an automatic ban based only on how recently you joined.