---
title: "Tally"
url: "https://showcaller.ai/features/tally/"
type: "page"
published: "2026-06-28T11:29:17+00:00"
modified: "2026-10-08T10:44:23+00:00"
author: "admin"
---

[Features · Trust](/features/)

# Tally

 Confirmed means the device said so.

Most show-control tools stop at “command sent.” Tally is the part of Showcaller that doesn’t. After a command goes out, Showcaller checks the state the device reports. It only calls a change done when the device agrees. Where a device can’t report a change, Tally says it was sent but not confirmed.

 [Start free trial](https://app.showcaller.ai)

No prior integration or training needed.

01

## Two different claims, and only one of them should count

Sending a command and having it actually happen are two different events. Think of a network hiccup, a desk that’s mid-save or a device that’s slow to respond. Any of these can mean the instruction went out and the hardware just didn’t do it.

Most systems can’t tell the difference. They sent the command, so as far as they’re concerned, the job is done. Tally checks. After a command goes out, Tally reads back the state the device reports. Only then does it confirm the cue took. Some devices can’t report every change. Then Tally tells you the command was sent but not confirmed.

02

## After, not before

Tally isn’t a pre-flight gate that holds a command up for inspection before it runs. That would add latency exactly when you can’t afford it. Instead, the check runs right after the command. The command isn’t held up while Tally checks. And “confirmed” means the device itself reported the change. Confirmed values also update [Pulse](/features/pulse/), so its picture of your gear stays current.

03

## When something doesn’t take

Say a scene didn’t recall, an input didn’t switch or a mute didn’t latch. If the device reports that a cue didn’t take, you hear about it right away. Not when someone in the room notices something looks wrong. Not after the show. Right away, while there’s still time to do something about it. A change Tally can’t confirm is flagged, not hidden.

04

## Every confirmation, kept

Every one of these checks gets written into [Air Check](/features/air-check/)‘s timeline, pass or fail. So the record of a show isn’t just “what we told the system to do.” It shows what the devices reported back. Tally is what makes that record trustworthy in the first place.

## Know which changes the device confirmed

That’s Tally: verify after, not before. It checks every change the device can report. Where it can’t, Tally tells you so. Either way, you know what was confirmed and what wasn’t.

[See how Pulse powers Tally →](/features/pulse/) · [See where confirmations get recorded →](/features/air-check/)
