How to read a plan table without over-reading it
A blank cell on a feature grid usually means excluded, because grids are built to sell the upgrade. It can also mean the line was cut for space. Neither reading is a statement by the vendor, and the difference matters when the question is serious. As of 2026-09-12.
| The table says | It does not say |
|---|---|
| Removal is a benefit of this plan | What the mark looks like |
| This tier includes watermark-free export | Whether anything is written into the file |
| Upgrading removes the mark | Whether earlier output changes |
Inclusion rule. Claims plan tables make, set against what a reader usually wants to know. Order. Paired, claim first.
1Grids are built to make the upgrade obvious
A pricing grid exists to move a reader up a tier. Everything about its design serves that: the middle column is highlighted, the features that differentiate are listed, and features shared by every tier are frequently omitted because they do not help the sale.
That last habit is the trap. A feature absent from every column might be universal rather than unavailable, and a reader scanning for what a tier includes cannot tell which.
2The three states a cell can be in
Stated present: the phrase appears with a tick or a value. Stated absent: the phrase appears with a cross or the word no. Not mentioned: the phrase does not appear at all. The first two are statements; the third is not.
Most disagreements about what a vendor permits come from treating the third as the second. It is a reasonable inference on a well-built grid and it is still an inference, and the vendor has not said it.
3Why the distinction survives being pedantic
Grids get redrawn. When a row is renamed or a tier is restructured, an inference drawn from an old layout quietly stops holding, and nothing announces it. A statement stays quotable across redesigns because it was a sentence.
For anything that will be documented, screenshotted or relied on months later, the practical advice is to prefer a sentence from a policy page over a cell on a grid, and where only the grid exists, record that it was a grid.
4What to do when the grid is all there is
Write down what you read, the date you read it, and the URL. Note whether it was a statement or an absence. If the question is significant, ask the vendor in writing and keep the reply, which converts an inference into a statement with a name attached.
That last step takes ten minutes and almost nobody does it, which is why so many production conversations about permissions end in somebody recalling a page that has since changed.
5Free tiers are the worst documented and the most used
The lowest tier is where evaluation happens, where the first draft gets made, and where the clip somebody liked came from. It is also the column with the fewest words, because a grid spends its space on the tiers it wants you to buy.
When a free-tier question matters, it is usually worth more than a grid can support. This is the single most common place where a record built from grids has to say the evidence is thin.
6Prices on a grid are a snapshot of a moment
Tier names change, prices move, and features migrate between tiers. A note that says commercial use started at the second tier is only meaningful with the date and the tier name attached, because both can be different next quarter.
The same applies to currency and billing period. A figure quoted without saying monthly or annual, and without saying which currency, is the kind of note that causes an argument rather than settling one. Write the whole thing down or do not bother.
7Screenshots age badly and are still worth taking
A screenshot proves what a page looked like on a day, which is exactly what a grid-derived inference needs. It does not prove what the vendor meant, and it will not persuade anyone on its own if the page now says something else.
Take one anyway, name the file with the date and the URL, and store it with the production record rather than in a chat. The cost is seconds and the alternative is recalling a layout from memory under pressure.
8A short checklist
Is this a statement or an absence. Is this page a policy or a sales grid. What is the date. Does the tier I am reading match the tier the work was actually produced on. Has the grid changed since the file was made.
Five questions, all answerable in a couple of minutes, and between them they cover almost every way a confident reading of a pricing page turns out to be wrong later.
A mechanism explainer, not a field in the table. No sentence here belongs to a generator, and none should be quoted as one. The sourced material is on the support table. Related: Metadata vs watermark, Reading a plan table.