Reports: every report on one date range

Reports is one page. Every report you can open sits in the left rail, grouped Delivery, Team, Finance, Service and Sales, and all of them read the one date range at the top of the page.

Sales reports used to be a second page in the navigation with a date control of its own. It is now the Sales category in this rail, and a link you saved to it lands on the matching report here. Links to the old delivery lenses land the same way, and an old range value carried in one of those links resolves to the nearest window on the new control.

The rail is the grouped navigation Settings and Integrations already use. A category is drawn only when you can open at least one report inside it, so it never offers you an empty page. With no report named in the address, Reports opens on Portfolio overview, or on Pipeline & forecast for someone in sales who does not have the delivery reports.

One control above the report sets the window for every number in it: This month, Last month, This quarter, Last quarter, Year to date, Last 30 days, Last 90 days, Trailing 12 months, All time, or a custom start and end day. A first visit opens on This month, and after that Reports remembers the range you last used. The range travels in the page address too, so a link you paste to a colleague opens on the window you were reading. While the numbers are being read again for a new range, the control shows Updating beside it.

All time starts on your workspace's first day of data and runs to today. That first day is the earliest of the oldest ticket and ticket time your PSA has sent Current, the oldest time entry, the oldest project milestone, the oldest opportunity and activity (for someone with CRM access), the oldest agreement start date (for someone who can see recurring revenue), the oldest survey answer, and the day the workspace was created. PSA history Current synced from before your workspace existed is therefore inside All time. If Current cannot read that first day, the range is labelled Through and today's date rather than with a start date nobody chose.

A custom range can be up to 3 years long. The calendar will not apply a longer pair and says why: a custom range can be up to 3 years, and All time is the choice for everything. A link that carries a longer custom range opens on the last 3 years of it, and the control says so with Longer than 3 years, so the last 3 years are shown. A range picked in the wrong order is read in order, and an end day after today is read as today.

Every window is cut in your workspace's time zone: today, this week, this month, this quarter. There is one zone for the whole workspace rather than one per person, so a report means the same thing to everyone who opens it. A tenant admin sets it in Settings › General › Region and words, and it starts on the zone Current already used for notification timing and the lead response clock, so there is usually nothing to set. The printed header names that calendar under the date the report was generated, so a report you hand to a partner says which midnights its windows were cut on.

Money reads in your workspace currency, set in the same place, and is never converted. A figure your PSA holds as 12,400 is shown as 12,400 with your currency's symbol and separators on it, and a money column you export carries the three-letter code in its header.

The Compare switch sits beside the range and starts on. With it on, every number that covers a stretch of time carries the change against the period before it, and the chip names the period it measured against. What counts as the period before follows the range you picked.

• This month, This quarter and Year to date compare against the same days one month, one quarter or one year earlier. On 6 September that is 1 to 6 September against 1 to 6 August, not against the whole of August.
• Last month and Last quarter compare against the month or the quarter before them, whole against whole.
• Last 30 days, Last 90 days and a custom range compare against the same number of days, ending the day before your range starts.
• Trailing 12 months compares against the twelve months before it.
• All time has no period before it, so it carries no change figures at all. Where the Compare switch would sit, the control reads No earlier period to compare with.

A change figure is also left off when a report reads a shorter stretch than the range you picked (see "Long ranges" below). The two windows would no longer be the same length, so an arrow between them would compare different things. It is also left off when the period before starts before your data does, for example before your first synced ticket or survey answer, because that period would read as empty. A note under the figure says so.

• Over more than about a year, such as All time or a long custom range, a chart that draws one point a week draws one point a month instead, and its title says by month.
• Service desk reads the whole range when it can count the tickets in time. When a range holds too many tickets, or takes too long to count, the ticket numbers cover the last 370 days instead, and a note under the report names those days and says to pick a range of 370 days or less to see any other stretch. Survey answers and ticket signals read any range.
• Forecast accuracy follows the range: it covers the forecast snapshot weeks that start inside it. Current keeps 52 weeks of snapshots, so for a longer range the report names the day its weeks start from and says earlier weeks are not counted.
• Stage velocity, on Pipeline & forecast, covers every recorded stage change and is not narrowed by the date range. The chart and its note say so, so it is never read as a figure for the range above it.

• Utilization, on Capacity, measures hours logged and capacity over exactly the same days. Capacity stops at today, so a custom range that ends in the future is not counted as empty days of capacity. A person with no capacity set for the range is left out of the average and reads no capacity set for this window, rather than being averaged in at 0%.
• First-time appointments, on Book & activity, are counted on your workspace's own day. A meeting late in the evening on the last day of a month belongs to that month.
• Avg days to close, on Pipeline & forecast, averages only the wins with a created date before their close. The line under it says how many wins it left out, so an imported opportunity with a missing or later created date never pulls the average.

