# Reporting, Analytics, and Dashboards

> Chapter 14 of the Courseiva SERVICENOW-CSA curriculum — https://courseiva.com/learn/servicenow-csa/reporting-analytics-and-dashboards

**Official objective:** 4.1 — Create reports, dashboards, and use analytics for data-driven decisions.

## Introduction

Reporting, analytics, and dashboards. If you've ever wanted to know 'what happened, why it happened, and what's happening right now' in a business, this is the answer. For the ServiceNow Certified System Administrator exam, mastering these tools is essential because they turn raw data – like incident tickets or change requests – into clear pictures that help managers make smart decisions, not just guesses.

## The Restaurant Kitchen Dashboard Analogy

Ever wondered how a busy restaurant kitchen knows which dishes are selling out and which ingredients are about to run low, all without the chef screaming at the waitstaff every five minutes?

Here's how it works: In a restaurant, the head chef doesn't just cook. They need a real-time view of the entire operation. The chef has a whiteboard in the kitchen that shows every order that's come in, how long each dish has been waiting, which ingredients are running low, and which dishes are most popular tonight. That whiteboard is their **dashboard** – a single place where all the important numbers and statuses are displayed at a glance.

The individual orders that come in are like **reports**. Each order is a snapshot: 'Table 4: two steaks, one pasta, one salad.' That's a specific piece of information about what's happening right now. The chef doesn't just stare at one order; they look at the patterns. Over the evening, they notice that 80% of customers are ordering the special, and that the dessert stock is gone by 9 PM. This discovery process – spotting trends from lots of individual orders – is **analytics**. It's turning raw data (the orders) into a valuable insight (the special is a hit, order more dessert).

So, the dashboard is the big-picture display, reports are the detailed snapshots, and analytics is the thinking that turns those snapshots into smart decisions. Without these, the kitchen would be chaos – guessing what to cook next, running out of ingredients, and serving slow meals. For ServiceNow, this same idea helps IT teams see exactly what's happening with computer systems, fix problems before they spread, and make data-driven decisions that keep everything running smoothly.

## Core explanation

Reporting, analytics, and dashboards are the three pillars of turning raw data into actionable business intelligence in ServiceNow. Let's break down each one, starting from the ground up.

**What is a Report?**
A **report** is a snapshot of data at a specific moment. Think of it like a photograph. It answers questions like 'How many high-priority incidents were logged last week?' or 'What's the average time it takes to resolve a password reset request?' In ServiceNow, you create reports by choosing a **data source** (like the Incident table, which stores all IT support tickets), selecting what **columns** (fields) to show (like 'Priority', 'Assigned To', 'State'), adding **conditions** to filter only the data you want (for example, only incidents with Priority = 1), and then choosing a **chart type** (bar chart, pie chart, list, line chart, etc.) to visualise the data. Reports are static – they show data as it was when you created the report, unless you refresh it.

**What is Analytics?**
**Analytics** is the process of examining data to uncover patterns, trends, and insights. It's like being a detective. While a report tells you 'how many', analytics tells you 'why' or 'what if'. In ServiceNow, **Performance Analytics** is the main tool. It tracks **metrics** (things you measure, like 'number of incidents') over time and creates **indicators** (the metric plus breakdowns). For example, you might track 'average resolution time' over the last six months and see that it spikes every Monday morning. That insight – a trend – is analytics. It helps you predict future behaviour, like knowing you'll need extra staff on Monday mornings.

**What is a Dashboard?**
A **dashboard** is a collection of reports and analytics charts displayed on a single page. Think of it as a car's dashboard: the speedometer, fuel gauge, and engine light all in one place so you can see the overall health of the car at a glance. In ServiceNow, a dashboard might show six different reports: a pie chart of incident priorities, a bar chart of resolved vs. unresolved incidents, a line chart of incident trends over time, a list of the top 10 oldest open incidents, a gauge showing average response time, and a scorecard showing service level agreement (SLA) compliance. SLAs are contracts that promise a certain level of service, like '90% of critical incidents will be resolved within 4 hours'. A dashboard gives a manager an instant view of whether the team is meeting those promises.

**Why do these exist? What do they replace?**
Before these tools, IT teams might manually compile data from different systems, print spreadsheets, or ask each other 'how are things going?' This was slow, error-prone, and gave a historical view that was often outdated by the time it was shared. Reporting, analytics, and dashboards replace this with a **real-time, centralised, automated** system. Any manager can open ServiceNow and see exactly what's happening right now, drill down into details, and spot problems before they become crises.

