RUE at AI and Big Data Expo Global 2025 in London
Regulated United Europe attended AI & Big Data Expo Global at Olympia London on 5-6 February 2025. Our interest was practical: understanding how artificial intelligence, data analytics and automation could support licensing preparation, document review and compliance work. The event offered an opportunity to assess technology alongside the legal, security and governance questions that determine whether it is suitable for a client’s business.
- Two-day event held at Olympia London on 5-6 February 2025.
- RUE explored AI, data analytics and regulatory technology applications.
- The focus was potential improvements to legal and compliance workflows.
3 essential points
-
Technology assessed against real tasks. Document classification, information extraction and workflow monitoring can be useful when the task, required accuracy and review process are defined. RUE’s attendance focused on understanding these applications and the conditions under which they could add value to client work.
-
Human responsibility remains central. An AI-generated summary or risk score needs an appropriate review process. Legal conclusions, regulatory submissions and significant decisions should be supported by reliable evidence and accountable professionals. A technology demonstration does not establish that a tool is ready for use with confidential client information.
-
A changing regulatory context. The conference took place shortly after the EU AI Act’s first application milestone in February 2025. Subsequent implementation has made it increasingly important to assess an organisation’s role, the intended use of a system and the specific rules that apply to that use.
4 key figures
- 2 days Duration of the London event
- 7,000+ Attendees expected in the pre-event announcement
- 150+ Speakers announced for the programme
- 150+ Solution providers advertised for the exhibition floor
Reading the figures
The scale figures come from the event’s January 2025 promotional announcement and describe advertised expectations and programme size, not audited final attendance. The event formed part of the wider TechEx programme with co-located shows.
Why RUE attended the London event

