Under the hood

From regulation text to control update, automatically

How Regloom works in four stages. No manual reading. No routing decisions. Each stage runs continuously so the feed is always current.

Stage 1 of 4
01
Source monitoring

Continuous polling of 40+ regulatory sources

Regloom maintains a versioned index of every source it monitors. Every 4 hours, each source is fetched and compared against the prior version. The diff is computed at the document level: section-by-section changes are extracted as discrete change records. No change is skipped because the agency published at an odd hour or in a low-traffic format.

Polling interval: every 4 hours across all sources
Stage 2 of 4
02
Obligation extraction

Isolating what the regulation requires

Changed text is processed by Regloom's NLP extraction layer. The extraction model identifies obligation language: sentences and clauses containing modal verbs with compliance weight ("must," "shall," "required," "prohibited," "may not"). Each identified obligation becomes a candidate for control matching. Non-obligation text (preamble, definitions, effective dates, background context) is tagged and excluded from the matching queue to reduce noise.

Cross-references are also extracted. If an amendment to Reg E cites EFTA section 905, both the primary obligation and the cross-referenced obligation enter the queue. This is the part that most manual review misses: the downstream obligation buried in a citation, not in the amended paragraph itself.

Extraction model trained on US federal and state regulatory text spanning Federal Register rulemaking, agency guidance letters, and FINRA regulatory notices
Stage 3 of 4
03
Control matching

Matching obligations to your specific controls

Obligation candidates are matched against your uploaded control library using semantic similarity. Controls are represented as embeddings based on their description, scope notes, and linked regulation references. Matches above the high-confidence threshold are auto-tagged. Matches in the review threshold are queued without a notification so compliance team members can review and decide. Matches below the review threshold are discarded.

Confidence thresholds are configurable per control category on Professional and Institution plans.

Control library: CSV import or manual entry, up to unlimited on Institution plan
Stage 4 of 4
04
Alert delivery

The right person sees what changed

Matched controls and their assigned owners receive targeted alerts. The alert contains: the regulation source, the changed text, the obligation it creates, the affected control identifier, the confidence score, and the effective date if specified. Delivery is via email digest (daily or weekly), Jira ticket creation, Confluence page push, webhook, or REST API.

Your compliance team sees a structured diff with a control reference. Not a newsletter. Not a PDF to forward and hope someone reads it. A specific record with the changed obligation text, the affected control identifier, and the confidence score, going to the person who owns that control. Regloom does not tell your team what decision to make: it tells them when a decision needs to be made and which control it concerns.

Delivery: email, Jira, Confluence, webhook, REST API
Common questions

How it works, in more detail

Upload a CSV with required columns: control ID, control name, description, and optionally regulation references and owner email. We provide a downloadable CSV template with column specs and example rows. Manual entry is also supported for teams with smaller libraries. Edits to the control library take effect on the next mapping cycle.
All four major federal banking regulators (Federal Reserve, OCC, FDIC, NCUA), the CFPB, FINRA, the SEC, CFTC, FinCEN, Treasury, and the Federal Register as a catch-all. On Professional and Institution plans we also monitor all 50 state banking regulators. Custom source ingestion is available on the Institution plan for internal policy sources or niche regulators.
Each regulation-to-control mapping is stored as a separate record. A control can have multiple active mappings. When one of those regulations changes, only that specific mapping is updated and flagged for review. Other mappings to the same control are unaffected unless their source also changed. The control owner sees all active mappings on the control detail page, with dates and status for each.
Custom source ingestion is available on the Institution plan. We support standard HTML pages, RSS/Atom feeds, and PDFs from a stable URL. Internal policy document monitoring (e.g., board policies hosted on SharePoint) is available with an ingestion connector scoped to your domain. Contact us to discuss your source list.
Each source in Regloom is tagged with a document type (binding rule, guidance, supervisory letter, FAQs, examination procedures). The alert includes this tag so control owners know whether the change creates a hard obligation or a supervisory expectation. You can configure notification thresholds by document type, for example to receive immediate alerts only for binding rules and weekly digests for guidance documents.
Sources are polled every 4 hours. After detection, extraction and matching typically complete within 15 minutes. Total latency from publication to alert delivery is generally under 5 hours during business hours, and under 9 hours overnight. The Institution plan includes an SLA of 4 hours from publication to targeted alert delivery.