Skip to content

Example Everything on this site is sample data — one of the configurations this template ships with, built from the same repository.

Example: Program / cohort portal

Data Learning Cohorts

What our teams built with data

Browse capstone projects from every cohort — the question each team asked, the methods they used, and the dashboards, posters and write-ups they produced.

6 team projects 2 cohorts 5 with interactive dashboard

Browse by

Find team projects the way you think about them

  • Dashboard mock with a ranked bar chart of interpreter requests by language and a small grid of requests by hour of day.
    Featured Storytelling

    Which languages our front counters actually need

    Headline finding: Requests named 14 languages; the four we staffed for covered 62% of them

    Turned two years of interpreter request logs into a dashboard that shows which languages are asked for, at which counters, and at which hours.

    • Tableau
    • SQL
    • 2 more methods & tools
    Skills practiced: Visualization Skills practiced: Stakeholder interviews1 more
  • Two survival curves over twelve months showing repeat-violation-free share staying near 88 percent with an early re-inspection and falling to 67 percent without one.
    Featured Civic

    How soon does a critical violation come back?

    Headline finding: A re-inspection within 30 days cut the one-year repeat rate from roughly one in three to one in eight

    Measured how long facilities go after a critical inspection violation before the next one, and whether an early re-inspection changes that.

    • Survival analysis
    • Python
    • 2 more methods & tools
    Skills practiced: Statistics Skills practiced: Data cleaning1 more
  • Bar chart of missed-appointment rate by booking lead time, rising from 9 percent within a week to 24 percent beyond four weeks.
    Essentials

    Booking lead time and missed appointments

    Headline finding: Appointments booked more than three weeks out were missed almost twice as often as those booked within a week

    Tested whether how far ahead an appointment is booked predicts whether it is kept, using two years of de-identified scheduling counts from three community clinics.

    • Logistic regression
    • R
    • 2 more methods & tools
    Skills practiced: Data cleaning Skills practiced: Statistics1 more
  • Reading 1,800 survey comments without reading 1,800 comments

    Headline finding: Three themes covered 71% of comments; cost was named twice as often as opening hours

    Coded two years of open-ended community survey answers into a small set of themes, and published the codebook so the next survey can be compared with this one.

    • Qualitative coding
    • Python
    • scikit-learn
    • 1 more methods & tools
    Skills practiced: Data cleaning Skills practiced: Stakeholder interviews1 more
  • Line chart of weekly open permit reviews across a year with a shaded forecast band widening over the final eight weeks.
    Essentials

    Forecasting the permit review backlog

    Headline finding: A two-week staffing dip in March explained most of the backlog that was still there in July

    Built a weekly forecast of the permit review queue so the licensing team can see a backlog forming instead of discovering it two months later.

    • Time series
    • Python
    • 2 more methods & tools
    Skills practiced: Statistics Skills practiced: Automation1 more
  • Horizontal stage chart of median days per step, with the awaiting-verification stage at nine days dwarfing five other stages.
    Civic

    Where the two weeks go in a records request

    Headline finding: Mail-in requests spent 9 of their 14 days in a single hand-off between two systems

    Reconstructed the full path of a mailed-in vital records request from timestamps and found that most of the wait happened in a queue nobody owned.

    • Process mining
    • SQL
    • 2 more methods & tools
    Skills practiced: Data cleaning Skills practiced: Automation2 more

    Last confirmed Jun 2025

  • Dashboard mock with a ranked bar chart of interpreter requests by language and a small grid of requests by hour of day.
    Featured Storytelling

    Which languages our front counters actually need

    Headline finding: Requests named 14 languages; the four we staffed for covered 62% of them

    Turned two years of interpreter request logs into a dashboard that shows which languages are asked for, at which counters, and at which hours.

    • Tableau
    • SQL
    • 2 more methods & tools
    Skills practiced: Visualization Skills practiced: Stakeholder interviews1 more
  • Two survival curves over twelve months showing repeat-violation-free share staying near 88 percent with an early re-inspection and falling to 67 percent without one.
    Featured Civic

    How soon does a critical violation come back?

    Headline finding: A re-inspection within 30 days cut the one-year repeat rate from roughly one in three to one in eight

    Measured how long facilities go after a critical inspection violation before the next one, and whether an early re-inspection changes that.

    • Survival analysis
    • Python
    • 2 more methods & tools
    Skills practiced: Statistics Skills practiced: Data cleaning1 more
  • Bar chart of missed-appointment rate by booking lead time, rising from 9 percent within a week to 24 percent beyond four weeks.
    Essentials

    Booking lead time and missed appointments

    Headline finding: Appointments booked more than three weeks out were missed almost twice as often as those booked within a week

    Tested whether how far ahead an appointment is booked predicts whether it is kept, using two years of de-identified scheduling counts from three community clinics.

    • Logistic regression
    • R
    • 2 more methods & tools
    Skills practiced: Data cleaning Skills practiced: Statistics1 more
  • Reading 1,800 survey comments without reading 1,800 comments

    Headline finding: Three themes covered 71% of comments; cost was named twice as often as opening hours

    Coded two years of open-ended community survey answers into a small set of themes, and published the codebook so the next survey can be compared with this one.

    • Qualitative coding
    • Python
    • scikit-learn
    • 1 more methods & tools
    Skills practiced: Data cleaning Skills practiced: Stakeholder interviews1 more
  • Line chart of weekly open permit reviews across a year with a shaded forecast band widening over the final eight weeks.
    Essentials

    Forecasting the permit review backlog

    Headline finding: A two-week staffing dip in March explained most of the backlog that was still there in July

    Built a weekly forecast of the permit review queue so the licensing team can see a backlog forming instead of discovering it two months later.

    • Time series
    • Python
    • 2 more methods & tools
    Skills practiced: Statistics Skills practiced: Automation1 more
  • Horizontal stage chart of median days per step, with the awaiting-verification stage at nine days dwarfing five other stages.
    Civic

    Where the two weeks go in a records request

    Headline finding: Mail-in requests spent 9 of their 14 days in a single hand-off between two systems

    Reconstructed the full path of a mailed-in vital records request from timestamps and found that most of the wait happened in a queue nobody owned.

    • Process mining
    • SQL
    • 2 more methods & tools
    Skills practiced: Data cleaning Skills practiced: Automation2 more

    Last confirmed Jun 2025

Upcoming events

Full calendar
  1. Final showcase Showcase Cohort 2026

    1:00–4:00 PM Auditorium and online

  2. 12:00–1:00 PM Online

  3. 12:00–1:00 PM Online

  4. Applications close for the 2027 cohort Deadline

Real questions, real data

Every team picks a question that matters to their own area of work and works it end to end with coaching.

Methods and code you can borrow

Projects document their data sources and methods so the next cohort can start from what already works.

A growing body of practice

Filter by cohort year, area of work or track to see how the program has grown.

Share a team project

Fill out a short form. Maintainers review every submission before it goes live.

Submit a team project