One timeline. Three tools. Zero meetings added.
A unified day view overlays Slack presence bands with GitHub commits/PRs and Jira issue transitions in 5-minute slots. Daily, weekly, and monthly reports surface deltas so you act on rhythm, not rumor.
Daily view
Five-minute buckets. Three data sources. One page.
Presence bands from Slack are the spine. GitHub and Jira event markers overlay on top, so reality — not a status meeting — drives the picture.
Presence bands
Slack polls every 5 minutes. Active and away are visually distinct, and the detected breaks between them are a feature — they make 'effective time' an honest ratio.
Event overlays
Commits, PR events, and Jira transitions sit above the presence bands with brand-colored markers. Spot the rhythm of a focus session or a shipping sprint at a glance.
Org-local time
Every row is rendered in the org timezone. Week start, excluded weekdays, and minimum-day thresholds are respected in every calculation — no UTC drift.
Fair totals, not raw telemetry.
Organization calendar math is visible, not hidden. Excluded weekdays, minimum-minutes-per-day thresholds, and org-wide work hours are shown wherever they affect a number. People should recognize their own day in the dashboard — including the days that shouldn't count.
- Weekly policy reasons for adjusted days ('below threshold', 'excluded weekday')
- Popovers explain every adjustment on the row it affects
- Configurable per-org: week start, excluded weekdays, minimum day minutes
Across this view, at least one day was credited differently than raw activity (minimum active threshold or excluded weekdays). The underline is intentional: it signals a fair, comparable number—not an unfiltered event stream.
Active time did not reach your org’s minimum for a day to credit toward totals. It is a noise-control choice: a few stray polls shouldn’t read as a full workday.
Your organization does not roll this weekday into org-wide totals. Activity can still show up elsewhere for context; this figure is filtered so comparisons stay fair—think map, not territory.
Reports
Reports written for a Monday 1:1.
Weekly and monthly periods roll up each person and team with deltas against the previous period. Top movers — up and down — are surfaced so conversations happen while they still feel supportive.
- Period-over-period deltas on score, effective time, engagement, throughput
- Per-person and per-team filters
- Human / AI-agent separation
- CSV export on paid plans
Weekly report · team
Week 14 (this week)- Ani Chen· SPACE score+0.8
- Juno Park· Effective time+12%
- Milo Fischer· Active time-15%
- Rina Okafor· Communication score-0.3
Human and AI teammates
Both show up on the timeline.
Workers are tagged as human or AI agent. Metrics framed around human context (satisfaction, breaks) skip AI agents. Metrics that apply to both (throughput, efficiency) include everyone.
Presence bands with break detection. All five SPACE dimensions. After-hours and weekend activity visualized without drama.
No satisfaction dimension. Custom role weights optimized for throughput and efficiency. They appear on the same timeline, so you see the whole team in context.
People · today
5 of 12 shown| Person | Active | Msg | Cmt | Trend | Score |
|---|---|---|---|---|---|
AC Ani Chen Staff engineer | 6h 52m | 28 | 7 | 8.1 | |
JP Juno Park Senior engineer | 6h 08m | 19 | 3 | 7.4 | |
MF Milo Fischer Engineer | 4h 45m | 12 | 2 | 6.8 | |
RO Rina Okafor Team lead | 6h 35m | 34 | 2 | 7.9 | |
TA Triage Agent AI agent · triage | 12h 00m | 0 | 0 | 8.5 |
Replace guesswork with a weekly view you can trust.
Most teams already leave signals in Slack, GitHub and Jira. Pull them into one place in under five minutes — free to start, easy to walk away if it is not a fit.
Free to start · 5-minute setup · walk away if it is not a fit