Reports

Reports is the cross-employee view that individual module pages can’t give you. Where Presence shows you one person’s calendar, the Attendance Threshold report shows you every person who crossed a pattern in the same period. Where Expenses shows you one report at a time, the Company Spend report shows you where the money went across the whole organization.

• Who can use it: managers see results for the whole company. Supervisors see results scoped to their own team. HR see the HR-area reports only (nothing that draws on expenses, tasks, or other non-HR areas).
• Where: Sidebar → Reports.
• Default: off. Enable it at Settings → Modules.

Reports are organized by module. A report only appears in your catalogue when its source module is enabled - expense reports won’t show up until Expenses is on, attendance reports won’t show up until Presence is on, and so on.

Reports earn their keep when you need to step back from the day-to-day and look across the organization for a full period - a month, a quarter, a year.

Reach for Reports when:

• You’re preparing for a budget or planning meeting and need headcount numbers, expense totals, or training completion rates all in one place.
• You want to spot patterns that aren’t visible one record at a time: attendance habits by day of week, employees overdue for a check-in, a cluster of incidents in one team.
• You need to hand data off to someone without mizuiro access - finance for payroll processing, an auditor for a compliance review, HR for headcount planning. The CSV export is built for that handoff.
• You’re wondering whether your team’s check-in cadence is holding up in practice, or whether some people have gone weeks without a touchpoint.

Individual module pages are where you work on specific records. Reports is where you look across all of them at once.

1. Go to Sidebar → Reports and pick a report from the catalogue.
2. Adjust the filters - most reports offer a date range, a team filter, and a status or threshold depending on what the report is measuring.
3. Click Run.

Results appear on the page: summary cards at the top, one or more charts in the middle, and a full data table below. Change a filter and run again to slice the data a different way. You don’t need to leave the page between runs.

Every report can be exported once it’s been run.

• Small reports download immediately.
• Larger reports are queued and built in the background. The file appears in your report history when it’s ready - you don’t need to sit and wait on the page.

Note

Generated export files are cleaned up automatically after the retention period set in Settings → Reports. The history entry stays permanently - you always have a record of what was run and when - but the downloadable file is removed after the window passes. Re-run the report any time to get a fresh copy.

Employee Roster

A snapshot of everyone in your organization with their current status, tier, team, job title, and hire date. Useful for an org audit, feeding data into an external HR system, or producing a clean directory for a third party who doesn’t need mizuiro access. It opens on Current (everyone still with you); pick All, Retired or Terminated from the Status filter to include people who have left.

Headcount Summary

Team sizes and how people are distributed across the organization, broken down by employment status. The quick answer to “how many people do we have, and where are they?” when you need it for a budget conversation, a board update, or a planning session.

Seniority

Everyone ranked by length of service, longest-tenured first, from their hire date. People hired the same day are ordered by last name; anyone without a hire date sorts to the bottom.

Departures

Who left in a period (terminated or retired), the date, how long they’d been here, who recorded it, and the note. The period defaults to the last twelve months. It reads the employment status history, so it covers departures recorded as a status change. There’s no team filter: people are taken off their teams when they leave. A supervisor in assigned scope sees the departures they recorded themselves.

Activity Summary (360)

Everything on file per person over a period you choose (days back), in one row: the total of every presence status, plus kudos, concerns, warnings, and incidents. Filter to one person or a team. It draws only on what the person running it could open anyway, so a supervisor’s version never reveals a record they couldn’t see on its own.

Task Summary

Open, at-risk, and overdue tasks for each person. Self-assigned tasks are never counted: they’re people’s private follow-ups, private from you too. The “who’s carrying the most, and who’s slipping?” view. Needs the Tasks module.

The Presence module needs to be enabled for these reports to appear in your catalogue.

The attendance reports work best once you have a few months of Presence data behind them. One or two records in isolation don’t tell you much - patterns across 60 or 90 days tell you a great deal.

Attendance Threshold

Every employee who has had a given presence status at least a set number of times within your chosen date range. Set the status (sick, no-show, late) and the threshold (four or more times, say), and the report surfaces everyone who crossed it.

