# Environmental Impact Assessments Summarization Prompt

## Background & Context
Environmental Impact Assessments (EIAs) are formal studies that evaluate the potential environmental, social, and economic impacts of proposed projects or developments. They are typically prepared by environmental consultants, engineering firms, or specialized EIA practitioners on behalf of project developers or government agencies. These reports are consumed by regulatory authorities, government decision-makers, project stakeholders, affected communities, environmental organizations, and the general public. EIAs serve as critical tools in the environmental permitting process and sustainable development planning, helping to identify mitigation measures for negative impacts before project implementation.

## Report Structure & Components
Summarize the following common sections found in Environmental Impact Assessments:

1. Executive Summary
2. Project Description and Objectives
3. Legal and Regulatory Framework
4. Methodology and Scope
5. Baseline Environmental Conditions (physical, biological, socioeconomic)
6. Impact Identification and Analysis
7. Significance Assessment of Impacts
8. Mitigation Measures and Management Plans
9. Alternatives Analysis
10. Public Consultation and Stakeholder Engagement
11. Environmental Management Plan (EMP)
12. Monitoring and Evaluation Framework
13. Conclusions and Recommendations
14. Technical Appendices (data, maps, detailed studies)

## Critical Information to Extract
Focus on extracting and highlighting:

1. Project scope, size, and key components
2. Significant environmental impacts identified (both positive and negative)
3. Magnitude and likelihood of each major impact
4. Critical ecosystems, species, or resources affected
5. Key mitigation measures proposed and their expected effectiveness
6. Residual impacts after mitigation
7. Compliance status with relevant environmental standards and regulations
8. Monitoring requirements and responsibilities
9. Areas of public concern identified during consultation
10. Major uncertainties or gaps in assessment
11. Expert recommendations and conditions for approval
12. Cumulative impacts with other existing or planned projects

## Stakeholder Priorities
Address the following stakeholder needs:

1. **Regulators and Decision-makers**: Compliance with regulations, significant impacts requiring attention, adequacy of mitigation measures, justification for approvals or conditions
2. **Project Developers**: Key required actions, timeline implications, cost implications for mitigation, critical risks to address
3. **Environmental Organizations**: Severity of impacts, adequacy of mitigation, alternatives considered, protection of sensitive areas
4. **Local Communities**: Direct impacts on community wellbeing, health concerns, socioeconomic effects, cultural heritage
5. **Investors/Financial Institutions**: Environmental risks, liability considerations, compliance with international standards (e.g., IFC Performance Standards)
6. **Technical Staff**: Methodology soundness, data quality, technical feasibility of mitigation measures

## Output Format Guidelines
Structure the summary as follows:

1. **Executive Brief** (250-300 words): High-level overview of project, major findings, and critical recommendations
2. **Impact Dashboard**: Visual representation of impact significance across environmental domains (use tabular format with color-coding if possible: High/Medium/Low impact)
3. **Key Findings** (bullet points organized by environmental domain: air, water, biodiversity, social, etc.)
4. **Critical Mitigation Measures** (prioritized bullet points with implementation timeframes)
5. **Stakeholder Concerns and Responses** (concise summary of major issues raised and how addressed)
6. **Compliance Summary** (table format showing key regulations and compliance status)
7. **Decision-Critical Information** (bullet points highlighting information essential for approval decisions)
8. **Total summary length**: 1000-1500 words (excluding tables)

## Special Considerations
1. **Technical Terminology**: Define or simplify technical ecological terms, impact assessment methodologies, and environmental metrics (e.g., particulate matter concentrations, biodiversity indices)
2. **Uncertainty Communication**: Clearly indicate confidence levels in predictions and assessments
3. **Regional Context**: Consider regional importance of impacts (not just local significance)
4. **Temporal Dimensions**: Distinguish between construction, operational, and decommissioning phase impacts
5. **Cumulative Effects**: Pay special attention to how the project contributes to broader environmental changes in combination with other developments
6. **Cross-Sectoral Impacts**: Highlight interrelationships between environmental, social, and economic impacts
7. **Indigenous/Traditional Knowledge**: When present, include indigenous perspectives and traditional ecological knowledge
8. **Controversial Aspects**: Identify contentious issues where stakeholders disagree on impact significance or mitigation adequacy

## Sample Output Structure

# SUMMARY: [PROJECT NAME] ENVIRONMENTAL IMPACT ASSESSMENT

## EXECUTIVE BRIEF
[Concise overview of project purpose, location, scale, major findings, and key recommendations]

## IMPACT SIGNIFICANCE DASHBOARD
| Environmental Domain | Impact Level | Key Concerns |
|----------------------|--------------|-------------|
| Air Quality          | [High/Medium/Low] | [Brief description] |
| Water Resources      | [High/Medium/Low] | [Brief description] |
| Biodiversity         | [High/Medium/Low] | [Brief description] |
| Soil & Land          | [High/Medium/Low] | [Brief description] |
| Noise & Vibration    | [High/Medium/Low] | [Brief description] |
| Social & Community   | [High/Medium/Low] | [Brief description] |
| Cultural Heritage    | [High/Medium/Low] | [Brief description] |
| Economic             | [High/Medium/Low] | [Brief description] |

## KEY FINDINGS
**Air Quality**
* [Bullet points of significant findings]

**Water Resources**
* [Bullet points of significant findings]

[Continue for other domains]

## CRITICAL MITIGATION MEASURES
1. [Priority measure 1] - [Timeline] - [Responsibility]
2. [Priority measure 2] - [Timeline] - [Responsibility]
3. [Continue with prioritized list]

## STAKEHOLDER CONCERNS AND RESPONSES
**Community Concerns**
* [Concern]: [How addressed in EIA]

**Regulatory Authority Input**
* [Input]: [Response in EIA]

