iMATRIX · Resources
Organise working time and leave requests in one place
Record time, request absences and review decisions clearly: iMATRIX brings these tasks into a shared workspace with defined responsibilities and existing user permissions.
A shared view of time and absence
When working hours live in a list and holiday requests arrive in separate messages, coordination can soon become difficult. Employees want to know whether their request has arrived. Managers need a clear overview before making a decision. A shared workspace helps people consider these tasks in context.
With the relevant iMATRIX functions enabled, employees can record their own time and submit absence requests. Authorised managers review those requests through the intended approval process. Recording, checking and deciding remain separate steps. A requested absence is not yet a confirmed absence, even when its details have already been saved.
From a time record to an understandable decision
Record your time promptly
Enter working time as close as possible to the actual working day. Check the date, start, finish and required assignments. If something is unclear, resolve it with the team rather than simply estimating a missing detail.
Request leave or another absence
Select the appropriate absence type and the period you want to request. Review the duration shown and complete the required information. A clear handover helps the team organise outstanding tasks during the absence.
Review the request in context
Authorised managers consider the requested period, the available information and possible overlaps within the team. Check that the responsibility has also been assigned correctly. The decision should rest on an understandable and current picture.
Record a deliberate decision
Approve or reject a request after completing your business review. Add an understandable decision note where helpful. Employees can then refer to the saved status rather than relying on scattered conversations or assumptions.
Clear responsibilities support the team
A digital process works best when everyone understands their part. Clarify who can complete time records, who reviews requests and how questions are handled. Not everyone needs the same level of access.
The person making a decision remains responsible when approving through the mobile app. Check the information and period displayed before confirming an action. If a function is blocked or available only for reading, the responsible administrator must first check the configured state. Choosing a different access route is not a substitute for a missing approval or permission.
What to consider during everyday use
Review time records regularly
A short, regular check helps identify open or incomplete entries. Corrections should follow the intended paths so that the relationship with the original transaction remains understandable.
Plan absences together
Consider planned handovers and colleagues who may be absent at the same time. The information displayed supports planning. It does not replace operational agreements or a review of the rules that apply within your company.
Preserve historical information
Unclear legacy records and historical conflicts are not automatically confirmed working hours. Retain their identification and history. New approvals should not be used to silently resolve earlier uncertainties or change their meaning.
Frequently asked questions
Can anyone approve leave requests?
No. Approval requires the appropriate user permissions, enabled functions and intended business prerequisites. Seeing an action in the app does not grant any additional rights.
Does a saved request already confirm the leave?
No. Submitting the request records the wish to take an absence. An authorised decision through the intended process sets the corresponding status. Check that status before treating the absence as approved.