Legal horizon scanning in a UK firm of twenty lawyers is not an attempt to see everything. It is a short weekly list of developments that touch matters the firm actually has, each with a named owner and a date. LegalAI Space builds that list from six packs of public regulator and legislature sources, links a development to the matters it affects, and keeps a register of what the firm saw and what it did.
A development without an owner and a date is not being managed
In a firm of twenty, the reading of the regulators belongs to a partner on the 07:42 and a WhatsApp group with four practice heads in it. This is arithmetic, not carelessness: nobody is billing while they read the ICO's news page. The usual result is not that a firm misses a development. It is that the development is seen, agreed to be important, and then nothing happens to it.
So every development is judged, given a materiality band, and then a human either gives it an owner and a date or dismisses it with a reason. There is no state called 'read it'. The register carries six states: new, changed, triaged, assessed, actioned, and dismissed.
The six source packs
The packs are curated bundles of public sources, switched on when you set up a watch. UK financial services covers the FCA, the Bank of England and PRA, HM Treasury, OFSI, the Pensions Regulator and the FRC. UK core legal covers legislation.gov.uk, the judiciary, the SRA, the Law Commission, Parliament bills and the CMA. Data and privacy covers the ICO, the EDPB, the EDPS and the CNIL.
EU regulatory covers ESMA, the EBA, EIOPA, the European Commission and ECB banking supervision. US enforcement covers SEC, CFTC, FTC, DOJ, CFPB, FinCEN and OFAC actions. Life sciences covers the MHRA. Choosing well matters more than choosing many: a firm that switches on all six learns to skim the digest; a firm that switches on two reads them.
What the scan does with a development
Each candidate is judged against the watch's sectors. What comes out is a title, a document type, one or two neutral sentences of summary, a line on why it matters that names the affected activity, a suggested next step, and a materiality band of high, medium or low. Two dates are extracted where the source states them: the commencement date and the consultation close. If the source does not state a date, the field stays empty; dates are not inferred.
From there you assign an owner, add a disposition note, and link it to the matters it affects. A development routinely touches several engagements, and an engagement collects several developments, so the link works in both directions. That link is the point of the feature. It turns 'the ICO published this' into 'this changes what we told that client in March'.
The Monday digest
The roll-up email answers two things: what a partner needs to know this week, and what falls due next. You choose the cadence, and it goes out at 08:00 in the firm's own timezone, before the first meeting. It contains the top three open developments ordered by urgency and materiality, every deadline in the next fourteen days labelled as a consultation close or a commencement, and the counts.
Coverage is written from the scan's own record of what it read. If a source failed, it is named in the email rather than dropped. A scan that had no sources to read is recorded as skipped, with the reason, because seventeen scheduled scans of nothing look, from every other angle, exactly like seventeen quiet weeks.
The register is what you show the risk committee
The horizon register exports as a PDF covering the last 90 days. It sets out the firm's watching process, what each scan covered source by source, every scan that ran including the ones that were skipped and why, every development with its judgement, and every human disposition and sign-off with a name against it.
That is a different artefact from a reading list. The SRA thematic review of compliance officers (December 2025) and the SRA guidance update on new technology and COLP responsibility (February 2026) both address how compliance work is carried out where technology is doing part of it, and a register is the kind of thing you would want in front of you in either conversation.
What this does not do
Every source in every pack is a regulator, a legislature, a court service or an official body publishing openly. A development that appears only in a subscription newsletter or a paywalled trade title will not be there; we refuse paywalled sources deliberately. A watch with no sources produces nothing, and the firm has to choose packs that match where it practises.
The materiality band is a starting point written by a model, not a decision. Dates come from the source or not at all. We cover UK and EU sources plus a US enforcement pack; we do not cover US, Canadian or Australian law as a practice area. Nothing links itself to a matter: that connection is made by a person who knows the file.