Why a team view and not a GitHub view
GitHub shows repositories and organizations. Managers run teams, and the two rarely match: one squad works across four repositories, one monorepo hosts six squads, a contractor commits from a second account. Squadlog starts from the team as you actually run it. You pick its repositories across any connected organization, name its managers, and every number on the dashboard is computed for that group of people only.
The result is a page you can read in a minute on Monday morning: what did the team ship over the period, is review flowing, is anything stuck, and who carried what.
The four numbers at the top
Commit effort is the sum of effort scores of the period’s commits, so a week of small fixes and a week with one large feature read differently. Merged PRs counts pull requests merged into the default branch. Time to first review is the median delay between a PR being opened and the first review from someone else. Stuck PRs counts open PRs over your own thresholds.
Each card carries the delta against the previous period of the same length, so a 30-day view compares with the 30 days before. Negative deltas are shown in amber, never red: a slower week is a signal to look at, not a verdict.
Who ships, ranked by work
The Who ships card ranks members by commit effort or by merged PRs depending on the team’s primary measure. Bars are relative to the top member, so the shape of the team is visible at a glance: one person carrying most of the load, or a flat distribution.
The ranking is a view of what shipped, not a grade. There is no threshold on people, no colour coding of individuals, and nothing is sent to anyone outside the team’s managers.
Periods, comparison and export
Switch between 7, 30 and 90 days; the choice is remembered per user. The Compare toggle shows or hides deltas and the dashed previous-period line on the chart. Every table exports to CSV with the same numbers you see on screen.