Build a pre-send data check for recurring reports

Create an automated pre-flight checklist to stop recurring reports from sending broken data. Use this to catch expired tokens, schema shifts, and null records.

Prompt

Prompt
Act as a reporting operations lead. Create a pre-send validation checklist and automation rule set to catch broken data, schema changes, and expired tokens before scheduled reports ship to stakeholders.

Rules:
- Focus on the 4 most common silent failures: authentication expiration, schema alterations, missing values, and abnormal row variance.
- Define clear threshold conditions for each check (pass vs. fail criteria).
- Include explicit halt-and-notify instructions for automated email dispatch tools.

Output format:
### 1. Pre-Flight Validation Rules (Table: Check Name, Failure Condition, Action)
### 2. Alert & Halt Sequence (Automated fail-safe workflow)
### 3. Stakeholder Fallback Notification Template

Example output

1. Pre-Flight Validation Rules
Check NameFailure ConditionAction
Connection & AuthAPI response != 200 or token expiry < 24 hoursAbort job, trigger high-priority alert
Schema ConsistencyMissing expected columns or data type shiftHalt dispatch, log altered column names
Row Count VarianceRow count deviates by > 25% from 4-week averagePause report, mark for manual sign-off
Null Rate BreachPrimary key or critical metric column nulls > 0%Block send, dump null row IDs to error log
Timestamp FreshnessMax timestamp in source data is > 30 hours oldStop delivery, notify pipeline engineer
2. Alert & Halt Sequence
  1. Run the validation script 45 minutes prior to scheduled stakeholder dispatch.
  2. If any check fails, immediately pause the downstream email distribution task.
  3. Send an automated alert to the #report-ops Slack channel detailing the failing check name, run ID, and raw error.
  4. If unresolved within 30 minutes, automatically trigger the fallback delay notice to report subscribers.
3. Stakeholder Fallback Notification Template

Subject: Delay Notice: [Report Name] Delivery
Body:
Good morning,

The scheduled delivery of the [Report Name] is delayed while our engineering team verifies source data updates. We anticipate publishing the completed figures by [Target Time].

Thank you for your patience,
Operations Reporting Team

Written by AI from this prompt. Your results will vary.

Run this prompt directly in ChatGPT, Claude or Gemini without edits. To adapt it to your company, follow up with the names of the tools you use, such as Tableau, Looker, BigQuery, or Slack.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Automation & Workflows