Give employees clarity. Give managers control.

Access & responsibility

The right people. The right access.

Timento separates what someone does in the operation from what they can do in the platform. A shift leader in the kitchen is a job role. A planner who builds and publishes schedules is a permission role.

• Employee

  Works in the Employee Portal: schedule, hours, availability, leave requests and the operational information for their own shifts.

  • My Schedule
  • Clock In · Breaks · Clock Out
  • Availability & Leave
  • Worked Hours

• Planner

  Builds and publishes the schedule using availability, leave and roles, and follows up on what changes afterwards.

  • Smart Scheduling
  • Availability & Leave
  • Publish & Notify
  • Shift swaps

• Company Admin

  Manages the company setup: employees, roles, permissions, locations and the settings behind daily operations.

  • Employees
  • Permissions
  • Locations
  • Control Center

1. 01

   Request

   The employee submits a leave request in the Employee Portal, with the dates and any context.

2. 02

   Review

   A manager sees the request together with the rest of the team picture instead of judging it in isolation.

3. 03

   Approve

   The manager approves or declines, and the employee gets a clear answer.

4. 04

   Visible in planning

   Approved leave shows up while the schedule is being built, so nobody is planned into time off.

• The employee gets clarity

  A submitted request has a status and an answer, not an unread message.

• The manager keeps control

  Nothing is approved by accident, and decisions are made with the team in view.

• The planner sees the result

  Approved leave is planning information the moment the schedule is built.

Timento supports the request, review, approval and planning visibility of leave. It does not calculate statutory entitlements or process payroll.

Employee self-service

Everything employees need. Without the admin maze.

Give employees one simple mobile-friendly place for the information and actions they use during the working week.

No desktop login, no separate HR portal, no chasing a manager for an answer that already exists in the platform.

• My Schedule

  Upcoming shifts, times and location , always the published version.

• Calendar Export

  Your schedule, where you need it: export shifts as an iCalendar (.ics) file or subscription link and add them to a compatible calendar application. Timento stays the source of truth.

• Clock In · Breaks · Clock Out

  Start the shift, register breaks and clock out from the same place.

• Availability & Leave

  Share availability and submit leave requests without sending a message.

• Worked Hours

  See registered hours instead of counting them back from memory.

• Shift swaps

  Request a swap with a colleague and follow what happens with it.

• Operational Checklists

  The routines that belong to the shift, on the device already in hand.

• Knowledge Hub

  Procedures and guides where the work happens, not in a binder.

• Notifications

  Updates about schedules, requests and approvals that actually matter.

• Colleagues

  See who is on the team and who is working alongside them.

• Birthdays

  Small thing, real culture , the team knows when to say something.

Flexibility with control

Plans change. The schedule shouldn't become chaos.

People get sick, exams move, life happens. Timento gives employees a structured way to solve it without letting the published schedule drift away from the manager.

1. 01

   Employee requests swap

   The employee asks to hand over a shift instead of arranging it privately.

2. 02

   Colleague responds

   A colleague accepts or declines, so the replacement is a real agreement.

3. 03

   Manager oversight

   The change stays visible to the manager rather than happening behind the schedule.

4. 04

   Schedule stays controlled

   The result is one schedule everybody works from , including the people who never saw the conversation.

Employees get flexibility, managers retain visibility. Timento is built so shift changes remain part of the schedule, not a side conversation.

Keep everyone updated

The right update. The right person.

Notifications are updates triggered by workforce events. Messages are communication between people and teams. Timento keeps the two apart, so an update never disappears inside a conversation.

• Schedule published
• Schedule changed
• Open shift available
• Leave request submitted
• Leave request approved or declined
• Shift swap request and response
• Time approval
• Checklist and review follow-up

Every notification is tied to something that happened in the operation, so the update has a subject, an owner and a next step.

Role-based access

Everyone sees what they need.

Employees, planners and managers work in the same platform without needing access to the same information or controls.

• Role-based access

  What someone can see and do follows their permission role, not an informal agreement.

• Company separation

  Companies are kept apart, so information stays where it belongs.

• Location access

  Where multiple locations are used, access can follow the locations someone is responsible for.

• Manager permissions

  Managers get the planning, approval and follow-up controls their responsibility requires.

• Employee self-service

  Employees manage their own schedule, hours, availability and requests , and nothing else.

• Admin controls

  Company Admins manage employees, roles, permissions and the setup behind daily operations.

Access is described here as role-based access control inside Timento. Specific security certifications are covered separately on the security page.

1. 01Check schedule
2. 02Clock In · Breaks · Clock Out
3. 03Complete work
4. 04Check Knowledge Hub
5. 05Request leave
6. 06View worked hours
7. 07Stay updated

Breaks are part of the cycle on purpose. Registering them properly is what makes worked hours worth reviewing later.

Roles decide who is responsible, and the operational work follows the same roles , so nothing depends on remembering who normally does it.

Select an industry to see how Timento adapts to different operations.

The employee experience stays the same across all of them. What changes is the structure behind it.

From small team to multi-location

Add people without adding chaos.

Add employees, locations, managers, roles and permissions while keeping the same platform and familiar employee experience.

1. 01

   Small business

   One team, one location, one manager who does most of it personally.

2. 02

   Growing teams

   More people, more shifts, and the first need for structure around availability and approvals.

3. 03

   Multi-location

   Several locations, local managers and access that follows responsibility.

4. 04

   More complex organisations

   Multiple companies, layered permissions and managers who need overview rather than detail.

• Small Business
• Growing Teams
• Multi-location
• Enterprise

Why it matters

People data that actually helps run the day.

Availability affects scheduling. Roles affect responsibilities. Worked hours affect approvals. Leave affects staffing. Timento keeps those relationships connected.

Timento People Management covers the people needed to run the workforce and the working day. It is not a recruitment, performance review or benefits system.