Reports and exports
Every report is built from the same signals as the live score, so totals always match. The employee copy shows outcomes; the admin copy shows the working.
Periods, formats, audiences
- Periods: day, week, month, quarter, half year, year. Monthly means the calendar month: month-to-date when generated mid-month, the full previous month on the first.
- Formats: PDF or XLSX, downloaded or sent as a direct message.
- Employee copy: score, pillar scores, attendance, pings, strikes, task log and achievements. Admin copy: everything, including weights, the weighted subtotal, the location mix and the integrity signal, with a confidential footer.
- Direct-message sends, scheduled personal summaries and self-requested reports use the employee copy automatically.
The per-employee scorecard
When credited hours fall below a grace line, the admin copy shows an estimated base-salary adjustment as a percentage only, pro-rata and capped; it is hidden within grace and explicitly an estimate. Payroll decisions stay human.
scoring.salary_grace_pct scoring.salary_cut_cap_pct
| Twin headline | efficiency and the KPI mapping side by side; the KPI itself only on quarter-end months |
|---|---|
| Score bridge | format, absence and late deductions shown separately with the live tariffs |
| Why table | every strike with its date, type and plain-English reason; waived strikes greyed out with the reason |
| Hours | expected basis spelled out, hours worked, hours credited, verified overtime, short days against your own expected day |
| Task log | blocked, stalled and repeated items with since-dates, then recent completions |
| Main threads | completed work clustered into named themes |
| Items without full credit | the exact vague and coordination items the progress scorer refused, dated |
| Recommendations | up to four evidence-cited suggestions, labelled BETA |
| Goal and trajectory | target, band, team median and a six-month trend |
| Glossary | every term used, defined |
Organisation and dispute views
- Executive summary (monthly): a one to two page roll-up of average efficiency and band distribution, hours delivered against expected, top and bottom performers, strike hotspots and recommended actions, scoped to what you may see.
- Attendance detail (day by day): one employee and month, each calendar day with sign-in and sign-off in their timezone, hours against expected, late flags against their learned start, missed sign-offs and every strike labelled by type. Built for settling disputes. Employees can pull their own; managers can push it to a person, a team or everyone, each recipient getting only their own.
- Heatmap: every employee as a row, one cell per day, for one to six months; off-days and holidays are drawn differently so a quiet weekend never reads as low engagement.
Schedules
Reports can be sent automatically: daily on weekdays at 18:00, weekly on Friday at 17:30, monthly on the first at 09:00, quarterly and annually, each cadence switchable. Weekly summaries generate on Monday morning and the manager digest follows at 09:00.
reports.weekly_summary_enabled reports.weekly_summary_day reports.daily_digest_enabled reports.digest_hour_utc
CSV exports for BI
Exports are scoped to the people you may see, stream rather than buffer, and work with a personal API token so a BI tool can pull them on a schedule.
| attendance.csv | one row per employee per day, up to 366 days |
|---|---|
| hours.csv | per-employee totals: hours, days, late, unexcused, excused |
| efficiency.csv | one row per employee-week from the materialised scores; a week with no score exports empty, not zero |
Correcting a day
Managers may correct a sign-in time, a sign-off time or the hours credited for people on their team, admins for anyone. Every correction is audited with who made it and offers a 90-second undo. Editing a time re-derives the day, so a mistyped sign-in that looked late clears once fixed. Days beyond the daily ceiling wait in the long-session review queue where an admin confirms or rejects the span with the day’s evidence beside it.