This is the most direct way to turn Presence data into an actionable list. One sick day is nothing. Five in a month is a conversation worth having.

Day-of-Week Patterns

Every employee who has had a specific status on the same day of the week a set number of times. Recurring Monday absences or a pattern of Friday early departures are easy to miss when you’re reviewing individual days - this report makes them visible across the whole team at once.

Status Sequences

Every instance where one attendance status was followed by another within a set number of days. The most common use: a sick day followed by a no-show within three days is a very different pattern from a sick day followed by a return to work. Define the pair and the window, and the report finds everyone who matched it.

Time Off Summary

Needs the Time off module. Days taken per person over a period, split into vacation, sick, appointment and everything else, with anything still waiting on a decision alongside. Half days count as halves, and only working days count: a week off over a public holiday is four days, not five.

It is a record of what was taken, not an entitlement calculation. mizuiro deliberately holds no balances, so there is no “remaining” column and there won’t be one; what someone is owed lives in your payroll system, and this report is what you check it against.

The Performance module needs to be enabled for this report to appear in your catalogue.

Performance Review Status

Every review with its status, who’s conducting it, when it’s scheduled, and when it was completed, so you can see the whole review cadence in one place instead of clicking through records. Reviews that were scheduled for a date now in the past and still haven’t happened are flagged as Overdue, with a running count of how many days they’ve slipped, and you can filter the report down to just those. Summary tiles across the top give you the totals at a glance: scheduled, overdue, completed, and acknowledged.

Reach for it when you want to make sure reviews aren’t falling through the cracks, or before a planning cycle when you need to know who’s due.

Disciplinary Summary

Concerns, written warnings, and improvement plans together in one list across your chosen date range, each row tagged with its type. Filter to one type or see them all, with counts of each across the top and a by-type chart. It’s the single place to see the formal record of what’s been raised, rather than checking three separate tabs. (For a per-person rollup of the same data, the Activity Summary report counts these by employee.)

Upcoming Probation Endings

Everyone currently on probation and when it ends, sorted by how soon, with each person bucketed by urgency, ending this week, this month, or later, and anything already past its date flagged as overdue. Narrow it to the next 7, 30, 60, or 90 days. The point is simple: a probation decision (confirm, extend, or part ways) should be made before the date slips by, and this makes sure none do.

PIP Outcomes

Every improvement plan with its status, when it started, its planned end, any extension, when it ended, how many days it ran, and the outcome. The summary gives the share of completed plans that ended successfully and their average length. Nothing from inside the plan (objectives, notes, linked evidence) is in it. A supervisor in assigned scope sees the plans they created, as on the PIPs page.

The Kudos module needs to be enabled for this report to appear in your catalogue.

Recognition Summary

How much recognition each person has received in your chosen window: how many kudos, when the last one landed, and how many were shared back with them. Crucially, it lists everyone, including the people who haven’t received any kudos yet, flagged as “Not recognized yet.” That’s what the report is for: it’s easy to see who’s being celebrated, and much harder to notice who’s being overlooked. A recognized-vs-not chart gives you the balance at a glance.

Reach for it before a round of reviews, or now and then as a gut check that recognition is landing across the whole team and not only the loudest corner of it.

The Expenses module needs to be enabled for these reports to appear in your catalogue.

Expense Summary

Total approved spend per employee over a date range, broken down by expense type and approval status. Useful for identifying outliers, checking whether spending is within expected ranges, and giving finance a per-person breakdown to run alongside payroll.

Company Spend

Organizational total for approved expense reports, broken down by expense type. The big-picture view for month-end or quarter-end review, or for any discussion about where the company’s money is going.

The Incidents module needs to be enabled for this report to appear in your catalogue.

Incident Summary

Incident counts broken down by type, status, and involved employees across your chosen date range. Useful for identifying whether one team or one incident type is disproportionately represented over the period, and for preparing a summary for safety reviews, union meetings, or audits.

The Touchpoints module needs to be enabled for this report to appear in your catalogue.

Touchpoint Frequency

How often each employee has had a check-in within the date range, and who may be overdue for one. This is the fastest way to see whether your team’s 1-on-1 cadence is holding up in practice as well as in intention.

