Part 3 — Run Your Operation · Chapter 23

Reporting & Operational Visibility

BigWave has no separate reporting module you visit on Fridays, and that’s deliberate. The reporting engine is the grid system you’ve used since chapter 3, pointed at data the operating disciplines of chapters 15 through 22 kept truthful. This chapter says what to look at, and where, for each question a service company actually asks.

The engine: views and exports

Any question of the form “which records, with which columns, filtered how” is a chapter 3 view, and any view exports to a spreadsheet. Custom fields ride along as columns, so every field you defined in chapter 10 is reportable the moment it exists. Before hunting for a report, ask whether it’s a view you haven’t built yet. It usually is.

The recurring ones worth institutionalizing as shared views: the ready-to-invoice queue (chapter 19), per-status dispatch boards (chapter 15), a quotes-outstanding list (chapter 18), and an expiring-certifications view on technicians and partners (chapters 6 and 21).

The project Reporting screen

Each project carries a Reporting screen bundling the operational reports for that line of work:

  • Scheduled Events and Missed Schedule Dates. What’s coming and what slipped. Chapter 16.
  • Scheduled Reminder Report. Reminder state per upcoming visit, present when the project uses reminder alerts. Chapter 13.
  • Waiting For Confirmation and Rejected. Assignment confirmation state, the partner-dispatch safety net. Chapters 16 and 21.
  • Deliverables. Required paperwork across every work order, complete against owed. Chapter 12.
  • Document Uploads. What has landed, when, from whom. The field-discipline mirror. Chapter 17.
  • Technicians Used. Who has worked this project.
  • Timecards. The check-in and check-out record. Chapter 17.
  • Supplier Orders. Open purchasing across the project. Chapter 21.
  • Issues Summary and Issues Details. The punch list. Chapter 22.

Alongside Reporting sit the two count-based screens, Site Tracking for pipeline by status and Tag Report for counts by tag, both from chapter 22 and both clickable through to their lists.

Report windows

Report Windows, global in Setup or per project, define named recurring periods such as the contract month or the fiscal quarter, so recurring reporting slices time consistently instead of by whoever remembered the dates. Set them up when a customer or a contract expects numbers per period and the period isn’t the calendar month.

Deliverables as client-facing reporting

For commercial customers, the deliverables system doubles as the client report. Harbor Grill never asks for a dashboard. They ask which sites are done and where the paperwork is. Site Tracking answers the first in the portal, the completed deliverables are the second, and the close-out package per site is the Documents panel in chapter 12’s folders. Beacon’s contract reporting obligation costs about zero marginal effort, which is what happens when the operating system and the reporting system are the same system.

Residential (the Okafors): nobody reports to a homeowner. The residential reporting story is internal. Marcus’s monthly look at the Job Source field, chapter 10 promised he reads it and this is where, plus volume by status and revenue through the accounting export.

Audit trails

Every major record carries an Audit Trail panel: work orders, customers, sites, projects, technicians, partners, assets, and company setup itself. Who changed what, when, including changes made by automation such as imports, the asset engine and emailed approvals, which are attributed to the system rather than to a person. The audit trail isn’t a compliance decoration. It’s the operational answer to “who moved this to Invoiced” and “when did the address change”, and reaching for it should be reflexive.

The Accounting rollup

The Accounting screen’s Invoices / Payments report, chapter 19, is the cross-project money view, and the accounting export carries the detail into your ledger, where financial reporting proper lives. BigWave’s job ends at handing the ledger clean, coded lines.

Part 3 ends here. You’re running: work orders flowing, dispatch on the calendar, field data arriving, money invoiced, contracts renewing themselves, every question answerable from a screen. Part 4 is the reference shelf for the details this narrative compressed.