The View You Check Every Week, Saved

Build a Tracked Time view once — rows, columns, filters — and save it as a dashboard pinned in your sidebar. Share it, report on it, or read it through the Rize MCP.

How it works

A spreadsheet you don't have to build, saved as a dashboard your whole team can use.

01

Any View Becomes a Dashboard

In Tracked Time, pick the rows and columns — Date, Teams, Members, Clients, Projects, Tasks, Labels, Titles, or Departments — add a filter, then click Save. The dashboard keeps its grouping, filters, and a rolling range, so a view saved on 'this week' opens on the current week every time.

02

Pinned Where You Look

Saved dashboards are added to your favorites and pinned in your sidebar — the weekly burn view is one click away instead of a rebuilt query. The Dashboards page lists every saved dashboard with live preview cards for favorites at the top.

03

Tables, Charts, and the Log

Every dashboard has three views: a spreadsheet-style table with busy days shaded darker and an hours-or-percent toggle, grouped bar and pie charts, and the underlying entry log where admins can add, edit, or delete entries they're allowed to.

04

Shared at the Right Level

A dashboard starts private. Its owner opens it up from the visibility chip: Team shares it with that team's admins, Workspace with workspace admins. Tabs on the Dashboards page split views into Just Me, Team, and Workspace.

05

Reports and Chat on the Same View

Link an AI report to a dashboard and the analysis runs on exactly that saved view on a schedule. Or click Chat — or @mention the dashboard in the agent — and ask questions against the same data your team sees.

06

Export and MCP Access

CSV and PDF exports respect the on-screen layout — whatever rows, columns, and filters are showing is what the file contains. Every dashboard is also available through the Rize MCP, so Claude, ChatGPT, or Cursor can read your saved views.

The numbers

What changes when the view is saved instead of rebuilt.

9

Grouping fields, from Clients to Departments

3

Views per dashboard: table, charts, log

3

Sharing levels: Just Me, Team, Workspace

1 click

From sidebar pin to the view you check weekly

How teams use saved dashboards

Three worked examples, from an ops lead's burn view to a shared utilization board.

Ops lead's weekly burn view

Resourcing manager, 30-person agency

Her Monday check is always the same view — clients by week for her team — and she rebuilds it every time: same filters, same columns, same export to the same spreadsheet.

With Rize: The view is saved as a dashboard pinned in her sidebar with a rolling week range. She opens it, reads it, and a linked AI report runs the analysis on that exact view each week.

Partner's client margin board

Managing partner, flat-fee accounting firm

He wants hours by client and service line monthly, but asking the ops manager to pull it means a day of exports — so he asks quarterly instead of monthly.

With Rize: A Workspace dashboard holds clients by month with the service-line filter saved. He opens it himself; the ops manager's routine emails the analysis monthly.

Team's shared utilization view

In-house ops team sharing one plan

Everyone has a different bookmark: three versions of 'the' utilization view with different filters, and every meeting starts by arguing about which numbers are right.

With Rize: One Team dashboard is the shared source — planned vs. tracked on the Planned tab, same filters for everyone. The argument moves to what to do about the numbers.

Stop rebuilding the same report

Save the view once. It's one click away every week after. Free 7-day trial, no credit card required.

Frequently Asked Questions

The best time tracking dashboard is the view you already check every week, saved instead of rebuilt. In Rize, any Tracked Time view — clients by week, members by project, burn against retainer — saves as a dashboard pinned in your sidebar, with a rolling date range that always opens on the current period.

In Tracked Time, set rows to Clients and columns to week, filter to the team or projects that matter, and save it as a dashboard. Busy days are shaded so heavy weeks stand out, and you can toggle between hours and percent. Link an AI report to it and the burn analysis runs on that exact view every week.

Yes. Dashboards start private. The owner opens the visibility chip under the title and chooses Team to share with that team's admins or Workspace for workspace admins. The Dashboards page separates views into Just Me, Team, and Workspace tabs.

Tracked Time is the explorer — pick any rows, columns, and filters and the table rebuilds. A dashboard is a saved Tracked Time view: same explorer, frozen into a named, pinned, shareable view with a rolling range. Reports and chat analyze dashboards, so the AI reads the exact view you saved.

Yes. Preset dashboards are rolling out: Timesheets is available now, with Task Velocity, Capacity, Project Health, Client Health, Billable Time, Label Analysis, and Personal Productivity coming soon. Any preset can be adjusted and saved as your own.

Yes. CSV and PDF exports respect the on-screen layout — whatever rows, columns, and filters are showing is exactly what the file contains. Large exports are emailed to you instead of downloaded.

Yes. Every dashboard is available through the Rize MCP, so Claude, ChatGPT, or Cursor can read a saved view. Reports linked to dashboards run on the same saved views, so the agent analyzes exactly what your team sees.

Before dashboards, the agent had to rebuild the view through the MCP before analyzing it — slow and inconsistent. Now the view is already saved, so a linked report or an @mention in chat analyzes exactly the data your dashboard shows, faster and with consistent results.

Yes. If your workspace uses Resourcing, a Planned tab in Tracked Time shows planned hours beside tracked for any saved view — capacity and utilization on the same dashboard as the actuals.

Yes. A dashboard keeps its grouping and filters, and its range rolls forward — a dashboard saved on 'this week' opens on the current week every time. The underlying data is tracked automatically, so there is nothing to refresh or re-enter.