These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Remote Teams HRMS
- Features
- Leave and time
Leave and time
Collect leave requests and weekly time against the right employee and dates.
OverviewMy Leave Requests×
Remote Teams HRMS · Leave and time
New
My Leave Requests
Leave requests
| Request number | Leave type | Start date | End date | Status | |
|---|---|---|---|---|---|
| LR-89251 | LT-3681 | 08 Oct | 16 Oct | Draft | |
| LR-96446 | LT-7351 | 06 Oct | 15 Oct | Submitted | |
| LR-83440 | LT-4843 | 06 Oct | 12 Oct | Approved | |
| LR-86841 | LT-9828 | 25 Oct | 03 Nov | Taken | |
| LR-17772 | LT-7149 | 04 Oct | 11 Oct | Draft |
6 of 6 records
LT-3681Leave requests · LR-89251
DraftStart date08 Oct
End date16 Oct
What you can do
Keep requested time visible
Employees enter leave requests with a start and end date, leave type and reason. The request has a status and an approver reference. Leave balances keep accrued, taken, pending and carryover values by employee and leave type. A weekly timesheet groups time entries, which hold the date, hours and category of work. These records give the team a clear way to review requested absence and reported hours.
How the work is organized
- Leave request. Employee enters the leave type and date range; Admin checks the balance.
- Weekly hours. Employee records dated time entries under a weekly timesheet.
- Pay handoff. Payroll Admin reads approved requests and timesheets for the period.
The employee should know which leave type to choose and which approver will review the request. Payroll Admin can read leave requests and timesheets when preparing pay work; they should use the approved record as the handoff. Agree how balances are checked, how corrections are entered and when submitted time becomes approved. For a remote team, agree the local date convention so the employee and approver read the same interval.
What to agree during setup
Choose who reviews submitted leave and time; Admin can record the approval while Payroll Admin has read access for pay preparation. Agree which leave type applies to a remote employee and how the reviewer checks the available balance. Check the timesheet total against its dated entries. Rehearse a request that crosses a pay cutoff so submitted work is kept separate from approved input.
Check the handoff on an actual case
Take a colleague who requests leave across a payroll cutoff. Enter the start and end dates, select the leave type and submit the request. Review the available balance and approver reference. Once the decision is recorded, have Admin inspect the leave schedule while the employee checks their own request. Then enter a weekly timesheet with a regular time entry and review its total hours. The payroll reviewer should be able to distinguish submitted time from approved time before using it.
What your team sees
- My Leave Requests — An employee’s own dated requests and current status.
- Leave Approval Inbox — Submitted requests ready for the assigned decision.
Follow the work through
Start with the hiring path for a new colleague. Then use the operating cycle or the review cycle as the employee’s work continues. See the data model when mapping an existing register.
What it keeps track of
Data model- Leave requests
- Employee-submitted leave requests requiring manager approval.
- Leave balances
- Current leave balance per employee per leave type, maintained by accrual.
- Leave types
- Leave categories with country- and class-scoped accrual rules.
- Timesheets
- Weekly timesheet header per employee.
- Time entries
- Hours against a day, project or cost center.
- Employees
- Central person record for every worker; all suite transactions tie back to Employees.
Who uses it
Permissions- Employee
- Enters their own request and time.
- Payroll Admin
- Reviews the time context for pay.
- Admin
- Controls access.
Set up Remote Teams HRMS your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.