Measure engineering effort more accurately with the daily effort model

We’ve reworked how Swarmia calculates developer effort. Instead of calculating effort once from a whole month of activity, the model now looks at one working day at a time and adds the days together.

Under the previous model, a single busy stretch of a few days could account for a large share of the whole month. The new model gives every working day equal weight, so one busy day can’t dominate the rest. This means you get a fairer, more accurate picture of where engineering effort actually goes.

The monthly model could only report on a full calendar month. Because the new model produces a value for each working day, you can now view effort by day or week, not just by month. We’ll gradually roll out more capabilities to view effort in sub-month timeframes.

The new model now applies across every view. Individuals who consistently contribute code changes will see little change to their effort distribution.

Read more about the updated effort model.


Subscribe to our newsletter

Get the latest product updates and #goodreads delivered to your inbox once a month.

More changelog updates
· Sep 7, 2026

Connect GitHub Issues to Swarmia [beta]

You can now connect GitHub Issues to Swarmia as an issue tracker, alongside a growing number of other issue trackers . Once connected, your GitHub issues flow into Swarmia and behave just like any other issue. That means you get the full picture: metrics like cycle time and flow efficiency, plus an…
Read more
· Sep 4, 2026

Catch org-level changes early with new signals for engineering leaders

Signals are already great at flagging team-level anti-patterns like high work in progress or stale pull requests. Now, we’re expanding the set with signals built for engineering leaders, so you can catch the changes that matter at the organization level too. The newest additions to signals: -…
Read more