Legal and regulatory projects involve substantial amounts of information: corporate records, ownership documents, business plans, policies, financial forecasts and correspondence. Much of the work depends on checking that these materials are complete, consistent and relevant to the applicable requirements. This made the Expo a useful setting for exploring tools that could assist professionals with defined parts of the process.
Our team considered applications in document analysis, customer onboarding, compliance monitoring and business intelligence. The commercial question was whether a proposed tool could reduce repetitive work or make information easier to review. The legal question was whether it could do so with suitable controls over accuracy, confidentiality and responsibility.
From demonstrations to a useful evaluation
A demonstration shows what a product can do under selected conditions. A meaningful evaluation asks how it performs with the documents, languages and exceptions encountered in an actual project. Poor scans, inconsistent company names, incomplete records and changes in legal terminology can all affect the quality of the output.
For example, a system might extract directors’ names from a company register and compare them with an application form. That can help identify a discrepancy, but a reviewer still needs to establish which record is current and whether the difference is material. The value lies in directing attention to the right evidence and retaining a record of the review.
Professional exchanges and potential cooperation
The event also gave RUE an opportunity to discuss practical needs with technology providers and other industry participants. Such conversations can help define possible cooperation, including a limited trial, an integration assessment or a review of the provider’s documentation and contractual terms.
Any subsequent implementation should have its own scope, safeguards and acceptance criteria. The lessons from the Expo support that evaluation process; a decision to deploy a tool must be made for the particular workflow and data involved.
Where AI could assist licensing and compliance work
Useful applications tend to begin with a specific, measurable task. The examples below describe possible uses and the controls that should be considered before introducing them into a legal or regulatory workflow.
| Potential use | Practical benefit | Review or control needed |
|---|---|---|
| Document extraction | Organise names, dates and company details from submitted materials | Check source documents, uncertain fields and conflicting records |
| Completeness checks | Flag missing items against an agreed application checklist | Keep the checklist current and review jurisdiction-specific exceptions |
| Regulatory monitoring | Collect and classify updates from official sources | Verify effective dates, scope and legal significance |
| Onboarding support | Identify information requiring clarification or further review | Apply the relevant AML framework and review false matches |
| Project reporting | Summarise outstanding tasks and document status | Use accurate source records and show who owns each next action |
Accuracy and traceability
A useful output should be traceable to its source. For document review, that means preserving the original material and showing the basis for an extracted fact or flagged inconsistency. For regulatory research, it means checking the official text, jurisdiction, effective date and any transitional provisions before relying on a summary.
Generative systems can produce plausible but incorrect statements. Testing should therefore consider omissions and unsupported conclusions as well as obvious errors. A pilot can compare the assisted workflow with the existing process, measuring review time, missed issues, correction rates and the effort required to handle exceptions.
Confidentiality and provider arrangements
Before client information enters a tool, the organisation should understand where it will be processed, who can access it, how long it will be retained and whether the provider may use it for training. Contractual terms, access controls, deletion arrangements, incident procedures and any international data transfers should match the sensitivity of the information and the applicable obligations.
Early testing can use synthetic or appropriately de-identified material. The decision to use live data should follow a separate assessment of the purpose, permissions and safeguards. A provider’s product description or security claim should be checked against the evidence and contractual commitments available.
Realistic expectations for licensing projects
Automation may assist with preparation and administration, but it cannot determine the outcome of a licence application or control a regulator’s review period. Application quality also depends on the business model, management, funding, governance and the applicant’s ability to answer further questions. Any efficiency claim should relate to a measured task rather than a promised approval or guaranteed reduction in licensing time.
AI governance and the regulatory position today
The Expo was held in the United Kingdom, while many of the projects relevant to RUE involve the European Union. Businesses need to assess both the location and use of a system, the people affected and the jurisdictions involved. Conference participation is a historical event; compliance is an ongoing responsibility.
The EU AI Act timeline
The EU AI Act entered into force on 1 August 2024. Its provisions apply in stages, and the timeline has changed since the London conference. The following milestones reflect the European Commission’s current implementation guidance as at 18 November 2026.
| Date | Relevant milestone |
|---|---|
| 2 February 2025 | General provisions, including AI literacy, and prohibited AI practices became applicable. |
| 2 August 2025 | Rules for general-purpose AI models began to apply, subject to relevant transitional arrangements. |
| 2 August 2026 | Most AI Act rules became applicable, including transparency requirements, with specified exceptions and transitions. |
| 2 December 2027 | Application date for high-risk AI rules concerning Annex III systems under the amended timetable. |
| 2 August 2028 | Application date for high-risk AI rules concerning systems embedded in regulated products covered by Annex I. |
Official references: European Commission AI Act implementation timeline | AI Act enforcement framework
The relevant obligations depend on the system’s purpose and the organisation’s role. Purchasing a general-purpose tool does not settle the classification of its intended use. An implementation review should identify the applicable requirements and dates before the tool is introduced or materially changed.
Data protection remains a separate assessment
Where personal data is involved, the relevant EU or UK data protection framework must also be assessed. Key questions include the lawful basis, necessity of the processing, transparency, data minimisation, security and the rights of the people affected. AI Act compliance does not replace those obligations.
The UK Information Commissioner’s Office emphasises accountability and evidence-based assessment of AI use. A data protection impact assessment is required before processing likely to result in a high risk to individuals. That is an assessment of the proposed processing and its effects, rather than an automatic requirement for every use of AI.
Regulatory guidance: ICO guidance on AI accountability and governance | ICO guidance on data protection impact assessments
How RUE can support a project
The London event reinforced the value of assessing technology and legal requirements together. RUE can help clients identify the corporate, licensing and compliance questions arising from their proposed business model, coordinate the relevant documentation and determine where specialist technical or local professional input is needed.
To discuss a project, contact info@rue.ee with a description of the intended service, target markets, data involved and any existing authorisations. These details provide the basis for defining the scope of assistance and the next practical steps.
Related RUE resources: our team and contact RUE.
Discuss a regulatory or technology project
Describe your proposed service, target markets and compliance requirements so RUE can define the appropriate support.