Pando

Give your agent a table, not a paragraph

2026-08-16

An agent reading prose has to guess what the fields are. The same facts as a table cost fewer tokens and admit no guessing.

Ask an agent to track three supplier quotes and it will write you a paragraph. Ask it what the plumber quoted and it re-reads the paragraph, infers which number is a quote, and answers with a hedge. Do that twice a day for a month and you have paid for the same inference sixty times.

The fix is not a better prompt. It is giving the facts a shape.

The same facts, as a table

The agent-table template in Pando: a table whose first row names the columns Item, Status, Asked and Next, a filled example row, a placeholder row, and a footer note that briefs your agent

A table in Pando is not a different kind of document. It is one property on one bullet: the children become rows, their children become cells, and the first row names the columns. Set the property back and the same branch is an ordinary list again, with nothing moved and nothing lost.

That matters for a boring reason. You do not have to decide up front whether something is "a note" or "a database". Start as bullets, and the day you have four of them with the same three facts, make it a table.

What changes for the agent

Retrieval stops being inference. "What did the plumber quote" is a cell lookup, not a reading comprehension exercise.

Writing stops being risky. An agent updating a cell touches one cell. An agent updating a paragraph rewrites the paragraph, and rewrites are where facts quietly disappear.

The answer gets smaller. A table read back as markdown is a fraction of the prose that carried the same facts, and an agent that reads it every session pays that difference every session.

And the shape is legible to both of you. You look at the table and see a missing quote. So does the agent. Neither of you is reconstructing it.

The rule I would give an agent

"When a branch has three or more children that share the same fields, ask whether it should be a table, and say which columns you would use. Do not convert without asking."

The last clause matters: layout is a judgement about how YOU read, and an agent that reshapes your outline unasked is an agent you stop trusting for good reasons.

What tables are not for

Not for prose with a heading per row. Not for a list of five bullets that will never grow. A table pays for itself when the same facts repeat, and costs more than it gives when they do not.

Take the table

Open the template, press "Show in my Pando", and a working table stands in your outline with three rows in it. Change one cell, then set the layout back to a plain bullet and watch the same facts stand as a list.


More from the blog · Try Pando