1 Introduction

Visual representation of law and legal processes has potential to systematise decision-making in a way that mitigates risk and improves efficiency for lawyers, and lessens confusion and misunderstanding for their clients (Leiman 2016); both of which could decrease costs, especially those incurred relitigating matters (Fang 2014). In a system which is largely client funded this means there is potential for greater access to good quality legal assistance that a larger portion of the community can afford. Historic visual approaches like Wigmore Charts (Fig. 1) and Beardsley Diagrams have been proposed for analysis of trial evidence (Reed et al. 2007),Footnote 1 and newer methods like Araucaria Diagrams and Bayesian Networks (Fig. 2) have been used as visual steps to computational representation of legal argument in construction of AI (Reed et al. 2007; Fenton et al. 2013). However, in a recently published literature review it was found that in spite of calls for legal visualisations, use of diagrams to describe the inner workings of legislation or lawyerly processes remains rare (McLachlan and Webley 2020). This means that while diagrams and AI exist that exemplify a particular argument type, individual case or court judgment, there are very few exposing broader legal issues, legislation or categories of cases.

Fig. 1
figure 1

Wigmore diagram reproduced from Reed et al. (2007)

Fig. 2
figure 2

Bayesian Network for the case of R v Adams reproduced from Fenton et al. (2013)

Fig. 3
figure 3

The pathway to Legal AI

Fig. 4
figure 4

Extract of the multi-level Buyer pathway from conveyancing process lawmap

Visualisations of law and justice can be an important component for how lawyers and society more widely engage with the legal system. Legislation is infused with structure, and not just the visible structure of chapters, headings and statutory sections, but also an implicit structure that only becomes apparent when different sections and subsections interact as that legislation is analysed or when they are applied to a particular set of circumstances. The complex, verbose and abstruse nature of legislation means that it is difficult for those not trained in the law to comprehend the structure and meaning of legislation.

The systematic collation of interactions between legal provisions, processes and decision points could provide a formidable tool to support lawyer’s decision-making and a powerful representation of the law and legal system. Information visualisation (infovis) provides a mapping between discrete data and visual representations in order to improve memory, cognition and comprehension of otherwise abstract information (Huron 2014; Manovich 2011). Infovis reduces the variability of what is specific to individual instances of data or an activity to visually represent only the core characteristics in order to reveal the patterns and structures inherent to that data or activity. The process of developing infovis draws on two core principles (Manovich 2011):

  • The reduction of complex data and relationships to graphical primitives such as points, lines, curves and simple geometric shapes, and;

  • Use of spatial variables such as position, size, shape, colour and movement to represent key differences in data and reveal patterns.

Lawyers make countless decisions in the course of daily practice. Decisions about the relevant legal provisions that apply to a given matter, the scope of advice they give, the investigations they undertake on behalf of their client, and the context of submissions they draft. The vast array of complex legislation, practice rules and precedent all serve to make legal decision-making a challenging task (James 2007; Johnson 1999; Mulvenna and Hughes 1995). Lawyers adhere to relatively traditional ways of doing things, even as professionals in other domains adopt new technologies (Becerra 2018). While there have been numerous calls to develop approaches and train lawyers using infovis (Koch 2010; Leiman 2016; McCloskey 1998), these calls presently remain unanswered (Leiman 2016; McLachlan et al. 2020a, b, c).

Two problems are to be addressed in this work. The first is development of an infovis approach for the legal domain that can equally represent both the implicit structure of legislation and the stepwise nature of lawyerly processes. These visualisations are referred to as lawmaps. The second is to ensure that the resulting Lawmaps are sufficiently democratised to be comprehensible not just by experienced professionals, but also by law students and the general public. The goal is to reduce the apparent complexity of law and make lawmaps, and lawvis, ubiquitous tools that can enable law professionals, students and lay-people to visualise everyday legal activities.

2 The role of lawmaps in the pathway to legal AI

