← Back to Changelog

New Work Hours Calculation Method

May 10, 2026

Work Hours is one of the most important metrics in Rize — it shows how much you actually worked in a day. We've heard from a lot of you that the old calculation didn't quite fit how you think about your work, especially when you're across multiple teams or trying to exclude breaks. So we've launched a new way to calculate it.

Two calculation methods

Head to Settings → Time Entries and you'll see a new Work Hours Calculation Method dropdown with two options:

  • Time entries (the new default) — Work Hours is calculated from your approved and pending time entries. Clean, simple, and tied exactly to the work you actually logged.
  • Categories (deprecated, still supported) — The original calculation. Sums time spent in focus, meeting, and break blocks plus time in work categories.

Why we changed the default

The time-entries method makes things a lot simpler — especially for people working across multiple teams. Your Work Hours total now lines up exactly with how much time you committed to each team, and it naturally excludes break time without you having to configure anything.

Hover the Work Hours bar on the calendar and you'll see the team-color breakdown — so you can tell at a glance how today's hours split across teams.

Keep the old behavior if you want it

If you preferred the category-based calculation, it's still there. Switch to Categories in Settings → Time Entries and nothing else changes. We'll continue to support both.

Fixes shipped alongside

  • Work Hours no longer credits future time — A calendar entry running 14:00–21:00, viewed at 20:03, used to add the full 7 hours to your total (including the 3 hours you hadn't worked yet). Now it's capped at the current time.
  • Weekly breakdown no longer swaps meeting time and break time — A long-standing reporting bug, fixed.
  • The "Review Time Entries" button counts only entries actually awaiting review — Tracking and segmenting entries are in-flight, not pending, so they no longer inflate the count.

Related Changelog Entries