Show the working

Most AI answers ask to be believed. A Countdat answer can be checked - by a colleague, an auditor, or anyone who reads SQL.

#Open it

On any answer page, choose Show the working. It opens the Answer Log: every query the analyst ran to reach the answer.

#What's in the Answer Log

For each query you see:

• why it ran - a sentence in plain English,
• how many rows it read,
• how long it took,
• and the exact SQL.

At the top, a summary: the counter, the answer, and the total work - queries, rows read and time.

-- Answer Log
-- Counter: key-headroom · closest-to-full
-- Work: 5 queries · 9 rows read · 1,919 ms

-- 1. Finding the current table closest to full.
-- 1 row · 180 ms
SELECT ...

#Copy or download it

The whole log is one script. Copy it, or download it as a .sql file to keep with a report or send to whoever needs to check it.

#Reading it without knowing SQL

You don't have to read the SQL to get value from the log. The sentence above each query says what it was for, and the row counts tell you how much data the answer rests on. If an answer looks surprising, those sentences are usually enough to spot why - a filter you didn't expect, or a field read differently than you meant.

#If the answer is wrong

1. Open Show the working and read the sentence above each query.
2. Find where it went differently from what you meant.
3. Ask again, more precisely - name the field, the time range, or what to leave out.

Still not right? Email the downloaded .sql file and the question to support@countdat.com.