• Delivery. Portfolio overview: every active project at a glance, with health, hours, budget and open risk. If you are not a project manager or admin, the hours tile is labelled Your hours logged, because you can only see your own time entries, while the budget tiles always count the whole portfolio. Progress & milestones: on-time delivery, task throughput and the milestones ahead. Risk: AI-flagged risks and the logged risk register, by severity and by project.
• Team. Effort: hours logged over the period, by project and by person, with the billable mix. Capacity: who is over and under capacity, and where the open work sits.
• Finance. Budget: budgeted against actual hours and spend, project by project. Profitability: revenue, cost and margin per project from logged hours and cost rates.
• Service. Service desk: tickets opened and closed, response and resolution times, and where the load lands. Its figures come from the same definition your dashboards read rather than a second count of the same tickets, so the two cannot disagree.
• Sales. Pipeline & forecast: open pipeline by stage and owner, the weighted forecast, win rate and velocity. Forecast accuracy: past commit and best-case forecasts against what actually closed. Opportunities by type: new logo, expansion, renewal and project opportunities, open, won and lost in the period. MRR movement & churn: your recurring revenue from the agreements, who left, who shrank and who grew and what changed inside each customer, retention for the board, who is about to leave, and churn reasons (see "MRR movement and churn"). AE scorecard: pipeline, wins, activity and goal pace per account executive. Whitespace coverage: which offerings each account holds, and the biggest gaps. Book & activity: first appointments, headcount trend, revenue motions and the book at a glance.

Reports that break numbers down by company, such as Profitability, Whitespace coverage and Book & activity, offer a switch named "By" and your workspace's word for its customers ("By client", for example) once you can see a customer group. With it on, each group's sites become one row: counts, money and hours are added up, percentages and averages are worked out again from the totals rather than averaged, and a health score takes the worst site's. A scheduled report can be sent the same way, and each recipient's PDF uses only the groups that recipient can see. See "Customer groups: one customer with several sites".

A report you cannot open is not in your rail, so two people on the same team can open Reports and see different lists. The rail is the courtesy; the wall is underneath it. Every row a report reads comes back through your own database permissions, which is what stops a report you cannot see from being reachable by editing the address.

Three kinds of time entry sit on the Time page as real rows without being delivered work, and none of them counts in these reports: time a manager rejected, time your PSA voided or deleted during pre-invoice review, which nobody was ever billed for, and time a manager wrote off as unbillable. Rejected and voided time stopped counting on 26 July 2026, so Effort, Capacity, Budget and Profitability read lower than they did before that date, and the change is a correction rather than lost work.

• Effort and Capacity show fewer hours per person and per project.
• Budget shows less burn, so the burn-rate trend flattens slightly and the count of projects over budget can fall. A project that was only over budget because of voided or rejected hours stops being named, which is the point.
• Profitability moves on both sides, and not always the same way. On a project with a billable rate, revenue and cost both come from hours, so they fall together and the margin percentage shifts only a little. On a project with no billable rate, revenue is the budget amount and does not move at all, so dropping the voided and rejected cost makes that project's margin read higher than it did. The revenue basis is shown on the row, so you can tell which kind you are looking at.
• Export CSV moves with the reports, since its hours and budget-used figures are the same numbers. A spreadsheet you exported before 26 July will not match one you export now.

Export PDF prints the report you are looking at. The letterhead carries your workspace's own name rather than Current's, because the page you hand a partner should be yours, and under it sits the report name, the scope you filtered to, the period, the period it is compared against, the day it was generated and the calendar those windows were cut on. Tables print every row instead of stopping at the edge of the screen, and a card is never split across a page break.

Export CSV writes the same report as rows: the period and the comparison period, the scope, every key figure with its previous value, and every table on the page. A money column names its currency in the header, as in "Open value (GBP)", and the cell itself stays a plain number so a spreadsheet can add it up.

Schedules, at the top of the page, sends reports to an inbox on a repeat. One schedule holds up to eight reports and arrives as a single email with one PDF attached: a cover page, then a section per report.

You pick weekly on a weekday, or monthly on a day of the month or its last day, and an hour, which is read in your workspace time zone. Then the period the email describes: the previous full week or the previous full month, which is the default, or the last 30 days, the last 90 days, this quarter to date, this year to date, or All time. Comparison is on by default, so the email carries the same change figures the page does.

Every period in a scheduled email is made of whole days and ends on the day before it is sent. An email that arrives at 7 in the morning does not count those few hours of the send day against a full day in the period before. So the last 30 days and the last 90 days are the 30 or 90 days up to yesterday, compared with the same number of days before them, and quarter to date and year to date run to yesterday as well. An email sent on the first day of a quarter reports the quarter that just closed, compared with the quarter before it, and one sent on 1 January reports the year that just closed, compared with the year before.

All time covers your workspace's first day of data to the day before the email is sent. It has no period before it, so the comparison switch turns off for it and the email carries no change figures.

Anyone except a partner can set up a schedule for their own inbox, from the reports they can open. A tenant admin can also send it to other members of the workspace and to up to ten addresses outside it. Send a test now runs the whole thing once and delivers it to your own address, so you can read the real email before anyone else does. A schedule can be paused and resumed, and deleting one asks first.

If Current cannot read one of the systems behind a section, the section says so in a sentence instead of drawing a zero. A zero and a failed read look the same on a chart and mean opposite things, so a broken read never becomes a number: you get a line naming what could not be read and whether it is worth trying again, and the rest of the report still renders. The same rule follows the report into the PDF and into a scheduled email: the email still arrives, carrying the sentence where the figures would have been, and the run is logged as partial.

Reports is a staff surface. Partners never see the row in their navigation, and a partner who reaches the address gets a note pointing them back to their portal rather than a stripped-down version of the page. See "What partners can see, and what they never can" for the full partner contract.

An account executive without CRM access has no reports to open, so the row is not drawn for them either. Everyone else on staff has at least one.