**Key concepts you must understand for the exam:**
- **Data source:** The table (like Incident, Problem, Change) that holds the records you want to report on.
- **Conditions:** Filters to narrow down data. For example, 'State is not Closed' or 'Priority is 1 or 2'.
- **Chart types:** Bar (compare categories), Pie (show proportions), Line (show trends over time), List (show individual records), Pivot (cross-tabulate two fields).
- **Group by:** A way to organise data. For example, 'Group by Priority' would show a bar chart with one bar for each priority level.
- **Public vs. Private reports:** Public reports are visible to everyone; private reports are visible only to the creator.
- **Schedule:** Reports can be scheduled to run automatically and email the results to a group.
- **Drill down:** Clicking on a chart segment to see the underlying data. For example, clicking on the 'Priority 1' bar in a bar chart opens a list of all Priority 1 incidents.
- **Dashboard sharing:** Dashboards can be shared with users, groups, or roles, and can be set as the default homepage.

**How does it all fit together?**
You start by creating individual **reports** that give you specific snapshots. Then you take those reports and place them on a **dashboard** to get a big-picture view. Over time, you use **analytics** (like Performance Analytics) to track metrics and see trends. For example, you might create a report showing all open incidents, add it to a dashboard, and then create an indicator that tracks the average time to resolution each week. After a month, you notice the trend is going up, so you investigate and find a new software update is causing delays. You make a change, and the next month the trend goes down. That's data-driven decision-making.

In the exam, you will be tested on how to create reports (choosing the right type, adding conditions, grouping), how to build dashboards (adding reports, laying them out, sharing them), and how Performance Analytics works (indicators, breakdowns, scorecards). You will not need to write code; it's all done through the graphical user interface (GUI). The focus is on knowing which tool to use for which need.

## Real-world context

Meet Jamie, an IT service desk manager at a mid-sized company. Every day, Jamie has to know if the support team is keeping up with incoming requests and meeting their promised service levels (SLAs). Before ServiceNow, Jamie would manually email each team member at the end of the day asking for numbers, then compile a spreadsheet. It took 30 minutes and the data was already a day old.

Now Jamie uses ServiceNow reporting, analytics, and dashboards every day. Here's what a typical morning looks like:

Jamie logs into ServiceNow and opens a customised **dashboard** that is set as the homepage. The dashboard has six widgets:
- Widget 1: A pie chart showing how many incidents are currently in each state (New, In Progress, Resolved, Closed).
- Widget 2: A bar chart showing the number of incidents opened in the last 7 days, grouped by priority (1 Critical, 2 High, 3 Moderate, 4 Low).
- Widget 3: A gauge showing the percentage of incidents that were resolved within the SLA target (e.g., 92%). The gauge is green if above 95%, yellow between 80-95%, and red below 80%.
- Widget 4: A list of the top 5 oldest open incidents that are not yet resolved, with a note for items that are about to breach SLA.
- Widget 5: A line chart showing the average time to resolve incidents over the last 30 days, with a trend line.
- Widget 6: A scorecard from Performance Analytics showing the overall 'Service Desk Health' indicator, which combines several metrics into one score.

Jamie quickly sees that the gauge is yellow (89%), meaning the team is close to but not hitting the SLA target. The line chart shows a slight upward trend in resolution time in the last week. Jamie drills down on the list of oldest open incidents and sees three are high-priority issues related to a recent software update.

Instead of guessing, Jamie now has concrete data. Jamie creates a new **report** called 'High Priority Incidents - Software Update' with a condition filter on incidents where the category is 'Software' and priority is 1 or 2 opened in the last 7 days. This report is added to the shared departmental dashboard so the whole team can see it. Jamie also creates a **schedule** to email this report to the software team lead every morning.

Later that week, Jamie uses **Performance Analytics** to create an indicator tracking 'Time to Resolve' for software-related incidents. After three months, the data shows a pattern: resolution times spike every month when a patch is released. Jamie uses this insight to propose a change in the patch rollout process, reducing future spikes.

In summary, Jamie uses reporting to see the current state, analytics to spot trends over time, and dashboards to bring it all together in one place. This allows Jamie to make data-driven decisions, communicate effectively with the team and management, and continuously improve the service desk's performance. For the CSA exam, you need to understand that this is the core workflow: create individual reports, assemble them into dashboards, and use analytics to look for trends that inform decisions.

