Analytics

The "Analytics" page is in the main menu. It's only visible to users with the "Analytics" permission, and that permission can only be granted to a role with access to the whole organization: the page compares departments against each other, and a role scoped to its own departments would see cut-down, misleading numbers. That's why "Analytics" isn't available to department-scoped roles — by default only the owner and administrator have it.

The page has two blocks: "Department comparison" and "Scenarios".

Department comparison

At the top of the block is a month switcher (back and forward). The table shows one row per department, plus a separate "No department" row — shifts of employees who don't have a department assigned.

Columns:

• Planned, h and Actual, h — the department's planned and actual hours for the month, in hours.
• Deviation — how far actual hours are from planned, as a percentage: |actual − planned| × 100 / planned. If the department had no plan at all for the month, the column shows "—" — you can't take a percentage of zero.
• Coverage — the percentage of days in the month when the department had at least as many people planned as the minimum-presence setting in your alert settings. If the department has no such minimum configured, the column shows "—": there's nothing to compare against, which doesn't mean "bad".
• Lateness — the number of times employees in the department were late during the month. This column shows "—" for every department when lateness tracking is turned off for the organization.

In every numeric column, the best value is highlighted in light green, and the worst in amber. Highlighting only appears where there are at least two different values to compare — if there's only one department, or every department has the same value, there's nothing to highlight.

There is deliberately no overall score and no "best department of the month" — Smengo compares individual metrics (hours, deviation, coverage, lateness) rather than producing a combined rating. Every department has its own context, and a single ranking would be an unfair simplification.

Scenarios

The "Scenarios" block answers "what if" questions without touching your real schedule. There are two simple scenarios.

"+1 person on a weekday" — pick a department, a day of the week, and a shift, then choose +1 or −1. Smengo calculates how many people typically work that weekday right now ("Before") and how many would after the change ("After"). If the department has a minimum-presence setting or a demand-based recommendation (when you track demand signals such as revenue or foot traffic), a "Target met" or "Target not met" badge appears next to each number: the target is the larger of the two — the minimum-presence setting and the demand recommendation. If neither is set, the target comparison simply isn't shown.

"Change minimum presence" — pick a department and enter a new minimum. Smengo shows a table for all seven weekdays: how many people typically work that day, and whether it clears the current and new minimum. Below the table is the weekly deficit — how many person-shifts are missing for every weekday to clear the new minimum.

Both scenarios are computed from the same baseline — a "typical week": Smengo looks at the last 4 complete weeks of your schedule and averages how many people typically work each weekday. This is not the current week or a calendar month — a future plan is often still empty, so the calculation relies on what has already happened.

All hour and money estimates carry an "≈" sign and are shown "per week" and "per 4 weeks" — not per calendar month. The approximation sign is not a formality: hours and money are calculated from the department's average rates over the last 4 weeks — hourly and fixed per-shift, in the proportion they occur in the department — not the actual rate of each specific person, so the real number may differ slightly.

Money

The "Cost" column in the table, and the money estimates in scenarios, are only visible to users with the "Labor budget (rates and limit)" permission. Without that permission, the page still shows everything else — hours, deviation, coverage, lateness, and the before/after comparison in scenarios — just without any currency amount.

If you have the permission but still don't see an amount — the "Cost unavailable" message — it means rates haven't been set up yet for that department's employees. You can set them up under Settings → Organization → Labor budget.

Under the department comparison table you may see a note like "No rate: N shifts" — it shows how many shifts were left out of the cost total because no rate could be found for them. Those shifts aren't silently dropped: their count is always shown next to the total.

Don't want to check in yourself?

If you'd rather not open the "Analytics" page every week, turn on the weekly report in My Account — once a week you'll get a summary by Email or Telegram: hours, department comparison, risks, and — with the "Labor budget (rates and limit)" permission — money too.