Performance Reports & Schedules

Each report assembles the location's recent reality from the same sources the dashboard reads live: review volume and rating movement, ranking position shifts from scan history, post publishing activity, and call, direction, and click performance from snapshots. Topping the assembly sits an AI-written executive summary that narrates the period in plain language — what improved, what slipped, and what deserves attention — regenerable on demand when the first draft misses the emphasis.

The composition answers the three questions every stakeholder asks in order: are we winning, where exactly, and what next. Numbers carry the first two; the summary carries the third by translating metric movement into recommended focus. A report that only archives data is a filing cabinet; the summary turns it into counsel, which is what retains clients and budgets.

Generating a report is deliberately trivial: pick the location scope — one site or the workspace view — and trigger generation. The system compiles current data, writes the summary, and lands you on the finished report's detail view, often via direct navigation to the new document. No report builder with forty checkboxes stands between the impulse and the artifact, because friction at generation time is what turns monthly reporting into quarterly reporting into never.

The report list filters by business location, so multi-site operators move from empire view to single-store diagnosis in one selection. Every past report remains openable in full detail, which makes the archive a longitudinal record of each site: open this March beside last March and the year tells its own story without additional analysis.

Recurring schedules convert reporting from a task into infrastructure. Configure the cadence and recipients per workspace, and fresh reports arrive on rhythm without anyone remembering — the reliability clients interpret as professionalism and bosses interpret as control. Automation handles the remembering; humans keep handling the reading and the deciding.

The test send exists because untested automation is how embarrassing emails happen. Before any schedule goes live, fire a test delivery to your own inbox and inspect it like a recipient: subject line, numbers, summary tone, link behavior on a phone. Only then activate the real recipients. Schedules you would not preview are schedules you should not run — the button removes every excuse.

Reports are designed as clean, client-shareable detail views reached by link — readable on any device, focused on the location's story, suitable for forwarding. Dedicated white-label branding with agency logos and custom domains, and one-click PDF export, are not part of the current release. This page states that plainly because buying on an imagined feature poisons otherwise good relationships; the shareable report link is the deliverable, and it is a strong one.

The same honesty applies to data boundaries: reports compile what the workspace knows — reviews, scans, posts, snapshots accumulated since connection — and cannot retroactively manufacture history predating it. New clients get baselines and forward measurement, not rewritten pasts. Set that expectation in the first report's cover note and it never becomes an objection later.

Agencies live or die on demonstrated value between sign-up and results, and consistent reporting is the bridge across that gap. Twelve monthly reports showing baselines, actions taken, and early movements hold a client's confidence through the quarters before rankings fully compound. Silence, by contrast, lets imagination fill the void — and imagination bills against you.

Internal teams use the same cadence for resourcing arguments: snapshot trends plus report narratives convert marketing activity into budget language leadership understands. The business that documents its local SEO operation monthly funds it annually; the business that cannot show its work relearns the same lesson every budget cycle.

Reports reach full power when read as the narrative layer over the platform's evidence: heatmaps for visibility proof, review inboxes for reputation proof, snapshots for conversion proof. A quarterly business review that opens with the grid turning green, moves through review velocity doubling, and lands on direction requests climbing tells one coherent compounding story instead of four disconnected metrics. Assemble the exhibits deliberately — the report is the spine, the other features are the illustrations.

Sequence the exhibits for the audience's attention curve: lead with the outcome they feel (calls, visits, revenue-adjacent actions), support with the visibility that caused it (grids, rankings), and close with the work that sustains it (reviews answered, posts published). Attention peaks early and fades fast; front-loading outcomes respects that biology while the appendix carries methodology for the analytically curious.

Cross-reference explicitly rather than hoping audiences connect dots. This grid improvement followed the category correction documented in March; this call lift tracks the review-response push completed in May; this direction-request plateau coincides with the posting gap in July. Causal sentences, hedged honestly, transform parallel charts into a story of managed cause and effect — which is precisely what decision-makers fund.

Build the quarterly review as a repeatable ceremony with a fixed template: outcomes versus last quarter and versus last year, the three exhibits with causal narration, the three decisions for next quarter with owners and dates. Repetition of format focuses attention on content; novelty of format distracts from it. After four quarters the ceremony runs itself, and the business owns something rare — a documented, compounding, locally growing operation with the paper trail to prove every step.