Most people expect time-off requests to begin with the person taking the leave.
In RemoFirst, that isn’t always how the process works.
The platform allows a company to create a time-off request on behalf of a team member. This can be useful when a planned absence has already been discussed or needs to be recorded centrally.
However, a request created by a manager doesn’t always mean the absence has been fully confirmed.
The outcome depends on how the company handles the request.
How Managers Create Time-Off Requests
RemoFirst provides a dedicated Time off section for company administrators.
From the Requests tab, an authorized manager can select Add time-off.
The form requires the manager to choose the relevant team member, specify the dates, and select the appropriate reason.
Available reasons include vacation, sick leave, parental leave, caregiver leave, educational leave, bereavement, and other categories.
The manager can also add a description or supporting documents when appropriate.
Why Would a Manager Submit the Request?
There are situations where a company needs to record an absence that has already been agreed upon.
For example, a manager may be coordinating planned leave across a distributed team or documenting a schedule change.
Creating the request centrally can help maintain consistent records.
However, the request should still accurately reflect the dates and type of absence.
A manager-created entry shouldn’t be assumed to represent an agreement if the person concerned hasn’t reviewed the details.
Two Different Confirmation Options
This is where RemoFirst’s process becomes more interesting.
Earlier platform instructions describe manager-created requests as remaining pending until the worker approves them.
RemoFirst’s May 2025 product update introduced an additional option.
Companies can choose to approve the request automatically or require the worker’s acknowledgment.
That means two apparently similar requests can follow different workflows.
The important question is whether confirmation is required for the particular request.
When Your Confirmation Is Required
If the company chooses the acknowledgment workflow, RemoFirst notifies the worker about the request.
The worker must review it and respond through the platform.
Until that happens, the request remains pending.
Receiving a notification doesn’t mean the absence has already been finalized.
Review the dates and reason before confirming.
If something is incorrect, raise the issue rather than approving information that doesn’t match the agreed arrangement.
When the Request Is Automatically Approved
The automatic-approval option allows the company to create an approved absence without waiting for a separate acknowledgment.
This is useful for organizations that have already agreed on the dates outside the platform.
However, automatic approval doesn’t guarantee that every detail is correct.
Workers should still review their recorded absences and report discrepancies.
Half-Day Requests Work Here Too
Manager-created requests support the same half-day options available in the regular time-off form.
A manager can specify that leave starts during the second half of a day or ends during the first half.
RemoFirst calculates those selections as half-day periods.
This is useful when a person needs only part of a workday away.
Incorrect half-day settings can affect the recorded duration, so they’re worth checking carefully.
What About National Holidays?
RemoFirst calculates time-off duration without counting weekends or national holidays in the worker’s country of residence.
This is particularly relevant for international teams.
A manager based in one country shouldn’t assume that another country’s holiday calendar follows the same schedule.
The platform uses the worker’s country information when calculating the requested period.
Can the Manager Edit the Request?
RemoFirst’s documentation explains that managers can edit pending requests they’ve created.
They can open the request, update the relevant details, and save the changes.
Once a request is approved, ordinary editing is no longer available.
The manager may still be able to cancel it before the leave period begins.
This makes the request status important when correcting an error.
What If the Wrong Dates Were Entered?
First, check whether the request is pending or approved.
If it’s pending, the manager may be able to correct it directly.
If it’s already approved, the appropriate solution may involve cancellation and a replacement request.
Don’t create a duplicate absence without checking the original entry.
Two overlapping records can make the time-off history harder to understand.
Direct Managers and Notifications
RemoFirst also supports assigning a Direct Manager to a team member.
According to the platform’s documentation, when a Direct Manager is assigned, that person receives notifications about time-off requests.
However, all managers, including the company account owner, can still review and approve those requests.
This differs from RemoFirst’s timesheet approval permissions, which are more restricted.
The distinction matters when determining who can resolve a pending request.
A Useful Habit for Distributed Teams
When a company creates an absence on someone’s behalf, the worker should verify three things: the dates, the leave category, and the request status.
If acknowledgment is required, complete that step rather than assuming the manager’s submission was sufficient.
If the request was automatically approved, review the recorded information and flag any discrepancies.
Manager-Created Doesn’t Always Mean Final
RemoFirst gives companies flexibility in managing planned absences.
A manager can initiate the request, but the company can choose whether it requires the worker’s confirmation.
The practical rule is simple: when a time-off request appears in RemoFirst that you didn’t create, check its details and status. A pending request may still need your acknowledgment, while an automatically approved request should still be reviewed for accuracy.