Data & Analytics · Agent family

AI Data and Analytics Agent Roles

Explore data and analytics roles that prepare, inspect, summarize, and communicate business data while preserving source context and decision boundaries.

Get StartedReview the workflow

Best for

  • Analysts and operators with recurring data preparation, reconciliation, summary, and reporting work
  • Decision makers who need transparent assumptions, source notes, and review before acting on findings

Typical inputs

  • Spreadsheets, exports, database extracts, metric definitions, reporting calendars, and comparison periods
  • Schema notes, filters, business rules, quality thresholds, audience needs, and visualization requirements

Input quality determines output quality. Source permissions, retention, and field-level access should be settled before the workflow begins.

Core workflow

Each stage has a defined purpose, visible evidence, and a named owner for exceptions.

1

Frame the request

Identify the question, source authority, metric definitions, and intended audience

2

Gather context

Inspect structure, missing values, types, duplicates, and comparability before analysis

3

Prepare the work

Calculate descriptive results, trends, segments, or report views with assumptions attached

4

Review and hand off

Present findings for domain review and separate observations from recommendations

Actions it can perform

  • Clean tabular inputs, reconcile fields, calculate defined measures, identify anomalies, and prepare visual summaries
  • Compare periods, segment records, document caveats, refresh dashboards, and assemble recurring narratives

Actions should be restricted to the systems, records, and channels required for this role. Broader access is not a substitute for a well-designed workflow.

Outputs

  • Analysis tables, quality reports, trend summaries, dashboard inputs, chart-ready datasets, and annotated spreadsheets
  • Metric narratives, anomaly lists, source notes, assumptions, and questions requiring subject-matter judgment

Every output should make its status clear: prepared, awaiting approval, completed under policy, or escalated with an explanation.

Role-specific configuration details

Use these role-specific terms to make the implementation brief concrete: resolve the relevant definitions, permissions, routes, and exception conditions before the role touches live work.

  • explore-data
  • analytics-roles
  • prepare-inspect
  • inspect-summarize
  • communicate-business
  • business-data
  • decision-boundaries
  • boundaries-turn
  • turn-scattered
  • scattered-operational
  • operational-data
  • consistent-analyses
  • reporting-artifacts
  • artifacts-without
  • without-presenting
  • presenting-uncertain
  • uncertain-findings
  • authoritative-business
  • business-decisions
  • decisions-spreadsheets
  • spreadsheets-exports
  • exports-database
  • database-extracts
  • extracts-metric
  • metric-definitions
  • definitions-reporting
  • reporting-calendars
  • comparison-periods
  • periods-schema
  • schema-notes
  • notes-filters
  • filters-business
  • business-rules
  • rules-quality
  • quality-thresholds
  • thresholds-audience
  • audience-needs
  • visualization-requirements
  • requirements-identify
  • authority-metric
  • intended-audience
  • audience-inspect
  • inspect-structure
  • structure-missing
  • missing-values
  • values-types
  • types-duplicates
  • comparability-before
  • before-analysis
  • analysis-calculate
  • calculate-descriptive
  • descriptive-results
  • results-trends
  • trends-segments
  • report-views
  • assumptions-attached

Human approval and escalation

Approval boundary

Humans approve metric definitions, exclusions, consequential interpretations, forecasts, financial conclusions, and changes to authoritative datasets.

Escalation rule

Missing lineage, inconsistent definitions, sensitive data, low-quality sources, and decisions beyond descriptive analysis go to a data or domain owner.

What remains under human control

  • Data owners set access, definitions, retention, quality rules, and authoritative-source policy
  • Analysts validate methodology and decide how findings affect financial, staffing, customer, or strategic decisions

Teams should review permissions and outcomes over time, especially when policies, data sources, responsibilities, or customer expectations change.

Recommended integrations

Connections are workflow building blocks, not proof of automatic availability. Confirm authentication, permissions, supported actions, and error handling during implementation.

Google WorkspaceReview integration scopeMicrosoft 365Review integration scopeAirtableReview integration scopeNotionReview integration scope

Example workflow

A weekly operations export is checked for schema drift and missing values, summarized against agreed metrics, and delivered with anomalies and caveats for an analyst.

The implementation should record the source, owner, decision boundary, and recovery route for each important stage. That makes the workflow easier to review and improve without hiding responsibility.

Related agents

Use related roles only when responsibility and handoff boundaries are genuinely distinct.

Related use cases

Explore outcome-led workflows that can combine this role with approved systems and human review.

Design a responsible AI Data and Analytics Agent Roles workflow

Define the sources, controls, connected tools, exceptions, and owners before implementation.

Get Started