Should I slice reporting by business unit, job type or tags?
Business unit for anything financial, because it is the dimension that maps to how the company is managed and it is enforced on every job. Job type for operational and marketing analysis, because it describes the work. Tags for temporary or exploratory questions only, because tags are optional, multi-valued and applied inconsistently. Never build a permanent financial report on a field that a dispatcher can forget to set.
Rank dimensions by how hard they are to leave blank
The reliability of a reporting dimension is mostly a function of whether the system forces someone to fill it in. Business unit is typically required and inherited, so it is close to complete. Job type is required at creation but chosen from a list that grows without governance, so it is complete but noisy. Tags are optional, so they are neither.
That ordering should drive what you build on. A dimension that is ninety percent populated is not ninety percent useful in a financial report; it is a report with an unexplained bucket that someone will use to discredit the whole thing.
The job type sprawl problem
Job type lists grow because creating a new one is easy and nobody deletes the old ones. Within a few years you have near-duplicates that mean the same thing, seasonal types nobody retired, and types created for a single promotion. Reporting by raw job type then produces a long tail that hides the pattern.
The fix is a mapping layer: group raw job types into a small set of reporting categories that the business actually manages by, maintained outside the operational system so cleanup does not require a change to daily workflow. Ten to fifteen categories usually covers a trade well.
What tags are genuinely good for
- Time-boxed experiments. Marking jobs from a specific promotion for one season.
- Cross-cutting attributes. Something true of a job that does not fit the type hierarchy, like a specific equipment brand.
- Manual flagging by managers. Escalations, disputes, follow-up required.
- Never as the sole key for revenue reporting, because a job with two tags will be double counted in any naive sum.
A composite that works
In practice a good reporting model uses business unit as the financial spine, a curated job category derived from job type as the operational dimension, and a separate revenue class for anything that has no field job behind it. Tags ride along as filters. That structure survives reorganizations, because business units change slowly and job categories are yours to control.
Getting that model right up front is most of the work in a ServiceTitan integration, and it is what lets revenue reporting answer new questions without a rebuild.
Topics: dimensions · reporting · job types · taxonomy
Have a version of this question about your own business?
The useful answer usually depends on which systems you run and how they're connected. That's a conversation, not a blog post.