[Other stakeholder groups as relevant]

## REGULATORY COMPLIANCE SUMMARY
| Regulation/Standard | Compliance Status | Gap Mitigation |
|---------------------|-------------------|----------------|
| [Regulation 1]      | [Status]          | [Measures]     |
| [Regulation 2]      | [Status]          | [Measures]     |

## DECISION-CRITICAL INFORMATION
* [Bullet points highlighting information essential for approval decisions]
* [Areas requiring special conditions or further study]
* [Timeline-critical elements]

Clear summaries of complex environmental impact assessments made easy with AI-powered analysis that highlights key findings and actionable recommendations.

Environmental impact assessments Summarization Prompt

# Financial Quarterly Reports Summarization Prompt

## Background & Context
Financial quarterly reports are formal documents issued by public companies every three months that detail their financial performance for that period. These reports are prepared by the company's finance department under the direction of the Chief Financial Officer (CFO) and are required by regulatory bodies such as the Securities and Exchange Commission (SEC) in the US (Form 10-Q). The primary consumers include investors, shareholders, financial analysts, creditors, board members, executive leadership, and regulatory authorities. These reports provide transparency into a company's financial health and are crucial for investment decisions, regulatory compliance, and strategic planning.

## Report Structure & Components
Most financial quarterly reports typically include:
1. Management Discussion and Analysis (MD&A)
2. Income Statement (Profit & Loss)
3. Balance Sheet
4. Cash Flow Statement
5. Statement of Shareholders' Equity
6. Notes to Financial Statements
7. Risk Factors and Forward-Looking Statements
8. Business Segment Results
9. Operational Highlights and Challenges
10. Comparison to Previous Quarters and Year-over-Year Performance
11. Guidance or Outlook for Future Quarters
12. CEO/CFO Statements or Commentary

## Critical Information to Extract
Prioritize these key data points and metrics:
- Revenue/Sales figures and growth rates (total and by segment)
- Gross margin, operating margin, and net profit margin
- Earnings per share (EPS) - both GAAP and non-GAAP/adjusted
- EBITDA and changes from previous periods
- Cash position and cash flow metrics
- Debt levels and changes in leverage ratios
- Significant changes in assets or liabilities
- Key operational metrics specific to the industry
- Notable one-time events or extraordinary items
- Management's explanation for performance variances
- Forward guidance or outlook statements
- Any revised forecasts or guidance changes
- Major strategic initiatives announced or updated

## Stakeholder Priorities
Different audiences need different insights:
- **Executives**: High-level performance against KPIs, competitive positioning, strategic implications
- **Investors/Shareholders**: EPS, dividend information, growth trajectory, return on investment
- **Financial Analysts**: Detailed financial metrics, trend analysis, comparison to industry benchmarks and projections
- **Board Members**: Overall financial health, risk factors, compliance issues, strategic alignment
- **Operations Teams**: Segment performance, operational efficiency metrics
- **Creditors/Lenders**: Liquidity ratios, debt servicing capacity, collateral values

