How current is the ServiceTitan data in my dashboard, really?
Later than most people assume, and the lag is mostly human rather than technical. Sync interval adds minutes. Technician paperwork and invoicing add hours or a day. That means today's revenue is always understated until the work catches up. Every dashboard should display the timestamp of its last successful sync and be read with the paperwork delay in mind before anyone concludes the day was slow.
Three separate delays stacked on each other
The technical delay is the sync interval, and it is usually the smallest one. The operational delay is how long after work is completed the invoice actually gets posted, which depends on technicians, office staff and how busy the day was. The definitional delay is which timestamp your report uses — completion, invoice date, or payment date — because they can be days apart on the same job.
Added together, a same-day revenue figure is a partial count of a process still in motion, not a measurement of the day.
The predictable shape of intraday revenue
Because paperwork lands unevenly, today's revenue curve has a characteristic shape: low all morning, climbing through the afternoon, and jumping in the evening as tickets close out. Comparing today at two in the afternoon against yesterday's final total is comparing an incomplete number to a complete one.
The right comparison is same-time-of-day against the same weekday, or a completeness-adjusted estimate that accounts for how much of the day usually posts by that hour. Anything else generates a panicked message to the marketing manager about a problem that does not exist.
You can build that adjustment from your own history in an afternoon. Take several weeks of invoice timestamps, work out what share of a day's final total had posted by each hour, and use that curve to project the current day. It will not be exact, and it is enormously better than reading a partial number as if it were finished.
What a trustworthy dashboard displays
- Last successful sync time, per source, in plain language rather than buried in a tooltip.
- An explicit data cut-off for the reporting period, so people know what is and is not included.
- A stale-data warning when a sync has not completed in longer than its normal interval. A dashboard that silently serves yesterday's numbers is worse than one that is visibly down.
- Which date field drives the report, because completed-date revenue and invoiced-date revenue will not agree and both are correct.
Match freshness to the decision
Not everything needs to be current. Monthly marketing allocation is fine on data a day old. Dispatching a follow-up to a caller who did not book is worthless if it arrives tomorrow. Deciding required freshness per use case keeps you from paying for real-time infrastructure to feed a report someone reads on Mondays.
That distinction is where a morning briefing and a live alert differ in kind, not just in schedule. See daily intelligence briefs for the first and operational AI for the second.
Topics: data freshness · dashboards · sync · reporting
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.