ServiceNow Indicator Explained

Definition and Visual Purpose

An Indicator in ServiceNow is a visual widget that displays a single metric or KPI (such as “Average Incident Resolution Time” or “Open Change Requests”) on a dashboard, form, or workspace. Indicators typically show a number, gauge, or trend (up/down arrow) to communicate status quickly without requiring deep analysis. They are designed to catch attention and communicate status to decision-makers at a glance.

Indicators serve two functions: they communicate current state to decision-makers, and they alert when metrics drift from expected ranges (for example, average resolution time exceeds SLA, or open incident count spikes).

Creating and Configuring Indicators

Indicators are created within dashboards or individual pages. You define a data source (usually a query or script that produces a numeric result), refresh frequency (real-time, hourly, daily), thresholds for color coding (green = good, yellow = caution, red = problem), and a visual presentation (gauge, number, bar chart, trend).

Example: an Incident SLA compliance indicator queries the incident table for closed incidents with SLA met divided by total closed incidents, calculates a percentage, and displays it as a gauge. Thresholds: green if meets SLA, yellow if approaching threshold, red if failing. Administrators can adjust thresholds based on organisational targets.

Data Sources and Calculation

Indicator data sources can be: a saved report (aggregated query results), a database query (counted records matching a filter), a business rule (custom script that calculates a value), or a REST API call to an external system. The data source runs at the refresh interval and updates the indicator display.

Calculate complex metrics carefully. If an indicator query joins multiple large tables or runs a heavy aggregation, refresh it hourly or daily rather than real-time to avoid performance impact. For frequently-updated indicators, consider caching the result in a calculation table rather than querying on demand.

Displaying Indicators on Dashboards and Forms

Add indicators to dashboards via drag-and-drop components. Each indicator occupies a dashboard cell and updates according to its refresh schedule. You can group related indicators: “Support Operations Health” might contain incident volume, average resolution time, and SLA compliance indicators side by side.

Indicators can also embed on list views or form headers. For example, an employee form might show a “Open Requests” indicator at the top, allowing managers to see how many pending requests exist for that employee without leaving the form.

Common Indicator Mistakes and Best Practices

Using an indicator that queries millions of records in real-time causes performance problems. Instead, use a pre-calculated summary table updated by a scheduled job. Displaying too many indicators on one dashboard overwhelms users; prioritise the most critical metrics.

Indicators without clear context are meaningless. Always include a label, units (count, hours, percentage), and ideally a sparkline or trend comparison (“up compared to last week” or “down from peak”). Set thresholds based on actual SLAs and business targets, not arbitrary numbers.

Advanced Indicator Patterns

Multilevel indicators show a summary metric that links to detail dashboards: a single “Open Incidents” indicator on an executive dashboard, which when clicked, opens a detailed incident list filtered by SLA status. This allows drill-down analysis from high-level health checks to specific problems.

Predictive indicators use machine learning to forecast trends: “Projected Incident Backlog (next week)” alerts when volume trends suggest you will exceed capacity. These require historical data and integration with ServiceNow’s predictive intelligence module.

When designing indicators, avoid making them too detailed. A single headline number is often more powerful than showing multiple related metrics on one indicator. If you need to show related metrics (incident count, average resolution time, SLA compliance), use separate indicators grouped on the dashboard or use a multilevel indicator that expands on click.

Choosing the question an indicator must answer

An indicator earns its place by answering one question that someone acts on. Before building it, write the question in plain words, such as whether the backlog of unassigned incidents is growing, or whether changes are failing more often than the change board expects. Then name the person who will look at the answer and the action they will take if it is bad. With no decision attached, an indicator is only decoration, and dashboards often hold figures nobody can explain.

Question the indicator answers	Measure to build on	Likely reader
Is work waiting too long to be picked up?	Age of unassigned records, grouped by queue	Service desk manager
Are changes causing trouble after release?	Failed or rolled-back changes against the total closed in the period	Change manager
Is a team’s work becoming more repetitive?	Share of records that reopen within the period	Problem or quality lead
Are we meeting the agreed response target?	Records breaching the target, split by priority	Service owner

Turning a measure into an indicator people can trust

A performance indicator is more than a count. It has a definition, a source, a period, a target and a threshold, and each part needs to be agreed. The definition has to say exactly which records are included, because “open incidents” means different things to a service desk and to a reporting team. The target says where the business wants to be, and the threshold says when someone must act. Set the threshold with the owner of the service, using their tolerance for risk, rather than copying a number from another organization.

1. Write the definition in one sentence, listing the record types, states and date fields it uses.
2. Name the source and confirm that every field in the definition is populated consistently across teams.
3. Agree the period for the reading, such as daily for the queue and monthly for trend-based measures.
4. Set the target and the threshold with the service owner, and record the reason for each value.
5. Test the indicator against a known period, and check that the number matches a manual count taken from the list view.

Why the indicator slows down the platform

Indicators that scan large tables on every page view can cause real delays for everyone else on the instance. A query that looks harmless in a test with a few hundred records can become expensive when the table holds several years of history. Keep the expensive part in a scheduled job or a summarized source, and let the indicator read the result. Where an indicator must be near real time, limit the period it looks at, such as open records in the last week, rather than the full history.

Reading a red indicator without overreacting

When an indicator turns red, the first step is to check whether the definition still describes what the team cares about. Some red readings come from a change in how records are logged, such as a new category that is excluded by the definition. The second step is to look at the trend rather than the single reading, since one bad week rarely means a process is broken. The third step is to drill down to the records behind the number, and only then decide whether the problem is in the work or in the measure.

Signs the indicator set has grown too large

A set of indicators is working when each one has a named reader and a recent decision it informed. It is growing too large when people say they check the dashboard but cannot name a decision it changed, or when two indicators measure nearly the same thing with different definitions. Remove or merge indicators on a schedule, and keep a short note of why each one was retired, so the same measure does not return under another name a year later.

Checklist for a new indicator

• A single question written in plain words, with a named reader.
• A definition that lists the records, states and dates it uses.
• A target and a threshold agreed with the service owner, with the reason recorded.
• A query cost estimate and a note on whether it is read live or from a summary.
• A review date after which the indicator is kept, changed or retired.

Frequently asked questions about performance indicators

Should a single indicator show several metrics?

Keep one headline value per indicator and put the breakdown in a linked view. Mixing two measures in one tile hides which one moved, and the reader has to guess.

How do we stop two teams reporting different numbers for the same thing?

Publish the definition next to the indicator and make the owner of that definition accountable for changes. Disagreements often come from one team filtering a field the other did not know about.

Can an indicator be used to set individual targets?

It can inform a conversation, but using a team-level indicator to rank individuals tends to change what people record rather than how the work performs. Keep individual measures for coaching and separate from the service measures.

What is the difference between an indicator and a report?

An indicator gives a current or trend value against a threshold. A report gives the detail behind it. An indicator should link to the report, so that a reader who wants the records can get them in one step.

Next step

The guide on turning capacity signals into work covers how to decide what to review, change, defer or monitor, and the platform library gives an overview of the Now Platform that these indicators sit on.