Skip to content

Insights

What each branch cost, where the overtime is, who left, and what the roster is short of next week — with the caveat each figure comes with.

Updated View as Markdown
For humans

Insights is the one screen that reads across everything else. It answers the questions a chain owner has and no single console can: which branch is expensive, where overtime is growing, how many people left this year, and what next week’s roster is short of.

What you see depends on what you hold

Opening the screen needs the org-wide report permission. Each section additionally needs the permission for the data it summarises — the wage bill needs the payroll read, absence needs the org-wide leave read, and so on. A section you have no permission for simply is not on the page; nothing is greyed out and nothing refuses you.

The same is true of modules your organization has not bought. Without payroll, Insights is the whole page minus the money.

The window

One control, top right: Last 3 / 6 / 12 / 24 months. It scopes every section at once — there is deliberately no per-chart date picker, so two charts on the same screen can never be showing two different periods.

Every chart has a table

Each card has a Table button. It shows exactly the numbers the chart drew — the same figures, as text, when you need the value rather than the shape.

Wage cost, and the honesty line under it

What each branch cost is base wages from priced timesheet days, grouped by the branch the work happened at. Under it is a sentence you should read once:

N% of this bill is attributed from the roster and is authoritative; N% falls back to the earner’s home branch.

Those are two different qualities of number. When the roster says where a shift was, the cost books there and is certain. When there is no roster evidence, it books to the person’s own branch as a stand-in — fine for staff who never move, wrong for anyone who covers.

Split days is its own bar, not a footnote. When someone worked at two branches on one day, that day’s cost belongs to neither, so it is shown separately rather than guessed at. If that bar is large, cross-branch cover is a real part of your wage bill.

Overtime

Overtime by branch stacks approved overtime month by month. Cash or time off splits the same approved overtime hours by how each was settled, and the two are never added together: cash goes into a payment, 補休 becomes a credit in a leave balance — two different costs.

People

Joiners and leavers counts assignments that started and ended each month; Headcount over time is the number of active assignments at each month’s end. They are two charts on purpose — single-digit joiners and double-digit headcount on one axis would flatten the bars to nothing.

Absence

Leave taken is approved leave by type, month by month. A request that spans a month boundary counts whole, in the month it began — leave hours are stated by the requester, not divided by elapsed days.

Leave owed is different in kind: it is accrued, untaken leave as of today — a liability, not a cost. Unused 特休 is money owed if the year closes with it untaken. It is shown in hours, because converting it to money needs each person’s own pay rate.

Next seven days

Roster coverage is the only forward-looking chart: required against filled, day by day, for the coming week. An over-filled day does not repay an unfilled one — each shift’s shortfall is counted on its own, so the “Unfilled shifts” figure is a real work list. Fill them on the roster planner.

Approvals decided is throughput beside the backlog, with the date of the oldest request still waiting underneath. The Waiting over 72h tile at the top of the page is the one to act on; Approvals is where you act.

Commission

Units served comes from approved commission claims. Beside it, By item lists units and money.

Navigation

Type to search…

↑↓ navigate↵ selectEsc close