Early approaches to developing legal AI focused solely on understanding and modelling legal argument (Bench-Capon 1997; Rissland 1990). More recent projects have developed formulaic or rule-based approaches for performing routine tasks including predictive coding processes for e-Discovery, ranking of precedents during legal research, and predetermined routine document generation (Becerra 2018). While there have been a number of forays into predictive analytics these have usually sought to provide a limited prediction as to the potential outcome if a matter proceeds to trial, or the decision a particular judge might be expected to make based on past rulings (Becerra 2018). Issues have been raised with other predictive approaches that have drawn critical attention in the media, with claims that systems such as COMPASFootnote 2 and PredpolFootnote 3 are racist and prejudicially biased. However, these applications of AI more correctly exist within the policing and justice domains and are not routinely used by lawyers. For this reason, while their striking ethical issues should be foremost in the minds of all who are developing intelligent solutions, we consider them to exist outside the scope of AI for legal practice.

Real-world problems generally comprise multiple related but uncertain variables and data (Constantinou et al. 2016). Developing effective AI involves two major tasks: (1) determining the structure; and (2) specifying the computational parameters and values (Kyrimi et al. 2020). It can be difficult to determine the most appropriate inputs when developing a new AI. However, one approach that has shown success is when data is combined with expert knowledge (Constantinou et al. 2016; Kyrimi et al. 2020). The process of deriving knowledge from experts, or expert elicitation (Constantinou et al. 2016; Kyrimi et al. 2020), allows for interdisciplinary collaboration between those developing the AI and experienced practitioners from the domain under investigation. The goal should not be wholesale replacement of the expert practitioner. Rather, the goal should be to develop tools that can aid or enhance their practice, and reproduce elements of their expertise that may assist the untrained or inexperienced to identify when and why they have an issue that requires expert input.

With this in mind we have been developing lawmaps in a discrete set of legal domains. Figure 3 describes the relationships on our pathway to developing legal AI. Lawmaps (which we will define formally in Sect. 3) are developed from legislation, precedent and procedural rules, all framed by expert input that illuminates flow, meaning, decision-making and reasoning processes. We believe lawmaps provide a logical structure which, when combined with relevant legal datasets and a common data model (CDM) for law, can support production of Legal AI.

3 Lawmaps: an approach for representing legislation and legal processes

Lawmaps grew from a need for infovis in the legal domain and out of the prior efforts of several of this works’ authors to develop standard diagrams incorporating knowledge from clinical practice guidelines, published texts and clinical expertise in the medical domain. Known as caremaps (McLachlan et al. 2019), the resulting medical visualisations use a custom set of familiar unified modelling language (UML) elements to represent diagnostic and treatment activities, clinical decisions and the pathway a patient takes during the course of treatment for a given medical condition. Scaffolding a new infovis approach with an established presentation model that is familiar to the practitioner mitigated the need for extensive explanation and training of the representation framework, allowed the user to engage more freely with the knowledge content of the diagram, and resulted in an approach that practitioners agreed was simpler and easier to use than the text-based clinical guidelines and literature on which the caremap had, in part, been based (McLachlan et al. 2020b).

A recent review of process and flow diagram usage in legal literature published during the last two decades established that the concept flow (also known as flowchart or process map) was the most frequent visualisation in legal literature, and that UML was the single most recognisable representational language model (McLachlan and Webley 2020). For this reason the lawmaps approach described in this work draws on the UML activity diagram, a common flow chart structure, for its elements, notation and visual appearance.

3.1 Structure, elements and notation

A lawmap contains a pathway, and each pathway presents as a sequence of elements, including: (a) functional entry and exit points at which the pathway is initiated or concludes; (b) activity nodes which represent functional components of legislation or the practitioners lawyerly effort; and (c) decision points which represent some legal decision to be made based on one or more criterion. The flow from one activity to another is illustrated with arrows. The pathway describes both: (i) the timing of necessary activities, that is, when they should occur and any dependencies required before performing the next activity; and (ii) the route or order of events identified as a result of the impact of evaluation of criterion at decision points. All elements and notation for lawmaps are described in Table 1.

Table 1 The lawmap content type, activities and decisions (Adapted from 28)

3.2 Lawyerly process lawmaps

