Most MSPs underestimate what Autotask can do for reporting. They set up a dashboard when they first go live, populate it with a few standard widgets, and leave it there. The dashboard becomes wallpaper — always visible, rarely acted on, never updated to reflect how the business has changed.
The problem isn't the platform. It's the mental model. Autotask's reporting layer has two distinct tools — Dashboards and Widgets on one side, LiveReports on the other — and they serve fundamentally different purposes. Understanding when to use each, and how to use each well, is the difference between a reporting setup that tells you what happened and one that helps you run your business.
Most MSPs think of dashboards as static displays. You build them once, they show some numbers, and you glance at them occasionally. This is the least interesting way to use them.
The more powerful mental model is to treat widgets and dashboards as tools for rapid analysis and investigation — not just passive display. Because a widget can be built in under 30 seconds, you can create one for a specific question, get the answer, and discard it. Need to quickly see all open P1 tickets raised in the last 48 hours that haven't had an update? Build the widget, look at it, move on. The speed of construction is the point.
The primary function of a well-designed dashboard is to give each person in your MSP the data they need to do their job — updated in real time, without requiring them to run a report or ask someone else.
The key insight is that different roles need fundamentally different views. A sales manager doesn't need to see ticket queues — they need to see opportunities in the pipeline closing this quarter, revenue at risk, and account renewal dates. A service desk engineer doesn't need to see pipeline data — they need to see their assigned tickets, segmented by status, age, priority, and SLA proximity. A managing director needs neither of those in granular form — they need a high-level operational snapshot: SLA compliance rate, open ticket volume trend, billable hours this week against target.
Autotask allows each user to build and save their own dashboard configuration. The practical implication is that a well-designed dashboard rollout doesn't mean one dashboard for everyone — it means a defined set of dashboard templates for each role, deployed when a new team member is onboarded, and updated when the role's information needs change.
A widget that nobody looks at is worse than no widget — it trains your team to ignore the dashboard entirely. The widgets that get used consistently share three characteristics: they show information the viewer is responsible for acting on, they update without manual intervention, and they surface exceptions rather than confirming that everything is normal.
The last point is the most important. A widget showing "47 open tickets" tells you nothing actionable. A widget filtered to show tickets that are open, assigned to your team, with no update in the last 4 hours, and within 1 hour of SLA breach — that's a widget someone will check every time they sit down. Design widgets around the question "what do I need to act on right now?" rather than "what is the current state of everything?"
Beyond the daily dashboard, widgets have a second use that most MSPs never discover: rapid ad-hoc analysis. Because the construction time is so low, you can build a widget to answer a specific operational question, read the result, and delete it — or keep it temporarily on a side dashboard while you're investigating a pattern.
An engineer notices that a specific client's tickets are taking longer than usual to resolve. Instead of running a report, they build a quick widget filtered to that client, grouped by issue type and sorted by age. They have the answer in 90 seconds. This kind of lightweight, disposable analytics is what makes widgets genuinely useful as an investigative tool — not just a display mechanism.
Widgets are built for immediate visual impact. When you need calculations, formulas, complex tabular data, or a structured document that can be shared, scheduled, or used as the basis for business decisions — that's when you reach for LiveReports.
LiveReports is Autotask's built-in report builder, and it occupies a different tier of capability from the widget engine. Its interface will feel familiar to anyone who has used Crystal Reports or Excel for structured reporting — columns, rows, groupings, formulas, filters, and formatting controls that give you genuine flexibility over the output.
Formulas and calculated fields. LiveReports allows you to build calculated columns — percentage of SLA breaches, average resolution time by engineer, revenue per client per month, billable hours as a percentage of total hours logged. These are the metrics that actually tell you how your business is performing, and they require calculation logic that widgets can't provide.
Advanced filtering. LiveReports filters go beyond the basic field-value matching available in widgets. You can filter on calculated values, apply date ranges that adjust dynamically relative to when the report is run, combine multiple conditions with AND/OR logic, and exclude specific values. For reports that need to be run repeatedly against different time periods, dynamic date filters are particularly valuable — the report always shows the last 30 days, or the current month, without manual adjustment.
Conditional formatting. Colour-coded output based on field values makes structured reports significantly easier to read at volume. SLA compliance below threshold flagged in red, revenue above target highlighted in green, tickets overdue for more than 48 hours bolded — conditional formatting turns a data table into a decision-support document.
On-demand execution and publication. A LiveReport can be run manually at any time, published to other Autotask users so they can run it themselves, or scheduled for automatic delivery.
Scheduled delivery with dynamic filters. This is one of LiveReports' most underused capabilities. A report configured with dynamic date filters — "last 7 days", "current month", "previous quarter" — can be scheduled to run automatically and delivered to a defined list of recipients at a defined frequency. A weekly SLA compliance summary sent to your management team every Monday morning, a monthly billing reconciliation sent to your finance team on the first of the month — these are set up once and run without manual intervention indefinitely.
The same principle that applies to widgets applies to LiveReports: a report that nobody acts on is a wasted configuration. Before building a report, define the decision it supports. Who receives it, what action should it prompt, and how will they know when action is required?
Reports built without a clear recipient and a clear decision in mind tend to be over-engineered — too many columns, too much data, not enough signal. Start with the minimum data set that answers the question, add formatting that makes the answer obvious, and resist the temptation to include every available field because it might be useful. A concise, well-formatted report that gets read and acted on every time beats a comprehensive one that gets archived unread.
Dashboards and LiveReports are not competing tools — they're complementary layers of a complete reporting architecture.
Dashboards and Widgets handle the real-time, role-specific visibility that keeps your operation running day-to-day. They answer the question "what do I need to know right now?" They're fast to build, easy to personalise, and effective when designed around the actions they should prompt.
LiveReports handle the structured, periodic analysis that supports business decisions. They answer the question "how are we performing and what does it mean?" They take longer to build correctly, but once built, they run automatically and deliver consistent insight without ongoing effort.
The MSPs that get the most out of Autotask reporting are the ones who invest in both layers deliberately — designing dashboards for each role, building LiveReports for each recurring decision, and treating the reporting layer as a core part of their operational infrastructure rather than an afterthought.
A reporting architecture that actually gets used — dashboards your team checks daily, LiveReports that run automatically and surface what matters — is part of every Autotask implementation we do at Kinesys.
kinesys.it • info@kinesys.it • HaloPSA Official Partner & Autotask Experts