Define a query before writing it

Clarify grain, joins, filters, and expected output.

What this starting point does

Turn the supplied reporting need into a precise query specification. This is an editable instruction template, not a claim of tested performance on a particular model.

Make the inputs yours

• Reference material — fill {{MATERIAL}} with your own material, preserving line breaks where useful. This input is required for a filled prompt.

Reusable template

## Task
Turn the supplied reporting need into a precise query specification.

## Constraints
- Identify missing schema details.
- Clarify row grain, null handling, and date boundaries.
- Do not write final SQL until required relationships are confirmed.

## Output format
Output columns, source tables, join assumptions, filters, and clarifying questions

## Reference material
<source_material>
{{MATERIAL}}
</source_material>

A filled example

This example uses fictional demonstration material. It is an example prompt, not a generated answer or image.

## Task
Turn the supplied reporting need into a precise query specification.

## Constraints
- Identify missing schema details.
- Clarify row grain, null handling, and date boundaries.
- Do not write final SQL until required relationships are confirmed.

## Output format
Output columns, source tables, join assumptions, filters, and clarifying questions

## Reference material
<source_material>
Report the number of orders per customer. The date range, canceled-order handling, and table relationships are not yet confirmed.
</source_material>

Before using it

Review every instruction and replace the example material. Check that its constraints fit your task. The structural Analyzer can flag specific issues, but cannot verify facts or guarantee the quality of a model’s response.