---
title: "Define a useful recurring result | Grafana Labs"
description: "Connect the recurring task to the decision its output supports."
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

# Start with the morning decision

The checkout summary should help you decide whether errors need investigation before the working day begins. That purpose gives the prompt a clear scope: one service, a recent time window, and evidence about requests and errors.

A broad request such as “check everything” leaves the scope and output unclear. A focused summary is easier to assess because you know which question the result should answer.

Useful recurring work has an identifiable reader, a repeated question, and data that can answer it. For this example, the reader is the checkout service owner and the question is what happened over the last 24 hours.