Data & Analytics · Specialized agent role

Data Analyst Agent

The Data Analyst Agent supports preparing descriptive business analysis from defined metrics, traceable datasets, and explicit methodological assumptions. It works from approved datasets, data dictionaries, query extracts, reporting periods, business definitions, and comparison baselines, applies explicit operating rules, and makes incomplete or uncertain work visible instead of silently guessing.

Get StartedReview the workflow

Best for

  • Teams that repeatedly handle preparing descriptive business analysis from defined metrics, traceable datasets, and explicit methodological assumptions and can describe a dependable operating path
  • data analysts and domain decision makers who need consistent preparation, explicit ownership, and visible exception handling

Typical inputs

  • Authoritative inputs such as approved datasets, data dictionaries, query extracts, reporting periods, business definitions, and comparison baselines, with access restricted to what the role needs
  • Definitions, required fields, service expectations, approval thresholds, and checks for schema, missing values, duplicates, outliers, denominator choice, comparability, lineage, and metric definition

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

Confirm the request, responsible owner, permitted sources, and definition of completion for preparing descriptive business analysis from defined metrics, traceable datasets, and explicit methodological assumptions

2

Gather context

Collect approved datasets, data dictionaries, query extracts, reporting periods, business definitions, and comparison baselines and retain enough context to trace material facts and decisions

3

Prepare the work

Apply the configured rules, validate schema, missing values, duplicates, outliers, denominator choice, comparability, lineage, and metric definition, and prepare analysis tables, findings, assumptions, quality notes, reproducible calculations, and decision questions

4

Review and hand off

Send the result to data analysts and domain decision makers, pausing exceptions or consequential actions for an accountable person

Actions it can perform

  • Organize and prepare preparing descriptive business analysis from defined metrics, traceable datasets, and explicit methodological assumptions using the permitted sources and documented operating rules
  • Validate schema, missing values, duplicates, outliers, denominator choice, comparability, lineage, and metric definition, preserve source context, and route exceptions before consequential action

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

  • A reviewable package of analysis tables, findings, assumptions, quality notes, reproducible calculations, and decision questions with ownership, status, sources, and unresolved questions
  • An exception queue explaining which rule, field, source, or approval prevented safe completion

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.

  • data-analyst
  • supports-preparing
  • preparing-descriptive
  • descriptive-business
  • business-analysis
  • defined-metrics
  • metrics-traceable
  • traceable-datasets
  • explicit-methodological
  • methodological-assumptions
  • datasets-data
  • data-dictionaries
  • dictionaries-query
  • query-extracts
  • extracts-reporting
  • reporting-periods
  • periods-business
  • business-definitions
  • comparison-baselines
  • baselines-applies
  • applies-explicit
  • explicit-operating
  • operating-rules
  • makes-incomplete
  • visible-instead
  • silently-guessing
  • guessing-produce
  • produce-analysis
  • analysis-tables
  • tables-findings
  • findings-assumptions
  • assumptions-quality
  • quality-notes
  • notes-reproducible
  • reproducible-calculations
  • decision-questions
  • data-analysts
  • domain-decision
  • decision-makers
  • trace-back
  • authoritative-inputs
  • inputs-such
  • access-restricted
  • needs-definitions
  • definitions-required
  • required-fields
  • fields-service
  • service-expectations
  • schema-missing
  • missing-values
  • values-duplicates
  • duplicates-outliers
  • outliers-denominator
  • denominator-choice
  • choice-comparability
  • comparability-lineage

Human approval and escalation

Approval boundary

data analysts and domain decision makers approve consequential external actions, policy exceptions, irreversible record changes, and any output that represents a business commitment.

Escalation rule

Causal claims, forecasts, sensitive attributes, low-quality sources, conflicting definitions, and consequential automated decisions are routed with the source context, work completed, uncertainty, and requested decision intact.

What remains under human control

  • People define the source authority, permissions, quality rules, review gates, and acceptable boundaries for preparing descriptive business analysis from defined metrics, traceable datasets, and explicit methodological assumptions
  • data analysts and domain decision makers resolve ambiguity, approve consequential actions, and remain accountable for the final business outcome

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 recurring request involving preparing descriptive business analysis from defined metrics, traceable datasets, and explicit methodological assumptions is checked against schema, missing values, duplicates, outliers, denominator choice, comparability, lineage, and metric definition; routine preparation is completed, while exceptions are sent to data analysts and domain decision makers with the evidence needed to decide.

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 Data Analyst Agent workflow

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

Get Started