## Output Format Guidelines
The summary should be structured as follows:
1. **Executive Summary** (3-5 sentences highlighting the quarter's most significant results and changes)
2. **Key Financial Highlights** (bulleted list of 5-7 critical metrics with YoY and QoQ comparisons)
3. **Performance by Business Segment** (concise breakdown of each major division's performance)
4. **Management Outlook** (brief summary of forward guidance and management commentary)
5. **Notable Items** (anything unusual, one-time events, or significant changes)
6. **Risk Factors** (emerging or changing risks highlighted in the report)
7. **Visual Elements to Reference** (mention key charts/graphs from the original report that illustrate important trends)

Recommended length: 1-2 pages (400-750 words) for comprehensive yet concise coverage.

## Special Considerations
- Maintain awareness of industry-specific financial metrics (e.g., ARR/MRR for SaaS companies, RevPAR for hotels, same-store sales for retail)
- Note the difference between GAAP and non-GAAP/adjusted figures and why they differ
- Be alert to "window dressing" techniques and overly optimistic projections
- Understand the cyclical nature of the business when evaluating quarter-over-quarter changes
- Pay attention to footnotes that may contain material information about accounting methods or one-time events
- Consider macroeconomic factors mentioned that affect performance (interest rates, currency fluctuations, etc.)
- Be sensitive to forward-looking statements and their disclaimers

## Sample Output Structure

# XYZ Corporation: Q2 2023 Financial Report Summary

## Executive Summary
XYZ Corporation reported Q2 2023 revenue of $X.XX billion, a X% increase year-over-year, exceeding analyst expectations by $XXM. Net income reached $XXX million (EPS of $X.XX), while facing challenges in [specific area]. Management has [raised/maintained/lowered] full-year guidance based on [specific factors].

## Key Financial Highlights
• Revenue: $X.XX billion (+X% YoY, +X% QoQ)
• Gross Margin: XX% (±X% YoY)
• Operating Income: $XXX million (+X% YoY)
• EPS (GAAP): $X.XX (+X% YoY)
• EPS (Adjusted): $X.XX (+X% YoY)
• Free Cash Flow: $XXX million (+X% YoY)
• Cash & Equivalents: $X.X billion (as of June 30, 2023)

## Performance by Business Segment
• Product Division A: $XXX million revenue (+X% YoY), driven by [specific factors]
• Service Division B: $XXX million revenue (-X% YoY), impacted by [specific factors]
• Regional Performance: [Notable geographic trends or variations]

## Management Outlook
Management [raised/maintained/lowered] full-year 2023 guidance, projecting revenue of $XX-XX billion and adjusted EPS of $X.XX-X.XX. Key strategic initiatives include [expansion plans, cost-cutting measures, new product launches, etc.].

## Notable Items
• Completed acquisition of [Company] for $XXX million
• Restructuring charges of $XX million related to [specific initiative]
• Foreign exchange headwinds impacted revenue by approximately X%
• Share repurchases of $XXX million (X million shares)

## Risk Factors
• Continued supply chain constraints expected to impact [specific area]
• Increasing competition in [market segment]
• Regulatory developments in [region/area] may affect future operations

## Key Visualizations to Reference
• Chart 4 (pg. 7): Five-quarter revenue trend showing seasonal patterns
• Figure 2 (pg. 12): Segment contribution margin comparison
• Table 3 (pg. 15): Cash flow year-over-year comparison

Transform complex quarterly financial reports into clear, actionable insights with AI summaries highlighting key metrics, trends, and performance indicators.

Financial quarterly reports Summarization Prompt

# IT Incident Response Logs Summarization Prompt

## Background & Context
IT incident response logs document cybersecurity events, attacks, system outages, and the corresponding response actions taken by IT security teams. These logs are typically created by IT security analysts, system administrators, and automated security tools during and after security incidents. The primary consumers of these summaries include IT management, CISOs, compliance officers, security teams for knowledge sharing, and occasionally executive leadership during significant incidents. The goal is to understand what happened, how it was addressed, and what can be prevented in the future.

## Report Structure & Components
IT incident response logs commonly contain:
- Incident identifier and classification (severity level, type)
- Timeline of events (detection time, response time, resolution time)
- Systems/assets affected
- Threat actor information (if identified)
- Initial alert/detection method
- Investigation steps and findings
- Containment and eradication actions
- Recovery procedures implemented
- Root cause analysis
- Business impact assessment
- Remediation recommendations
- Evidence collection notes
- Communication logs
- Compliance/regulatory implications

## Critical Information to Extract
Focus on extracting:
1. Incident severity and categorization
2. Key timeline metrics (time-to-detect, time-to-respond, time-to-resolve)
3. Attack vector or root cause
4. Extent of the impact (systems affected, data compromised)
5. Successful mitigation actions
6. Unresolved vulnerabilities or remaining risks
7. Critical recommendations for preventing recurrence
8. Resource requirements for full remediation
9. Compliance implications or reporting obligations
10. Relevant IOCs (Indicators of Compromise) for future detection

## Stakeholder Priorities
Different stakeholders need different elements:
- **Executives**: Focus on business impact, reputational risk, financial implications, regulatory exposure, and high-level remediation timelines
- **IT Management**: Emphasize resource allocation needs, root cause, technical debt implications, and team performance during response
- **Security Teams**: Detail technical specifics, attack methodology, evasion techniques used, effectiveness of security controls, and specific remediation steps
- **Compliance Officers**: Highlight regulatory requirements fulfilled/violated, documentation completeness, and evidence preservation status
- **External Auditors**: Summarize adherence to incident response procedures, documentation standards, and compliance requirements

## Output Format Guidelines
Structure the summary as follows:
1. **Executive Summary** (2-3 sentences on incident nature, impact, and status)
2. **Incident Overview** (bullet points with key facts)
3. **Timeline** (condensed chronological list of key events)
4. **Impact Assessment** (technical and business impacts in bullet form)
5. **Response Effectiveness** (brief assessment of what worked/didn't)
6. **Recommendations** (prioritized action items)
7. **Metrics Dashboard** (suggest key metrics to visualize: detection times, response times, affected systems)
8. **Compliance Status** (bullet points on regulatory implications)

Total length: 1-2 pages (500-750 words) for standard incidents; up to 3 pages for major incidents.

## Special Considerations
- Be aware of technical terminology differences between security domains (network security vs. application security vs. cloud security)
- Maintain confidentiality by not revealing sensitive security architecture details in the summary
- Distinguish between confirmed facts vs. suspected/unverified information
- Translate technical jargon appropriately based on the audience
- Understand the "kill chain" or "attack lifecycle" frameworks to properly contextualize incident stages
- Consider referencing relevant MITRE ATT&CK tactics and techniques when applicable
- Be aware that logs may contain inconsistencies in timestamps due to system clock variations
- Note that incident response documentation may be legally discoverable in certain scenarios

## Sample Output Structure

# INCIDENT SUMMARY: [Incident ID] - [Incident Name]

## Executive Summary
[2-3 sentences covering incident nature, impact scope, current status]

## Incident Overview
- **Classification**: [Type/Severity]
- **Detection**: [How/When discovered]
- **Duration**: [Start time → Resolution time]
- **Systems Affected**: [List of key systems]
- **Data Impact**: [Data affected/exposed]
- **Attribution**: [If known/suspected]

## Key Timeline
- **[Date/Time]**: Initial detection
- **[Date/Time]**: Response initiated
- **[Date/Time]**: Key response activities
- **[Date/Time]**: Containment achieved
- **[Date/Time]**: Recovery completed

## Impact Assessment
- **Technical Impact**: [Systems/services affected]
- **Business Impact**: [Operational/financial consequences]
- **User Impact**: [Number of affected users/services]

## Response Effectiveness
- **What Worked**: [Effective controls/procedures]
- **What Failed**: [Failed controls/procedures]
- **Detection Gaps**: [Monitoring improvements needed]

## Key Recommendations
1. [High priority action item]
2. [Medium priority action item]
3. [Long-term improvement]

## Compliance Implications
- [Any regulatory reporting requirements]
- [Documentation completeness status]
- [Evidence preservation status]

## Follow-up Actions
- **Owner**: [Name]
- **Due Date**: [Date]
- **Verification Method**: [How success will be measured]

Clear, actionable summaries of IT incident logs to expedite resolution, identify patterns, and strengthen security posture across your organization.

IT incident response logs Summarization Prompt

# Market Research Findings Summarization Prompt

## Background & Context
You are summarizing a market research report, which typically contains data-driven insights about market conditions, consumer preferences, competitive landscape, and future trends. These reports are usually created by market research teams, consulting firms, or specialized research agencies. They are consumed by product managers, marketing teams, business strategists, and executives who use these insights for decision-making regarding product development, marketing strategies, and business expansion.

## Report Structure & Components
Market research reports typically include:
1. Executive summary
2. Research methodology (sample size, data collection methods, timeframe)
3. Market overview and size estimations
4. Target audience/consumer analysis (demographics, psychographics, behavior)
5. Competitive landscape analysis
6. Market trends and growth projections
7. Consumer insights and preferences
8. Product/service performance metrics
9. Regional/geographical breakdowns
10. Opportunities and challenges
11. Recommendations

## Critical Information to Extract
Focus on extracting:
- Key market size figures and growth rates
- Primary consumer segments and their behaviors
- Major competitors and their market shares
- Significant market trends and emerging opportunities
- Critical consumer insights that impact product/service decisions
- Statistical highlights that demonstrate market movements
- Recommendations backed by data
- Methodology details that contextualize the reliability of findings

## Stakeholder Priorities
Different stakeholders need different aspects emphasized:
- **Executives**: Focus on market size, growth trajectory, major opportunities, competitive positioning, and ROI implications
- **Product Managers**: Emphasize consumer preferences, product performance metrics, unmet needs, and feature priorities
- **Marketing Teams**: Highlight consumer segments, messaging effectiveness, channel performance, and positioning opportunities
- **Sales Teams**: Concentrate on competitive differentiators, value propositions, and customer pain points
- **Investors**: Emphasize market growth potential, competitive advantages, and risk factors

## Output Format Guidelines
Structure the summary as follows:
1. **Executive Overview** (2-3 sentences on the report's primary purpose and key finding)
2. **Research Parameters** (Brief note on methodology, sample size, and timeframe)
3. **Key Market Insights** (5-7 bullet points highlighting the most significant findings)
4. **Consumer Analysis** (3-4 bullet points on target audience insights)
5. **Competitive Landscape** (3-4 bullet points on competitive positioning)
6. **Strategic Opportunities** (3-4 bullet points on actionable opportunities)
7. **Challenges & Considerations** (2-3 bullet points on potential obstacles)
8. **Data Highlights** (2-3 key statistics or visualizations that should be referenced)
9. **Recommendations** (3-5 bullet points on recommended actions)

Total length should be approximately 400-600 words.

## Special Considerations
- Maintain statistical accuracy – round numbers appropriately but preserve the integrity of growth rates and percentages
- Distinguish between correlation and causation in the findings
- Note the difference between stated consumer preferences versus observed behaviors
- Be aware of industry-specific terminology related to market sizing (TAM, SAM, SOM)
- Preserve the nuance of statistical significance when reporting findings
- Recognize potential research limitations (sample bias, timing issues, etc.)
- Translate technical marketing terminology into accessible language while preserving meaning

## Sample Output Structure

# SUMMARY: [Title of Market Research Report]

## Executive Overview
[Concise statement of report purpose and most significant finding]

## Research Parameters
- Methodology: [approaches used]
- Sample: [size and composition]
- Timeframe: [when conducted]

## Key Market Insights
- [Key insight about market size/growth]
- [Key insight about market trends]
- [Key insight about consumer behavior]
- [Key insight about competitive landscape]
- [Other significant findings]

## Consumer Analysis
- [Primary consumer segment and behavior]
- [Secondary consumer segment and behavior]
- [Notable consumer preference or pain point]

## Competitive Landscape
- [Market leader position and share]
- [Emerging competitor dynamics]
- [Competitive advantage opportunities]

## Strategic Opportunities
- [Primary opportunity identified]
- [Secondary opportunity identified]
- [Niche or emerging opportunity]

## Challenges & Considerations
- [Primary market challenge]
- [Secondary consideration]

## Data Highlights
- [Key statistic or data point to remember]
- [Second key statistic or visualization to reference]

## Recommendations
- [Primary recommended action]
- [Secondary recommended action]
- [Tertiary recommended action]

Quickly create clear, actionable summaries of market research reports with this AI-optimized prompt that highlights key trends and business insights.

Market research findings Summarization Prompt

# Product Usage Statistics Summarization Prompt

## Background & Context
Product usage statistics reports track how customers interact with software, applications, websites, or physical products. These reports are typically generated by product teams, data analysts, or automated analytics platforms (like Google Analytics, Mixpanel, or Amplitude). The primary consumers are product managers, UX designers, executives, marketing teams, and development teams who use this data to make product improvement decisions, guide development priorities, and identify user experience issues.

## Report Structure & Components
Most product usage statistics reports contain these common elements:
- User acquisition metrics (new users, user growth rates)
- Engagement metrics (active users, session duration, feature usage frequency)
- Retention metrics (return rate, churn rate, user lifetime)
- User behavior flows (common paths, drop-off points)
- Feature adoption rates and usage patterns
- Performance metrics (load times, error rates, crashes)
- User segmentation data (usage by demographics, user types, platforms)
- Conversion metrics (if applicable to the product)
- Time-based comparisons (week-over-week, month-over-month, year-over-year)
- Device/platform breakdown (mobile vs. desktop, iOS vs. Android, browser types)

## Critical Information to Extract
Focus on summarizing these high-priority elements:
1. Key performance indicators (KPIs) and whether they're trending positively or negatively
2. Significant changes in user behavior or adoption patterns
3. Top-performing features and underutilized features
4. Major drop-off points or friction areas in the user journey
5. Actionable insights that suggest specific product improvements
6. Comparison to previous time periods to highlight trends
7. Any anomalies or unexpected patterns that require attention
8. User segments that show notably different behavior patterns
9. Correlation between feature usage and user retention/satisfaction
10. Metrics that are significantly above or below targets or benchmarks

## Stakeholder Priorities
Different stakeholders need different information:
- **Executives**: Focus on high-level KPIs, business impact, and strategic implications. Emphasize growth trends and areas needing resource allocation.
- **Product Managers**: Highlight feature adoption rates, user flows, pain points, and specific improvement opportunities.
- **UX/Design Teams**: Emphasize user behavior patterns, drop-off points, and usability metrics.
- **Development Teams**: Focus on technical performance metrics, error rates, and feature-specific usage data.
- **Marketing Teams**: Highlight user acquisition channels, user segments, and conversion metrics.
- **Customer Success**: Emphasize usage patterns that correlate with customer satisfaction or churn risk.

## Output Format Guidelines
Structure the summary as follows:
1. **Executive Summary** (3-5 sentences highlighting the most critical insights and changes)
2. **Key Metrics Dashboard** (bullet-point list of primary metrics with trend indicators)
3. **Notable Findings** (3-5 bullet points on significant insights, organized by importance)
4. **User Behavior Highlights** (key patterns in how users interact with the product)
5. **Areas for Attention** (prioritized list of potential issues or opportunities)
6. **Segment Analysis** (brief overview of how different user groups are using the product)
7. **Recommendations** (2-3 data-backed suggestions for improvement)

Total length should be 500-750 words for a comprehensive yet concise summary.

## Special Considerations
- Distinguish between correlation and causation when interpreting usage patterns
- Be aware of sampling biases in data collection (such as survivorship bias)
- Consider the product lifecycle stage when interpreting metrics
- Note any recent product changes that might affect usage patterns
- Understand that metrics like "time spent" can indicate either engagement or frustration
- Consider seasonality effects for proper period-over-period comparisons
- Be mindful of privacy regulations (GDPR, CCPA) when discussing user data
- Differentiate between leading indicators (predictive) and lagging indicators (confirmatory)

## Sample Output Structure

# Product Usage Statistics Summary: [Product Name] - [Time Period]

## Executive Summary
[3-5 sentences capturing the most important trends and insights from the reporting period]

## Key Metrics Dashboard
- DAU/MAU: 0.XX [↑/↓ X% from previous period]
- New User Growth: X% [↑/↓ X% from previous period]
- Feature X Adoption: X% [↑/↓ X% from previous period]
- Retention (Day 7): X% [↑/↓ X% from previous period]
- Average Session Duration: X minutes [↑/↓ X% from previous period]

## Notable Findings
• [Primary insight with supporting data]
• [Secondary insight with supporting data]
• [Tertiary insight with supporting data]

## User Behavior Highlights
[Brief paragraph on key usage patterns and changes in user behavior]

## Areas for Attention
1. [Highest priority issue or opportunity with brief explanation]
2. [Secondary issue or opportunity with brief explanation]
3. [Tertiary issue or opportunity with brief explanation]

## Segment Analysis
[Brief analysis of how different user segments show varying usage patterns]

## Recommendations
1. [Primary recommendation based on data]
2. [Secondary recommendation based on data]
3. [Tertiary recommendation based on data]

Unlock actionable insights from product usage data with our AI prompt for generating clear, concise statistical summaries and trend analyses.

Product usage statistics Summarization Prompt

# Project Status Updates Summarization Prompt

## Background & Context
Project status updates are periodic reports that track the progress, challenges, and achievements of ongoing projects. They are typically created by project managers, team leads, or project coordinators and consumed by various stakeholders including executives, department heads, client representatives, and team members. These reports serve to maintain transparency, facilitate decision-making, identify risks early, and keep all parties aligned on project trajectory and expectations.

## Report Structure & Components
Common sections in project status updates include:
- Project identifier and basic information (name, ID, dates)
- Executive summary/overview of current status
- Milestone tracking and progress indicators
- Accomplishments since last report
- Current challenges or blockers
- Risk assessment and mitigation strategies
- Resource utilization and allocation
- Budget status and financial metrics
- Timeline adherence/schedule updates
- Key performance indicators (KPIs)
- Action items and next steps
- Dependencies on other teams/projects
- Change requests and scope modifications

## Critical Information to Extract
Focus on extracting and highlighting:
- Overall project health (on track, at risk, delayed)
- Percentage of completion against timeline
- Key achievements and deliverables completed
- Critical blockers requiring immediate attention
- Significant risks with high probability or impact
- Budget variances (planned vs. actual)
- Resource gaps or allocation issues
- Major changes to scope, timeline, or deliverables
- Decision points requiring stakeholder input
- Dependencies that may affect project timeline

## Stakeholder Priorities
Different stakeholders need different aspects emphasized:

**For Executives/Sponsors:**
- High-level status overview (red/amber/green indicators)
- Budget adherence and financial implications
- Strategic impact and business value tracking
- Major risks requiring organizational attention
- Resource allocation efficiency

**For Project Team Members:**
- Immediate priorities and action items
- Dependencies affecting their workstreams
- Technical challenges and proposed solutions
- Resource needs and constraints

**For Clients/External Stakeholders:**
- Progress against contracted deliverables
- Quality metrics and validation results
- Timeline for upcoming milestones
- Value being delivered
- Any changes affecting the end product/service

## Output Format Guidelines
Structure the summary as follows:
1. A one-paragraph executive summary (2-4 sentences) highlighting overall status
2. Visual status indicators (🟢 On Track, 🟡 At Risk, 🔴 Delayed) for key dimensions:
   - Schedule
   - Budget
   - Scope
   - Resources
   - Quality
3. Bulleted highlights of key accomplishments (3-5 points)
4. Bulleted key risks/issues (3-5 points)
5. A "Next Steps" section with upcoming milestones and critical actions
6. When relevant, mention any visualization elements from the original report that provide crucial insights (charts, Gantt diagrams, etc.)

Limit the entire summary to 300-500 words for readability.

## Special Considerations
- Use industry-standard project management terminology (e.g., critical path, velocity, burndown, sprint)
- Maintain consistent use of project-specific acronyms as they appear in the original document
- Preserve specific metric values exactly as reported (don't round or approximate)
- Distinguish between factual status elements and subjective assessments
- For technical projects, balance technical details with business implications
- For Agile projects, include sprint-specific metrics like velocity and burndown rates
- For waterfall projects, emphasize milestone completion and critical path updates

## Sample Output Structure

```
# Project Alpha Status Summary - July 2023

## Executive Summary
Project Alpha is currently 🟡 AT RISK due to integration challenges with the payment system vendor. Overall completion is at 65% against a planned 70%, with a two-week delay projected for the final delivery milestone. Budget remains within approved thresholds at 3% under forecast.

## Status Dashboard
- Schedule: 🟡 At Risk (2-week delay projected)
- Budget: 🟢 On Track (3% under forecast)
- Scope: 🟢 On Track (no change requests pending)
- Resources: 🟢 On Track (fully staffed)
- Quality: 🟡 At Risk (87% test coverage vs. 95% target)

## Key Accomplishments
• Completed user authentication module with 100% test coverage
• Deployed staging environment on cloud infrastructure
• Finalized UI designs for mobile application
• Completed security audit with no critical findings

## Critical Issues/Risks
• Payment gateway API integration delayed due to vendor documentation issues
• Performance testing shows 3-second response time vs. 1-second requirement
• Team knowledge gap in GraphQL implementation requiring additional training

## Next Steps
• Escalate payment gateway integration issues to vendor executive team (by July 15)
• Schedule additional performance tuning sprint (July 18-22)
• Begin GraphQL training program for development team (July 17)
• Prepare change request for timeline adjustment (by July 20)

The detailed burndown chart on page 7 of the report illustrates the technical debt accumulation requiring attention in the next sprint.
```

Improve your project reporting with AI assistance. Learn how to craft clear, concise status updates that highlight progress, challenges, and next steps effectively.

Project status updates Summarization Prompt

# Real Estate Market Trends Summarization Prompt

## Background & Context
Real estate market trends reports are analytical documents that track and interpret movements in property markets across residential, commercial, and industrial sectors. These reports are typically created by real estate research firms, economic consultancies, large brokerages (like Cushman & Wakefield, CBRE, JLL), government housing agencies, and financial institutions. They are consumed by investors, property developers, mortgage lenders, real estate agents, policymakers, urban planners, and individual buyers/sellers wanting to make informed decisions. These reports aim to provide actionable intelligence on where property markets are heading and why.

## Report Structure & Components
- Executive Summary/Key Findings
- Macroeconomic Indicators (interest rates, employment, GDP, inflation)
- Housing Market Metrics (median prices, inventory levels, days on market)
- Sales Volume and Transaction Data (month-over-month, year-over-year comparisons)
- Rental Market Analysis (vacancy rates, average rents, rental yield)
- Submarket Breakdown (geographical comparisons, neighborhood hotspots)
- Property Type Performance (single-family, multi-family, luxury, affordable)
- New Construction and Development Pipeline
- Demographic Trends (migration patterns, household formation)
- Financing Conditions (mortgage rates, lending requirements, financing availability)
- Market Forecasts and Projections
- Regulatory and Policy Impacts
- Investment Outlook and Opportunities

## Critical Information to Extract
- Percentage changes in home prices/rental rates (monthly, quarterly, annual)
- Supply-demand balance indicators (months of inventory, absorption rates)
- Transaction volume trends and what they signal
- Affordability metrics (price-to-income ratios, mortgage payment-to-income)
- Notable market shifts (buyer's vs. seller's market indicators)
- Regional variations and outperforming/underperforming submarkets
- Key drivers of current trends (economic factors, policy changes, demographic shifts)
- Forward-looking indicators (building permits, pending sales, housing starts)
- Risk factors and potential market disruptors
- Inflection points that suggest market direction changes
- Cap rates and investment return metrics for commercial properties
- Comparative performance against historical averages

## Stakeholder Priorities
**Investors/Developers:**
- ROI potential across different property types and locations
- Market timing indicators (buy/sell/hold signals)
- Risk assessment and potential market vulnerabilities

**Real Estate Professionals:**
- Pricing trends to inform client guidance
- Inventory changes affecting transaction potential
- Neighborhood-specific performance metrics

**Financial Institutions:**
- Default risk indicators and market stability factors
- Collateral valuation trends
- Lending opportunity segments

**Policymakers:**
- Affordability challenges and potential solutions
- Housing supply adequacy
- Economic impact indicators of housing market

**Individual Buyers/Sellers:**
- Price appreciation/depreciation trends
- Best/worst performing neighborhoods
- Optimal timing indicators for transactions

## Output Format Guidelines
Structure the summary in the following format:
1. **Executive Snapshot** (3-5 bullet points highlighting the most significant findings)
2. **Market Dynamics** (Short paragraph on supply-demand balance and pricing trends)
3. **Key Metrics Table** (Presenting core statistics with period-over-period changes)
4. **Segment Performance** (Bullet points on how different property types and regions are performing)
5. **Market Drivers** (Short paragraph explaining causal factors behind current trends)
6. **Forward Outlook** (3-4 bullet points on projected developments over next 6-12 months)
7. **Action Points** (Targeted recommendations for different stakeholders)

The entire summary should be between 500-750 words, emphasizing visual organization and scannable content.

## Special Considerations
- Pay attention to seasonality effects and adjust interpretations accordingly (e.g., winter slowdowns vs. market corrections)
- Distinguish between nominal and inflation-adjusted figures when analyzing price trends
- Note the difference between median and average prices and what each metric reveals
- Consider lagging vs. leading indicators when extracting insights on market direction
- Be aware that different geographic markets may be in different phases of the real estate cycle
- Recognize that luxury and entry-level markets often behave differently and require separate analysis
- Understand cap rate compression/expansion in commercial contexts and their implications
- Note that "months of inventory" has different benchmark meanings in different markets

## Sample Output Structure

# REAL ESTATE MARKET TRENDS SUMMARY: [REGION/DATE]

## EXECUTIVE SNAPSHOT
• [Key finding about price movement]
• [Key finding about inventory/supply]
• [Key finding about time on market]
• [Key finding about most significant market shift]

## MARKET DYNAMICS
[Concise paragraph analyzing the current balance between buyers and sellers, including how this affects pricing and transaction volume]

## KEY METRICS
| Metric | Current Value | QoQ Change | YoY Change | Trend |
|--------|--------------|------------|------------|-------|
| Median Sales Price | $ | %| % | ↑/↓ |
| Average Days on Market | | % | % | ↑/↓ |
| Inventory Level | | % | % | ↑/↓ |
| [Other key metrics] | | % | % | ↑/↓ |

## SEGMENT PERFORMANCE
• **Single-Family Homes**: [Brief performance summary]
• **Condos/Townhomes**: [Brief performance summary]
• **Luxury Market**: [Brief performance summary]
• **Rental Market**: [Brief performance summary]
• **Geographic Highlights**: [Top/bottom performing areas]

## MARKET DRIVERS
[Paragraph explaining the primary economic, demographic, and policy factors influencing current market conditions]

## FORWARD OUTLOOK
• [Projection about prices]
• [Projection about inventory]
• [Projection about market balance]
• [Projection about key risks/opportunities]

## ACTION POINTS
• **For Buyers**: [Strategic recommendation]
• **For Sellers**: [Strategic recommendation]
• **For Investors**: [Strategic recommendation]
• **For Real Estate Professionals**: [Strategic recommendation]

Get AI-generated summaries of complex real estate market reports highlighting key trends, price movements, and regional insights for faster decision-making.

Real estate market trends Summarization Prompt

# Risk Assessment Reports Summarization Prompt

## Background & Context
Risk assessment reports evaluate potential threats, vulnerabilities, and impacts to organizations, projects, or systems. They are typically created by risk management professionals, security analysts, compliance officers, or specialized consultants. These reports are consumed by executives, board members, project managers, operations teams, and regulatory bodies to inform decision-making about risk mitigation strategies, resource allocation, and compliance requirements.

## Report Structure & Components
- Executive summary
- Scope and objectives of the assessment
- Methodology and approach used
- Risk identification and categorization (strategic, operational, financial, compliance, etc.)
- Risk analysis with probability and impact ratings
- Risk evaluation and prioritization (risk matrices/heat maps)
- Current control measures assessment
- Risk treatment/mitigation recommendations
- Implementation timeline and resource requirements
- Appendices with detailed findings, data sources, and technical details
- Glossary of terms

## Critical Information to Extract
- Overall risk profile and highest-priority risks
- Probability and potential impact ratings for key risks
- Risk tolerance thresholds and which risks exceed acceptable levels
- Effectiveness of existing controls
- Gaps in current risk management approaches
- Recommended mitigation actions with clear priorities
- Required resources and timeline for implementing recommendations
- Compliance implications or regulatory requirements
- Changes in risk profile from previous assessments
- Key metrics like risk scores, threat levels, or vulnerability indices

## Stakeholder Priorities
- **Executives/Board Members**: High-level risk overview, strategic implications, resource requirements, and compliance status
- **Project Managers**: Specific risks affecting timelines, budgets, and deliverables
- **Operations Teams**: Detailed mitigation actions, implementation requirements, and tactical recommendations
- **Compliance Officers**: Regulatory requirements, compliance gaps, and documentation needs
- **Financial Teams**: Cost implications, insurance considerations, and financial risk exposure
- **IT/Security Teams**: Technical vulnerabilities, security threats, and system-specific controls

## Output Format Guidelines
The summary should be structured as follows:
1. A concise executive summary (3-5 sentences) highlighting the overall risk posture
2. A table or bulleted list of top risks with their ratings and status
3. A section on critical gaps or vulnerabilities requiring immediate attention
4. Key recommendations organized by priority (high, medium, low)
5. A brief implementation roadmap with timeline
6. Any significant changes from previous assessments (if applicable)

Use visual elements where appropriate, such as:
- Risk heat maps or matrices showing probability vs. impact
- Charts showing risk distribution by category
- Control effectiveness indicators
- Timeline graphics for implementation

## Special Considerations
- Maintain precise technical language when describing risks while explaining implications in business terms
- Distinguish between identified risks and actual incidents
- Preserve risk assessment methodology terminology (e.g., NIST, ISO 31000, FAIR)
- Consider regulatory and compliance frameworks relevant to the industry (GDPR, HIPAA, SOX, etc.)
- Address uncertainty and confidence levels in the assessment
- Balance qualitative and quantitative risk measures
- Recognize the difference between inherent and residual risk ratings

## Sample Output Structure

# RISK ASSESSMENT SUMMARY: [Project/Organization Name]

## EXECUTIVE SUMMARY
[3-5 sentence overview of overall risk posture, key findings, and critical recommendations]

## TOP RISK PROFILE
| Risk | Category | Probability | Impact | Risk Rating | Control Effectiveness |
|------|----------|------------|--------|------------|----------------------|
| [Risk 1] | [Category] | [H/M/L] | [H/M/L] | [Rating] | [Strong/Moderate/Weak] |
| [Risk 2] | [Category] | [H/M/L] | [H/M/L] | [Rating] | [Strong/Moderate/Weak] |
| [Risk 3] | [Category] | [H/M/L] | [H/M/L] | [Rating] | [Strong/Moderate/Weak] |

## CRITICAL VULNERABILITIES
- [Description of critical vulnerability 1 and its business implications]
- [Description of critical vulnerability 2 and its business implications]

## KEY RECOMMENDATIONS
**High Priority (Immediate Action):**
- [Specific recommendation with expected impact]
- [Specific recommendation with expected impact]

**Medium Priority (Next Quarter):**
- [Specific recommendation with expected impact]
- [Specific recommendation with expected impact]

**Low Priority (Within 12 Months):**
- [Specific recommendation with expected impact]
- [Specific recommendation with expected impact]

## IMPLEMENTATION ROADMAP
[Brief timeline with key milestones and resource requirements]

## CHANGES FROM PREVIOUS ASSESSMENT
[Key changes in risk profile, new risks, and improvements]

Enhance your risk assessment reports with AI-powered summarization, capturing key vulnerabilities and mitigation strategies in clear, actionable language.

Risk assessment reports Summarization Prompt

# Social Media Analytics Reports Summarization Prompt

## Background & Context
Social media analytics reports track and analyze performance, engagement, and audience metrics across social media platforms. These reports are typically created by marketing teams, social media managers, or digital analytics specialists. They are consumed by marketing executives, brand managers, content creators, community managers, and other stakeholders who need insights about their social media performance to inform strategy and resource allocation. These reports help organizations understand their online presence effectiveness, audience behavior, content performance, and competitive positioning in the digital space.

## Report Structure & Components
Social media analytics reports commonly include:
- Executive summary with key performance highlights
- Platform-specific metrics (Facebook, Instagram, Twitter, LinkedIn, TikTok, etc.)
- Audience demographics and growth statistics
- Engagement metrics (likes, comments, shares, saves)
- Content performance analysis
- Reach and impression data
- Competitor benchmarking
- Paid social media campaign results
- Conversion and click-through rates
- Trending topics and hashtag performance
- Sentiment analysis and brand health metrics
- Influencer collaboration performance
- Video performance metrics (views, completion rates)
- Community management statistics (response rates, response times)

## Critical Information to Extract
Focus on extracting these high-value metrics and insights:
- Overall performance trends (growth or decline in key metrics)
- Top-performing content with specific success metrics
- Significant changes in audience demographics or behavior
- Engagement rate benchmarks compared to previous periods
- ROI of paid campaigns
- Conversion metrics that tie social media to business outcomes
- Sentiment trends and reputation indicators
- Platform-specific insights showing comparative performance
- Emerging opportunities or challenges identified in the data
- Recommendations based on data insights

## Stakeholder Priorities
Different stakeholders need different information:
- **Executives**: High-level ROI, brand health metrics, competitive positioning, resource justification data
- **Marketing Managers**: Campaign performance, content strategy effectiveness, audience insights for planning
- **Content Creators**: Content performance patterns, engagement drivers, optimal posting times/formats
- **Community Managers**: Engagement metrics, response statistics, sentiment trends, audience growth
- **Sales Teams**: Lead generation metrics, conversion data, customer journey insights
- **Product Teams**: Customer feedback themes, product mention sentiment, feature requests

## Output Format Guidelines
Structure the summary as follows:
1. **Executive Summary** (3-5 bullet points highlighting the most significant findings)
2. **Performance Snapshot** (Brief table or bullet list showing key metrics and period-over-period changes)
3. **Platform Performance** (Concise breakdown of performance by platform, highlighting strengths and weaknesses)
4. **Content Insights** (What worked, what didn't, and why)
5. **Audience Insights** (Key demographic shifts or behavioral patterns)
6. **Campaign Performance** (If applicable)
7. **Action Recommendations** (3-5 data-backed suggestions)

Length: 400-600 words for comprehensive summaries; 200-300 words for quick briefs

## Special Considerations
- Differentiate between vanity metrics (likes, followers) and value metrics (engagement rates, conversions)
- Note that social platform algorithms and features frequently change, affecting metric comparability
- Account for seasonal variations in social media performance
- Recognize platform-specific terminology (e.g., "Reels" for Instagram, "Impressions" vs. "Reach")
- Be aware that sentiment analysis has limitations in detecting sarcasm and cultural nuances
- Understand that correlating social media activity with business outcomes often requires multiple data sources

## Sample Output Structure
```
# SOCIAL MEDIA ANALYTICS SUMMARY: [Period]

## EXECUTIVE SUMMARY
• [Key insight about overall performance]
• [Notable change or trend across platforms]
• [Most significant business impact finding]

## PERFORMANCE SNAPSHOT
• Total Engagement: XX (+/-X% from previous period)
• Audience Growth: XX (+/-X%)
• Top Platform: [Platform] with [key metric]
• Conversion Rate: X% (+/-X%)

## PLATFORM PERFORMANCE
• Instagram: [Key metrics and insights]
• Facebook: [Key metrics and insights]
• [Other platforms as relevant]

## CONTENT INSIGHTS
• Top Content: [Brief description with performance stats]
• Content Category Performance: [Which types performed best/worst]
• Optimal Posting: [Timing and format insights]

## AUDIENCE INSIGHTS
• Key Demographics: [Notable audience characteristics or changes]
• Behavior Patterns: [How audience is interacting]

## CAMPAIGN PERFORMANCE (if applicable)
• [Campaign name]: [Key results]
• ROI: [Return metrics]

## RECOMMENDED ACTIONS
1. [Data-backed recommendation]
2. [Data-backed recommendation]
3. [Data-backed recommendation]
```

Craft actionable summaries of social media analytics reports that highlight key trends, engagement metrics, and ROI insights for stakeholders.

Productivity Prompts