Each activity in the lawyerly process lawmap represents an activity that the lawyer undertakes in furtherance of a client’s matter, including but not limited to: (a) taking instructions; (b) providing advice; (c) receiving or responding to correspondence; (d) investigation and consideration of legal matters; (e) generating briefs, written submissions or other legal documents; (f) recording resource expenditure and accounting to client; and (g) regulatory compliance activities. Additionally, an explanation associated with the activities, decision points and/or arrows may also be present. This could include an explanation for why the lawyer undertakes a particular activity, a description of the task to be performed, advice that should be given to the client, information that must be recorded, or correspondence to be generated. The example in Fig. 4 is extracted from a larger conveyancing lawmap.Footnote 4 It demonstrates a primary lawmap with nested lawmaps for each primary activity, along with examples for most explanation types.

3.3 Legislative lawmaps

Each activity of the legislative lawmap represents either: (a) application of a specific section or subsection of the legislation; (b) a specific activity required by the legislation; or (c) the outcome from consideration of application of a section or subsection of the legislation (i.e. the outcome of decision points identified within the legislation). As with the lawyerly process caremaps there are a number of explanation breakouts that may be necessary. The example in Fig. 5 is extracted from the Application for Interim Rent processFootnote 5 found in Part II of the United Kingdom’s Landlords and Tenants Act 1954 and shows that these include references to the subsection of legislation from which the activity node, decision point or pathway has arisen, as well as references to relevant caselaw that establish or further refine that area of legislation.

Fig. 5
figure 5

Extract of the Application for Interim Rent pathway drawn from the Landlords and Tenants Act 1954

4 Lawmap development

As shown in yellow at the apex of Fig. 6, the first phase in developing any lawmap is selection of the process to be mapped. The lawmap development lifecycle operates in the same way whether a legislative or lawyerly process is selected. The second phase, in green, locates source material and a practitioner with expertise relevant to the process under development. Third, in blue, the source materials are investigated to identify the overarching process flow which, using the source materials, standard constructs known as legal idioms and expert input, is analysed and broken down into component processes. The fourth phase in red draws on expert reasoning and evaluates the process flow and component processes to identify decision points at the apex of divergences described in the lawmap and the criterion relevant to each child path. Using an iterative review and refine approach, the fifth phase in purple draws on the outputs of all previous steps to design and draft the resulting lawmap.

Fig. 6
figure 6

The Lawmap Development Lifecycle

As legislation is amended or new legal judgements reported, the lawmap may be updated through reprise of the lawmap development lifecycle with the updated source materials.

The design process described below assumes that the process being mapped has been identified and begins with collection of the source materials. The process for resolving the structure and flow of a lawmap follows an iterative per-node standard process described in points iii-vi below, with addition of the Extract step which is used to prepare legislation for direct application in that iterative standard process.

  1. i.

    Locate

  • Input: the selected legislative or lawyerly process to me mapped

  • Process: locate and collect relevant source materials to the process under investigation.

  • Output: a collection of relevant source material for use in development of the lawmap.

  • Relates to: the green phase in the Lawmap Development Lifecycle

  1. ii.

    Extract (for legislation)

  • Input: legislation from the source material collection

  • Process: extract plain language logic from the law, making the legislation approachable and explaining its core elements, activities and application.

  • Output: a plain language process flow that describes the source legislation in simple terms.

  • Relates to: the blue phase in the Lawmap Development Lifecycle.

  1. iii.

    Identify

  • Input: output from the Locate and Extract steps.

  • Process: identify the requirement for a node. Such requirement will be indicated from the plain language logic of legislation, conditions of a judgement or common law test, the structure of a legal idiom, or as a necessary step in procedural rules or lawyerly process being undertaken.

  • Output: a collection of identified nodes with analysis of their requirements, dependencies and operative rules.

  • Relates to: the blue phase in the Lawmap Development Lifecycle.

  1. iv.

    Distinguish

  • Input: output from the Identify step.

  • Process: distinguish the type of node by its action and the effect it will have on the process flow. For example: where a node is an action or step to be undertaken and will be followed by another action or step, this will most likely be an activity node. Where there will be multiple pathways diverging from the identified node, this is most likely a decision point and necessitates identification of criterion to define the metric for selecting the individual divergent path to be taken.

  • Output: a complete set of nodes classified as activities or decision points.

  • Relates to: the red phase in the Lawmap Development Lifecycle.

  1. v.

    Sequence

  • Input: output from the Identify and Distinguish steps.

  • Process: the process to sequence a node requires identification of: (i) those activities that must be completed or that are necessary to the activity or decision to be undertaken in this node and which this node would have to follow; and (ii) any activities that depend on the outcome or completion of the activity or decision of this node and which this node must precede.

  • Output: the constructed lawmap.

  • Relates to: the purple phase in the Lawmap Development Lifecycle.

  1. vi.

    Traceability

  • Input: Output of all previous steps.

  • Process: this step annotates the lawmap and enables traceability back to the legislation, case law or source material for nodes and the overall structure. Where the node has been resolved from a particular subsection of legislation, this should be indicated. In cases where a node arises from application, discussion or refinement of the law in judgement, the case law should be referenced with attention drawn to the legal reasoning that is required.

  • Output: annotations for key nodes and pathways in the completed lawmap.

  • Relates to: the purple phase in the Lawmap Development Lifecycle.

