Map the service that uses AI
Put people, applications, AI steps, data stores and vendor boundaries in one service flow. Make the intended use and the information crossing each boundary clear.
AI governance software · Operations, risk & technology
AI governance, connected to the work it governs.
Map AI-enabled services, connect controls and evidence, and make ownership clear across operations, risk and technology teams.
Liquid Learn is an AI service governance platform. Use a shared operating record to work through everyday decisions: a model change, a missing control, a human handoff or the next service review.
24 questions · Immediate results · Downloadable PDF roadmap
The product workspace
One service flow. Shared governance context.
Liquid Learn’s AI governance software connects the service map to review work. Teams maintain the record as the service and its operating decisions change.
Make ownership and oversight visible
Identify owners at the steps they are responsible for. Show human review, approval and escalation alongside AI activity so teams can agree who intervenes and when.
Connect controls to the work
Record controls and data classifications on service steps and connections. Use that context to discuss safeguards, review requirements and unresolved gaps.
Keep a reviewable service record
Bring evidence references into review packets and retain reviewed service snapshots with reviewer details and comments. Give the next review a clear starting point.
Illustrative service · Customer support assistant
Make the human decision part of the flow.
An assistant drafts a response using approved support material. A person reviews exceptions before a response is sent. This example shows how to document the service; it is not an automated workflow integration.
- 01 · Intake
Customer request
Record the information entering the service and the support team responsible for it.
Control to consider: limit sensitive data. - 02 · AI activity
Draft a response
Show the knowledge source, model provider and information crossing the vendor boundary.
Evidence to consider: approved source and vendor instructions. - 03 · Human oversight
Review or escalate
Name the reviewer and document when a request needs escalation to the service owner.
Evidence to consider: an exercised exception procedure. - 04 · Service review
Record the decision
Connect the reviewed flow, controls and evidence references to the next operating review.
Decision to consider: what must change before wider use?
A shared view across teams
Govern the operating decisions together.
Operations
Clarify handoffs, exceptions and who owns the outcome when AI supports service delivery.
Risk
Connect governance controls, evidence and review gaps to the service you are assessing.
Technology
Make systems, data movements and external dependencies visible to reviewers.
Your team determines legal applicability, implements controls in the systems doing the work and validates the evidence. Liquid Learn supports that governance process; it does not certify compliance or automatically enforce controls in third-party systems.
AI Governance & Regulations
Understand what the next review needs.
Practical guides with dated official sources, current legal status and clear product limitations.
European Union · Enacted law
Explore governance resources EU AI Act: from obligations to service records
Provider and deployer roles, the amended timetable, transparency and human oversight.
Read the EU guide United States · Law and guidanceUS AI governance: scope the decision first
California, Colorado, Texas, FTC enforcement and the voluntary NIST AI RMF.
Read the US guideSee Liquid Learn in context
Request a product demo
Bring an AI-enabled service you need to govern. We can walk through its boundaries, owners, controls and review record together.
Enquiries are reviewed by Fluid Business in Seattle, Washington.
Read the security overview