# Final Artifact : Organizer Query Brief

## Artifact overview

- **Artifact name**: Organizer Query Brief
- **Audience**: Organizers, campaign staff, data volunteers, and teammates who need a clear starting point for working with a dataset
- **Purpose**: Turn a real organizing question into a documented BigQuery starting point
- **Format**: One-page written brief with a query sketch and plain-language explanation
- **Recommended length or size**: 250–400 words plus one query block or pseudocode block

## Required sections

- [ ] Title
- [ ] Organizing question
- [ ] Why this matters to the team
- [ ] Project, dataset, and table to inspect
- [ ] One starter query or query sketch
- [ ] Plain-language finding or expected finding
- [ ] Limitation or next question
- [ ] Source note

## Build-by-module plan

| Module | Artifact component | Learner output |
|---|---|---|
| 1 | Case theory | One organizer question and one-sentence explanation |
| 2 | Data location | Named project, dataset, and likely table |
| 3 | Table inspection | Schema notes and what the table appears to contain |
| 4 | Starter query | SELECT/FROM/LIMIT draft |
| 5 | Filtering plan | One useful WHERE condition |
| 6 | Summary insight | One grouped or counted finding |

## Plain-language explanation frame

> I looked at **[project.dataset.table]** to explore **[organizing question]**.
>
> My first SQL step was **[query action]**.
>
> The main thing this helps us see is **[pattern or expected pattern]**.
>
> This matters because **[team relevance]**.
>
> One limitation or next question is **[limitation]**.