Separate technical data into an executive appendix

Extract dense technical metrics and background data into a structured appendix while keeping your primary memo strictly under one page.

You getExecutive Brief, appendix Directory and full Appendix Items

Prompt

Prompt
Act as an executive editor. Review the text provided and separate it into two clean parts: a lean, one-page executive brief and a reference appendix.

Rules:
- Keep only core conclusions, strategic impacts, and key decisions in the main brief.
- Move technical methodologies, raw figures, calculation breakdowns, and historical context into the appendix.
- Link each appendix item to the main brief using simple cross-references (e.g., "See Appendix A").
- Do not invent any numbers, quotes, or findings; use only what is provided.

Output format:
1. Executive Brief (Title, Key Takeaways, Strategic Recommendation)
2. Appendix Directory (Alphabetical list of appendix sections)
3. Full Appendix Items (Detailed data organized under clear headings)

Here is the draft report:

Example output

Example for: an internal quarterly infrastructure cost audit

1. Executive Brief

Key Takeaways

  • Cloud hosting costs increased by 28% quarter-over-quarter, driven primarily by unindexed database queries and stale dev environments.
  • Immediate migration of dormant storage tiers will reduce monthly expenditure by $14,000 starting next billing cycle (See Appendix A).
  • Long-term architectural fixes require a dedicated two-week sprint in Q3 to avoid projected overages of $45,000 by year-end (See Appendix B).

Strategic Recommendation
Approve the automated storage lifecycle policy immediately and schedule the engineering remediation sprint for August.


2. Appendix Directory
  • Appendix A: Storage Tier Cost Breakdown
  • Appendix B: Engineering Hours and Projected Overages

3. Full Appendix Items

Appendix A: Storage Tier Cost Breakdown

  • Hot storage active volume: 142 TB at $0.023/GB ($3,266/mo)
  • Cold archival candidates: 89 TB at $0.004/GB ($356/mo vs. current $2,047/mo)
  • Estimated net savings upon transition: $1,691/mo on primary assets, combined with idle cluster decommissioning for $14,000 total monthly run-rate reduction.

Appendix B: Engineering Hours and Projected Overages

  • Current run-rate trajectory: $62,000/mo baseline expanding to $77,000/mo by November without query optimization.
  • Remediation scope: 2 senior backend engineers for 80 hours total.
  • Capitalized labor cost: $11,200 against $45,000 projected unbudgeted overage.
Written by AI from this prompt. Your results will vary.

Paste your long draft directly after the prompt into ChatGPT, Claude, or Gemini. For a follow-up, ask the model to format the appendix tables into markdown or suggest which appendix sections can be cut entirely.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Writing