A city clerk wants help exploring a CSV of 311 ticket volumes for operational insights. Which Copilot capability fits best?

City clerks exploring a CSV of 311 ticket volumes need Analyst-style assistance for reasoning over tabular operational data and exploring insights. Analyst is the Copilot capability class oriented to tables, measures, trends, and operational pattern finding—exactly what a volume CSV demands when the clerk wants insight rather than a prose policy brief or meeting summarization for transcribing clerk hearings and drafting follow-up emails.

Meeting summarization for transcribing clerk hearings and drafting follow-up emails fails the use case: it captures spoken dialogue and follow-up tasks but does not analyze ticket-volume tables. Presentation generation for creating council briefing slides from existing operational reports fails the use case: it formats slide decks from finished reports rather than reasoning over tabular operational data and exploring insights in the CSV. Document translation for converting policy memos between languages for residents fails the use case: it changes the language of policy text but does not produce analytical insight from ticket volumes.

Exam caveat: Distinguish Analyst (tabular operational insight) from Researcher (multi-source long-form investigation) and from ordinary chat rewrites. Data must remain within authorized municipal systems; do not export 311 extracts to unapproved consumer tools.

Operational check: Open the 311 volume CSV in an Analyst-capable Copilot experience with a licensed clerk account, ask for peak-hour or category patterns, and verify insights reference the table—not meeting summarization or document translation.