Lesson Content

Format is not cosmetic – it determines usability.

A well-reasoned Claude response in the wrong format requires significant rework before you can use it. A response in the right format can go directly into a document, a system, or a decision. Specifying format is not a cosmetic preference – it is part of the task definition.

Common format types and when to use them:

• Numbered list: Step-by-step instructions, ranked priorities, sequential processes
• Bullet list: Unranked items, features, considerations, brainstorm outputs
• Table: Comparisons, feature matrices, schedules, structured data with categories
• Prose paragraphs: Narrative explanations, essays, emails, reports
• Checklist: Audit steps, review criteria, pre-launch verification
• Two-column comparison: Side-by-side evaluation of two options
• JSON / XML / CSV: When output needs to feed into a system or tool
• Outline (H1/H2/H3): Document structure, course curriculum, presentation structure
• Q&A format: FAQ documents, interview prep, knowledge base articles
• Slide deck outline: Presentations with speaker notes

Specifying format by example.

If you cannot describe the format you want in words, show it. Paste a small example of the structure and ask Claude to follow it. This is particularly useful for custom data formats, branded templates, or unusual structural requirements.

Example: "Use this structure for each item: [Name] | [Description: one sentence] | [Risk level: Low/Medium/High] | [Owner: TBD]"

Requesting format for downstream use.

If the output is going into a system, tell Claude what the system expects. "Format this as a Markdown table," "Return this as valid JSON with these keys: name, priority, deadline, owner," "Format as a numbered list compatible with Microsoft Word styles." Claude handles a wide range of format requests – but only if you ask.

Format and length are related.

A table with 20 rows is often more scannable than 20 prose paragraphs. A numbered five-step process is faster to follow than a narrative description. When you choose format, consider how the reader will use the output – reading linearly, scanning for a specific item, copy-pasting into a system, presenting to an audience.