A municipal permitting office needs reasoning over tabular operational data rather than a multi-source policy research brief. What should staff choose?

When a municipal permitting office needs reasoning over tabular operational data rather than a multi-source policy research brief, staff should choose Analyst. Analyst targets tables and operational metrics—permit throughput, backlog aging, fee collections—whereas Researcher targets grounded long-form investigation across documents. Matching the tool to tabular insight prevents using the wrong Copilot mode for the job.

Choosing Researcher when staff need reasoning and insight over tabular operational data fails by concept: Researcher targets grounded long-form investigation across documents, not tabular reasoning; Analyst is specifically for tables and owns this scenario. Using Researcher when staff need analysis across permit spreadsheets and tables fails by concept: Researcher targets grounded long-form investigation across documents, not spreadsheet metrics; Analyst owns the tabular lane. Choosing Analyst when staff need workflow approvals across tabular permit records fails by concept: this scenario calls for reasoning and insight over operational data, not approval routing; Analyst targets tabular insight, not workflow approvals.

Exam caveat: Many real tasks blend a short table glance with a policy cite—still pick the primary capability by the dominant need (tabular insight vs multi-source research). Confirm licenses and feature enablement for Analyst before promising it to permitting staff.

Operational check: Give permitting analysts one backlog spreadsheet task and one multi-ordinance research brief; confirm they select Analyst for the spreadsheet and Researcher for the brief, without using Researcher when staff need analysis across permit spreadsheets and tables or using Analyst when staff need workflow approvals across tabular permit records.