Does this really need a table?

Three possible venues. Three paragraphs of enthusiastic description. Somewhere in them are the room sizes, available evenings and whether anybody has actually confirmed the booking.

The descriptions may be pleasant reading. They make comparison unnecessarily difficult.

A table earns its space when the reader needs the same questions answered about several things. It puts each answer in a predictable place and makes missing answers conspicuous. That last quality is often its most useful one.

Give every column a real question

For a small evening class, a working comparison might look like this:

Example venue comparison for an evening class

Venue	Evening available	Booking status
Community room	Tuesday	Awaiting confirmation
Workshop studio	Thursday	Provisional hold
Library room	To confirm	Enquiry sent

This fictional table distinguishes an available evening from a booking. Without that distinction, “Tuesday” might be mistaken for a commitment rather than an answer received during an enquiry.

Column headings are the questions in abbreviated form. Evening available asks something specific. Details permits almost anything, which means the cells soon contain information that cannot sensibly be compared.

Use an explicit phrase such as “To confirm” where a missing answer matters. An empty cell may mean unknown, irrelevant, zero or forgotten. The reader should not have to choose among them.

Do not force the decision into the grid

The table can reveal the choices. It may not explain which one you should make.

The workshop studio could be more suitable for messy materials, while the library room could suit a discussion class. If those differences require explanation, put a paragraph below the table. Repeating a long qualification in each cell makes the table harder to scan without making the decision more rigorous.

The same applies to actions. “Ask whether sinks are available” is useful work to record, but it is not a confirmed property of the room. Put it in a short task list with a recognisable finish, or label it clearly as an open question.

When there are only two brief observations and no repeated dimensions, prose may be clearer. A table should reduce the effort of finding an answer, not simply make the page look prepared.

Know what the format can carry

Markdown tables are supported by many tools, but they are not a universal feature of every Markdown implementation. If the document is going somewhere specific, check its table support and the result there.

Keep cell contents short and structurally simple. In Clarity, Markdown table cells contain a single line of text; the table guide covers creating and editing them. An elaborate layout with merged cells, nested material or precise widths belongs in a tool designed for that work.

A spreadsheet is also the better choice when the table needs calculations, sorting large amounts of data or ongoing numerical analysis. You can write the interpretation in a Markdown document and keep the working data separately, with a clear reference to the relevant file.

Before sending the venue comparison, read down each column. Are the answers comparable? Are their uncertainties visible? Then read across each row and ask whether someone could mistake an enquiry for a booking. That is a more useful final check than making every cell equally full.