Supervisors often intend to check in weekly but drift under workload. This report makes the drift visible early - before it becomes long enough to matter.

The Training module needs to be enabled for this report to appear in your catalogue.

Training Completion

Training records for every employee across the date range, broken down by course, delivery method, status (completed, scheduled, cancelled), and certification state. Useful for compliance checks, finding who still needs to complete a required course, and confirming that certifications are current before an audit or inspection.

Required Training Gaps

For every active training requirement, who’s missing it, whose certificate has lapsed, who’s still inside their deadline, and whose certificate expires soon, with the date that matters for each. Switch Show to Everyone to see who’s up to date as well. It uses the same rules as the Training requirements page, so the two always agree.

The Conferences module needs to be enabled for this report to appear in your catalogue.

Conference Attendance

Who attended which conferences across the date range, with the dates, how many days each ran, and where. A quick way to see how conference time is being spent across the team, prepare a professional-development summary, or check who’s been out at events recently.

Costs aren’t shown here on purpose: money lives in Expenses. File an expense report against the attendance’s reference number and the Company Spend report picks it up there.

Requires the Policies module.

Policy Acknowledgements

Across every published policy that asks for a signature, who hasn’t acknowledged its current version yet, with the deadline and whether they’re past it. Switch Show to Everyone to include who has signed, and which version. The same answer as each policy’s own CSV, for all of them at once.

Settings → Reports

Export file retention

How long generated CSV files are kept after they are built. The run history is kept permanently; only the downloadable file is removed after this window. Set it long enough that you can always retrieve a recent export, and short enough that old files don’t accumulate indefinitely.

Widget colour

Sets the accent colour for Reports dashboard widgets.

A report I expect isn’t showing up in the catalogue.

The report won’t appear until its source module is enabled. Go to Settings → Modules and confirm the relevant module is turned on, then come back to Reports.

Do people who have left show up in reports?

It depends on the question the report answers. Reports about what’s true right now - the roster, seniority, headcount, touchpoint frequency - leave them out, because they’re not part of the picture any more. Reports about what happened over a period - who went to conferences last year, training completed, kudos, expenses, incidents - keep them, because it happened while they were here. Their name carries (left) so it’s clear at a glance.

Can supervisors run reports for the whole company?

No. Supervisors see results scoped to their own team only. Only managers see the full organization in report results.

A report never shows more than the module it reads from. So for a supervisor in assigned scope, Incident Summary lists the incidents they reported (as the Incidents page does), Touchpoint Frequency doesn’t count a private 1-on-1 another supervisor ran, and Headcount Summary shows their own teams.

My export is queued - how do I know when it’s ready?

It appears in your report history on the Reports page when the file is built. You don’t need to keep the page open - come back any time, check the history, and download when the link is there. The entry shows the report name, who ran it, the date, and a download link once it’s ready.

How long are my exported files kept?

The retention period is set under Settings → Reports → Export file retention. After that window the file is removed automatically, but the history entry stays so you can see what was run. Re-run the report any time to get a fresh file.

Can I schedule a report to run automatically?

Not currently. Reports are run on demand. For recurring reviews, a calendar reminder to run the report at the start of each month is the practical workaround.

Why does the Expense Summary only show approved reports?

Reports are built from finalized data. Expense reports still in draft or pending approval haven’t been signed off and could still change. Including them would mix confirmed and unconfirmed spend in the same total. Run the report after your approval cycle closes for a clean, actionable number.

The Training Completion report is missing a certification I expected.

Certification tracking only applies to courses marked as granting certification in the course catalogue. If a course wasn’t configured with that flag set, mizuiro has no expiry date to track and won’t include certification data for it. Check the catalogue at Settings → Training and confirm the certification option is enabled on the relevant course.

Note

How to read this: ✓ can see it, ✗ can’t, ○ depends on a setting or condition (explained under the table). As a manager, you always see everything in your company.

• ○ Supervisor: in shared scope, supervisors can run reports with full company data. In assigned scope, supervisors can run reports but the data is automatically filtered to their own teams.
• ✗ Employee: employees have no access to the Reports module.