Artificial Intelligence (AI) and Law

An organisation deploying an AI system acquires obligations it may not have read: for the data it trained on, for decisions the system makes about people, for what it tells customers, and for what a vendor contract actually transfers. Most of the exposure is not new law but existing law applied to a system nobody can fully explain, which is the difficulty. This week covers data protection, automated decision making, rights in training data and output, procurement terms, and the governance a board has to be able to answer for. It is a legal and risk course rather than a technical one.

It runs 7 times over the published calendar, in 6 cities and live online. Every date is the same programme with the same content and the same certificate.

• Identify the lawful basis for processing personal data in a specific use case, or establish that there is none.
• Apply automated decision making rules to a system that scores or ranks people.
• Assess the intellectual property position of training data and of generated output.
• Read a vendor contract for what it does and does not transfer on liability, data and indemnity.
• Build an approval and record keeping process a regulator or a board could inspect.

In house counsel, compliance and data protection officers, risk managers, and the IT and procurement staff who select and contract for AI systems.

Short input, then work. Across 5 days of roughly 6 teaching hours each, the balance sits deliberately with the second: a programme where the trainer talks for six hours produces notes rather than capability.

• Your own material

  Exercises run on situations delegates bring, not on a case study written for a different organisation in a different decade.

• A capped cohort

  Small enough that everybody is asked something. Executive programmes are capped tighter still.

• Practice under scrutiny

  The difficult conversation, the challenged assumption, the decision defended out loud. Judgement is not built by watching.

• Something to take back

  Each day ends with a thing you can use on Monday rather than a slide deck you will not reopen.

• A risk assessment for one AI system the delegate's organisation uses or is considering.
• A contract review checklist for an AI vendor, including the clauses to refuse.
• A governance and approval process, written, with decision rights named.

A GATI certificate recording what you attended, issued after the programme has run and attendance has been taken. Attending at least 80 per cent of the days earns a certificate of completion; attending less earns a certificate of attendance stating exactly what was attended.

Every certificate carries a code that anybody can check against GATI's own record, which is what makes it worth holding. It records participation. This site will not imply one it does not have.