## Exam focus

The SNOW-CSA exam will test your ability to know *what* each tool does, *when* to use it, and *how* to configure basic options. You will not be asked to build a complex multi-sourced dashboard from scratch. But you will need to answer questions about the steps, the buttons, and the logic.

**Specific concepts the exam loves to test:**
- **Report types:** You need to know the difference between a List report, Bar chart, Pie chart, Line chart, Pivot table, and Scorecard. The exam will give you a business need (e.g., 'show the proportion of incidents by category') and you must pick the correct chart type (answer: Pie chart).
- **Group by:** This is a frequent trick. 'Group by' organises data into categories. For example, if you group a count of incidents by 'Assignment Group', you get one bar per group. If you don't group, you get one bar total. The exam often asks which option to use to 'show one bar per category'.
- **Conditions (Filters):** You must know how to apply conditions. For example, 'Show only incidents where Priority is 1 and Active is true'. The exam will test whether you add the condition to the report or the dashboard level. Answer: You add conditions to the report itself. Dashboards only display existing reports.
- **Public vs. Private:** The exam loves this. A Public report is visible to all users with the 'report_admin' role or 'report_user' role (depending on exact permissions). A Private report is visible only to the creator. The trick: when sharing a dashboard, if it contains a private report, other users won't see that specific report on the dashboard.
- **Dashboard sharing:** You can share a dashboard with a user, group, or role. You can also set a dashboard as the default homepage for a user. The exam may ask: 'How does a manager ensure their team sees the same dashboard when they log in?' Answer: Share the dashboard with the group or role, and set it as their homepage.
- **Performance Analytics:** You need to know what an 'indicator' is (a metric you track over time), a 'breakdown' (how you slice that metric, e.g., by department), and a 'scorecard' (a combination of indicators shown in a visual like a traffic light). The exam will not ask you to create a script for an indicator but will ask what tool to use for 'trending data over time'.
- **Schedule reports:** Know that reports can be scheduled to run automatically and emailed. The exam may ask: 'How do you send a weekly summary of open incidents to a manager every Monday?' Answer: Create a report, then schedule it with a condition and email recipients.
- **Drill down:** This is a key feature. The exam may describe a scenario where a manager clicks on a segment of a pie chart and sees a list of underlying records. The correct term is 'drill down'.

**Traps to watch for:**
- The exam will mix up 'report' and 'dashboard'. Remember: a report is a single data view; a dashboard is a collection of reports.
- They might claim that you cannot edit a report from within a dashboard. Actually, you can click a report on a dashboard and then click 'Edit Report'.
- They might confuse 'group by' with 'sum'. 'Group by' organises rows; 'sum' adds up numbers. For example, grouping by category does not automatically sum anything – you need to set the aggregation (count, sum, average).
- They might say 'a dashboard automatically refreshes every 5 minutes'. This is false. Dashboards do not auto-refresh unless configured with a dashboard-level auto-refresh setting (usually in the dashboard properties).

**Key definitions to memorise:**
- Report: A single view of data (list, chart, etc.).
- Dashboard: A page showing multiple reports.
- Performance Analytics: A module for tracking indicators over time.
- Indicator: A specific measurement (e.g., number of incidents resolved).
- Breakdown: A way to split an indicator (e.g., by department, region).
- Scorecard: A visual summary of indicators with thresholds (green/yellow/red).
- Public report: Visible to others with reporting roles.
- Private report: Visible only to you.
- Scheduled report: A report that runs automatically and sends results via email.

