Reporting Overview

Current V2 web has one read-only reporting area. Open Business > Reports in the left sidebar, or go directly to /reports. It opens a hub that lists every report you can see as a card, grouped into four categories. Selecting a report opens it on its own page, with a persistent row of report tabs across the top so you can jump straight to any other report without going back to the hub first; ← All reports returns to the hub. The native app's separate read-only Analytics workspace is documented below.

Each report requires its own permission — most need View financial reports, two need something else — so the hub and the report tabs only ever show reports a teammate's role can actually query; see Categories and Permissions below.

Filters

The controls at the top of the hub and every report page apply to that page's figures:

• This week, This month, This quarter, and This year presets
• Exact from and to dates for a custom range
• All locations or one location

These carry over automatically when you switch reports with the tabs or return to the hub with ← All reports — moving between reports never resets the range or location you had selected.

Calendar dates are interpreted in the selected location's reporting timezone. With All locations selected, V2 uses the organization's configured default location timezone, then the oldest location, then UTC as a final fallback.

Categories and Permissions

The hub groups its cards into four categories, matching the order the report tabs appear in:

Sales And Growth — revenue, margins, pipeline, and source performance reports that stay close to how work is sold.

• Revenue — booked, collected, and net revenue, plus the month-by-month

trend; see Revenue and Pipeline Reporting

• Pipeline — funnel stages by lead count and value, plus estimate

win-rate performance

• Margins — gross margin by module, client, crew, and service, plus

callback leakage; see Margin Analysis

• Lead Sources — lead, estimate, win-rate, revenue, and modeled

commission results; see Lead Source Performance

• Sales Cycle — stage velocity, close-rate trend, best send day, and

lost reasons; see Sales Cycle Analytics

• Services — top services by sold line count and value; see [Service

Mix Analytics](/analytics/services)

• Geography — revenue, win rate, and expansion opportunities by ZIP

code; see Geography Analytics

Customer Health — retention and at-risk views that help the office react before repeat revenue slips.

• Retention — active, at-risk, dormant, and new clients by health

bucket, lifetime value, open renewal quotes, and overdue balance; see Retention and At-Risk

Operations — crew, jobs, AR, and location rollups that tie field execution back to cash flow.

• Operations — crew productivity and the overdue-invoices queue with

its own Send Reminder action; see Operations Reporting

• Jobs — weekly completed-job throughput and schedule efficiency (fill

rate, on-time rate, a crew comparison table, and reschedule/cancellation reasons); see Schedule Efficiency

• Maintenance Plans — active plan count, annual value, and upcoming

rollovers

• Crew Pay — crew pay by crew, plus retained commission and hourly-pay

totals

• Invoice Aging — accounts receivable aging across V1's five buckets

(Current, 1-30, 31-60, 61-90, 90+ days). This report needs Manage invoices instead of View financial reports.

• Locations — booked, net collected, completed jobs, and win rate by

location, with an org total row; see Franchise Reporting

Specialty — seasonal and workflow-specific analytics that complement the core reporting stack.

• Holiday Lights — shrinkage return count and value, plus seasonal

revenue, close rate, rebooking rate, installs/takedowns, and inventory; see Holiday Lights Analytics

• Automations — runs, sends, exits, and conversions per workflow. This

report needs View automations instead of View financial reports; see Automation Analytics

• Rehash — recovered closes, recovery rate, recovered revenue, and

active stage load; see Rehash Analytics

Every report above needs View financial reports except the two called out inline: Automations (View automations) and Invoice Aging (Manage invoices). A report a teammate's permissions don't allow shows neither a hub card nor a nav tab, and the server denies the query directly if requested anyway.

Current V2 web does not expose the V1 report rail or dedicated analytics tabs; the hub's cards and the persistent report-tab row are its navigation. Every report above can be exported to CSV or Print; see Exporting a Report below. The native app does ship a separate, read-only More > Analytics workspace for owners and managers with View Analytics permission; see the Mobile Fusion Workspace for its seven mobile reports and period filters.

Exporting a Report

A teammate with the Export data permission sees a format select (CSV or Print) and an Export button next to the title of every exportable section on a report page. Getting to the report page itself is still gated on that report's own permission (View financial reports for most, View automations for Automations, Manage invoices for Invoice Aging); Export data is a separate permission on top of that, so a teammate can see the numbers without being able to export them.

A report page built from more than one section on the old combined hub — Revenue, Pipeline, Jobs, and Operations — shows one Export button per section, each exporting only that section's table. Every other report page has a single export.

Export always formats the same already-filtered data the section is already showing, never a fresh query, so the file always matches whatever the range and location filters produced on screen.

• CSV downloads a file named {report_type}_{YYYY-MM-DD}.csv, the date

being the day you exported it, not the report's date range (V1's exact filename pattern). A cell that would open as a spreadsheet formula, once leading spaces or tabs are trimmed off, gets a leading apostrophe so it never executes.

• Print downloads an .html file styled for printing (landscape letter),

not a generated PDF.

Each section's export columns:

The lead-source report has no marketing-spend denominator, so it does not calculate ROI or cost per lead. Its modeled commission applies the current/default source rate to accepted work and is not a payment ledger. Location-comparison Net Collected uses refund event dates; legacy amounts are included only when not already represented in the refund ledger, keeping the total aligned without counting a refund twice.

Message Delivery Is in the Inbox

Message delivery is operational, not financial, and office roles need it even when they cannot view financial reports. From Inbox, open Delivery to review email and text handoff outcomes by date and location.

Email rows include later provider facts such as confirmed delivery, bounce, spam complaint, delay, suppression, open signals, and link clicks. Text rows now include delivery and failure facts when the carrier reports them, though coverage varies by carrier — some report only that a text was sent, never that it reached the handset.

See Automation Analytics (Clean Estimate V1) for the boundary between this current delivery report and the broader V1 workflow analytics that remain unported.

V1 Reporting Baseline

The other articles in this section preserve the richer V1 reporting baseline. When an article or section is labeled Clean Estimate V1, it is a parity specification, not a current V2 navigation instruction. Where V2 already has a smaller equivalent on Reports, the article calls that subset out explicitly.