> ## Documentation Index
> Fetch the complete documentation index at: https://docs.omnifact.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Controlling Output Format and Style

> Get responses in exactly the format you need - from bullet points to formal reports, emails to presentations.

<Card title="Format Control" horizontal>
  Format control is your secret weapon for getting AI responses that are immediately useful in your work. No more reformatting - get it right the first time.
</Card>

## The Core Principle

When you specify format and style, you:

* **Save time**: Get responses ready to use immediately
* **Ensure consistency**: Maintain professional standards across all AI-generated content
* **Match your needs**: Get bullet points for quick reference, paragraphs for reports, tables for data
* **Control tone**: From casual team updates to formal client communications

The key is to **be specific about structure and tone** in your requests.

For standing preferences, set your default format and tone once in **[Personalization](/en/platform/core-features/account-settings/user-profile-and-personalization#response-preferences)** (Account Settings > **Response Preference Description**). You can still override those defaults in any prompt when a task needs something different.

## Format Request Formula

```
[YOUR REQUEST] + [FORMAT SPECIFICATION] + [TONE/STYLE]
```

**What You Want** + **How You Want It Formatted** + **What Tone to Use** = Great Prompt

**Examples:**

* "Summarize this feedback **in bullet points** with **professional tone for executives**"
* "Draft a follow-up email **in formal email format** with **client-appropriate language**"
* "Compare these options **in table format** with **columns for features, pricing, pros/cons**"

## See the Difference

**❌ Without Format Control:**

> "Summarize the key points from this team meeting."
>
> *Result: Long paragraph mixing different types of information*

**✅ With Format Control:**

> "Summarize this team meeting in the following format:
>
> * **Key Decisions** (bullet points)
> * **Action Items** (numbered list with owners)
> * **Next Steps** (numbered by priority)"
>
> *Result: Perfectly organized summary ready to share with the team*

## Essential Format Types

<CardGroup cols={2}>
  <Card title="List Formats" icon="list">
    * Bullet points
    * Numbered lists
    * Checklists
    * Priority rankings
  </Card>

  <Card title="Text Formats" icon="text">
    * Email format
    * Report structure
    * Executive summary
    * Paragraph format
  </Card>

  <Card title="Data Formats" icon="table">
    * Tables
    * Comparison charts
    * Spreadsheet format
    * Side-by-side analysis
  </Card>

  <Card title="Presentation Formats" icon="megaphone">
    * Slide outlines
    * Talking points
    * Meeting agendas
    * Action items
  </Card>
</CardGroup>

## Tone Control Options

**Formal Business**: "Use formal business language suitable for executive review"\
*Best for*: Board reports, client presentations, official communications

**Professional but Friendly**: "Use professional but approachable tone"\
*Best for*: Team communications, customer emails, internal updates

**Casual Internal**: "Use casual, friendly tone for internal team communication"\
*Best for*: Team Slack messages, informal updates, brainstorming sessions

## Most Useful Format Phrases

<AccordionGroup>
  <Accordion title="Structure Formats">
    * "in bullet points with brief explanations"
    * "as a numbered checklist"
    * "in table format with columns for \[specify columns]"
    * "as an executive summary with key findings"
    * "in professional email format with subject line"
  </Accordion>

  <Accordion title="Tone Specifications">
    * "Use professional tone appropriate for senior leadership"
    * "Use friendly but professional language for team communication"
    * "Use formal business language suitable for client presentation"
    * "Use casual tone for internal team updates"
  </Accordion>

  <Accordion title="Length and Detail">
    * "Keep responses concise - 2-3 sentences per point"
    * "Provide detailed explanations with examples"
    * "Create a one-page summary with highlights"
    * "Format as talking points for a 10-minute presentation"
  </Accordion>
</AccordionGroup>

## Common Format Mistakes

<Accordion title="Being too vague about format">
  **Instead of:** "Make it look professional"
  **Try:** "Format as a formal business email with clear subject line and professional closing"
</Accordion>

<Accordion title="Forgetting to specify tone">
  **Instead of:** "Create a summary"
  **Try:** "Create a summary in bullet points using professional tone suitable for executive review"
</Accordion>

<Accordion title="Not matching format to use case">
  **Instead of:** "Analyze this data" (unclear how you'll use it)
  **Try:** "Analyze this data in table format for inclusion in my quarterly report to leadership"
</Accordion>

## Quick Format Reference

| When You Need...     | Use This Phrase...                        |
| -------------------- | ----------------------------------------- |
| Easy scanning        | "in bullet points"                        |
| Step-by-step process | "as a numbered checklist"                 |
| Data comparison      | "in table format"                         |
| Email ready          | "in professional email format"            |
| Presentation ready   | "as talking points for slides"            |
| Action-oriented      | "as prioritized action items with owners" |

<Tip>
  Combine format and tone specifications for best results. Example: "Create a project update **in bullet points** using **professional but friendly tone** for the team."
</Tip>

## You've Mastered the Basics!

You now have the four essential skills of prompt engineering:

1. ✅ **Basic Structure** - Clear, complete, standalone prompts
2. ✅ **Clear Direction** - Direct, imperative language that eliminates confusion
3. ✅ **Role Assignment** - Transform Omnifact into domain experts
4. ✅ **Format Control** - Get responses in exactly the format you need
