People operations
Attendance and leave, in the same place as the work
Attendance and leave in Matrix
Import the attendance machine's own export
Upload the spreadsheet your device produces — legacy .xls or modern .xlsx, and the importer copes when the extension lies about which one it is.
In, out, work duration, total duration
The importer reads the columns the machine writes and matches each row to an employee by code, so what lands in Matrix is what the reader recorded.
Corrections without a rewrite
Every attendance record can be edited when someone forgot to badge, and the corrected day is what the report uses.
Leave types you define
Casual, sick, earned, unpaid, whatever your policy calls them — leave types are a catalogue you maintain, not a fixed list.
Company holidays
Maintain the holiday calendar once, and it shows up on the team calendar and on employees' own dashboards.
Apply, approve, reject, cancel
Each step emails the people involved, with the leave type, dates, duration, reason and the approver's comments included.
Balances and summaries
My Leave Summary for the individual; Leave Summary, Monthly Leave Summary and Upcoming Leave for whoever needs the team picture.
Additional leave and deductions
Grant extra leave when it is warranted and record deductions when it is not, both as first-class records rather than notes.
Work from home
Work-from-home is its own request type, so a remote day is not filed as leave and does not disappear from the record.
The import is the point
Attendance data almost always exists already — it is sitting in a device by the door, exported weekly into a workbook that somebody then reconciles by hand. The reconciliation is where the hours go and where the errors come from.
Matrix reads that workbook. It finds the attendance date, finds the header row, and reads every row underneath it whose employee-code column is a number. Rows that do not match a known employee are visible rather than silently dropped.
Leave that leaves a trail
A leave request in a chat thread is invisible three weeks later. In Matrix it is a record: who applied, for which type and dates, who approved or rejected it, what comment they left, and what it did to the balance.
The email at each step exists so nobody has to log in to find out what happened — and any individual can turn leave emails off for themselves if they would rather read it in the app.
- Application, approval, rejection and cancellation each notify by email
- Approver comments travel with the decision
- Per-user opt-out in Notification Settings
Why it belongs next to the delivery data
A sprint that slipped and a week of approved leave are the same story told twice. When attendance, leave and delivery live in one workspace, that connection is visible without anyone cross-referencing two systems by hand.
It also means a manager checking on a project sees the same people, the same names and the same reporting line they see everywhere else in Matrix.
People operations: common questions
Which attendance file formats can Matrix import?
Can we define our own leave types?
Is working from home tracked separately from leave?
Related
Hiring and talent
The employee directory, documents and reporting hierarchy
For HR and people ops
How the people side of Matrix fits together
Getting attendance data off spreadsheets
Why the monthly reconciliation is the expensive part
Or go back to all features.
Try it against your own work
A workspace takes a couple of minutes to create. Put one real project in it and see whether this shape matches how your team already works.