There is of course a major leap from step ii to step iii and there has been no single universally agreed method for doing this. However, simple Boolean algebra can greatly assist in this process. Use of Boolean Algebra (Boole, 1847) for expressing the final structure of law or legal rules after thorough analysis, including rules of precedence, is not new (Kort 1963; Allen and Caldwell 1963). More recently this approach has been applied in the form of Temporal and Boolean Logic to model traffic law and road rules (Prakken 2017; Alves et al. 2020). It’s application in this work would help as the basis for developing machine interpretable visualisations in the form of Lawmaps that can aid lawyers and clients to better understand the law and legal processes, as well as AI developers and decision scientists in their efforts to develop machine learning (ML), neural networks (NN) and other forms of AI. This process of deconstructing law and lawyerly process means each lawmap has a sound formal basis, which also promotes future bi-directional automatic generation of Lawmaps-based output from NLP methods, and the incorporation into and validation of laws in AI. For law and regulation the process begins with investigation of the underlying structure and infers the inherent intention and flow; identifying the key points, actors, processes and chronology of operations and representing them by application of Boolean logic and algebra.

5 Demonstration of the lawmap approach

It is beyond the space limitations of this paper to reproduce an entire stepwise case study for developing either type of Lawmaps: legislative or lawyerly. Instead, this section demonstrates a number of component examples from each lawmap type using the terminology and activities described in the six-step design process described in Sect. 4.

5.1 Legislative process: the United Kingdom road rules

As a simplified example, if we were examining the requirements of Sect. 5(1) of The Motor Vehicles (Wearing of Seat Belts) Regulations 1993 (MVWSBR) shown in Fig. 7, which are already the underlying basis for Road Rule 99 shown in Fig. 8, we see that: (a) the actors are adults and persons over the age of 14 years; (b) that they are driving or riding in a motor vehicle; and (c) they must wear a seat belt; (d) where that seat belt has been fitted or is available.

Fig. 7
figure 7

MVWSBR s5(1)

Fig. 8
figure 8

United Kingdom Road Rule 99

Table 2 provides the resulting Boolean logic pseudocode meeting the requirements of MVWSBR s5(1) as expressed by Road Rule 99.

Table 2 Boolean logic pseudocode for MVWSBR s5(1) as represented in Road Rule 99

Road Rule 99 could be written in Boolean logic and expressed in pseudo-English as follows:

$$\begin{gathered} {\text{IF A and C}} \hfill \\ {\text{THEN X}} \hfill \\ {\text{ELSE IF A and NOT C}} \hfill \\ {\text{THEN Y}} \hfill \\ \end{gathered}$$

Boolean Algebra is well-established, mathematically sound, complete, and utilizes the following operators: conjunction ( ×), disjunction ( +), and negation ( ~). This algebra is simple and is sufficient to express most legal rules in a way that most people would understand. In Boolean Algebra, the Boolean logic of Rule 99 would be expressed as:

$$\begin{gathered} {\text{X}} = {\text{A}} \times {\text{C}} \hfill \\ {\text{Y}} = {\text{A }} \times \sim {\text{C}} \hfill \\ \end{gathered}$$

These logic models simplify creation of LawmapsFootnote 6; giving Lawmaps a sound formal basis. The resulting Lawmap for Road Rule 99 combined with its partner rule Road Rule 100, is shown in Fig. 9. Lawmaps are an intelligent, clear and concise but democratised tool for visualising the structure and flow of law and lawyerly processes.Footnote 7 These Lawmaps provide a visual primer of the potential paths and decision points that result from review of a particular law, regulatory rule or legal process. Exemplar Lawmaps are provided for Road Rules in the practical evaluation section of this work.

