Reports That Run Whether You Remember or Not

Link a report to a dashboard and Rize runs the same AI analysis on a schedule — weekly burn, client profitability, team reviews. Same view every run, every run kept.

How it works

A report analyzes a saved view on a schedule, so the numbers are consistent from week to week.

01

Reports Linked to Dashboards

Pick a saved dashboard and a cadence, and Rize runs an AI analysis of exactly that view. Because the view is already saved, every run covers the same data — the insights stay consistent week to week instead of depending on how the question was phrased.

02

Templates to Start From

Start from a template like weekly team overview or client profitability, customize the prompt, choose the scope — yourself, a team, or the whole workspace — then run it once or on a schedule.

03

Scheduled Runs

Dashboard reports default to weekdays at 8 PM, and each run can cover the dashboard's own range. The weekly burn review, the Monday capacity check, and the month-end margin readout happen whether or not anyone remembers to open the report.

04

A Page per Report, a Run per Row

Every report has its own page. The list shows what each report runs for, its schedule, format, linked dashboard, and last and next run. Inside a report, runs are listed down the left and the selected run's analysis — summary and insight cards — is in the middle.

05

Chat with Any Run

Click Chat on any report or on an individual run to ask follow-up questions from that exact output. The agent reads the saved view instead of rebuilding it, so the analysis is faster and more accurate.

06

Dashboards in the Rize MCP

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.

The numbers

What changes when the report writes itself on a schedule.

8 PM

Default weekday schedule for dashboard reports

1 view

Per run — the saved dashboard, every time

0

Spreadsheet exports between tracked time and the report

Every run

Kept on the report's page for comparison

How teams run scheduled analysis

Three worked examples, from an agency's Monday burn review to a firm's month-end margin check.

Agency weekly burn review

Resourcing manager, 25-person agency on retainers

Every Monday she rebuilds the same burn view in a spreadsheet from timesheet exports — and it only works if people did their timesheets, so some weeks the report just doesn't happen.

With Rize: The clients-by-week view is saved as a dashboard with the report linked. The analysis lands on a schedule, each run is kept on the report page, and an over-burning client shows up in week two.

Accounting partner's month-end margin check

Managing partner, value-priced CPA firm

The firm prices on flat monthly fees, so nobody knows which engagements are underwater until the partner pulls hours by hand — which he does maybe twice a year.

With Rize: A client profitability report runs monthly against the client dashboard. Hours and margin by client arrive without an export, and repricing conversations start from the same numbers.

Ops lead's capacity readout

Director of ops, in-house client services team

Leadership asks for utilization numbers at the quarterly business review, and assembling them takes a week of Slack pings and stale spreadsheets.

With Rize: The capacity dashboard runs a scheduled analysis each week. The readout for the quarter is a scroll through past runs, not a new project.

Put your weekly review on a schedule

Link a report to a dashboard and the analysis runs itself. Free 7-day trial, no credit card required.

Frequently Asked Questions

Save your burn view — clients or projects by week — as a dashboard in Rize, then link a report to it. Rize runs the same AI analysis on that view every week, so the burn report is waiting for you instead of being rebuilt from timesheet exports.

The best reporting tool analyzes a fixed view on a schedule, not whatever someone remembered to filter that week. Rize links reports to saved dashboards, so the AI analyzes exactly the rows, columns, and filters your ops lead saved — automatically tracked hours underneath, no manual entry.

Yes, when the underlying hours are trustworthy. Rize tracks time automatically by client and project, so the AI report analyzes complete data. Start from the client profitability template, link it to your client dashboard, and each run produces a summary plus insight cards you can chat with.

A spreadsheet export is a snapshot someone has to rebuild and re-read every week. A Rize report is linked to a saved dashboard: the same view runs on a schedule, the AI writes the analysis, and every past run stays on the report's page so you can compare week over week.

Each report's settings show its schedule, format, and linked dashboard. Reports run on demand with Run now or on a cadence — dashboard reports default to weekdays at 8 PM — and each run can cover the dashboard's own rolling range.

Yes. Every report and every individual run has a Chat action. The agent opens with that run's output as context, so 'why did the Acme hours spike' is answered from the same data the analysis used.

Yes. Flat-fee and value-priced firms use the client profitability report to compare hours and margin by client against the fixed fee. Because Rize tracks time automatically, the report reflects real effort — including the clients who pay well but consume the team.

Yes. Every dashboard is exposed through the Rize MCP, so Claude, ChatGPT, or Cursor can read saved views. Reports linked to those dashboards run on the same data.

Reports run for the scope you set — yourself, a team, or the whole workspace. Dashboards start private and can be opened to team admins or workspace admins from the visibility chip, so the analysis follows the same sharing boundary as the data.

No. Rize tracks application metadata — which app is in the foreground and for how long — with no screenshots and no keystroke logging. Reports analyze hours by client, project, and member, not activity surveillance.