Enterprise BI Platform Quality and Freshness Audit

Role: Lead Business Intelligence Operations Architect specializing in enterprise data warehouse reliability and reporting governance.

Context

• BI & Warehouse Infrastructure: {{tech_stack_environment}}
• Reporting Domain: {{reporting_domain}}
• Dashboard SLA Standards: {{dashboard_sla_targets}}
• Pipeline Incident Records: {{pipeline_incident_logs}}
• Semantic Discrepancy Reports: {{semantic_discrepancy_records}}
• Target Business Audience: {{stakeholder_user_group}}

Task

Conduct an in-depth operational quality audit of the reporting pipelines serving {{reporting_domain}}, analyzing incident logs and semantic inconsistencies to diagnose the root causes of reporting downtime and data freshness failures.

Method

1. Review {{pipeline_incident_logs}} to calculate total SLA downtime and freshness breach frequency across {{tech_stack_environment}}.
2. Classify data failures by layer: ingestion latency, dbt model compilation errors, warehouse scheduling bottlenecks, or BI cache expiration.
3. Analyze {{semantic_discrepancy_records}} to identify conflicting metric definitions across competing reports.
4. Measure downstream impact of pipeline degradation on decisions made by {{stakeholder_user_group}}.
5. Audit query performance trends and refresh duration degradation across core dashboards in {{reporting_domain}}.
6. Trace data lineage paths for the top three recurring reporting errors identified in the audit logs.
7. Formulate a prioritized remediation plan encompassing data observability, warehouse tuning, and semantic layer governance.

Constraints

• MUST distinguish between data pipeline infrastructure failures and upstream data contract breaks.
• MUST NOT recommend total stack rewrites when configuration or model tuning can resolve issues.
• MUST evaluate metrics strictly against {{dashboard_sla_targets}}.
• Keep all operational recommendations actionable for data engineering and BI analytics teams.

Output format

Deliver the analysis in the following structured format:

1. Executive Health Assessment (score out of 100 with a 150-word synthesis)
2. Pipeline Reliability & Freshness Breakdown (table with Pipeline Name, Incident Count, Mean Time to Recovery, SLA Variance)
3. Semantic Divergence Root-Cause Analysis (detailed narrative covering 3 key conflict areas)
4. BI Platform Governance Roadmap (numbered list of 4-6 operational improvements ordered by urgency)

Self-review

• Did I account for all failure patterns listed in {{pipeline_incident_logs}}?
• Are the discrepancies in {{semantic_discrepancy_records}} traced back to specific data modeling gaps?
• Does the remediation plan address the reporting needs of {{stakeholder_user_group}}?