Skip to content
back to achievements

Case study · Stadium Rover

Client project · AugmentProject period2024 – 2025

Review-summary pipeline

Orchestrated an AI stadium-review-summary pipeline with GCP Workflows and implemented scheduled sports-data ingestion to keep downstream functionality current.

01

Why

Each stadium collects many reviews. Summarizing when nothing has changed wastes money, and a summary that doesn't reflect new reviews feels stale.

02

Decision

A GCP Workflows run starts every midnight and checks for new reviews. If there are none, it doesn't run, so the AI isn't paid to repeat itself. When there are new reviews, it regenerates the summary. Two ideas keep it accurate:

  • Latest 50. The summary uses the latest 50 reviews, because older ones often describe problems that have since been fixed.
  • Tags for unresolved issues. New reviews are tagged by topic, such as cleanliness, food quality and the general experience. A few flagged older reviews are included, so a serious issue that was never resolved isn't dropped. For example, a long-ago "the toilet is not clean" review stays visible until it's resolved.

How it fits

Hover or focus a box for the story behind it.

Every midnight a workflow checks for new reviews. If there are none it stops. Otherwise it tags the reviews by topic, picks the latest 50 plus flagged older ones, and the AI writes a fresh summary for each stadium.GCP WorkflowsNoneA scheduled GCP Workflows run starts every midnight.Midnight run Every nightLooks for reviews that arrived since the last run. If there are none, nothing runs, so the AI is not paid to repeat itself.New reviews? Skip if noneNew reviews are tagged by topic, such as cleanliness, food quality and the general experience.Tag reviews By topicTakes the latest 50 reviews, because older ones often describe problems that have since been fixed, plus a few flagged older reviews so an issue that was never resolved stays visible.Pick reviews Latest 50+The AI condenses the picked reviews into a short summary for each stadium.AI summary Per stadiumThere is nothing to summarize, so the run ends here.Run stops Nothing new

New reviews arrived since the last run: they are tagged, the right ones are picked, and the AI writes a fresh summary.

03

Alternatives considered

Summarizing on every request, which wastes money when nothing is new. Waiting for a call before updating, which saves cost but shows stale data. I chose fresh data over saving that cost.

04

What I built

Designed and implemented an automated AI-processing workflow for consolidating user reviews associated with stadium experiences.

When users submit new stadium reviews, the system incorporates the newly available review information into a processing pipeline used to generate an updated consolidated representation of the stadium's review data.

Designed the workflow using GCP Workflows to coordinate the different processing stages required to retrieve relevant reviews, process the information, and generate an updated AI-produced summary.

The workflow was designed to process accumulated review information on a scheduled basis, including a midnight processing cycle, rather than repeatedly performing the complete summarization process for every individual user request.

Also developed AI evaluation tests for the review-summary functionality to validate generated results and support improvements to the summarization process.

05

Trade-offs

Even a single new review means going through the whole summary again.

06

Outcome

Each stadium has an up-to-date summary, and unresolved issues stay visible.

Technologies