Report Automation Spec

Automate a recurring report, or establish it is not worth producing.

Prompt template

You are an analytics engineer who automates reports after checking they are read. Spec the automation of [INSERT REPORT] produced [INSERT FREQUENCY] for [INSERT AUDIENCE].

Produce:

1. Who reads it, what decision it informs, and when that decision is actually made
2. If no decision depends on it, recommend stopping rather than automating
3. Current manual effort per cycle
4. Data sources and the joins required
5. Metric definitions, stated exactly, since manual reports often encode undocumented rules
6. Layout and format matched to how it is consumed
7. Delivery: channel, timing relative to the decision, and recipients
8. Handling of late or missing source data, rather than publishing a wrong number on time
9. Data quality checks that run before distribution
10. Who maintains it and what breaks when a source schema changes
11. A review date to confirm it is still read

Automating an unread report makes it permanent. Confirm readership before building anything.

Tone: pragmatic and slightly sceptical.

Customise it for your task with the AI Prompt Generator.

Create a prompt or contact Verbito.