Ask for the shape your next step needs: table, checklist, message, calendar, script or structured data.
Do now: Take one answer and request it in two formats for different users.
The best format is useful to the person doing the next action.Format turns information into work. It reduces copying, exposes missing fields and helps people scan on their actual device.
Start from the next action
If someone must compare, use a table. If they must perform steps, use a checklist. If they must send, use a message draft. If software must process the result, use a documented structured format.
Name required columns or headings and request unknown rather than invented values.
Format is part of the task, not a cosmetic afterthought.
Design for real devices and people
A phone-friendly answer uses short sections, descriptive headings and limited width. Avoid giant tables when a list would be easier to scroll.
Request plain language, alt-text suggestions, captions or reading level when the audience needs them. Then test with a real user or accessibility tool.
Preserve what must not change
Tell the model to keep exact figures, quotes, names or identifiers only when authorised and necessary. Ask it to flag missing fields.
Compare the formatted result to the source; reformatting can introduce omissions or altered numbers.
A tidy error is still an error.