Fig. 9
figure 9

Exemplar Lawmap for Road Rules 99–100

Finally, many legal practitioners would be familiar with logical thinking and expressing laws and legal rules in the form of Boolean expressions (Aldisert 2001). They are also aware of the need for probabilistic extensions like Bayesian theory when applying the law to the cases, e.g., Bayesian Theory (Fenton et al. 2013; McLachlan 2020).

5.2 Legislative Process: The Landlords and Tenants Act 1954

This example applies the Lawmaps design process to an article of legislation; Sect. 24C of the Landlords and Tenants Act 1954 (the Act).

Locate: Table 3 reproduces section 24C of the Act.

Table 3 Landlords and Tenants Act 1954, s24C

Extract: Review of s24C using a plain language logic approach simplifies it into the listing presented in Table 4. This process investigates the underlying structure and infers applicable intention; identifying key points, processes and the chronology of operations from within the legislation and representing them by application of Boolean algebra as discussed in Sect. 4.

Table 4 Plain language logic listing of s24C of the Act

For example, the above legal rule could be expressed in pseudo-English as follows:

$$\begin{gathered} {\text{IF }}\left( {\text{A or B}} \right){\text{ and C}} \hfill \\ {\text{THEN X}} \hfill \\ {\text{ELSE IF }}\left( {\text{A or B}} \right){\text{ and NOT C}} \hfill \\ {\text{THEN Y}} \hfill \\ \end{gathered}$$

In Boolean Algebra, this may also be written as follows:

$$\begin{gathered} {\text{X}} = \left( {{\text{A}} + {\text{B}}} \right) \times {\text{C}} \hfill \\ {\text{Y}} = \left( {{\text{A}} + {\text{B}}} \right) \times \sim {\text{C}} \hfill \\ \end{gathered}$$

Thus, laws would become machine interpretable as such logical expression could be write into formal legal knowledge-bases, e.g., using languages such as Prolog. The laws could also be directly translated to visual form referred to herein as Lawmaps using flowcharts (detailed Lawmaps) or digital logic notation (Maini 2007). While we are aware of the arguments on the limitations of logical schematisation of legal concepts (Lacock 1964), we contend that use of Boolean logic and logic diagrams could help to formalise some aspects of laws and regulations to allow basic incorporation into AI paradigms and are suitable for high-level visualisation of laws and regulations as well as expressing the core essence of the legal rules as illustrated for the example above using logic diagrams in Figs. 10 and 11 below. Further to this, such a formal basis for legal logic could be easily simulated and so would be very useful in validating the result of the analysis.

Fig. 10
figure 10

The high-level Boolean Algebra-based logic underlying s24C expressed using digital logic notation, which is formal and capable of machine interpretation. The Lawmap visual language and notation presented in this paper presents a more detailed visualisation of this this high-level logic

Fig. 11
figure 11

