Intro to SQLfor Organizing
Module 6 · Summarizing and Sharing: GROUP BY, COUNT, Saved Queries › 6.5 Submit the brief
Subsection 6.5

Submit the brief

~3 min

Reading

You have now built the pieces of the Organizer Query Brief.

Your final brief should be one page. It should be clear enough for a nontechnical teammate to understand what you asked, where the data came from, what SQL you used, and what the result means.

The final brief includes:

  1. Organizing question.
  2. Project, dataset, and table.
  3. Table inspection notes.
  4. Starter query.
  5. Filter and sort logic.
  6. Summary insight.
  7. Saved or shared query link.

Use plain language. The goal is not to impress someone with syntax. The goal is to help an organizer, campaign director, program manager, or coalition partner make a decision.

The lesson wrap-up from the slide deck says you have covered:

  • Database structures and the role of SQL.
  • Basic SQL grammar, syntax, and punctuation.
  • SQL's SELECT statement with WHERE clauses.
  • Additional SQL commands and concepts, including DISTINCT, COUNT, AND, OR, NOT, and NULL values.

Reflection questions

  • What was the most useful SQL feature you learned?
  • How will you apply it to your daily workflows?
  • What question can your team now answer faster because of this query?

Final submission frame

My organizing question was: [question]
I used this table: [project.dataset.table]
One row represents: [plain-language row meaning]
My query filters for: [WHERE logic]
My query summarizes by: [GROUP BY field]
The main finding is: [plain-language result]
This matters because: [organizing decision]
Saved/shared query link: [link]

This is the final step. Fill in the plain-language finding, run through the checklist, and your brief is done.

Plain-language finding template

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]. This matters because [team relevance]. One limitation or next question is [limitation].

Final checklist : every section of the brief

  • ☐ Title
  • ☐ Organizing question (Module 1)
  • ☐ Why this matters (Module 1)
  • ☐ Project, dataset, table (Module 2)
  • ☐ Table inspection notes (Module 3)
  • ☐ Starter query (Module 4)
  • ☐ Filter and sort (Module 5)
  • ☐ Summary insight : grouped count, sum, or average (Module 6)
  • ☐ Plain-language finding (Module 6)
  • ☐ Limitation or next question (Module 6)
  • ☐ Source note (where the table came from)
Knowledge check

Filter the groups, not the rows

You want the count of signups per zip code, but only for zip codes with more than 50 signups. Which two clauses do you need together?

You earned the Brief Finisher badge

You can group, count, filter groups with HAVING, save and share queries, and write a plain-language finding for a non-technical reader. You completed the full loop from organizing question to documented finding.

What we covered (deck slide 53)

  • Database structures and the role of SQL.
  • Basic SQL grammar, syntax, and punctuation.
  • SELECT statements with WHERE, ORDER BY, GROUP BY, and HAVING.
  • DISTINCT, COUNT, SUM, AVG, MIN, MAX, AND, OR, NOT, LIKE, and NULL handling.

Done. Submit your Organizer Query Brief and explore the rest of the DatosLab Courses catalog when you're ready for joins, advanced aggregations, and storytelling.

Back to course overview