General analytics
AuraScore 79/100

Data Governance and Tracking Telemetry Audit

Conduct a technical data quality and tracking schema audit to uncover telemetry discrepancies and schema drift across software platforms.

Deploy this template when data trust breaks between engineering, product, and analytics teams, or prior to migrating customer data platforms. It delivers a comprehensive assessment of event integrity and downstream impact.

Template

Role: Senior Analytics Engineer and Data Governance Architect specializing in modern data stacks and event instrumentation.

Context

  • Scope of Systems: {{platform_scope}}
  • Tracking Framework: {{tracking_framework}}
  • Reported Data Anomalies: {{known_data_anomalies}}
  • Downstream Models Affected: {{upstream_data_models}}
  • Impacted Stakeholder Groups: {{business_stakeholders}}
  • Governance Standard: {{compliance_standard}}

Task

Synthesize an enterprise data governance and telemetry audit report that catalogs tracking integrity failures across systems, diagnoses pipeline breakages, and outlines a governance remediation plan to restore metric trustworthiness.

Method

  1. Map the end-to-end event lifecycle from {{platform_scope}} client capture through ingestion into {{tracking_framework}}.
  2. Cross-reference documented schema definitions against {{known_data_anomalies}} to isolate syntax errors, missing properties, and event duplication.
  3. Measure the blast radius of unvalidated schema changes on transformation jobs and tables in {{upstream_data_models}}.
  4. Evaluate compliance risks and data privacy boundary controls in accordance with {{compliance_standard}}.
  5. Interview secondary impacts on operational decisions and dashboards relied upon by {{business_stakeholders}}.
  6. Classify each identified tracking defect by severity: Critical (broken pipelines), High (inaccurate attribution), and Medium (schema inconsistency).
  7. Formulate a technical implementation plan for schema enforcement, CI/CD telemetry testing, and automated alerting.

Constraints

  • MUST adhere strictly to the governance requirements specified under {{compliance_standard}}.
  • MUST NOT recommend total pipeline rewrites when targeted schema validation fixes suffice.
  • Every identified telemetry anomaly MUST link directly to at least one downstream model in {{upstream_data_models}}.
  • Maintain focus on technical data governance, schema structure, and ingestion fidelity.

Output format

Deliver an audit report formatted into the following sequential sections:

  1. Audit Executive Overview (max 150 words)
  2. Telemetry Ingestion & Health Scorecard (table: Platform, Ingestion Reliability, Schema Compliance, Defect Count)
  3. Critical Anomaly & Downstream Impact Catalog (max 400 words)
  4. Regulatory & Governance Risk Findings (max 250 words)
  5. Technical Governance Remediation Blueprint (numbered step-by-step phases with timelines)

Self-review

  • Are all listed anomalies connected to downstream business and analytical models?
  • Is the tone authoritative, technical, and objective?
  • Does the remediation blueprint account for both engineering validation and governance policies?
AuraScore breakdown
79/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering10/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

data-analytics
data-general
technology-software
data governance
telemetry audit
analytics engineering