Analysis

Explain A Data Anomaly In A Report

Writes up a spike, drop, or unusual pattern the way an analyst should, starting from the anomaly description, time range, affected metrics, magnitude, and supporting data. States what happened in one sentence, quantifies the business impact beyond a percentage change, presents likely causes with evidence, rules out false positives like seasonality or pipeline bugs, and recommends both immediate action and prevention — tailored to a chosen audience and tone.

Prompt
Write a report explaining this data anomaly:

What happened: {anomaly_description}
When: {time_range}
Affected metric(s): {affected_metrics}
Magnitude: {magnitude}

Investigation data:
{supporting_data}

The report should:
1. State what happened in a single sentence
2. Quantify the business impact, not just the percentage change
3. Present the most likely causes with supporting evidence
4. Rule out common false positives (seasonality, pipeline issues, one-time events)
5. Recommend any immediate actions
6. Suggest preventive measures for catching this sooner next time
7. Note whether this changes any existing forecasts or targets

Write it for {audience} in a {tone} tone.
Download .md

Variables