In your exam, expect to see questions that give you a business scenario and ask you to pick the correct approach. For example: 'A manager needs to see the number of incidents by category for the last month, and they want to update this data every Monday morning. What should they do?' The answer: Create a report (bar chart grouped by category with a condition for last month's data), then schedule the report to email the chart every Monday.

## Step by step

1. **Define your reporting need** — Decide what data you need to see. For example, 'I need to see how many high-priority incidents are open this week.' This determines the data source (Incident table), conditions (Priority = 1 or 2, Active = true), and chart type (bar chart grouped by priority).
2. **Create the report** — Navigate to the Reports module, click 'Create New', select the data source (table), choose a report type (List, Bar, Pie, etc.), add conditions to filter records, and choose grouping if needed. Then click 'Run' to preview and 'Save' with a meaningful name like 'Open High Priority Incidents - Weekly'.
3. **Build a dashboard** — Go to the Dashboards module, click 'New Dashboard', give it a name (e.g., 'Service Desk Operations'), and select a layout (e.g., two columns). Then click 'Add Report' and select the report you created. You can add multiple reports and rearrange them by dragging.
4. **Configure report options** — After adding a report to a dashboard, you can click on the report and adjust its display options, like changing chart colours, enabling drill down, or setting the window size. You can also set an auto-refresh interval for the dashboard (e.g., every 15 minutes) by editing the dashboard properties.
5. **Share the dashboard** — Click the 'Share' button on the dashboard. You can share with specific users, groups, or roles. For example, share with the 'Service Desk Managers' group. You can also set this dashboard as the default homepage for those users so they see it every time they log in. Make sure all reports on the dashboard are public (or shared appropriately) so that users with the right roles can view them.
6. **Use Performance Analytics for trends** — If you need to track metrics over time, navigate to Performance Analytics and create a new indicator. For example, create an indicator called 'Average Time to Resolve' that tracks the 'Duration' field on resolved incidents. Then set up a breakdown by 'Assignment Group'. Add this indicator to a scorecard widget on your dashboard. After a few weeks, you can see trend lines and identify patterns.

## Comparisons

### Report vs Dashboard

**Report:**
- Single view of data (list, chart, or pivot).
- Static or manually refreshed snapshot.
- Created from one data source (table).

**Dashboard:**
- Collection of multiple reports on one page.
- Displays live data (reports update if underlying data changes).
- Can include reports from different data sources.

### Performance Analytics Indicator vs Report with Trend Line

**Performance Analytics Indicator:**
- Specifically designed to track metrics over time.
- Requires manual setup of breakdowns and scorecards.
- Supports forecasting and historical comparisons out of the box.

**Report with Trend Line:**
- Can show a line chart of data but is not automatically historical.
- No built-in forecasting without custom scripting.
- Typically used for current state, not long-term trend analysis.

### Public Report vs Private Report

**Public Report:**
- Visible to all users with the 'report_user' role (or 'report_admin').
- Can be added to shared dashboards.
- Suitable for team-visible metrics.

**Private Report:**
- Visible only to the user who created it.
- Cannot be directly added to a shared dashboard (others won't see it).
- Suitable for personal analysis or drafts.

### Condition Filter on Report vs Condition Filter on Dashboard

**Condition Filter on Report:**
- Applied to the report itself to limit which records are shown.
- Part of the report definition, saved with the report.
- Changes affect the report everywhere (e.g., in all dashboards using it).

**Condition Filter on Dashboard:**
- Applied to a specific dashboard instance of a report (if supported).
- Does not change the underlying report.
- Useful for creating different views of the same report on different dashboards.

### Group By (Report) vs Aggregation (Report)

**Group By (Report):**
- Organises data into categories (e.g., one bar per priority).
- Works with count, sum, average, etc.
- Creates multiple data points (one per group).

**Aggregation (Report):**
- Computes a single number from a field (e.g., total count, average value).
- Does not break data into categories.
- Returns one value (e.g., total number of incidents).

## Diagram

_This diagram shows how raw data from ServiceNow tables flows into reports and Performance Analytics indicators, which are then combined into dashboards for at-a-glance monitoring._

```mermaid
flowchart TD
    A[Raw Data in Tables] --> B[Create Report]
    B --> C{Choose Report Type}
    C --> D[Bar Chart]
    C --> E[Pie Chart]
    C --> F[Line Chart]
    C --> G[List]
    C --> H[Pivot Table]
    B --> I[Add to Dashboard]
    I --> J[Shared Dashboard]
    A --> K[Performance Analytics]
    K --> L[Indicators]
    L --> M[Scorecards]
    M --> J
```

## Common misconceptions

- **Misconception:** You can only create reports from the Incident table. **Reality:** You can create reports from any table in ServiceNow, including custom tables, tables from applications, and database views. (Beginners often only see the default Incident module and assume it's the only option. In reality, ServiceNow is a platform where every record in any table can be reported on.)
- **Misconception:** A dashboard and a report are the same thing. **Reality:** A report is a single snapshot or chart of data. A dashboard is a page that displays multiple reports, allowing you to see several data views at once. (The terms are used loosely in everyday conversation, but the exam is precise. People might say 'check the dashboard' when they mean 'look at the chart', causing confusion.)
- **Misconception:** Once you add a report to a dashboard, you cannot change how it looks unless you delete and recreate it. **Reality:** You can edit the underlying report from the dashboard by clicking on the report and selecting 'Edit Report'. Changes you make will automatically update on the dashboard. (Users who have not used dashboards often assume they are static screenshots. The exam tests that you know dashboards are live and editable.)
- **Misconception:** Performance Analytics is the same as reporting. **Reality:** Reporting gives you a snapshot of current data. Performance Analytics tracks how indicators change over time, often using historical data and trends. They are different tools for different purposes. (Both involve data and charts, so beginners lump them together. The exam clearly separates them, and questions will test which tool to use based on the need (e.g., trends = Performance Analytics, current state = report).)
- **Misconception:** You can only share a dashboard with individual users by adding them one by one. **Reality:** You can share a dashboard with a group or a role, which automatically gives access to all users who are members of that group or role. This is more efficient for team access. (New administrators might only know the manual way of adding users individually. The exam expects you to know the role/group sharing options for scale.)

## Key takeaways

- A report is a single view of data (list, chart, or pivot) created from a data source with specific conditions.
- A dashboard is a collection of reports (and sometimes scorecards) displayed on one page for at-a-glance monitoring.
- Use a bar chart to compare quantities across categories, like the number of incidents by assignment group.
- Use a pie chart to show the proportion of a total, like the percentage of incidents by priority.
- Use a line chart to show trends over time, such as the average resolution time each week.
- Performance Analytics tracks indicators (metrics) over time and is used for trend analysis and forecasting.
- Public reports are visible to other users with reporting roles; private reports are only visible to the creator.
- Scheduled reports can send automated email summaries of data at regular intervals.
- Drill down allows you to click on a chart segment to see the underlying records.
- When sharing a dashboard, ensure all reports on it are public (or shared appropriately) so viewers can see them.

## FAQ

**What is the difference between a report and a dashboard in ServiceNow?**

A report is a single visualisation of data (like a bar chart or list). A dashboard is a page that displays multiple reports together, so you can see several data views at once.

**How do I create a report that shows only incidents from the last 7 days?**

When creating the report, add a condition on the 'Opened' field. Set the condition to 'Opened is greater than or equal to (dynamic) 7 days ago'. This filters the data to only include records opened in the last week.

**Can I schedule a report to be emailed to me automatically?**

Yes. After saving a report, go to the 'Schedule' option for that report. Set the frequency (e.g., daily, weekly) and time, and add email recipients. The report will run automatically and email the results in the chosen format (PDF, CSV, etc.).

**How do I share a dashboard with my entire team?**

Open the dashboard, click 'Share', then either share with a group (like 'Service Desk Team') or with a role. Adding a role gives access to all current and future users who have that role.

**What is the difference between a private and a public report?**

A private report is visible only to you. A public report is visible to other users who have the 'report_user' or 'report_admin' role, depending on the access level.

**What is Performance Analytics used for?**

Performance Analytics is used to track how metrics (like resolution time) change over time. It helps you spot trends, compare performance across teams, and make data-driven decisions.

**Can I create a report from a table that is not the Incident table?**

Yes. You can create reports from any table in ServiceNow, including Problem, Change, or even custom tables you have built for specific applications.

## Check your understanding

1. **You need to show the number of incidents by assignment group. Which report type should you use?**

   Answer: A bar chart with 'Group by' set on the 'Assignment Group' field.

2. **What is the purpose of a 'condition' in a report?**

   Answer: A condition filters the records displayed in the report so that only records meeting the criteria (e.g., Priority = 1) are included.

3. **A manager wants to see a single page that shows incident priorities, average resolution time, and a list of open high-priority tickets. What should they create?**

   Answer: A dashboard that includes three separate reports: a pie chart for priorities, a gauge for resolution time, and a list for high-priority open tickets.

4. **What is an 'indicator' in Performance Analytics?**

   Answer: An indicator is a specific metric that you track over time, such as 'average time to resolve incidents'.

5. **How can you make sure a dashboard displays automatically when a member of the service desk team logs in?**

   Answer: Share the dashboard with the team's group or role, and then set that dashboard as the default homepage for the group or role.

---

Interactive version with quiz and diagrams: https://courseiva.com/learn/servicenow-csa/reporting-analytics-and-dashboards