Glean Regulatory

Compliance teams at financial institutions operate in an environment where missing a single regulatory update can trigger audit findings, fines, or enforcement action. Yet the current workflow at most institutions is a patchwork of email alerts, manual document review, and ad hoc searches across dozens of regulatory sources. The signal-to-noise ratio is brutal. Glean Regulatory is a purpose-built intelligence platform that tracks, surfaces, and prioritises regulatory changes for compliance analysts, designed around the compliance workflow, not a generic news aggregator.

1. 1.
   Multi-Source Tracking: Aggregate regulatory updates across SEC, CFPB, OCC, FINRA, and targeted state-level sources into a single normalised feed.
2. 2.
   Compliance Workflow Integration: Design the interface around what compliance analysts actually do with regulatory updates, triage, assign, annotate, escalate, not just surface them.
3. 3.
   Priority Ranking: Develop a relevance scoring model that weights updates by proximity to the institution's product lines, recency, and enforcement history context.
4. 4.
   Audit Readiness: Build action logging so every triage decision is timestamped and attributable, giving compliance teams a defensible record of their review process.

• ◆
  Domain Research: Mapped the compliance analyst workflow through structured interviews, identifying the five highest-friction points in the current manual process.
• ◆
  Source Taxonomy: Catalogued 23 regulatory sources by jurisdiction, publication frequency, and relevance to the target institutions, then prioritised ingestion by analyst-reported impact.
• ◆
  UI Prototyping: Built low-fidelity wireframes tested with three compliance analysts before writing production UI, validating triage flow, filter logic, and notification thresholds.
• ◆
  Deployment: Shipped as a Next.js application on Vercel with environment-controlled source configuration, enabling institution-specific source sets without code changes.

Not all regulatory updates are equal, and showing a compliance analyst 200 updates of equal weight is no better than showing them nothing. The relevance model scores updates across three axes: product proximity (does this update affect our specific product category?), recency weight (how close to effective date?), and enforcement signal (does this source have a history of subsequent enforcement action?). The composite score drives visual prioritisation and notification thresholds.

The difference between a regulatory intelligence platform and a news aggregator is workflow integration. A news aggregator tells you what happened. Glean Regulatory tells you what to do about it, by surfacing the right update to the right analyst, attaching it to the relevant product line, and tracking whether it was acted on. The product is the workflow, not just the feed.

I shadowed the compliance workflow before writing a spec. The product decisions, what to surface, how to rank it, what actions to expose, came from understanding what 'relevant' means inside a regulated institution. That research is what separates this from a generic news aggregator.

A purpose-built intelligence layer for compliance teams, designed to surface what matters and suppress what doesn't.