Lloyd's of London Market Bulletins Monitor

Tracks Lloyd's of London Market Bulletins -- the official notices Lloyd's issues to its own market (managing agents, brokers, coverholders): capacity-market rules, annual charges/subscriptions, country-by-country regulatory changes, quarterly major-loss reporting (QMR), byelaw/rulebook updates, and similar binding notices.

What you get

One record per bulletin checked this run, tagged with an explicit matchState: FIRST_SEEN (your own baseline run), NEW (published since your last check), UPDATED (a previously-seen bulletin whose title, category, date or PDF link has changed), UNCHANGED (re-confirmed, no change), or REMOVED (was present last time this Actor checked that part of the archive, no longer there). Each record carries the bulletin's own reference code (e.g. Y5492), title, category, published date, and a direct PDF link.

What it does not do

No personal data, ever. Each bulletin on the live page is published alongside a "Signatory" column naming the individual Lloyd's officer who issued it (e.g. "Rizwan Kermali"). This Actor's parser never extracts that column's text into memory at all -- there is no code path anywhere in src/ that reads the Signatory cell, so there is nothing to redact after the fact. A second, independent guard (_shared/pii.js's key-based stripper, reused from this project's other Actors) is also applied to every output record before it is pushed, as a structural safety net against a future code change accidentally reintroducing a signatory-shaped field.

The source is the live bulletins search, not a bulk archive download. Lloyd's publishes this as a paginated search widget (~274 pages, ~10 bulletins/page, ~2,740 bulletins total as of this Actor's build date), not a single downloadable file. This Actor checks the most recent pages by default (see maxPages below) rather than crawling the full archive on every run.

Why you might need this

Market Bulletins are binding on everyone operating in the Lloyd's market -- missing one (a charge deadline, a country-specific authorisation change, an updated capacity rule) is a real compliance and operational risk, not just an inconvenience. This Actor exists so you find out the moment a new or changed bulletin is published, on your own schedule, instead of manually re-checking the bulletins page.

Input

{
  "maxPages": 5,
  "maxChecked": 100
}

• maxPages (default 5): how many pages to check this run, most recent first (~10 bulletins/page). A routine scheduled run rarely needs more than the default: the Actor stops early, before using the full budget, once it reaches a page it has already seen with no changes (everything older is necessarily already known too, since the source is sorted newest-first). Raise this for a deeper historical backfill on your first run.
• maxChecked (default 100): a hard, independent cap on how many bulletin rows are inspected (and charged) this run.

Sample output

One real bulletin (captured in this Actor's own test fixture, test/fixtures/page1-live.html, from the live bulletins search), run through this Actor's own buildBulletinRecord() as its first-ever run against that bulletin (hence matchState: "FIRST_SEEN"; a later run that finds this same bulletin unchanged or edited would report UNCHANGED or UPDATED instead, never FIRST_SEEN again):

{
  "bulletinId": "Y5492",
  "title": "Y5492 - Q3 2026 QMR - major loss, exchange rate and other information",
  "description": "Q3 2026 QMR - major loss, exchange rate and other information",
  "category": "Finance Risk Mgmt and Operations",
  "publishedDate": "2026-10-01T00:00:00.000Z",
  "pdfUrl": "https://uksprctx112strgacc.blob.core.windows.net/media-651c0e64-c1d0-4f97-90f7-883c69fe2ef2/d4f7e723-1a2e-415b-869d-c602f0561a6e/Y5492.pdf",
  "matchState": "FIRST_SEEN",
  "firstSeenAt": "2026-10-09T21:30:00.000Z",
  "lastSeenAt": "2026-10-09T21:30:00.000Z",
  "checkedAt": "2026-10-09T21:30:00.000Z",
  "sourceUrl": "https://www.lloyds.com/market-resources/market-bulletins"
}

Note the absence of any Signatory-officer field, per "What it does not do" above.

Change tracking across runs

Run this Actor on a schedule (weekly is more than enough given Lloyd's own real publishing cadence of roughly 1-3 bulletins/week). Each bulletin's first-seen/last-seen timestamps and last-known content are stored per Actor, so a later run only reports what actually changed, not a re-dump of everything checked.

REMOVED is only ever reported within the page range a run actually re-checks. This Actor does not re-crawl the full ~274-page archive every run (that would be slow and expensive for essentially a static, append-only publication history). If a bulletin further back in the archive than this run's early-stop point is ever withdrawn, this Actor will not notice until a run's page range happens to reach that far again (e.g. a deliberately large maxPages value). In practice, Lloyd's own bulletin archive is append-only -- bulletins are not routinely withdrawn -- so this limitation rarely matters; it is documented here rather than silently assumed away.

Pricing

Pay per run started, plus per bulletin record produced (new, updated, unchanged, or removed). See the Pricing tab for exact rates.