
AI agents monitor hundreds of legal and regulatory sources around the clock, detect exactly what changed between one version of a document and the next, and score the likely business impact. Your domain experts make the call that matters.
Across every market an organisation operates in, someone is responsible for watching the law change. The work is essential and it is almost entirely manual.
Each country keeps its own list of trusted sources: government portals, legal journals, regulatory websites. Expert hours go into checking rather than interpreting.
Nothing moves until a compliance professional has read it and judged it relevant. Passing low-impact items downstream floods everything behind it, so the filter stays one document at a time.
The operational impact is assessed, then translated into functional tickets for product and business tickets for client-facing teams. Same change, two write-ups.
Every new jurisdiction adds the same manual load. Thresholds drift from one country to the next, and the reasoning stays in the heads of the people doing the checking.
A change caught late becomes an implementation done late, and in regulated services that reaches clients before it reaches the roadmap.
Faktion partnered with SD Worx to build a production-grade Legal Watch platform: agentic AI that scans hundreds of sources, detects regulatory changes, and assesses business impact per domain, so legal experts focus on judgment, not legwork.
We did not want to remove the domain experts. We wanted to give them a tool.
Five steps, done in sequence. Each one makes the next one more effective:
Continuously scan the sources that matter, across formats and jurisdictions. Some publish structured feeds. Most do not, so a scraping engine renders complex pages the way a browser would, works through nested repositories and anti-bot measures, and returns clean structured output. Scheduled per source, run automatically, with notification in-app and by email.

Filter the noise, so only what actually applies surfaces. AI agents classify each document against your own domains and score how likely it is to affect the business, with the reasoning attached to the score.

Version every change, so you see precisely what moved and when. New version against previous version, down to the clause, with the original rendered in-page and amendments highlighted. Summaries in the source language and in English.

This is the step a subscription cannot do. A legal update service tells you the law changed. It has no view of your products, your markets or your clients, so the translation from "this changed" to "this is what it means for us" lands back on your experts every time. The engine carries that mapping, built against your domains and your impact criteria, and your experts confirm or correct it.

Turn the assessment into the next step, and connect it to the systems where the work already happens.
Human judgment stays in the loop by design. The engine does the scale. People do the decisions. Steps one and three are mechanical and repetitive. Automating them returns expert attention to the question only a domain specialist can answer.

Add, update or retire sources through the interface, with scrape frequency set per source. The platform flags a source the moment it breaks or goes stale, before a gap opens in your coverage.
Single sign-on, with users assigned by country, domain and role so each person sees only their subset. Every status change and intervention is logged, which is what makes a decision defensible months later.
Countries and domains are added at any time without losing historical data. An evaluation dashboard shows how the AI is performing by type, so accuracy is monitored rather than assumed.
Add, update or retire sources through the interface, with scrape frequency set per source. The platform flags a source the moment it breaks or goes stale, before a gap opens in your coverage.
Single sign-on, with users assigned by country, domain and role so each person sees only their subset. Every status change and intervention is logged, which is what makes a decision defensible months later.
Countries and domains are added at any time without losing historical data. An evaluation dashboard shows how the AI is performing by type, so accuracy is monitored rather than assumed.
Producing a system that summarises legislation impressively is not the hard part. Producing one that does it reliably, across languages, across domains, on documents nobody has seen yet, is a different engineering problem.
Input samples paired with human-validated outputs, maintained by business users through the platform rather than by developers through scripts.
Specialised prompts judge the system's output against domain checklists your experts define, weighted so the criteria that matter most count for more. Users see the score and can open the reasoning behind it.
Every model call logged: prompt, cost, latency, output, feedback. When behaviour shifts, you can see where and when.
Business users draft and test changes in a safe environment. Promotion to production runs through approval and version tracking.
The architecture is domain-agnostic. What changes between deployments is the source list, the taxonomy and the impact criteria.
The same engine that tracks payroll legislation extends to adjacent domains such as data protection and anti-money laundering with adapted terminology and prompts.
Where legislative change across markets drives product changes and client communication directly
Where regulatory horizon scanning is a supervisory expectation
Where product compliance depends on tracking substance restrictions and labelling rules across markets
No. The platform syncs automatically on a schedule, with scraping jobs run overnight at the frequency set per source. Users are notified in-app and by email when new documents are detected.
Most do not. Legal updates are frequently buried in complex websites, dynamically loaded pages and nested document repositories. The scraping engine renders JavaScript-heavy pages as a real browser would, handles rate limits and anti-bot measures, and returns clean structured output ready for the AI pipeline.
A built-in monitoring system alerts administrators when a source is outdated, inaccessible or flagged for review, with a dashboard showing source health and coverage. Sources are managed through the interface rather than in code, so a replacement URL is a configuration change.
No. The AI detects the change, classifies it against your domains, summarises it and scores likely business impact with an explanation. The decision stays with your domain experts, who keep or discard each document and record their reasoning.
Each document receives a likelihood label with a written explanation. Beyond that, a certainty score can be produced by running the classification against a checklist of criteria defining what makes a change relevant to a given domain, built with your experts and weighted so the most critical criteria count for more. The reasoning is visible in the interface.
Yes. Documents are processed in their source language and every summary, key-change list and impact explanation is produced in both the source language and English, so cross-border teams work from the same text.
Human feedback is captured as structured ratings for classification and impact labelling, and as free text for summaries. Validated outputs build into curated reference datasets that evaluation pipelines run against, so a change can be measured rather than assumed. Free-text feedback can be grouped automatically into recurring categories, and annotated samples used to test prompt variations.
Domains and countries are added or modified at any time through the admin panel without losing historical data, preserving long-term traceability. The classification agent takes new categories as requirements evolve. Expansion is a configuration and prompt task rather than a rebuild, which is what allows your own team to take it on.
It does not write your legal analysis, and it does not decide business impact. Extending the AI further into drafting legally sound summaries and generating functional requirements from legal language is the direction of travel rather than what ships on day one.