# Output Formats

## Universal Requirements
Every substantive deliverable should include:
- draft-only and human-review language;
- scope, review period, and files reviewed;
- data-quality and confidence limitations;
- a clear distinction between facts, assumptions, and judgment calls; and
- identified value at review, potential savings, and realized savings only if each is supported.

Use [references/output-selection-guide.md](references/output-selection-guide.md) when the user asks for the best output format or requests CSV, Excel, PDF, or PowerPoint-ready artifacts.
Must Apply [references/visual-output-rules.md](references/visual-output-rules.md) whenever generating PDF, Word, PowerPoint, or other visual artifacts.

Before generating any file artifact or final report, confirm or explicitly state:
- Deliverable type;
- Output format;
- Intended audience; and
- Confidentiality or anonymization requirements.

Do not use a safe default for output format or audience. Ask the user for both before generating the final deliverable.
Do not silently default to markdown, DOCX, PDF, XLSX, CSV, or PowerPoint-ready output.

## 1. Quick Audit Summary
Use when the user wants a concise invoice-review or pre-bill-review output.

Required sections:
1. Disclaimer;
2. Scope and files reviewed;
3. Top findings;
4. Key metrics;
5. Highest-priority line-item or category issues;
6. Questions that could change the outcome; and
7. Recommended next actions.

## 2. Detailed Audit Report
Use for dispute preparation, Legal Ops review, or a large invoice population.

Required sections:
1. Executive summary;
2. Data-quality assessment;
3. Compliance findings by category;
4. Rate and discount findings;
5. Staffing findings;
6. Budget and forecast findings if available;
7. Benchmarking findings;
8. Identified value and potential savings;
9. Issue log table; and
10. Appendix tables.

Recommended issue-log columns:
- Invoice ID;
- Line ID;
- Matter;
- Timekeeper;
- Issue category;
- Evidence summary;
- Confidence;
- Billed value;
- Challenged value; and
- Proposed action.

Use stable issue labels from [references/issue-taxonomy.md](references/issue-taxonomy.md). If the user wants a paste-ready review sheet, use [references/dispute-log-template.md](references/dispute-log-template.md).
For PDF or Word outputs, avoid wide dense tables if descriptions or assessments are verbose. Use short summary tables plus detailed issue cards or appendix tables instead.

## 3. MBR or QBR
Use for GC, legal leadership, management, finance, or procurement audiences.

Required sections:
1. Period summary;
2. Spend trend and budget view;
3. Law-firm comparison;
4. Compliance trend view;
5. Staffing and rate trend view;
6. Forecast and overrun risk;
7. Notable savings or value opportunities;
8. Watch items and relationship implications; and
9. Recommended actions for the next period.

Keep the tone executive-ready and avoid overloading the report with line-item detail in the main body.
Do not assume the user wants an MBR or QBR from a single invoice review unless they ask for it or ask for executive or quarter-level reporting.
For PowerPoint-ready outputs, do not use spreadsheet-like dense tables. Split content into summary slides and issue-highlight slides with wrapped bullets or cards.

## 4. Firm Comparison or Panel Review
Use when multiple firms are in scope.

Required dimensions:
- Spend;
- Budget predictability;
- OCG compliance;
- Staffing efficiency;
- Discount realization;
- Narrative quality;
- Rate governance; and
- Notable strengths, risks, and next actions.

## 5. Dispute or Negotiation Log
Use when the legal department wants challenge points or talking points.

For each issue, provide:
- What the charge is;
- Which rule, commercial term, or comparator is implicated;
- Why it may be challengeable;
- What clarification would resolve it; and
- Suggested next step.

Do not overstate certainty or accuse misconduct.
Prefer the CSV or markdown structures in [references/dispute-log-template.md](references/dispute-log-template.md) when the user wants an exportable log.
For PDF or Word, prefer issue cards or 4-to-5-column tables with short display labels rather than large multi-column tables containing long rationale text.

## 6. Executive Scorecard
Use when the audience wants an at-a-glance summary.

Suggested scorecard dimensions:
- Compliance;
- Rate discipline;
- Staffing discipline;
- Budget predictability;
- Narrative quality;
- Responsiveness or execution signals if supplied; and
- Overall confidence.

Always accompany the scorecard with a short explanation of the scoring basis.

## Optional Next Outputs
After delivering the requested output, it is appropriate to mention other useful deliverables the user may want next, such as:
- Issue log;
- Negotiation points;
- Executive scorecard;
- MBR; or
- QBR.

Executive scorecard, MBR, and QBR are important options to highlight when relevant.
Do not generate those extra outputs unless the user requests them or explicitly asks for bundled deliverables.
If the user expresses interest in one or more of them, ask the follow-up questions needed for that deliverable(s) before generating it.