A simulation (using https://logic.ly/demo/) of how the legal rule of s24C would operate depending on the facts at A, B and C according to the scheme in the previous figure. Blue colour indicates that the legal condition is satisfied. In this snapshot, B and C are satisfied, in which case decision X applies

The notation of logic diagrams illustrated in Figs. 10 and 11 is widely associated with the domain of Electrical and Computer Engineering, which is why this paper proposes the Lawmap diagrammatic notation presented in Table 1. This visualisation language and notation allow Lawmaps to be rendered in the form of flowcharts and are most suitable for expressing the detailed nuances of the flow of logic in the law or regulations as illustrated in Fig. 12. This expressiveness is the reason we have chosen this visual language as the primary notation for Lawmaps in this paper.

Fig. 12
figure 12

Extract of the Application for Interim Rent pathway drawn from s24C of the Landlords and Tenants Act 1954

Identify and distinguish: This portion of the Act provides several relevant examples for describing the lawmap modelling approach. Analysis identified structurally necessary decision points that are shown in the lawmap extract presented in Fig. 12 and which arose out of consideration of points 1, 3, 3a and 3b of the plain language logic. While decision points are also evident from application of point 2 and its sub-points, in sequencing the lawmap we found these occur in the lawmap prior to the reproduced section. Review of other source material identified relevant case law such as that of Cardshops v DaviesFootnote 8 wherein the court found where there is any remaining dispute regarding the terms or term of the tenancy, then these matters must be resolved prior to commencing the interim rent hearing. The effect of this judgment is supported by s34 of the Act which in context assumes the existence of agreed terms by obliging the court to have regard to the terms of the tenancy when determining rent. Sequence: It would be impossible for the court to determine an analogous valuationFootnote 9 for the tenancy where the terms or term of the tenancy remain irresolute. Sequencing this decision required identification of: (i) those activities whose completion would lead to consideration of terms; and (ii) any activities that depend on the presence of settled terms. First, consideration of terms would be unnecessary until, and only after, the tenant has sought a new tenancy which is unopposed by the landlord. Second, given that unresolved terms would prevent an interim rent application being brought before the court, the question of terms must have been resolved prior to those portions of s24C which, if in dispute, would necessitate adjudication of interim rent, and especially those that lead to a s34 rent determination. Traceability: Annotations and explanations have been incorporated into the lawmap that call back to the source materials from which key nodes and pathways were resolved.

5.3 Lawyerly process: conveyancing

Locate: The conveyancing process is normally outlined to law students as a list or table of activities as shown in Table 5.Footnote 10

Table 5 General conveyancing: Outline of a simple conveyancing transaction (adapted from Abbey & Richards)

Identify and distinguish: Each component of the outline described in the source material was first analysed by the lawmap author and later reviewed with input from an expert conveyancing solicitor to identify the node, or nodes, and node type necessary to undertaking that activity as a step in the overall process.

Sequence: While a relationship between seller and buyer activities may be implied by their being colocated in the same row in the source table, relationships and dependencies between different activities were found to be more easily identified and located on the map when the basic process flow was represented in sequence for the expert. The first half of the conveyancing lawmap is shown in Fig. 13 with the seller and buyer pathways represented in corresponding colours to Table 5. Dependencies between Seller and Buyer activities identified by the expert are indicated with a black dashed arrow.

Fig. 13
figure 13

Extract of the overarching primary activities of the Conveyancing lawmap

As shown in Fig. 4 for the first few activity nodes of the Buyer pathway, each of the primary activity nodes in an overarching process flow will consist of either: (a) a nested lawmap: that is, a process flow that is undertaken to completion in order to complete the primary activity node; or (b) a component process represented in legislation, consistent with an established legal idiom or established from regulated procedure, practice rule or due diligence requirement. Often the individual steps of these component processes will be familiar to the expert practitioner, even though they may not be documented in textbooks or procedural practice notices with the same degree of granularity. It is these situations where expert elicitation is of primary importance.

Traceability: For the conveyancing lawmap we found a large number of activities that are undertaken by the experienced conveyancer arising from practice rules, regulatory policy and interaction between these and the requirements of legislation, for example: the Money Laundering, Terrorist Financing and Transfer of Funds (Information on the Payer) Regulations 2017. Traceability for the lawyerly process lawmap also includes annotations describing the content of specific work product that should be produced, such as the client engagement letter.

6 Discussion and future work

Prominent global issues during the first half of 2020 have resulted in significant job losses and an overwhelming economic downturn. Longstanding problems in the way legal services are delivered (Rhode 2012), major reductions in funding and eligibility for legal aid (Flynn and Hodgson 2017),Footnote 11 and an almost intentional lack of information regarding where people should go to get help when a legal issue arises all compound access to justice issues (Sudeall and Richardson 2018). Often, complex situations arise either because a person lacks understanding about their rights and possible remedies in a given situation, or because they lack the knowledge for informed decision-making to understand whether they have taken the necessary actions to enact those rights (Sudeall and Richardson 2018).

This paper presented Lawmaps: an approach to visualising the implicit structure of legislation and the processes practitioners undertake when engaged in work on behalf of their clients. An ostensibly similar infovis approach exists in the medical domain: Caremaps. Like Lawmaps, Caremaps are an expert elicitation process describing domain and expert knowledge that has been demonstrated capable of supporting development of clinical software applications and medical AI (Chowdhury et al. 2020; Hazra and Byun 2020; McLachlan 2020a, b, c; McLachlan et al. 2020c; Wu 2020). We are not the first group to promote the need, or even propose an approach, for infovis in the legal domain. However, we believe ours to be the first of a new breed of simple solutions capable of application across all facets of the legal domain, from legislation to practice; and capable of accelerating development of legal AI. We also believe the knowledge and skills to create process-based infovis like Caremaps and Lawmaps can be acquired by others outside respectively those in the medical and legal domains.

It is not unusual in the legal domain for formulaic approaches like these to be dismissed. Some scholars caution against innovation or change in legal inculcation, practice or reasoning using approaches like the one proposed in this paper, which they describe as cookie-cutter methods (Tarr 2004; Walton and Gordon 2005). They do this often while simultaneously demanding broader and more enriched learning experiences for law students (Tarr 2004). However, it becomes clear why many both within and outside the legal domain still consider the law to be unnecessarily complex and incomprehensible (Wagner and Walker 2019)Footnote 12 when efforts that seek to bring clarity and ease of comprehension to the law like infovis or requirements to couch legislation in plain language continue to be derided in this way (McLachlan and Webley 2020).Footnote 13

While justice should be blind to those who come before the court, the right of those being judged to transparency of the judicial decision-making process means courts have a duty to explain why and how a given ruling has come about (Brennan 1985). Similarly, explainability is a key issue for any application of legal AI. Judges, lawyers, legal scholars and the general public have all decried the black-box nature of many legal AI and espoused the need for those developing and using such systems to ensure they meet the legal requirement for explainability (Deeks 2019; Olsen et al. 2019; Yu and Alì 2019). One who is subject to a decision made by or with the assistance of AI has the same right to explainability as another receiving a jury or judge-alone verdict. Overall, the need for explainability is intended to avoid judgments made at random or in circumstances of uncertainty (Englich et al. 2006). Lawmaps support explainability for both human and algorithmic decision-makers by providing an approachable visual chart of the structure of rules, legislation and precedent used in the decision-making process.

Recent articles provide diametrically opposed views on plain language law, AI and other technologies: while some welcome technology and promote new working models for lawyers, others engender fear through dire warnings that technology’s sole purpose is wholesale replacement of the lawyer.Footnote 14 The latter may be the intention of some technology companies, however legal AI, democratising law and other approaches that produce digital disruption in the legal domain need not bring redundancy for the skilled practitioner. Legal training and practice must accept the inevitability of disruption and begin seeking approaches for transformation. If acknowledged and adopted within the legal domain, rather than replacing lawyers, approaches that may bring disruption can be used to: (i) streamline and improve delivery of legal services, (ii) reduce potential for errors and malpractice; and (iii) increase metaphorical foot traffic through the law firm door by providing those not trained in the law with a way to identify when, and why, they have an issue that should be brought to the expert practitioner.

Digitising lawmaps, merging them with data using a common data model and other structures like legal idioms and ontologies like SALI (www.sali.org) will extend, and may actually simplify, the pathway to developing Legal AI. Figure 14 shows the approach currently employed by the Innovate UK funded Engine B project (www.engineb.com) which delivered complete versions of the examples presented in Sect. 5. Engine B is in the final stages of developing a Common Data Model (CDM) and Knowledge Graphs for commercial property transactions (conveyancing and leasing). These will be used, along with Lawmaps, to develop practitioner-facing AI that will collect and aggregate property data from multiple sources and inform the practitioner’s legal decision-making process.

Fig. 14
figure 14

The Engine-B pathway to Legal AI using Lawmaps

7 Conclusion

Lawmaps are a simple tool for visualising legislation and legal processes that present otherwise complex topics in a way that is approachable to all while, at the same time, facilitating formalisation to allow incorporation into AI paradigms for supporting legal experts. With inherent clarity, Lawmaps are able to expose the implicit flow, knowledge and reasoning of a domain that has clung to incomprehensible text. Lawmaps represent one possible solution to mitigating access to justice issues by providing the untrained person with a visual primer to navigate their way through the intricacies of our legal system while also allowing communicating the law for formalisation by AI technology experts. We believe, and have observed first-hand as part of the Engine B project, that information visualisations like Lawmaps improve comprehension of the rights and duties imposed by law, and represent a significant step on the pathway to developing ethical, accurate and useable legal AI.