Product
When a Report Needs a Chart, and When the Table Is the Point
Look up a value, use a table. Show a change, use a chart. A buyer works from one kind of report and a meeting reads the other.
A report you work from and a report you present from are different objects
Most reporting problems are really audience problems. The person who builds a report is usually the person who uses it hardest. They scan it, filter it and act on it line by line. Then the same report gets pasted into a weekly update, and people who will never act on a single line have to dig through it to find out whether things are getting better or worse.
Cole Nussbaumer Knaflic calls this the difference between exploratory and explanatory analysis. Exploratory work is how you find what’s interesting. Explanatory work is how you show it to someone else. Handing the audience the exploratory version is easy to do by accident. Every column you used to get to the answer is still there, and the answer itself isn’t marked.
So before deciding what a report should look like, decide who it’s for. The rest follows from that.
| Aspect | Working report (table) | Presented report (chart) |
|---|---|---|
| Who uses it | The person who acts on it, like a buyer or an ops lead | People who read it but don’t act on lines, like the owner or a weekly meeting |
| Question it answers | “What exactly is this item’s value?” | “Which way is this moving, and what stands out?” |
| Precision | The exact figure matters | The direction and size matter more than the decimals |
| Kind of analysis | Exploratory: finding and acting | Explanatory: showing a conclusion |
| Example | A reorder or low-stock list someone works through | Sales over time for a weekly review |
The rule: is the answer in a single value, or in the shape?
Stephen Few put the test in two sentences: “Tables work best when the display will be used to look up individual values or the quantitative values must be precise. Graphs work best when the message you wish to communicate resides in the shape of the data (that is, in patterns, trends, and exceptions).”
That turns the choice into a question you can ask of any report: does the reader need one specific value, or the shape of the data? A reorder list is all specific values, since the buyer needs this variant and this quantity. Revenue over time is shape. Nobody in the meeting needs Tuesday’s exact figure. They need to see whether the line is climbing.
The reason the rule holds is in how each format is read. A table is read one cell at a time. The eye goes to a row, then across to a column, and the number it finds is exact. That’s slow for spotting a pattern, but it’s the only way to get a figure you can act on without guessing. A chart is read all at once. The eye picks up slope, gaps and outliers before it reads a single label, which makes a trend or an exception obvious and makes any one value approximate.
So each format fails in the other’s job. Ask a reader to find a trend in a table of numbers and they have to hold dozens of values in their head and compare them. Ask a buyer to pull an order quantity off a chart and they’re estimating between gridlines. Neither reader is doing anything wrong. The format is giving them the wrong kind of answer.
Some reports need both. The person who works the lines needs the precise version, and the people who only need to see the trend need the shape. The rule doesn’t make you choose one for good. It tells you which version each reader should get.
Keep the table when the reader acts on single rows
If someone acts on individual rows, a chart gets in their way. They have to read values off an axis, estimate between gridlines and give up precision they need. When the job is to check one figure, the table is the best format.
That’s also where an AI-built report starts in Assisty. You type what you want to know, and Atlas queries your synced store data and answers with a live table. You can ask for sales, inventory, forecasting, replenishment, lost-revenue or stock-availability reports, by product, variant, category, vendor, location, customer or over time, from the last 7 days to year-over-year.
The working version is also the one you refine. Ask Atlas to add a column or change the time range, and it changes only what you asked for and leaves the rest of the report as it was. Each filter shows as a chip you can remove, so the person relying on the numbers can see exactly what’s included.
From an answer to a saved report in Assisty
Save as Custom Report and it joins My Reports beside your custom reports. From there, open it in the full report editor to add charts for the people who need the shape. For the whole path from asking to saving to scheduling, see ask it, save it, or schedule it.
| Reader | What they need | Where Assisty gives it |
|---|---|---|
| The person acting on rows | Exact values | The live table Atlas answers with, refined by talking, with each filter as a chip you can remove |
| A reader who opens Assisty and needs the shape | The trend | The full report editor, where you add charts to the saved report |
| A reader who won’t open Assisty | The report, delivered | A scheduled email with a CSV, Excel, or PDF attachment, to multiple recipients at once, with the schedule’s columns and filters editable without touching the report |
| A reader who works in their own tool | The data in their own tool | Export as CSV, PDF, or Google Sheets, like any other report |
Deliver it to the people who won’t open Assisty
Some readers won’t open Assisty to find the report, so send it to them. Open the report and choose Quick Actions → Schedule Report, and it goes out by email on a daily, weekly, or monthly schedule. The scheduled email carries the report as a CSV, Excel, or PDF attachment, and it can go to several recipients at once.
Those readers probably don’t need every column the buyer uses. You can edit a schedule’s columns and filters without touching the report itself, so the delivered copy can carry fewer columns. The owner gets just the columns that answer their question, while the buyer’s working table stays complete. For when the override is the wrong tool, see when a scheduled report stops being right. Run now sends a test delivery the moment you save.
For delivering the same report to more than one place, like a sheet, a Drive folder or a Shopify Flow trigger, see where your reports should land. If you’re still building the Monday report by hand, start with the post on stopping that.