Saved Report

A saved report is a view a user builds once with chosen filters, range and breakdown, and saves, so they can return to the same analysis each time without rebuilding it.

A saved report is not a time-saver but a consistency tool: when all team members look at one shared saved report, there is no more arguing over 'how did you get that number', because the definition and filters are the same. That advantage is also its risk: a saved report freezes its definition, so if the business logic changes but the report is not updated, the team decides on a stale definition. Its difference from a board is that a saved report is usually one view with set configuration, while a board is a collection of several reports. The common trap is a pile of ownerless, duplicate saved reports that itself becomes confusion; so a saved report needs clear naming and ownership, like any other data asset.