--- title: "Reports" slug: admin/reports url: https://projectri.com/docs/admin/reports section: admin audience: admin app_route: "/[slug]/admin/reports" mobile: false updated: 2026-09-08 source: Projectri documentation --- # Reports Workspace-wide reporting over a rolling window — budget against spend, effort against capacity, and portfolio health worst first, each exportable as CSV. ![Reports](https://projectri.com/docs-shots/admin-reports.png) ## What it is Three workspace-wide reports over a rolling window: **Financial** (budget against spend, by project and client), **Utilization** (effort logged against capacity declared) and **Executive** (portfolio health, worst first). Each can be downloaded as a CSV generated from the same payload the screen renders. This is a different surface from the member-facing [Reports](/docs/workspace/reports), which is scoped to what its reader may see. These three roll up budget and per-person effort across the whole workspace. ## How to get there **Insight → Reports** in the admin console rail. The gate is the **ADMIN** role, not a permission key — every request is refused for anyone else, and the console itself bounces non-admins anyway. There is no plan gate, and no per-tab permission split: if you can open the console, you can read all three tabs. For money reports with a finer permission model — where revenue is separated from cost, and cost is separated again — use [Financials](/docs/admin/financials). ## How to use it ### Choose the report and the window 1. Pick a tab: **Financial**, **Utilization** or **Executive**. The line under the title tells you what the current tab measures. 2. Pick a window on the right: **30**, **90**, **180** or **365** days. Ninety is the default. A hand-edited query string is clamped to between 7 and 365 days. 3. **CSV** downloads the current tab at the current window. The file is built server-side from the payload the screen drew, so an export can never disagree with the screen it came from — and every money column in it carries its own currency, because a spreadsheet has no page around it to infer one from. ### Financial 1. Five tiles: **Budget** with how many projects are tracked, **Spent** with what remains, **Budget used** as a percentage of tracked budget, **Untracked spend** with how many projects have no budget at all, and **Billable hours** with the share of logged time they represent. 2. The project table gives budget, spent, left and a used meter, banded green under 85%, amber from 85%, red at 100% and over. A project with no budget reads **not tracked** rather than 0%. 3. A project whose own budget is in another currency shows that native figure under its name — the columns are converted so they sum to the tiles, but the number the person who set the budget typed is still a fact worth keeping. 4. A **By client** table appears once there is more than one client. ### Utilization 1. Five tiles: utilisation, billable share, tasks completed, how many people are **over capacity**, and how many logged **no time** at all. 2. Above them sits a strip of three productivity KPIs — productivity, efficiency and delay — each printing its own coverage, because a figure computed from four of two hundred tasks is not wrong but reading it as the team's number is. The day window is mapped onto the nearest finance period for that strip, since those KPIs think in calendar months and this page thinks in rolling days. 3. **Where the hours went** breaks logged time down by activity type. 4. The member table lists capacity, logged, billable, tasks done and a utilisation meter per person, with suspended members dimmed and labelled. ### Executive 1. Four tiles: **Needs attention** (over budget or badly late), **Watch** (one warning sign), **On track** (none) and **Velocity**. 2. Below, one card per project with a coloured edge for its health, the client, member and milestone counts, open, overdue and done task counts, velocity, milestones at risk, a progress bar and a budget meter. 3. The chips at the bottom of a card are the *reasons* for the rating — "38% of open work overdue", "over budget", "82% of budget used", "2 milestones at risk" — so a red project always says why it is red. ## What it affects - **Nothing is written here.** All three tabs are reads, and the CSV is a read. - **Exports leave the product.** A CSV of budget or per-person effort is data the workspace no longer controls; see [Exports](/docs/features/exports). - **It surfaces missing setup.** Untracked spend counts projects with no budget; the FX notes name any currency with no rate. Both are fixed elsewhere — the first on the project, the second on [Finance setup](/docs/admin/finance). ## On mobile This screen is web only. The phone app's **Reports** screen is the member-facing delivery report, not this workspace-wide one, and the finance side of the console is covered by the **Financials** screen instead. ## Limits and gotchas - **Converted figures always name their rate.** When a currency has been converted the note says at what rate; when there is no rate, the note says the budgets in that currency are counted **without conversion**. Health is a ratio and cannot move with a rate, but the Executive tab carries the same note anyway, because its CSV exports converted budget columns. - **Untracked spend is not a rounding error.** Projects with no budget contribute spend and no budget, so the "budget used" percentage is only about the tracked ones. The tile says how many projects are excluded. - **The window is rolling days, not calendar months.** It will not reconcile with a period on the finance reports, and it is not meant to. - Utilisation here divides by declared capacity for the window. The holiday-and-leave-aware version, with targets and burnout, is on [Financials](/docs/admin/financials). ## Related - [Financials](/docs/admin/financials) — margin, WIP, realisation and the finer permission model. - [Reports](/docs/workspace/reports) — the member-facing delivery reports. - [Workload](/docs/admin/workload) — who is loaded with what, right now. - [Exports](/docs/features/exports) — what leaves the product, and in what shape. ## Related - [Financials](https://projectri.com/docs/admin/financials.md): The finance reports — a scorecard, utilisation, project profitability, WIP and ageing, the tax return, and the exceptions list that says what to do on Monday. - [Reports](https://projectri.com/docs/workspace/reports.md): The fixed report page — completion, throughput, burndown, team performance and the effort figures, for this week, this sprint, this month or all time. - [Workload](https://projectri.com/docs/admin/workload.md): Who is carrying what and who has room — open tasks, overdue work and logged hours against each person's weekly capacity, with the capacity and skills editable in place. - [Exports and downloads](https://projectri.com/docs/features/exports.md): What you can take out of Projectri, in which formats, who is allowed to, and what a download deliberately leaves behind.