Insight
Reports across delivery, hours, attendance and leave
The reports
Hours Per Project
Where a month of the team's time actually went, project by project, from the hours recorded on Daily Status Reports.
Effort Allocation
The split of effort across projects, for a person or a team — the report to open before promising anyone's time to a new engagement.
Project Dashboard and Project Analytics
The state of a single project: tasks, bugs, open work and reopened issues, alongside its stored analytics counters.
Sprint analytics
How each sprint went, using the sprint dates and issue history the board already produced.
Issues and Project Users
Filterable views across issues and across who is assigned to which project.
Employee DSRs and Missing DSRs
The narrative side of reporting, and the list of people and dates where it is absent.
Attendance Report
Attendance across the team for a period, built on imported and corrected records.
Leave Summary and Monthly Leave Summary
Leave taken and remaining, per person and per month.
Email Logs and Chat History
Every email Matrix attempted to send, and — for the companies that use the assistant — the questions asked of it.
Reports are only as good as the record underneath them
A utilisation report assembled from a timesheet tool, a project tool and an HR tool spends most of its life being reconciled. The numbers disagree because the systems disagree about who was on what, and about which week a piece of work belonged to.
In Matrix there is one record. The issue on the board, the hours on the DSR, the approved leave and the person's reporting line are rows in one database with one company boundary around them. That is why these reports need no export step.
Every report is permissioned
Each report sits behind its own named permission, so a team lead can be given Hours Per Project without also being given the Leave Summary for the whole company, and a finance user can have the effort reports without the issue detail.
The permission grid is the same one that controls the sidebar. Grant the permission, the report appears; revoke it, the route stops resolving as well as the menu item disappearing.
Projects carry their own counters
Alongside the reports, each project stores its own totals — tasks, bugs, open tasks, open bugs, reopened issues — with the time they were last updated, so a project list can show the shape of a project without recomputing it on every page load.
Insight: common questions
Do reports need an export or a separate BI tool?
Can we control who sees which report?
Related
Daily Status Reports
The source of the hours in every effort report
Roles and permissions
How access to each report is granted
Tracking billable hours per project
Getting from logged hours to a number you would show a client
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.