OpenKnowledgeBank
Bundle catalog

roles bundle

Business Intelligence Analyst

A free, open-source set of 10 Markdown files that gives an AI assistant practical guidance for the Business Intelligence Analyst role.

Use the Business Intelligence Analyst bundle to frame a decision, define metrics, reconcile source schemas and dashboards, review trends, and produce a BI brief without inventing data lineage, freshness, access, values, or causality.

Project-reviewed beta
Preview contents Download bundle Inspect source

10 Markdown files · 1,019 words · no signup · CC-BY-4.0

Inspect before downloading

See what is inside

These previews come from the published bundle files, so you can judge the method and writing before using it.

Role guide

Business Intelligence Analyst

- Frame the requested decision and required evidence. - Reconcile domain records, definitions, dates, states, and owners.

Read the file

Overview

Business Intelligence Analyst Overview

ONET describes business intelligence analysts as querying repositories, generating reports, identifying patterns and trends, testing consistency, and supporting recommendations.

Read the file

Workflow

Business Intelligence Analyst source-backed Triage

1. State the requested decision or deliverable. 2. Inventory evidence: business question and decision, metric and dimension definitions, source schemas and grain, keys, lineage, and refresh.

Read the file

Template

Business intelligence analysis and reconciliation brief

State the decision, recommendation, or draft purpose.

Read the file

Is this bundle right for your task?

Who it is for

  • Business intelligence analysts, analytics teams, dashboard owners, data engineers, and decision-makers reviewing operational metrics

When to use it

  • A business question needs precise metric, dimension, grain, filter, date, and decision definitions before analysis begins.
  • Two dashboards, queries, or exports disagree and schema, key, lineage, refresh, access, and calculation evidence must be reconciled.
  • A trend or KPI review needs a decision-ready brief that separates verified observations from assumptions and causal hypotheses.

What you need to provide

  • Business question and decision, metric and dimension definitions, source schemas and grain, entity keys, lineage, refresh state, filters, and access rules.
  • Queries, dashboard or export evidence, comparison periods, validation sources, known transformations, data-quality issues, and owner approvals.

Tasks and expected outputs

Questions it helps answer

  • Prepare business intelligence analysis and reconciliation brief without fabricating local facts.
  • Separate verified, provided, assumed, and missing evidence.
  • Produce review-ready decisions with explicit verification and approval boundaries.

What it helps produce

  • Business intelligence analysis and reconciliation brief

Practical example

Use it with an agent

Load the bundle as context, provide the evidence named above, then adapt this example to your situation.

Load the Business Intelligence Analyst bundle and provide the decision question, competing dashboard exports, metric definitions, source schemas, grain and keys, filters, refresh timestamps, lineage notes, and validation owner. Ask the agent to reconcile the discrepancies, identify missing evidence, and produce a BI analysis and reconciliation brief without asserting unsupported causes.

Context path: bundles/roles/business-intelligence-analyst

What the bundle includes

Frameworks

  • source-evidence matrix
  • metric-lineage matrix
  • qualified-review gate

Evaluations

  • Business Intelligence Analyst source verification check

Sources used to build this bundle

These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.

O*NET OnLine — Summary / 15 2051.01 Role or occupation reference for Business Intelligence Analyst scope and source checks.

Limitations and safe use

Do not use this for

  • Inventing tables, fields, joins, metric values, dashboard state, data freshness, permissions, or causal conclusions, or running production queries and changing dashboards without confirmation.

Known limitations

  • Use as occupational context; schemas, metrics, grain, lineage, refresh, permissions, report state, and values require inspected local evidence.
  • Task-specific work requires current evidence for business question and decision, metric and dimension definitions, source schemas and grain, keys, lineage, and refresh state, filters and access rules, query or export evidence, validation and owner approvals.
  • Do not infer tables, fields, joins, metric values, dashboard state, data freshness, access, causal claims.

Safety notes

  • Minimize personal, customer, employee, financial, credential, and other sensitive data.
  • Require explicit confirmation before data access, production queries, dashboard changes, sensitive data, or consequential business reliance.
  • Route legal, privacy, security, compliance, financial, employment, and other qualified judgments to accountable reviewers.

Next step

Inspect it before relying on it

Download the bundle for use, review its source files and evidence, or read the agent guidance. If the project is useful, starring the repository helps others discover it.

Download Review source Agent guidance Star on GitHub