> ## Documentation Index > Fetch the complete documentation index at: https://docs.loisforword.com/llms.txt > Use this file to discover all available pages before exploring further. # Output Control > How to get exactly the format and structure you need from LOIS for Word AI, including tables, redlines, comments, summary emails, and structured legal memos. Getting the right information is only half the battle. The other half is getting it in a format you can actually use. Output control means telling the AI exactly how you want your results delivered. ## Why output format matters The same information can be useful or useless depending on how it's presented. A wall of text analysis might contain great insights, but if you need a quick email to send to a client, it's not helpful. Being specific about output format saves you from reformatting or rewriting. ## Common output formats ### Tables for comparison Tables work best when you need to compare multiple items or see patterns quickly. **When to use tables:** * Comparing terms across multiple documents * Risk assessment across different clauses * Tracking changes between contract versions * Summarizing multiple issues at once **How to request:** ```markdown theme={null} Create a table with columns: Clause | Current Language | Issue | Proposed Change ``` **What you'll get:** Organized data that's easy to scan, copy into Excel, or share with others. ### Bullet points for quick scanning Bullets are ideal for lists of issues, action items, or key points. **When to use bullets:** * Issues lists for internal review * Key negotiation points * Summary of changes made * Quick risk assessment **How to request:** ```markdown theme={null} Provide a bulleted list of the top 5 risks, with clause reference and one-line explanation for each ``` ### Numbered lists for process steps Use numbers when order matters or when you need to reference specific items. **When to use numbers:** * Step-by-step negotiation strategy * Priority-ordered issues * Sequential approval requirements * Escalation paths **How to request:** ```markdown theme={null} List negotiation priorities in order: 1. Most critical (non-negotiable) 2. Important (try to get) 3. Nice to have (tradeable) ``` ### Prose for external communication Full sentences and paragraphs work for emails, memos, and explanations. **When to use prose:** * Emails to counterparties * Executive summaries * Client explanations * Internal memos **How to request:** ```markdown theme={null} Draft a 2-paragraph email explaining our position on these liability terms. Professional but firm tone. ``` ## Controlling detail level ### Executive level High-level summary focusing on business impact and key decisions needed. ```markdown theme={null} Provide executive summary: 3 bullet points covering main risks and recommended action ``` ### Working level Detailed analysis with specific clause references and technical issues. ```markdown theme={null} Detailed review with clause numbers, specific issues, and fallback positions for each ``` ### Technical level Deep dive including regulatory citations, case law references, or technical requirements. ```markdown theme={null} Include regulatory basis for each requirement with specific HIPAA/GDPR section references ``` ## Specifying length Be explicit about how much content you want. The AI defaults to being thorough, which isn't always helpful. **Length controls:** * "One sentence per issue" * "Maximum 3 bullet points" * "2-3 paragraph email" * "Single page summary" * "Comprehensive analysis" (when you do want everything) ## Mixed format outputs Sometimes you need multiple formats in one response. Structure your request to get each piece. **Example multi-format request:** ```markdown theme={null} Provide: 1. One-paragraph executive summary 2. Table of specific issues and fixes 3. Draft email to counterparty (2 paragraphs) ``` ## Output for different audiences ### For legal team Can include technical terms, clause references, and detailed legal analysis. ```markdown theme={null} Include specific clause references and legal basis for each position ``` ### For business team Focus on commercial impact, practical implications, and clear recommendations. ```markdown theme={null} Explain in business terms, avoiding legal jargon. Focus on cost and operational impact. ``` ### For counterparty Professional, justified positions without internal strategy or thinking. ```markdown theme={null} Draft response suitable for opposing counsel. Include business rationale but not internal reasoning. ``` ### For executives High-level risks, required decisions, and business impact. ```markdown theme={null} Executive brief: What's the issue, why it matters, what you need from leadership ``` ## Controlling tone Specify the tone to match your situation and audience. **Professional variations:** * "Formal and conservative" (for traditional law firms) * "Professional but conversational" (for longtime clients) * "Firm but respectful" (for pushback) * "Collaborative problem-solving" (for partners) * "Direct and concise" (for busy executives) ## Special output instructions ### For redlines ```markdown theme={null} Show additions in [brackets] and deletions with strikethrough Include brief comment explaining each change ``` ### For risk assessment ```markdown theme={null} Use risk levels: High (must fix) | Medium (should address) | Low (nice to have) Include business impact for any High risk items ``` ### For negotiation planning ```markdown theme={null} Format as: Opening Position | Fallback | Walk-away Point Include brief rationale for each fallback ``` ## Common output problems and fixes | Issue | Problem | Fix | | ---------------------- | ------------------------------------------------------------ | ------------------------------------------------------------------------- | | Too much information | AI provides exhaustive analysis when you need a quick answer | Specify "Brief response" or "One sentence summary" | | Wrong format | Getting prose when you wanted a table | Start with "Create a table..." or "In table format..." | | Mixed audiences | Technical language for business audience | Explicitly state "For non-legal audience" or "Plain English only" | | Inconsistent structure | Different format for similar items | Provide template: "For each issue show: \[Issue] \| \[Risk] \| \[Action]" | ## The output checklist Every output instruction should answer: 1. **What format?** (table, bullets, prose) 2. **How much?** (length/quantity) 3. **What detail level?** (executive, working, technical) 4. **Who's reading?** (internal, external, technical, business) 5. **What tone?** (formal, conversational, firm) Add precision phrases like "cite sources," "prioritize by importance," or "focus on material issues only" to sharpen results further. ## Remember The goal isn't to get an answer — it's to get an answer you can use right away. Taking 30 seconds to specify format, length, and audience saves minutes of reformatting.