TeamsPricingBook Demo
Guides/AI Agent & Reports

AI Reports in Rize

Build a Rize report from a template or a prompt, scope it to yourself, a team, or the workspace, and have finished runs delivered by email, Slack, or in-app notification.

Open Rize and build your first report.

Open in RizeDownload

What an AI Report Is

An AI report in Rize is a saved question about tracked time that runs on a schedule. It stores whose data it covers, what period, which sections, and who receives it, then adds an AI read on top of the numbers.

Reports live under Insights > Reports. The page holds your saved reports plus Recent runs, every finished run ordered newest first.

Template or AI Generated

Rize offers two layouts, and the choice decides how much latitude the AI gets.

| | Template | AI Generated | |---|---|---| | You configure | The sections to include | A plain-language prompt | | A run looks like | Your chosen sections, rendered from live data, with an optional AI summary and insight cards on top | A written report the AI composes from your data | | Best for | Numbers you want in the same place every week | An open question, or a narrative for someone else to read | | PDF export | Not available | Available once the run is ready |

Pick Template when you want consistency. AI Generated hands the model full control over the report's shape, which is right for an exploratory question and wrong for a figure a client sees every Friday.

A Template report can still be part AI. Adding the AI Summary and AI Analysis sections puts a short overview and prompt-driven insight cards above the data.

Building a Report

  1. Open Insights > Reports and create a new report.
  2. Pick a template from the Personal or Team gallery, or choose Start from scratch.
  3. Choose the layout: Template or AI Generated.
  4. Set the scope: Just Me, Team, or Workspace.
  5. Set the cadence, send time, and the period each run covers.
  6. Choose delivery: email, Slack, in-app notification, or any combination.

A template prefills all of it. Everything stays editable after you pick one.

Scope Decides What the Report Can See

Scope is about ownership, not filtering. Clients, projects, tasks, and labels are filters you apply on top of a scope, not scopes of their own.

  • Just Me covers your own tracked time and defaults to owner-only visibility.
  • Team covers one team's members and defaults to team-member visibility.
  • Workspace covers every team and defaults to admin visibility.

Scope also decides which sections are available. Work Hours, Focus, and Apps & Websites cover personal activity, so they appear on individual reports only. Members and Teams appear on team and workspace reports. Client Profitability is workspace scope, since it is built from workspace-wide contracts.

Schedules and Periods

Cadence is On-demand, Daily, Weekly, or Monthly, and each one fixes the period a run covers.

  • On-demand runs when you click Run now. You choose the period: today so far, the last 1 to 30 days, or a custom date range.
  • Daily runs cover today so far.
  • Weekly runs cover the previous week. The window is configurable: full week, work week, Monday to Saturday, or a custom start and end day.
  • Monthly runs cover the previous calendar month, sent on the day you choose including the last day of the month.

Scheduled runs cover complete periods. A weekly report sent Friday afternoon reports on the week that just closed, not a partial one.

Delivery

Finished runs go out by email, Slack, in-app notification, or any combination of the three. Email adds a recipients picker: the creator, team admins, the whole team, workspace admins, everyone in the workspace, or specific addresses including people outside Rize.

Email links to the hosted run rather than attaching a file, so a recipient who opens it next week sees the current version.

Reading a Run

A run moves through pending, running, then ready or failed. Reports show a New badge for an unread run and Failed when the last one errored.

Once a run is ready you can:

  • Chat with it, which opens the agent already holding the run's period, scope, and filters.
  • Export PDF on AI Generated runs, once the analysis has finished.
  • Rate it thumbs up or down, with optional free text on a thumbs down.
  • Send it to specific addresses as a one-off, without touching the recurring recipients.

Names inside a run are pills, the same as in chat. Hover a project, client, or member for details, click to open it.

Pulling Runs Into Other Tools

Finished runs are readable outside Rize. The Rize MCP server exposes list_report_runs and get_report_run, and the public GraphQL API exposes reportRuns and reportRun.

That makes a report a building block rather than an endpoint. A scheduled report does the analysis on Rize's side, and another agent reads the finished run instead of re-querying months of raw entries. Useful for feeding a weekly summary into a client update, or asking what changed across the last six monthly reviews.

Tips

  • Start with a template. The prompts that ship with them are specific: they name the sections to cover, the order, and the rule that every claim gets a number.
  • Start structured, then loosen. Run a Template report for a few weeks first. Once you know which numbers you actually read, an AI Generated version has something concrete to aim at.
  • Write prompts that name comparisons. "Compare my deep work this week vs last week, flag any project where meetings exceeded 2 hours" produces a better run than "summarize my week".
  • Rate the bad runs. Thumbs down with a sentence of context is what improves the output.
  • Check tagging first. A report is only as good as the entries behind it. See reviewing time entries.

More in AI Agent & Reports

Using the Rize AI Agent