60 Prompt Output Formats for ChatGPT
Key Takeaways:
- Specifying output format dramatically improves the usability of ChatGPT responses
- Different formats serve different purposes; match format to intended use
- Structured formats like tables and JSON integrate with other tools more easily
- Code formats enable direct use in development and automation workflows
- Visual formats communicate relationships that text obscures
Most ChatGPT conversations produce text walls that require manual formatting before use. You copy, paste, and restructure the output into formats that actually serve your needs. This adds work that defeats much of AI’s efficiency advantage.
Specifying output format in your prompt eliminates this rework. The AI produces content in the structure you need, ready for direct use. Tables instead of paragraphs. Code instead of descriptions. JSON instead of prose.
This guide provides 60 prompt formats that produce structured output. Each format serves specific purposes and integrates with different workflows.
Data and Tabular Formats (1-15)
Format 1: Comparison Table
Prompt pattern: “Create a comparison table of [items] with columns for [characteristics].”
Use when evaluating options or comparing alternatives side-by-side. Comparison tables enable quick scanning and direct decision support.
Format 2: Feature Matrix
Prompt pattern: “Generate a feature matrix showing [products/services] across [requirements].”
Use for requirements analysis or vendor evaluation. Feature matrices reveal gaps and overlaps at a glance.
Format 3: Pros and Cons Table
Prompt pattern: “List pros and cons for [decision] in a two-column table with examples for each.”
Use for balanced decision-making. Each point gains clarity through its opposite.
Format 4: Pricing Table
Prompt pattern: “Create a pricing comparison table for [options] including [features] and [limitations].”
Use when evaluating subscriptions, services, or product tiers. Pricing tables surface value differences.
Format 5: Timeline Table
Prompt pattern: “Generate a table showing [project/process phases] with columns for [timing, dependencies, owners].”
Use for project planning and status tracking. Timeline tables make scheduling explicit.
Format 6: Inventory Table
Prompt pattern: “List [items to track] with columns for [attributes: quantity, location, status, reorder point].”
Use for asset management or supply chain tracking. Inventory tables enable systematic review.
Format 7: Contact Directory Table
Prompt pattern: “Create a contact table with columns for [name, role, company, contact info, relationship notes].”
Use for networking or client management. Directory tables support relationship maintenance.
Format 8: Competitor Analysis Table
Prompt pattern: “Generate a competitor analysis table covering [competitors] with [strengths, weaknesses, market position, pricing].”
Use for strategic planning. Competitor tables inform positioning decisions.
Format 9: Skills Assessment Table
Prompt pattern: “Create a skills assessment table for [role/domain] with [skill areas, current level, target level, development path].”
Use for professional development planning. Skills tables reveal learning priorities.
Format 10: Risk Register Table
Prompt pattern: “Generate a risk register table listing [risks] with [likelihood, impact, mitigation, owner].”
Use for project or business risk management. Risk registers formalize contingency thinking.
Format 11: Meeting Notes Table
Prompt pattern: “Create a table summarizing key meetings with columns for [date, attendees, decisions, action items, owner, deadline].”
Use for stakeholder management and accountability tracking.
Format 12: Content Calendar Table
Prompt pattern: “Generate a content calendar table for [platform/topic] with [dates, content type, topic, status, publish date].”
Use for editorial planning. Calendars make publishing commitments visible.
Format 13: Budget Breakdown Table
Prompt pattern: “Create a budget table for [project/event] with [categories, allocated amount, actual spent, variance, notes].”
Use for financial tracking. Budget tables enable variance analysis.
Format 14: Survey Results Table
Prompt pattern: “Generate a summary table of survey responses with [question, response count, percentage, key themes].”
Use for research synthesis. Survey tables make patterns visible across many responses.
Format 15: Decision Criteria Table
Prompt pattern: “Create a decision criteria table for [decision] with [criteria, weight, score for each option, weighted total].”
Use for structured decision-making. Criteria tables make trade-offs explicit.
Structured Data Formats (16-25)
Format 16: JSON Object
Prompt pattern: “Return the following information as a JSON object: [data structure].”
Use when data needs to integrate with other tools or APIs. JSON format enables automation.
Format 17: JSON Array
Prompt pattern: “Generate a JSON array of [items] with fields for [attributes].”
Use for list data that downstream tools can process. Arrays handle collections efficiently.
Format 18: Key-Value Pairs
Prompt pattern: “Create key-value pairs for [data set] in the format: [key]: [value].”
Use for configuration data or lookup tables. Key-value pairs are human-readable while machine-parseable.
Format 19: Markdown List
Prompt pattern: “Generate a markdown checklist for [task/project] with [checkboxes] for each step.”
Use for task tracking or process documentation. Markdown lists render nicely in most tools.
Format 20: Structured Note-Taking
Prompt pattern: “Format these notes as: ## Key Point, ### Supporting Detail, #### Example, ##### Action Item.”
Use for organizing research or meeting notes. Headers create navigable structure.
Format 21: FAQ Document
Prompt pattern: “Create an FAQ document with [questions] as headers and [answers] as content.”
Use for customer support or internal knowledge bases. FAQs enable self-service.
Format 22: Decision Tree Outline
Prompt pattern: “Generate a decision tree outline for [situation] with [choice points] and [consequences].”
Use for mapping complex decisions. Trees reveal options that might otherwise stay implicit.
Format 23: Hierarchical Outline
Prompt pattern: “Organize this content into a hierarchical outline with [levels] using Roman/Arabic/alpha numbering.”
Use for structuring complex topics. Hierarchies make relationships between points explicit.
Format 24: Two-Column Document
Prompt pattern: “Format this as a two-column document with [content type A] on the left and [content type B] on the right.”
Use for comparisons or parallel content. Two columns enable direct scanning.
Format 25: Step-by-Step Numbered List
Prompt pattern: “Generate a numbered step-by-step guide for [process] with each step on a new line.”
Use for instructions or procedures. Numbered steps create clear sequence.
Code and Technical Formats (26-35)
Format 26: Python Function
Prompt pattern: “Write a Python function that [does X] with parameters for [inputs] and return [output].”
Use for automating repetitive tasks. Functions enable code reuse.
Format 27: SQL Query
Prompt pattern: “Write a SQL query to [retrieve data description] from [tables] where [conditions].”
Use for database access. SQL queries extract specific data efficiently.
Format 28: Regular Expression
Prompt pattern: “Generate a regex pattern that matches [description of pattern] with explanation of each component.”
Use for text processing. Regex patterns enable sophisticated text matching.
Format 29: Bash Script
Prompt pattern: “Create a bash script that [does X] with comments explaining each step.”
Use for automating command-line operations. Scripts enable repeatable processes.
Format 30: API Request Template
Prompt pattern: “Generate an API request template for [endpoint] including headers, body structure, and example payload.”
Use for integrating with web services. Templates accelerate development.
Format 31: Configuration File
Prompt pattern: “Create a [JSON/YAML/TOML] configuration file for [application] with [settings and comments].”
Use for application setup. Config files formalize environment setup.
Format 32: HTML Snippet
Prompt pattern: “Write an HTML snippet that [does X] with semantic markup and inline comments.”
Use for web development. HTML snippets integrate into larger projects.
Format 33: CSS Styling
Prompt pattern: “Generate CSS for [element] with [properties] and responsive breakpoints.”
Use for web styling. CSS enables consistent visual presentation.
Format 34: Markdown Table
Prompt pattern: “Create a markdown table with [headers] and [rows] that can be copied directly.”
Use when markdown tables render in your target platform. Direct generation saves reformatting.
Format 35: Mermaid Diagram
Prompt pattern: “Generate a Mermaid diagram for [flowchart/sequence/entity relationship] with [specific content].”
Use for visual documentation that auto-generates from text definitions.
Visual and Diagram Formats (36-42)
Format 36: ASCII Diagram
Prompt pattern: “Create an ASCII diagram showing [system/process] with [components] and [relationships].”
Use for text-based documentation. ASCII diagrams work anywhere without rendering tools.
Format 37: Flowchart Description
Prompt pattern: “Describe a flowchart for [process] including [decision points, actions, start/end].”
Use when visual flowcharts need text-based representation.
Format 38: Sequence Diagram Description
Prompt pattern: “Generate a sequence diagram description for [interaction] between [participants] showing [message flow].”
Use for documenting interactions. Sequence descriptions clarify temporal dependencies.
Format 39: Mind Map Structure
Prompt pattern: “Create a mind map structure for [topic] with [main branches] and [sub-branches] using indentation.”
Use for brainstorming organization. Mind maps reveal associations between ideas.
Format 40: Org Chart Format
Prompt pattern: “Generate an org chart in text format for [organization] with [roles] and [reporting relationships].”
Use for HR documentation or team planning. Org charts clarify structure.
Format 41: Gantt Chart Description
Prompt pattern: “Describe a Gantt chart for [project] showing [phases, durations, dependencies] as text.”
Use when visual charts need text representation. Descriptions work where rendering fails.
Format 42: Network Diagram Description
Prompt pattern: “Create a network diagram description for [system] showing [nodes], [connections], and [data flows].”
Use for infrastructure documentation. Network descriptions enable visualization.
Communication Formats (43-52)
Format 43: Email Template
Prompt pattern: “Write an email template for [purpose] with subject line, body, and signature placeholders.”
Use for recurring communication types. Templates ensure consistency.
Format 44: Meeting Agenda
Prompt pattern: “Create a meeting agenda with [sections], [time allocations], and [expected outcomes].”
Use for productive meetings. Agendas focus discussion and respect time.
Format 45: Presentation Outline
Prompt pattern: “Generate a presentation outline for [topic] with [slides], [key points per slide], and [suggested visuals].”
Use for talks or pitches. Outlines organize content flow.
Format 46: Client Report Structure
Prompt pattern: “Create a client report structure with [sections], [key metrics], and [recommendations] sections.”
Use for professional deliverables. Report structures ensure completeness.
Format 47: Executive Summary
Prompt pattern: “Write an executive summary of [document/report] in [number] paragraphs: [situation], [what we did], [results], [next steps].”
Use for busy stakeholders. Summaries enable informed decisions without full document review.
Format 48: Status Update
Prompt pattern: “Generate a status update for [project] covering [completed], [in progress], [blockers], [next steps].”
Use for regular project communication. Status updates keep stakeholders aligned.
Format 49: Project Brief
Prompt pattern: “Create a project brief with [background], [objectives], [scope], [timeline], [budget], [success criteria].”
Use for project initiation. Briefs align stakeholders before work begins.
Format 50: Product Requirement Document
Prompt pattern: “Generate a PRD for [feature] with [user story], [requirements], [acceptance criteria], [technical notes].”
Use for product development. PRDs clarify what to build and why.
Format 51: Case Study Format
Prompt pattern: “Write a case study for [situation] following: challenge, solution, implementation, results, learnings.”
Use for marketing or training. Case studies demonstrate capability through example.
Format 52: FAQ with Expandable Answers
Prompt pattern: “Create an FAQ with [questions] using markdown expandable sections: question header, answer hidden below.”
Use for knowledge bases. Expandable FAQs save space while enabling access.
Analysis and Planning Formats (53-60)
Format 53: SWOT Analysis
Prompt pattern: “Conduct a SWOT analysis for [organization/decision] with [strengths, weaknesses, opportunities, threats].”
Use for strategic planning. SWOT frameworks organize environmental analysis.
Format 54: Porter’s Five Forces
Prompt pattern: “Apply Porter’s Five Forces to [industry] analyzing [competitive rivalry, supplier power, buyer power, substitutes, new entry].”
Use for industry analysis. Five Forces clarify competitive dynamics.
Format 55: Business Model Canvas
Prompt pattern: “Generate a business model canvas for [business] covering [segments, value prop, channels, relationships, revenue].”
Use for business planning. Canvas formats enable quick business model visualization.
Format 56: OKR Structure
Prompt pattern: “Create OKRs for [team/quarter] with [objectives] and [key results] that are measurable.”
Use for goal-setting. OKRs align effort with strategic priorities.
Format 57: Root Cause Analysis
Prompt pattern: “Conduct a root cause analysis for [problem] using [5 Whys/fishbone] methodology.”
Use for problem-solving. RCA prevents treating symptoms rather than causes.
Format 58: Decision Matrix
Prompt pattern: “Generate a decision matrix for [decision] evaluating [options] against [criteria] with [weightings].”
Use for structured decisions. Matrices make trade-offs explicit and auditable.
Format 59: Lessons Learned Format
Prompt pattern: “Document lessons learned for [project] covering what went well, what did not, and what to do differently.”
Use for continuous improvement. Lessons learned prevent repeating mistakes.
Format 60: After-Action Review
Prompt pattern: “Conduct an after-action review for [event/project] addressing: what was supposed to happen, what actually happened, why it happened, what to do next.”
Use for operational excellence. Reviews extract learning from both successes and failures.
Specifying Formats Effectively
Include format specifications clearly in your prompts. The more specific your format request, the closer the output matches your needs.
Effective specifications: “Create a comparison table with columns for name, price, and key features.” “Return this data as JSON with fields for id, name, and email.” “Generate markdown with a table containing headers X, Y, Z.”
Ineffective specifications: “Make this a table.” “Put this in a good format.” “Organize this nicely.”
The specificity guides the AI toward your intended structure.
Common Format Mistakes
Asking for format without specifying structure. “Make this a table” produces whatever table structure the AI decides.
Mismatching format to purpose. Detailed tables serve analysis but overwhelm quick scans. Match format to use case.
Ignoring output limitations. Some formats have length constraints. Long tables or code may require multiple prompts.
Frequently Asked Questions
Can I combine formats?
Yes. A report might combine tables, lists, and structured sections. Specify each section’s format separately.
What if the output exceeds length limits?
Break into multiple prompts. Ask for sections separately, then combine. Chunk large requests to stay within limits.
Do formats work across all ChatGPT versions?
Most formats work across versions. Some newer formats may be version-specific. Test with your typical version.
Can I specify my own custom format?
Yes. Describe the format structure you want clearly. The AI can follow custom specifications if described precisely.
Conclusion
Specifying output format transforms ChatGPT from a text generator into a structured data producer. These 60 formats cover the range of common needs across professional contexts.
Start using format specifications in your prompts. Match format to purpose. Build a personal toolkit of formats that serve your recurring needs.
The time spent specifying format returns many times over in reduced reformatting work.