Module 1
What legal engineering is: the job, the roles around it and why it exists
Legal work has always been done by people with a craft: read the facts, find the rule, apply it, write it down. What has changed is the volume of that work, the cost of doing it by hand and the technology available to help. Legal engineering is the discipline of looking at a piece of legal work as a system, a set of inputs, rules, decisions and outputs, and then designing a better way of doing it. This course, and the program it opens, teach that discipline. This first module explains what it is, who does it and why it exists, before the later modules teach the method.
Hover over an idea to light up what it connects to, click it for its definition, minimum requirements, an example and the usual trap, press Play to watch the map build step by step, or trace a short case through it.
Simplified teaching map, in general terms. Check the law where you work. On a small screen, scroll the map sideways.
By the end of this module you can
- Say what legal engineering is in one sentence.
- Tell a legal engineer from a lawyer, a developer and a legal operations manager.
- Name the related roles and what each contributes.
- Explain why the field exists now.
- List the skills a legal engineer needs and where you stand.
Part 1. The lecture
A working definition
There is no single agreed definition, and job titles vary between organisations. A useful working definition is this: legal engineering is the design, building and measurement of better ways of doing legal work.
Each word matters. Design means deciding what the process should be before building anything. Building means turning the design into something that runs: a template, a workflow, a data structure, an AI-assisted step. Measurement means checking, with evidence, that the result is faster, cheaper, more accurate or safer than the old way. A project that skips any of the three is not legal engineering; it is a guess, an experiment or a purchase.
| Not legal engineering | Why not | Legal engineering |
|---|---|---|
| Buying software and hoping it helps | No design and no measurement. | Choosing or configuring a tool to fit a process you have mapped, then measuring the result. |
| Asking an AI tool to answer a legal question | A one-off use, not a redesigned process. | Designing a workflow in which AI drafts, a rule-check validates and a lawyer approves. |
| Writing a clever macro that only you understand | Not documented, tested or owned. | Building a tested, documented tool that others can run and maintain. |
| Giving legal advice on a technology contract | Valuable, but advice, not building. | Designing the process by which technology contracts are requested, reviewed and tracked. |
The legal engineer and the roles around it
A legal engineer works between three worlds: the law and the lawyers, the business or client, and the technology. Understanding the roles that touch the same work helps you see where you fit. The titles below overlap, and many organisations use them loosely.
| Role | What it focuses on | How it differs |
|---|---|---|
| Lawyer | Giving legal advice and representing clients, applying judgement to the facts. | Legal engineering supports and scales the lawyer’s work; it does not replace the lawyer’s judgement. |
| Legal engineer | Designing and building the processes, rules, documents, data and automation behind legal work. | Works from the process outward: map it, specify the rules, build and test. |
| Legal technologist | Selecting, implementing and supporting legal technology across a firm or department. | Often tool-centred; a legal engineer is more often problem-centred. In practice the roles overlap. |
| Legal operations manager | Running the legal function as a business: budget, vendors, metrics, process and technology. | Wider management scope; a legal engineer usually builds what operations prioritises. |
| Knowledge engineer or knowledge lawyer | Capturing the firm’s know-how in precedents, playbooks and guidance. | Closely related: the rules a knowledge engineer captures are the logic a legal engineer builds. |
| Legal data analyst | Collecting and analysing data about matters, costs and outcomes. | Provides the measurement that legal engineering depends on. |
| Software developer | Writing and maintaining code. | May build what a legal engineer specifies, or the legal engineer may build with low-code tools. |
| Project or product manager | Delivering the change on time and getting people to use it. | A legal engineer often plays this part on small projects. |
In a small team one person may do all of this. In a large organisation the work is split. What matters for you is not the title but the mix of skills, which the next sections describe.
Why the field exists
Several long-running pressures have come together. None is new, but together they changed how legal work is organised.
- Cost pressure. Clients and employers want more value for less money, and are less willing to pay senior rates for routine work.
- Volume and complexity. More regulation, more contracts and more data mean more legal work to do and to track.
- Fixed or capped fees. When a matter is priced at a fixed fee, inefficiency comes straight out of the firm’s margin, which creates a reason to redesign the work.
- Technology that is finally usable. Document assembly, workflow tools, data analysis and AI assistants are now accessible to people who are not programmers.
- Client expectations. Clients accustomed to fast, transparent services elsewhere expect the same from their lawyers.
- Risk and consistency. A good process produces the same answer to the same question, which is what regulators, boards and clients want.
- Talent. Lawyers do not want to spend their careers on copy-and-paste, and organisations that remove it keep their people.
The result is a demand for people who can think like a lawyer about risk and rules, like an engineer about systems and testing, and like a manager about people and change. That combination is the legal engineer.
A caution
The field is young and fashionable, and some of what is said about it is hype. Technology rarely replaces a profession wholesale; it changes the mix of tasks. A sensible legal engineer is more interested in a boring, reliable improvement that saves two hours on a thousand matters than in a dramatic demonstration.
The skills a legal engineer needs
| Skill | What it looks like | Where it is taught in this program |
|---|---|---|
| Legal understanding | Knowing how the law and legal practice work, where the risks are and what a lawyer must decide. | Throughout, and in your own background. |
| Process thinking | Seeing work as a sequence of steps, hand-offs and decisions, and finding where it wastes time. | Foundations and Process Mapping. |
| Logic and rules | Turning a legal rule into if-then logic that can be tested. | Process Mapping and Decision Design. |
| Document and template design | Building documents that assemble correctly from data. | Document Automation. |
| Data literacy | Structuring information and asking it questions. | Legal Data and Dashboards, Contract Analytics. |
| AI literacy | Knowing what AI can and cannot do, and how to check it. | AI Workflows, Checking Legal AI Tools. |
| Communication and change | Listening to lawyers, explaining clearly and getting people to adopt a new way. | This course (module 4) and the portfolio. |
| Ethics and risk | Professional duties, confidentiality, bias and accountability. | This course (module 6) and throughout. |
| Measurement | Setting a baseline and showing a result with numbers. | This course (module 7) and the portfolio. |
Notice what is not on the list: you do not need to be a programmer. Many of the tools in this program are built into the courses, and many legal engineering tasks use low-code tools, spreadsheets and templates. If you can code, it helps; if you cannot, you can still specify, test and manage what is built, and that is the harder skill.
Where do you stand?
Look at the table and give yourself an honest score from 1 to 5 for each skill. Most lawyers are strong on the first and weaker on logic, data and measurement; most technical people are strong on logic and data and weaker on legal judgement and change. Knowing your gap tells you which courses to put first.
What legal engineering is not
- It is not replacing lawyers. It removes routine work and adds consistency, so that lawyers can spend more time on judgement, advice and clients.
- It is not buying tools. The tool is the last choice, after the process is understood.
- It is not only technology. Most projects succeed or fail on people, process and trust. A perfect template nobody uses has no value.
- It is not unregulated. Lawyers have duties of confidentiality, competence and supervision, and building tools for the public may raise rules on who may provide legal services. Module 6 covers this.
- It is not only for big firms. A solo practitioner with a good checklist and a tested template does legal engineering too.
The rest of this course gives you the foundation: how legal work is organised (Module 2), how to find work worth improving (Module 3), how to work with the lawyers who do it (Module 4), the landscape of tools (Module 5), the risks and ethics (Module 6) and how to measure and justify the result (Module 7). The later courses teach the craft: mapping, logic, documents, data and AI.
Part 2. Lab: Who Does What?
Each task belongs mainly to one role. Sort it to the role that would normally lead it.
Situation 1 of 8
Advise the client on whether to settle the dispute.
Where does this belong?
Part 3. Lab: Is This Legal Engineering?
Click each statement that describes legal engineering as defined in this module: design, building and measurement of a better way of doing legal work. Some do not.
Which of these are legal engineering?
Look for a designed process, something built and a measured result.
Click every sentence that causes a problem, then press Check. There may be 3 problems, and some sentences are fine.
Part 4. Check your understanding
Ten questions drawn from a larger pool. Sign in to have your score saved towards your certificate.
You have finished the free module
Here is what you can do now, and where the course goes next
Module 1 gave you
- Say what legal engineering is in one sentence.
- Tell a legal engineer from a lawyer, a developer and a legal operations manager.
- Name the related roles and what each contributes.
- Explain why the field exists now.
- List the skills a legal engineer needs and where you stand.
Next, 6 more modules and a capstone
- Module 2: How legal work is organised: matters, tasks, documents, decisions and where time goesYou will learn to describe a legal matter as inputs, tasks, documents, decisions and outputs.
- Module 3: Finding work worth improving: opportunities, criteria and the ladder from eliminate to automateYou will learn to judge an opportunity against eight criteria.
- Module 4: Working with lawyers: listening, requirements, trust and getting a new way adoptedYou will learn to Interview and observe the people who do the work.
- Module 5: The toolbox: categories of legal technology, build or buy, and choosing wellYou will learn to name the main categories of legal technology and what each does.
- Module 6: Risk, ethics and governance: building tools that lawyers can responsibly use
- Module 7: Measuring value: baselines, metrics, business cases and telling the story
- Capstone: Capstone: choose your first project and make the case for it
Each module has its own practice labs and a graded quiz, and a Certificate of Completion follows when you pass them all. The whole course is $15 once, or included in an All-Access Membership.
Two Ways In
Introductory PriceLegal Engineering Foundations: buy it on its own, or get it with All-Access
Unlock all of Legal Engineering Foundations on its own with a one-time purchase, or get it as part of an All-Access Membership, which also covers every course and the other paid tools. A member never needs to buy it separately.
This is an early, introductory price for a brand-new product — it’s expected to rise as we add more content. Buy now and it’s yours at today’s rate, forever.
No account needed: you pay, and we email you a one-click sign-in.
All-Access is $19.99 a month or $149 a year, and covers every course and most tools, this one included. Create a free account to subscribe.
Look first, then buy. Free previews on every product page. Secure payment by Stripe. Pay once, keep it forever. Details
See what is included in All-Access →Not ready to buy? Create a free account to save your quiz scores and your place in this course, and to get the printable reports from the practice rooms.
General education on legal engineering, using invented organisations, people and figures. It is not legal advice, technical advice or investment advice. Business-case examples are illustrations: real results depend on your own data and circumstances.
Teaching? Share this with your class
Free to use in class. The free parts open for everyone, no account needed.