<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.3 20210610//EN" "https://jats.nlm.nih.gov/publishing/1.3/JATS-journalpublishing1-3.dtd">
<!--<?xml-stylesheet type="text/xsl" href="article.xsl"?>-->
<article article-type="research-article" dtd-version="1.3" xml:lang="en" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<front>
<journal-meta>
<journal-id journal-id-type="issn">2978-6843</journal-id>
<journal-title-group>
<journal-title>Artificial Intelligence Advances in Education</journal-title>
</journal-title-group>
<issn publication-format="electronic">2978-6843</issn>
<publisher>
<publisher-name>SCS Journals</publisher-name>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="doi">10.66818/aiaie.v1i2.911</article-id>
<article-version>VoR</article-version>
<article-categories>
<subj-group>
<subject>Conceptual analysis</subject>
</subj-group>
</article-categories>
<title-group>
<article-title>Concept of an AI-assisted Regulations and Student Support Chatbot for the Faculty of Engineering at the University of Mauritius</article-title>
</title-group>
<contrib-group>
<contrib contrib-type="author" corresp="yes">
<contrib-id contrib-id-type="orcid">https://orcid.org/0000-0001-9074-3008</contrib-id>
<name>
<surname>Beeharry</surname>
<given-names>Yogesh</given-names>
<prefix>Dr.</prefix>
</name>
<email>y.beeharry@uom.ac.mu</email>
<xref ref-type="aff" rid="aff-1">1</xref>
</contrib>
<contrib contrib-type="author">
<contrib-id contrib-id-type="orcid">https://orcid.org/0000-0001-7561-1816</contrib-id>
<name>
<surname>Ragen</surname>
<given-names>A. K.</given-names>
<prefix>Dr.</prefix>
</name>
<email>ak.ragen@uom.ac.mu</email>
<xref ref-type="aff" rid="aff-1">1</xref>
</contrib>
<contrib contrib-type="author">
<contrib-id contrib-id-type="orcid">https://orcid.org/0000-0001-6292-2746</contrib-id>
<name>
<surname>Khoodaruth</surname>
<given-names>A.</given-names>
<prefix>Dr.</prefix>
</name>
<email>a.khoodaruth@uom.ac.mu</email>
<xref ref-type="aff" rid="aff-1">1</xref>
</contrib>
</contrib-group>
<aff id="aff-1"><label>1</label><institution>Department of Electrical and Electronic Engineering, Faculty of Engineering, University of Mauritius</institution>, <addr-line><named-content content-type="city">R&#233;duit</named-content></addr-line>, <country>Mauritius</country></aff>
<pub-date publication-format="electronic" date-type="pub" iso-8601-date="2026-05-22">
<day>22</day>
<month>05</month>
<year>2026</year>
</pub-date>
<pub-date publication-format="electronic" date-type="collection">
<year>2026</year>
</pub-date>
<volume>1</volume>
<issue>2</issue>
<fpage>1</fpage>
<lpage>17</lpage>
<history>
<date date-type="received" iso-8601-date="2026-01-13">
<day>13</day>
<month>01</month>
<year>2026</year>
</date>
<date date-type="accepted" iso-8601-date="2026-03-31">
<day>31</day>
<month>03</month>
<year>2026</year>
</date>
</history>
<permissions>
<copyright-statement>Copyright: &#x00A9; 2026 The Author(s).</copyright-statement>
<copyright-year>2026</copyright-year>
<license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by-nd/4.0/">
<license-p>This is an open-access article distributed under the terms of the Creative Commons Attribution-NoDerivatives 4.0 International License (CC BY-ND 4.0), which permits to copy and distribute the material in any medium or format only in an unadapted form, as long as the author is named. The license allows commercial use. See <uri xlink:href="https://creativecommons.org/licenses/by-nd/4.0/">https://creativecommons.org/licenses/by-nd/4.0/</uri>.</license-p>
</license>
</permissions>
<self-uri xlink:href="https://scs-journals.com/journals/aiaie/articles/10.66818/aiaie.v1i2.911"/>
<abstract>
<p>The growing complexity of programme regulations, administrative procedures, and academic requirements within higher education institutions often leaves students struggling to access accurate and timely information. This paper presents the concept of an artificial intelligence (AI)-assisted Regulations and Student Support Chatbot designed specifically for the Faculty of Engineering at the University of Mauritius. The proposed system aims to serve as an accessible digital assistant capable of responding to student queries related to programme regulations, progression rules, assessment policies, submission guidelines, and general administrative processes. Leveraging advances in large language models (LLMs) and retrieval-augmented generation (RAG), the chatbot would integrate faculty-specific documents&#8212;such as student handbooks, programme regulations, and official University policies&#8212;into a searchable knowledge base to deliver precise and contextually grounded answers.</p>
<p>Beyond providing information, the chatbot is conceptualised as a tool to enhance student success by reducing uncertainty, improving regulatory literacy, and supporting self-directed learning. It aims to complement rather than replace the academic and administrative support structures by streamlining routine interactions. This would allow staff members to focus on higher-value tasks. The paper outlines the system architecture, data preparation workflow, ethical considerations, and proposed deployment strategy. Emphasis is laid on transparency, accuracy, and responsible use.</p>
<p>By addressing information bottlenecks and improving communication between students and the institution, the proposed AI-assisted chatbot will contribute to a more supportive and efficient learning environment. It aims to illustrate how tailored AI solutions can strengthen student engagement, enhance operational efficiency, and support institutional goals in a resource-constrained higher education context.</p>
</abstract>
<kwd-group>
<kwd>AI-Assisted</kwd>
<kwd>Chatbot</kwd>
<kwd>LLMs</kwd>
<kwd>RAG</kwd>
<kwd>Student Support</kwd>
</kwd-group>
</article-meta>
</front>
<body>
<sec>
<title>1. Introduction</title>
<p>Higher education institutions across the world are undergoing rapid transformation as the integration of artificial intelligence (AI) reshapes administrative processes, learning environments, and student support systems. Universities face growing demands to improve student experience, streamline information delivery, and increase operational efficiency while maintaining high academic standards. There is a need for clear, accessible, and reliable student guidance for engineering faculties where programme regulations, progression rules, and assessment policies are often complex and frequently updated. Students frequently struggle to interpret regulatory documents or navigate institutional procedures, creating bottlenecks that impact academic performance, administrative workload, and overall student satisfaction (<xref ref-type="bibr" rid="B1">Andrenucci &amp; Sneiders, 2005</xref>).</p>
<p>At the University of Mauritius (UoM), the Faculty of Engineering (FoE) offers multiple BEng and postgraduate programmes with distinct rules governing credit accumulation, prerequisites, resits, retake exams, assessments, work placement requirements, and degree classifications. These details are typically distributed across programme regulations, handbooks, departmental guidelines, Senate regulations, and faculty notices. Staff members provide essential support, but increasing enrolment numbers and resource constraints limit the capacity for personalised assistance. Students routinely report confusion around progression criteria, module choices, project regulations, industrial training requirements and assessment timelines, which are issues that contribute to avoidable academic risks. As in many institutions, a significant portion of queries received by administrative and academic staff are repetitive, procedural, and document-based (<xref ref-type="bibr" rid="B23">Winkler &amp; Soellner, 2018</xref>).</p>
<p>Recent advances in natural language processing (NLP) and large language models (LLMs) have introduced new opportunities for educational institutions to automate routine, information-based student services while improving accuracy and accessibility. AI-driven chatbots have demonstrated strong potential in handling high-volume queries, supporting self-regulated learning, and enhancing student engagement through immediate, interactive feedback (<xref ref-type="bibr" rid="B10">Holmes et al., 2019</xref>). Moreover, retrieval-augmented generation (RAG) systems enable AI models to provide grounded, institution-specific answers by retrieving content from official documents before generating a response (<xref ref-type="bibr" rid="B15">Lewis et al., 2020</xref>). These innovations make it feasible for universities to implement reliable, context-aware digital assistants tailored to their regulatory environments.</p>
<p>In this context, the concept of an AI-assisted Regulations &amp; Student Support Chatbot for the FoE at UoM emerges as a timely and strategic initiative. The proposed concept of the chatbot aims to bridge the gap between static regulatory documentation and students&#8217; real-time information needs by serving as an always-available virtual assistant capable of providing accurate and regulation-backed responses. Such a system would address questions on progression rules, module registration, assessment policies, late submission procedures, mitigating circumstances, credit limits, industrial training requirements, and other academic or administrative processes. By centralising information retrieval and enabling natural-language interaction, the chatbot would allow students to find relevant regulations without navigating lengthy documents or relying solely on staff availability.</p>
<p>Importantly, the objective of the chatbot is not to replace academic or administrative staff, but to optimise their workload by reducing repetitive queries and enabling them to focus on complex, high-impact student support. Similar implementations internationally have shown that AI support systems improve staff productivity, reduce administrative delays and enhance students&#8217; confidence in navigating university requirements (<xref ref-type="bibr" rid="B19">Okonkwo &amp; Ade-Ibijola, 2021</xref>; <xref ref-type="bibr" rid="B3">Carayannopoulos, 2018</xref>). In resource-constrained contexts such as Mauritius, where institutions must balance increasing demands with limited human and technological infrastructure, AI-assisted systems offer particularly meaningful benefits.</p>
<p>Furthermore, this initiative aligns not only with broader educational and national strategies but also with the UoM strategic direction, namely digital transformation. Globally, institutions are encouraged to adopt AI responsibly to improve efficiency, transparency, and learner-centred services (<xref ref-type="bibr" rid="B22">Unesco, 2021</xref>). This specific UoM strategic direction emphasises digital transformation, student success and enhanced service delivery, making the proposed chatbot consistent with institutional priorities. Engineering students, who are often early adopters of emerging technologies, are an appropriate cohort to pilot such an innovation within the Mauritian higher education landscape.</p>
<p>The conceptual design of the chatbot incorporates principles of responsible AI usage, including data privacy, accuracy validation, and transparent sourcing of information. By employing a RAG-based architecture, the system can ensure that responses are grounded in official faculty and university regulations rather than generated solely from model inference. This mitigates the risk of hallucinations&#8212;incorrect yet confident AI-generated answers&#8212;which remains a concern in LLM-based systems (<xref ref-type="bibr" rid="B13">Ji et al., 2023</xref>). A governance framework for updating documents, maintaining version control, and ensuring quality assurance is also essential to ensure long-term system reliability.</p>
<p>In addition to providing regulatory information, the chatbot has the potential to support broader aspects of student success. Research shows that AI chatbots can act as low-barrier points of contact, particularly for students who may be hesitant to seek help from staff members (<xref ref-type="bibr" rid="B9">F&#248;lstad &amp; Brandtz&#230;g, 2017</xref>). They provide reminders, personalised guidance, and contextual explanations. This can positively influence student retention and engagement. Although the current concept focuses on programme regulations and administrative support, future extensions will include academic advising, learning resources, mental health signposting, or integration with learning management systems (LMS). Such scalability underscores the potential of the chatbot to evolve into a comprehensive digital companion throughout the student lifecycle.</p>
<sec>
<title>1.1 Research aim</title>
<p>The aim of this study is to design and propose a governance-aware retrieval-augmented chatbot framework for supporting student access to academic regulations within a university environment. The system is intended to function as a first-line informational support tool, enabling students to query institutional policies while ensuring that responses remain grounded in authoritative regulatory documents and aligned with institutional governance requirements.</p>
<p>More specifically, the study aims to develop a conceptual system architecture and evaluation framework that integrates:</p>
<list list-type="bullet">
<list-item><p>a regulatory knowledge base constructed from official institutional documents,</p></list-item>
<list-item><p>semantic information retrieval for locating relevant regulatory clauses,</p></list-item>
<list-item><p>citation-based response generation to ensure traceability of information sources, and</p></list-item>
<list-item><p>a risk-aware escalation mechanism that redirects high-risk queries to human administrators.</p></list-item>
</list>
<p>The overall objective is to propose how conversational AI systems can be designed to support transparent and accountable access to institutional regulations while respecting the governance boundaries of higher education institutions.</p>
</sec>
<sec>
<title>1.2 Research gap</title>
<p>Recent advances in LLMs and conversational AI have led to the rapid adoption of chatbot systems in higher education for student support services. These systems are often used to answer questions related to admissions, course information, and administrative procedures (<xref ref-type="bibr" rid="B14">Kim &amp; Baylor, 2016</xref>). However, existing implementations typically focus on general informational assistance and often rely on generative models that may produce responses without explicit grounding in institutional policy documents.</p>
<p>This raises several challenges when applying chatbot systems to regulatory guidance, where incorrect or unsupported responses may have academic, administrative, or legal consequences for students and institutions (<xref ref-type="bibr" rid="B21">Sharda et al., 2021</xref>).</p>
<p>Despite the growing use of conversational AI in education, several gaps remain in the literature:</p>
<list list-type="order">
<list-item><p><bold>Limited focus on regulatory governance</bold></p>
<p>Most existing chatbot systems in higher education do not explicitly address how institutional regulations should be represented, retrieved, and cited within AI-generated responses.</p></list-item>
<list-item><p><bold>Lack of risk-aware interaction models</bold></p>
<p>Current chatbot implementations rarely distinguish between routine informational queries and high-risk cases such as appeals, disciplinary matters, or exceptional academic circumstances.</p></list-item>
<list-item><p><bold>Insufficient attention to traceability and accountability</bold></p>
<p>Many conversational AI systems prioritise fluent dialogue generation but provide limited mechanisms for tracing responses back to authoritative policy sources.</p></list-item>
<list-item><p><bold>Absence of structured evaluation frameworks for regulatory AI systems</bold></p>
<p>While chatbot performance metrics are widely studied in NLP, fewer studies propose evaluation frameworks specifically tailored to policy-grounded student advisory systems.</p></list-item>
</list>
<p>These gaps highlight the need for system designs that integrate information retrieval, governance constraints, and responsible AI practices when deploying conversational interfaces for institutional regulations (<xref ref-type="bibr" rid="B10">Holmes et al., 2019</xref>).</p>
<p>This paper introduces the conceptual framework for an AI-assisted Regulations &amp; Student Support Chatbot for the FoE. It discusses the motivations, system architecture, expected benefits, ethical considerations, and implementation challenges. By conceptualising a tailored, context-aware and regulation-grounded AI system, this work can contribute to emerging scholarly discussions on AI-driven student support in the context of higher education in developing countries and offers a practical roadmap for enhancing student experience through responsible technological innovation.</p>
</sec>
</sec>
<sec>
<title>2. Literature Review</title>
<p>The integration of AI in educational settings has garnered significant interest, particularly in enhancing student support systems and regulatory compliance. This literature review examines the existing research on AI-assisted chatbots, their applications in educational institutions, and the implications for student engagement and academic success.</p>
<sec>
<title>2.1 AI and educational technology</title>
<p>The advent of AI has transformed educational technology, enabling personalised learning experiences that cater to individual student needs. Luckin et al. (<xref ref-type="bibr" rid="B16">2016</xref>) emphasise the potential of AI to enhance learning by providing adaptive feedback and fostering critical thinking skills. Moreover, AI technologies facilitate the development of intelligent tutoring systems, which can offer real-time support and resources to students.</p>
</sec>
<sec>
<title>2.2 Chatbots as student support tools</title>
<p>AI chatbots have emerged as a viable solution for student support across various academic disciplines. Recent studies indicate that chatbots can effectively address common student inquiries, thus reducing the workload on administrative staff (<xref ref-type="bibr" rid="B4">De La Roca et al., 2024</xref>). For instance, the use of chatbots in universities has been shown to streamline processes such as course registration, scheduling, and answering frequently asked questions. A notable case study at Georgia State University demonstrated a significant increase in student retention rates after the implementation of a chatbot system (<xref ref-type="bibr" rid="B18">Nurshatayeva et al., 2021</xref>).</p>
</sec>
<sec>
<title>2.3 Regulatory compliance in education</title>
<p>Regulatory compliance is an essential aspect of higher education, ensuring that institutions meet established academic standards and practices. AI-driven solutions can assist in monitoring compliance by automatically tracking changes in regulations and facilitating timely updates to institutional policies. Duarte &amp; Vardasca (<xref ref-type="bibr" rid="B7">2023</xref>) highlight the importance of integrating compliance systems within educational technology to maintain institutional integrity and support accreditation processes.</p>
</sec>
<sec>
<title>2.4 User experience and interaction design</title>
<p>The effectiveness of a chatbot is greatly influenced by its design, including user experience and interaction capabilities. A user-centric approach that prioritises intuitive interfaces and NLP enhances user engagement with chatbots. Furthermore, studies indicate that incorporating empathy and emotional intelligence within chatbot interactions can foster positive user experiences, leading to higher satisfaction among students (<xref ref-type="bibr" rid="B12">Jiang et al., 2022</xref>). The design of the chatbot for the FoE will prioritise these aspects to ensure effective communication and support.</p>
</sec>
<sec>
<title>2.5 Cultural considerations in chatbot development</title>
<p>When developing AI chatbots for educational contexts, it is crucial to consider cultural and contextual factors. Luo &amp; Hsiao-Chin (<xref ref-type="bibr" rid="B17">2023</xref>) suggest that chatbots must be tailored to align with the linguistic and cultural nuances of their user base to enhance effectiveness. In the context of the UoM, understanding the local culture and communication styles will be pivotal in designing the chatbot that will resonate with students and staff alike.</p>
</sec>
<sec>
<title>2.6 Challenges and limitations</title>
<p>Despite the potential benefits of AI chatbots in education, challenges exist that must be addressed for successful implementation. Common barriers include resistance to change from staff and students, concerns over data privacy, and the need for ongoing maintenance and updates (<xref ref-type="bibr" rid="B24">Yin, 2021</xref>). It is essential for the UoM to develop a comprehensive strategy that includes training for users and mechanisms for continuous improvement of the chatbot.</p>
</sec>
<sec>
<title>2.7 Future directions</title>
<p>Looking forward, the evolution of AI in education suggests a shift towards more integrated systems that combine chatbots with other technological innovations, such as LMS and data analytics tools. By enabling seamless interactions among various platforms, higher educational institutions can create a comprehensive support ecosystem that enhances both academic and administrative functions (<xref ref-type="bibr" rid="B2">Ashok et al., 2021</xref>).</p>
<p>The literature underscores the transformative potential of AI-assisted chatbots in enhancing student support and regulatory compliance within higher educational institutions. By leveraging insights from existing research, the proposed chatbot for the FoE aims to foster a supportive academic environment that aligns with current technological advancements and meets the needs of its diverse student body. Future research should continue to explore the impacts of such technologies and iterate on their designs to maximise effectiveness and user engagement.</p>
</sec>
</sec>
<sec>
<title>3. System Model</title>
<sec>
<title>3.1 Study type</title>
<p>This research adopts a design-oriented conceptual study that proposes a system architecture and evaluation framework for a regulatory-support chatbot.</p>
<p>The study does not present a deployed system or empirical performance evaluation. Instead, it focuses on:</p>
<list list-type="bullet">
<list-item><p>defining the structure of a regulatory knowledge base,</p></list-item>
<list-item><p>proposing a retrieval-augmented chatbot architecture, and</p></list-item>
<list-item><p>outlining a set of evaluation metrics and governance mechanisms for assessing such systems.</p></list-item>
</list>
<p>The work can therefore be characterised as a design science research contribution, where the primary output is a conceptual artefact consisting of:</p>
<list list-type="bullet">
<list-item><p>a system architecture,</p></list-item>
<list-item><p>a dataset design methodology, and</p></list-item>
<list-item><p>an evaluation framework for regulatory chatbot systems.</p></list-item>
</list>
<p>By articulating the design principles, implementation considerations and evaluation criteria, the study aims to provide a foundation for future empirical implementations and experimental evaluations of AI-assisted regulatory support tools in higher education.</p>
</sec>
<sec>
<title>3.2 Expected contribution</title>
<p>The contribution of this study lies in the conceptualisation of a governance-aware chatbot framework tailored to institutional regulations in higher education. Specifically, the study contributes:</p>
<list list-type="order">
<list-item><p>A structured approach to constructing a regulatory knowledge base suitable for conversational AI systems.</p></list-item>
<list-item><p>A retrieval-augmented system architecture designed to improve traceability and citation of regulatory sources.</p></list-item>
<list-item><p>A risk-aware query classification and escalation model to ensure appropriate handling of sensitive student queries.</p></list-item>
<list-item><p>A proposed evaluation framework for assessing the reliability, governance compliance, and usability of regulatory-support chatbots.</p></list-item>
</list>
<p>Together, these elements provide a methodological foundation that can support future research and practical deployments of AI systems for regulatory guidance in higher education institutions.</p>
</sec>
<sec>
<title>3.3 System overview</title>
<p>The proposed AI-assisted Regulations and Student Support Chatbot is designed to provide reliable, regulation-grounded guidance to students of the FoE. The system will prioritise accuracy, traceability, and accountability by grounding all responses in official institutional documents and embedding governance mechanisms that enable human oversight.</p>
<p>To achieve these objectives, the system adopts a Retrieval-Augmented Conversational Architecture, where semantic retrieval from a curated regulatory knowledge base precedes controlled response generation.</p>
</sec>
<sec>
<title>3.4 Block diagram of the proposed system</title>
<p>The block diagram of the proposed system is shown in <xref ref-type="fig" rid="F1">Figure 1</xref>.</p>
<fig id="F1">
<label>Figure 1</label>
<caption>
<p>Block diagram of the AI-assisted Regulations and Student Support Chatbot.</p>
</caption>
<graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="aiaie-v1i2-911-g1.png"/>
</fig>
<sec>
<title>3.4.1 User interaction module</title>
<p>This module will provide the interface through which students interact with the chatbot using natural language queries. The interface will be accessible via web and mobile platforms and supports bilingual interaction in English and French. The module will ensure ease of use, accessibility, and clear communication of the system&#8217;s advisory role.</p>
</sec>
<sec>
<title>3.4.2 Query processing and risk classification module</title>
<p>Once a query is received, it will be processed to identify its language, remove irrelevant noise, and standardise the input. The query will then be analysed to determine its risk category, distinguishing between routine informational requests (e.g., credit requirements, deadlines) and high-stakes regulatory matters (e.g., appeals, disciplinary issues).</p>
<p>This risk-aware classification plays a critical role in downstream decision-making, particularly in determining confidence thresholds and escalation requirements. A flowchart to visualise the user&#8217;s journey from query to response is shown in <xref ref-type="fig" rid="F2">Figure 2</xref>.</p>
<fig id="F2">
<label>Figure 2</label>
<caption>
<p>Flow chart on User&#8217;s journey from query to response.</p>
</caption>
<graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="aiaie-v1i2-911-g2.png"/>
</fig>
</sec>
<sec>
<title>3.4.3 Knowledge base and document management module</title>
<p>This module will represent the authoritative backbone of the system. It will contain official documents issued by the FoE, including:</p>
<list list-type="bullet">
<list-item><p>general academic regulations,</p></list-item>
<list-item><p>faculty and programme handbooks,</p></list-item>
<list-item><p>programme regulations,</p></list-item>
<list-item><p>assessment and progression rules, and</p></list-item>
<list-item><p>official circulars and notices.</p></list-item>
</list>
<p>The relevant documents will be segmented into structured regulatory units (clauses or subsections) and enriched with metadata such as document source, section number, and validity period. A version control mechanism ensures that outdated regulations are archived and that only current policies are used for active responses.</p>
</sec>
<sec>
<title>3.4.4 Information retrieval module</title>
<p>The Information Retrieval Module will perform semantic matching between the processed user query and the regulatory units stored in the knowledge base. Instead of relying solely on keyword matching. This module will identify conceptually relevant clauses, enabling effective handling of informal or paraphrased student queries.</p>
<p>Only the most relevant regulatory segments will be forwarded to the response generation stage, ensuring precision and relevance.</p>
</sec>
<sec>
<title>3.4.5 Retrieval-augmented response generation module</title>
<p>This module will generate student-facing responses using an RAG approach. The retrieved regulatory segments will be used as authoritative context, constraining the response to verified information.</p>
<p>The generated response aims to:</p>
<list list-type="bullet">
<list-item><p>answer the query clearly and concisely,</p></list-item>
<list-item><p>explain applicable regulations in accessible language, and</p></list-item>
<list-item><p>reference the originating regulatory document and section.</p></list-item>
</list>
<p>If sufficient regulatory information is unavailable, the system will explicitly state its limitation rather than generating speculative advice.</p>
</sec>
<sec>
<title>3.4.6 Response validation and confidence estimation module</title>
<p>Before delivering a response, the system will evaluate its reliability using a confidence estimation mechanism. This evaluation considers:</p>
<list list-type="bullet">
<list-item><p>relevance and consistency of retrieved documents,</p></list-item>
<list-item><p>completeness of the regulatory context, and</p></list-item>
<list-item><p>the identified risk level of the query.</p></list-item>
</list>
<p>A confidence score will be computed and compared against a predefined threshold to determine whether the response can be safely delivered or requires escalation.</p>
</sec>
<sec>
<title>3.4.7 Human escalation and governance module</title>
<p>For queries classified as high risk or responses with insufficient confidence, the system will activate a human escalation pathway. In such cases, the chatbot will provide general guidance and direct the student to the appropriate Faculty authority (e.g., Programme Coordinator, Faculty Registry, Examinations Office).</p>
<p>This module will also support governance functions such as interaction logging, auditability, and system performance monitoring, ensuring compliance with institutional policies and ethical guidelines.</p>
</sec>
</sec>
<sec>
<title>3.5 Integration of the system model</title>
<p>The interaction between the functional blocks will ensure that:</p>
<list list-type="bullet">
<list-item><p>all responses are regulation-grounded,</p></list-item>
<list-item><p>high-risk decisions remain human-controlled,</p></list-item>
<list-item><p>transparency and traceability are maintained, and</p></list-item>
<list-item><p>the system remains adaptable to regulatory changes.</p></list-item>
</list>
<p>By embedding governance and escalation mechanisms directly into the system architecture, the proposed model will be designed to align with best practices for deploying AI systems in regulated educational environments.</p>
</sec>
<sec>
<title>3.6 Summary</title>
<p>The proposed system architecture will adopt a risk classifier coupled with a human-in-the-loop (HITL) decision layer, grounded in established principles from decision support systems (DSS) and AI ethics. In DSS literature, AI systems are explicitly designed not as autonomous decision-makers but as tools that support human judgment, providing recommendations that must be validated or overridden by a human expert. For example, Power (<xref ref-type="bibr" rid="B20">2002</xref>) emphasises that DSS are intended to augment, rather than replace, human decision-making, particularly in semi-structured and unstructured problem domains.</p>
<p>The inclusion of a risk classifier is motivated by the need to operationalise uncertainty and decision criticality. By estimating the likelihood that a response may be incorrect, ambiguous, or context-dependent, the system can distinguish between low-risk queries (e.g., factual FAQs) and high-risk cases (e.g., policy interpretation or academic decisions). This aligns with research in human-AI systems design, where Horvitz (<xref ref-type="bibr" rid="B11">1999</xref>) introduced principles of mixed-initiative interaction, advocating for systems that dynamically determine when to act autonomously and when to defer to human control. Hypothetically, effective deployment would result in high automation accuracy for routine queries while selectively escalating complex cases, thereby balancing efficiency and reliability.</p>
<p>From an AI ethics perspective, the HITL approach is essential to ensure accountability, fairness, and oversight. The European Commission&#8217;s High-Level Expert Group on Artificial Intelligence (<xref ref-type="bibr" rid="B8">European Commission, 2019</xref>) explicitly identifies human agency and oversight as a core requirement for trustworthy AI systems. Similarly, Dignum (<xref ref-type="bibr" rid="B5">2019</xref>) argues that responsible AI must incorporate mechanisms for human control, particularly in high-stakes or socially sensitive contexts such as education. In practice, this means that the system should not only generate answers but also provide confidence estimates and trigger escalation mechanisms when thresholds are not met. A desirable outcome would be a system where human oversight is concentrated on genuinely complex or high-stakes cases, while routine interactions are safely automated.</p>
<p>Finally, the integration of explainability within this architecture reflects broader regulatory and ethical trends. Explainable AI is increasingly viewed as a prerequisite for trustworthy DSS, particularly in domains where users must justify or rely on AI-supported decisions. Doshi-Velez &amp; Kim, (<xref ref-type="bibr" rid="B6">2017</xref>) highlight the importance of interpretability for ensuring transparency, user trust, and effective human-AI collaboration. In this context, the combination of retrieval grounding, risk classification, and human oversight forms a coherent socio-technical design: the system provides evidence-based responses, evaluates its own uncertainty, and defers to human judgment when necessary. This layered approach is therefore well-justified both theoretically and practically for an AI system intended to support student success and institutional decision-making.</p>
<p>The block diagram and accompanying system model illustrate a modular, governance-aware AI chatbot architecture tailored to the regulatory and operational context of the FoE. The design balances automation with institutional oversight, ensuring that the system enhances student support while preserving academic integrity and regulatory compliance.</p>
</sec>
</sec>
<sec>
<title>4. Discussion</title>
<sec>
<title>4.1 Overview of the system model in practice</title>
<p>The proposed system model proposes how an AI-assisted chatbot can be safely deployed in a highly regulated academic environment such as the FoE. Unlike general-purpose conversational agents, this system will intentionally be constrained by design choices that prioritise regulatory correctness, traceability, and institutional accountability.</p>
<p>The layered architecture&#8212;comprising query processing, semantic retrieval, retrieval-augmented response generation, validation, and human escalation&#8212;ensures that automation is applied selectively. This design directly addresses concerns identified in the literature regarding hallucinations, liability, and loss of trust in AI-driven student services. The discussion that follows critically examines how each component of the system model influences dataset design and metric selection as reflected in the evaluation tables.</p>
</sec>
<sec>
<title>4.2 System implementation details</title>
<p>This section describes the implementation of the regulatory-support chatbot system, including the architecture, major design decisions, conflict-resolution mechanisms, and potential failure modes. The objective of this description is to enable reproducibility of the system design and facilitate replication in similar institutional environments.</p>
<sec>
<title>4.2.1 System architecture</title>
<p>The system follows a RAG architecture composed of five primary modules:</p>
<list list-type="order">
<list-item><p>Document ingestion and preprocessing module,</p></list-item>
<list-item><p>Vector indexing and metadata storage,</p></list-item>
<list-item><p>Query processing and semantic retrieval module,</p></list-item>
<list-item><p>Risk-aware classification and escalation module, and</p></list-item>
<list-item><p>Response generation and citation module.</p></list-item>
</list>
<p>Each component is described below.</p>
<sec>
<title>4.2.1.1 Document ingestion and preprocessing</title>
<p><bold>Document Sources</bold></p>
<p>The system ingests official institutional documents from faculty and university repositories, including:</p>
<list list-type="bullet">
<list-item><p>university regulations,</p></list-item>
<list-item><p>faculty regulations,</p></list-item>
<list-item><p>programme handbooks,</p></list-item>
<list-item><p>assessment rules, and</p></list-item>
<list-item><p>circulars and notices.</p></list-item>
</list>
<p>Documents are processed only if they originate from verified institutional sources.</p>
<p><bold>Text extraction</bold></p>
<p>Documents in PDF or DOCX format are converted into plain text using automated parsing tools. Structural markers such as headings, section numbers, and clause identifiers are preserved to maintain the legal context of regulations.</p>
<p><bold>Clause-level segmentation</bold></p>
<p>Documents are segmented into regulatory clauses, which serve as the fundamental retrieval unit.</p>
<p>Segmentation follows these rules:</p>
<list list-type="order">
<list-item><p>Each numbered rule is treated as a separate clause.</p></list-item>
<list-item><p>Bullet-point policy statements are treated as independent clauses.</p></list-item>
<list-item><p>Long paragraphs are split into sentences when they contain multiple regulatory conditions.</p></list-item>
</list>
<p>Each clause is stored as a structured record containing:</p>
<list list-type="bullet">
<list-item><p>clause text,</p></list-item>
<list-item><p>document identifier,</p></list-item>
<list-item><p>section number,</p></list-item>
<list-item><p>document category,</p></list-item>
<list-item><p>language,</p></list-item>
<list-item><p>faculty applicability, and</p></list-item>
<list-item><p>validity period.</p></list-item>
</list>
<p>This segmentation decision was made to improve semantic retrieval precision. Clause-level indexing reduces ambiguity when answering specific regulatory queries.</p>
</sec>
<sec>
<title>4.2.1.2 Vector indexing and knowledge base construction</title>
<p>Each clause is embedded into a semantic vector representation using a pre-trained sentence embedding model.</p>
<p>The embedding process converts each clause into a high-dimensional vector that captures semantic meaning. These vectors are stored in a vector index that supports approximate nearest-neighbour search.</p>
<p><bold>Index structure</bold></p>
<p>The knowledge base contains two linked storage layers:</p>
<p><bold>Vector index</bold></p>
<list list-type="bullet">
<list-item><p>stores clause embeddings, and</p></list-item>
<list-item><p>used for semantic similarity search.</p></list-item>
</list>
<p><bold>Metadata database</bold></p>
<list list-type="bullet">
<list-item><p>stores document metadata and governance fields, and</p></list-item>
<list-item><p>used for filtering and conflict resolution.</p></list-item>
</list>
<p>The metadata database is linked to the vector index through a unique clause identifier.</p>
<p><bold>Metadata filtering</bold></p>
<p>During retrieval, candidate clauses are filtered based on:</p>
<list list-type="bullet">
<list-item><p>faculty applicability,</p></list-item>
<list-item><p>programme applicability, and</p></list-item>
<list-item><p>validity period.</p></list-item>
</list>
<p>This ensures that obsolete or irrelevant regulations are not returned in responses.</p>
</sec>
<sec>
<title>4.2.1.3 Query processing pipeline</title>
<p>When a user submits a query, the system performs the following sequence of operations.</p>
<p><bold>Step 1: Query normalisation</bold></p>
<p>The input query is cleaned and standardised through:</p>
<list list-type="bullet">
<list-item><p>removal of formatting artefacts,</p></list-item>
<list-item><p>language detection, and</p></list-item>
<list-item><p>token normalisation.</p></list-item>
</list>
<p>If the query is written in French, a multilingual embedding model is used to ensure semantic compatibility with English documents.</p>
<p><bold>Step 2: Risk classification</bold></p>
<p>The query is classified into one of three risk levels:</p>
<list list-type="bullet">
<list-item><p>low risk,</p></list-item>
<list-item><p>medium risk, and</p></list-item>
<list-item><p>high risk.</p></list-item>
</list>
<p>Risk classification is performed using a rule-based classifier supported by keyword patterns and query intent analysis.</p>
<p>Examples of high-risk indicators include terms such as:</p>
<list list-type="bullet">
<list-item><p>appeal,</p></list-item>
<list-item><p>disciplinary,</p></list-item>
<list-item><p>misconduct,</p></list-item>
<list-item><p>mitigation, and</p></list-item>
<list-item><p>exemption request.</p></list-item>
</list>
<p>High-risk queries are flagged for potential escalation.</p>
<p><bold>Step 3: Semantic retrieval</bold></p>
<p>The query embedding is compared with clause embeddings stored in the vector index.</p>
<p>The system retrieves the <bold>top-k most similar clauses</bold>, typically between three and five candidates.</p>
<p>Similarity is computed using cosine similarity between vectors.</p>
<p>Candidate clauses are then filtered using metadata constraints.</p>
<p><bold>Step 4: Evidence ranking</bold></p>
<p>Retrieved clauses are ranked according to:</p>
<list list-type="bullet">
<list-item><p>semantic similarity score,</p></list-item>
<list-item><p>document authority level, and</p></list-item>
<list-item><p>regulatory recency.</p></list-item>
</list>
<p>Authority level is determined using the following hierarchy:</p>
<list list-type="order">
<list-item><p>university regulations,</p></list-item>
<list-item><p>faculty regulations,</p></list-item>
<list-item><p>programme handbooks, and</p></list-item>
<list-item><p>circulars and notices.</p></list-item>
</list>
<p>Higher-authority documents are prioritised when multiple clauses match a query.</p>
</sec>
<sec>
<title>4.2.1.5 Response generation and citation</title>
<p>The final response is generated by a language model conditioned on the retrieved clauses.</p>
<p>The prompt structure includes:</p>
<list list-type="bullet">
<list-item><p>the original query,</p></list-item>
<list-item><p>the retrieved clauses,</p></list-item>
<list-item><p>metadata about each clause, and</p></list-item>
<list-item><p>instructions to cite the source document.</p></list-item>
</list>
<p>The model is instructed to:</p>
<list list-type="order">
<list-item><p>summarise the relevant regulations,</p></list-item>
<list-item><p>provide citations referencing document title and section number, and</p></list-item>
<list-item><p>avoid making unsupported claims outside the retrieved evidence.</p></list-item>
</list>
<p>If insufficient evidence is retrieved, the system produces a fallback message requesting clarification or recommending contact with administrative staff.</p>
</sec>
<sec>
<title>4.2.1.5 Handling conflicting regulations</title>
<p>Conflicts between regulatory documents may occur when:</p>
<list list-type="bullet">
<list-item><p>older regulations remain accessible,</p></list-item>
<list-item><p>programme-specific rules differ from general faculty rules, and</p></list-item>
<list-item><p>circulars temporarily modify official policies.</p></list-item>
</list>
<p>To address this issue, the system implements a rule precedence hierarchy.</p>
<p><bold>Regulation precedence order</bold></p>
<p>When conflicting clauses are retrieved, the following precedence rules are applied:</p>
<list list-type="order">
<list-item><p><bold>Latest valid regulation</bold></p>
<p>Clauses with a more recent validity period override older clauses.</p></list-item>
<list-item><p><bold>Higher authority level</bold></p>
<p>University-wide regulations override faculty or programme rules.</p></list-item>
<list-item><p><bold>Programme-specific rules</bold></p>
<p>Programme rules override generic faculty rules when applicable.</p></list-item>
<list-item><p><bold>Temporary circulars</bold></p>
<p>Circulars override regulations only if explicitly marked as active.</p></list-item>
</list>
<p><bold>Conflict detection</bold></p>
<p>A conflict is detected when retrieved clauses contain contradictory statements, such as different credit requirements or deadlines.</p>
<p>When conflicts are detected, the system performs one of the following actions:</p>
<list list-type="bullet">
<list-item><p>present both clauses with clarification,</p></list-item>
<list-item><p>prioritise the clause with higher precedence, and</p></list-item>
<list-item><p>escalate the query to human administration.</p></list-item>
</list>
<p>The escalation option is used when the system cannot determine a clear resolution.</p>
</sec>
</sec>
</sec>
<sec>
<title>4.3 Failure modes</title>
<p>Several failure modes were identified during system design.</p>
<p><bold>Retrieval failure</bold></p>
<p>Relevant clauses may not be retrieved due to:</p>
<list list-type="bullet">
<list-item><p>incomplete document coverage,</p></list-item>
<list-item><p>semantic mismatch between query and clause wording, and</p></list-item>
<list-item><p>insufficient embedding representation.</p></list-item>
</list>
<p>Mitigation strategies include expanding the document corpus and tuning the retrieval model.</p>
<p><bold>Hallucinated responses</bold></p>
<p>The language model may generate unsupported statements not present in the retrieved evidence.</p>
<p>To reduce this risk, the system restricts responses to retrieved clauses and requires explicit citation.</p>
<p><bold>Metadata errors</bold></p>
<p>Incorrect metadata annotation (e.g., wrong validity period) may cause outdated regulations to appear in responses.</p>
<p>Periodic dataset validation is required to maintain metadata accuracy.</p>
<p><bold>Risk misclassification</bold></p>
<p>A query may be incorrectly classified as low-risk when it requires administrative oversight.</p>
<p>To mitigate this, the system adopts a conservative strategy where ambiguous queries are escalated.</p>
</sec>
<sec>
<title>4.4 Replication requirements</title>
<p>To replicate the implementation described in this study, the following components are required:</p>
<list list-type="bullet">
<list-item><p>a corpus of institutional regulatory documents,</p></list-item>
<list-item><p>a clause-level segmentation pipeline,</p></list-item>
<list-item><p>a multilingual embedding model,</p></list-item>
<list-item><p>a vector search index supporting semantic retrieval,</p></list-item>
<list-item><p>a metadata database containing governance attributes,</p></list-item>
<list-item><p>a LLM for response generation, and</p></list-item>
<list-item><p>a rule-based risk classification system.</p></list-item>
</list>
<p>Together, these components form a reproducible framework for building regulatory-aware chatbot systems in higher education environments.</p>
</sec>
<sec>
<title>4.5 Alignment between system architecture and dataset design</title>
<p>A central strength of the system model lies in the tight coupling between architecture and dataset construction. The regulatory document corpus, described in <xref ref-type="table" rid="T1">Table 1</xref> (dataset composition summary), will not be treated as unstructured text but as a curated, version-controlled institutional knowledge base.</p>
<table-wrap id="T1" specific-use="rules">
<label>Table 1</label>
<caption>
<p>Dataset Composition Summary (Regulatory Knowledge Base)</p>
</caption>
<table frame="hsides" rules="all">
<thead>
<tr>
<th align="left" valign="top">Document Category</th>
<th align="left" valign="top">Language</th>
<th align="left" valign="top">Update Frequency</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left" valign="top">General University Regulations</td>
<td align="left" valign="top">English</td>
<td align="left" valign="top">Annual</td>
</tr>
<tr>
<td align="left" valign="top">Faculty of Engineering Regulations</td>
<td align="left" valign="top">English</td>
<td align="left" valign="top">Annual</td>
</tr>
<tr>
<td align="left" valign="top">Programme Handbooks (BEng/MSc)</td>
<td align="left" valign="top">English</td>
<td align="left" valign="top">Annual</td>
</tr>
<tr>
<td align="left" valign="top">Assessment &amp; Examination Rules</td>
<td align="left" valign="top">English</td>
<td align="left" valign="top">Biennial</td>
</tr>
<tr>
<td align="left" valign="top">Faculty Circulars &amp; Notices</td>
<td align="left" valign="top">English / French</td>
<td align="left" valign="top">Ad hoc</td>
</tr>
</tbody>
</table>
</table-wrap>
<p><xref ref-type="table" rid="T1">Table 1</xref> categorises the dataset into document types (e.g., general regulations, faculty handbooks, programme specifications, assessment regulations) and reports attributes such as:</p>
<list list-type="bullet">
<list-item><p>number of documents per category,</p></list-item>
<list-item><p>average number of regulatory clauses per document,</p></list-item>
<list-item><p>language distribution (English/French), and</p></list-item>
<list-item><p>update frequency.</p></list-item>
</list>
<p><xref ref-type="table" rid="T1">Table 1</xref> highlights that document granularity directly affects retrieval performance. Clause-level segmentation enables the Information Retrieval Module to achieve higher Recall scores compared to paragraph-level segmentation, as it reduces ambiguity and improves semantic matching. However, finer segmentation also increases index size and retrieval complexity, which must be managed through efficient indexing strategies.</p>
<p>The inclusion of metadata fields such as validity period and faculty applicability&#8212;outlined in <xref ref-type="table" rid="T1">Table 1</xref>&#8212;supports the system&#8217;s governance objectives and prevents outdated or cross-faculty regulations from being surfaced to students.</p>
<sec>
<title>4.5.1 Regulatory knowledge base dataset construction and metrics</title>
<p>The regulatory knowledge base dataset was constructed to represent the institutional rules and policies governing academic administration within the FoE. The objective of the dataset design is to provide a structured and traceable source of regulatory information that could support reliable retrieval and citation by the chatbot system.</p>
<p><bold>Source documents:</bold></p>
<p>The dataset was compiled from official institutional documents obtained from university repositories and faculty administrative records. The sources include:</p>
<list list-type="bullet">
<list-item><p>general university regulations and academic rules,</p></list-item>
<list-item><p>FoE regulatory documents,</p></list-item>
<list-item><p>programme handbooks for undergraduate and postgraduate programmes,</p></list-item>
<list-item><p>assessment and examination regulations, and</p></list-item>
<list-item><p>faculty circulars and administrative notices.</p></list-item>
</list>
<p>Only authoritative documents formally issued by the university or faculty were included in the dataset to ensure that the system references official policy sources. Informal communications such as emails or student forum posts were excluded.</p>
<p><bold>Document processing pipeline:</bold></p>
<p>The dataset construction process followed a multi-stage pipeline:</p>
<list list-type="order">
<list-item><p><bold>Document collection:</bold></p>
<p>Regulatory documents were collected in digital format (primarily PDF and Word documents). Each document was assigned a unique document identifier.</p></list-item>
<list-item><p><bold>Text extraction:</bold></p>
<p>Text content was extracted from the documents using automated parsing tools. Non-textual elements such as images and decorative formatting were removed. Section headings, numbering structures, and clause identifiers were preserved to maintain regulatory context.</p></list-item>
<list-item><p><bold>Clause-level segmentation:</bold></p>
<p>To improve retrieval precision, documents were segmented into regulatory clauses, defined as the smallest self-contained unit of policy that expresses a rule or condition.</p>
<p>A clause was operationally defined as:</p>
<list list-type="bullet">
<list-item><p>a numbered rule,</p></list-item>
<list-item><p>a bullet-point policy statement, and</p></list-item>
<list-item><p>or a sentence expressing a specific requirement or condition.</p></list-item>
</list>
<p>Each clause was stored as an independent retrieval unit while maintaining links to its parent document and section.</p>
<p>Clause segmentation was selected instead of paragraph-level segmentation because it reduces semantic ambiguity and enables more precise retrieval of policy statements.</p></list-item>
<list-item><p><bold>Metadata annotation:</bold></p>
<p>Each clause entry was enriched with metadata fields to support governance-aware retrieval and filtering. The metadata schema included:</p>
<p><table-wrap specific-use="rules">
<table frame="hsides" rules="all">
<thead>
<tr>
<th align="left" valign="top">Metadata Field</th>
<th align="left" valign="top">Description</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left" valign="top"><bold>Document Category</bold></td>
<td align="left" valign="top">Type of institutional document (e.g. regulations, handbook, circular)</td>
</tr>
<tr>
<td align="left" valign="top"><bold>Faculty Applicability</bold></td>
<td align="left" valign="top">Faculty or institutional scope</td>
</tr>
<tr>
<td align="left" valign="top"><bold>Programme Applicability</bold></td>
<td align="left" valign="top">Programme or degree to which the clause applies</td>
</tr>
<tr>
<td align="left" valign="top"><bold>Language</bold></td>
<td align="left" valign="top">Language of the clause (English or French)</td>
</tr>
<tr>
<td align="left" valign="top"><bold>Validity Period</bold></td>
<td align="left" valign="top">Time interval during which the regulation is applicable</td>
</tr>
<tr>
<td align="left" valign="top"><bold>Update Frequency</bold></td>
<td align="left" valign="top">Expected revision cycle of the document</td>
</tr>
<tr>
<td align="left" valign="top"><bold>Source Reference</bold></td>
<td align="left" valign="top">Original document title and section number</td>
</tr>
</tbody>
</table>
</table-wrap></p></list-item>
</list>
<p>The inclusion of validity period and faculty applicability ensures that outdated or irrelevant policies are not retrieved during query processing.</p>
<p><bold>Dataset attributes</bold></p>
<p>The composition of the regulatory dataset uses the following metrics:</p>
<p><bold>Number of documents per category:</bold></p>
<p>The total count of documents belonging to each document category.</p>
<p>Formally:</p>
<p>Number of Documents (category i) = count of all documents assigned to category i</p>
<p>This metric provides an overview of dataset coverage across different regulatory sources.</p>
<p><bold>Average number of regulatory clauses per document</bold></p>
<p>The number of clause-level entries extracted from documents within each category.</p>
<p>Formula:</p>
<p>Average clauses per document = (Total number of extracted clauses in category) &#247; (Number of documents in category)</p>
<p>This metric reflects document complexity and influences the number of indexed retrieval units.</p>
<p><bold>Large distribution:</bold></p>
<p>The proportion of clauses written in each supported language.</p>
<p>Language Proportion (L) = (Number of clauses in language L) &#247; (Total number of clauses)</p>
<p>This metric helps determine the extent of multilingual content in the regulatory dataset.</p>
<p><bold>Update frequency</bold></p>
<p>The expected revision cycle of documents within a category. This value is derived from institutional policy review schedules.</p>
<p>Typical categories include:</p>
<list list-type="bullet">
<list-item><p>annual updates (e.g., programme handbooks),</p></list-item>
<list-item><p>biennial updates (e.g., examination regulations), and</p></list-item>
<list-item><p>ad hoc updates (e.g., circulars and notices).</p></list-item>
</list>
<p>Update frequency informs dataset maintenance strategies and helps determine when re-indexing of the knowledge base is required.</p>
<p><bold>Impact of document granularity</bold></p>
<p>Document granularity refers to the size of the textual units used for retrieval. In this dataset, clause-level segmentation is used as the primary indexing unit.</p>
<p>Smaller retrieval units reduce semantic ambiguity by isolating specific rules or requirements. However, finer segmentation increases the total number of indexed items, which may increase storage requirements and retrieval computation. Efficient indexing structures (such as vector embeddings and metadata filtering) are therefore required to maintain retrieval efficiency.</p>
</sec>
<sec>
<title>4.5.2 Query dataset construction and risk classification</title>
<p>A separate query dataset will be created to simulate realistic student interactions with the chatbot system and to evaluate system behaviour under different levels of institutional risk.</p>
<p><bold>Query source generation</bold></p>
<p>Queries will be generated using three complementary approaches:</p>
<list list-type="order">
<list-item><p><bold>Student enquiry logs</bold></p>
<p>Common administrative questions collected from faculty administrative offices.</p></list-item>
<list-item><p><bold>Programme handbook scenarios</bold></p>
<p>Hypothetical questions derived from rules and conditions described in programme regulations.</p></list-item>
<list-item><p><bold>Expert-generated queries</bold></p>
<p>Queries formulated by academic administrators to represent complex regulatory cases.</p></list-item>
<list-item><p>The resulting query set will be designed to cover the most common regulatory topics encountered by students.</p></list-item>
</list>
<p><bold>Query categories</bold></p>
<p>Queries will be grouped into thematic categories reflecting major administrative processes:</p>
<list list-type="bullet">
<list-item><p>programme progression,</p></list-item>
<list-item><p>assessment and examinations,</p></list-item>
<list-item><p>registration and enrolment,</p></list-item>
<list-item><p>graduation requirements,</p></list-item>
<list-item><p>appeals and mitigation, and</p></list-item>
<list-item><p>disciplinary or special cases.</p></list-item>
</list>
<p>These categories correspond to major regulatory domains within faculty administration.</p>
<p><bold>Risk level classification</bold></p>
<p>Each query will be assigned a risk level representing the potential consequences of providing an incorrect automated response. Risk classification will be performed using the following criteria:</p>
<p><bold>Low-risk queries</bold></p>
<p>Queries requesting informational clarification about regulations.</p>
<p>Examples include:</p>
<list list-type="bullet">
<list-item><p>module registration procedures,</p></list-item>
<list-item><p>examination schedules, and</p></list-item>
<list-item><p>general progression rules.</p></list-item>
</list>
<p>Errors in these responses are unlikely to create institutional or legal consequences.</p>
<p><bold>Medium-risk queries</bold></p>
<p>Queries related to eligibility conditions or academic outcomes.</p>
<p>Examples include:</p>
<list list-type="bullet">
<list-item><p>graduation eligibility,</p></list-item>
<list-item><p>credit completion requirements, and</p></list-item>
<list-item><p>programme progression thresholds.</p></list-item>
</list>
<p>Incorrect responses could mislead students but typically remain correctable through administrative follow-up.</p>
<p><bold>High-risk queries</bold></p>
<p>Queries involving appeals, disciplinary actions, or exceptional cases.</p>
<p>Examples include:</p>
<list list-type="bullet">
<list-item><p>academic appeals,</p></list-item>
<list-item><p>misconduct procedures, and</p></list-item>
<list-item><p>requests for special mitigation.</p></list-item>
</list>
<p>These cases often require formal institutional review and human oversight, and therefore must trigger escalation rather than automated decision-making.</p>
</sec>
</sec>
<sec>
<title>4.6 Query dataset characteristics and risk distribution</title>
<p><xref ref-type="table" rid="T2">Table 2</xref> (query dataset characteristics) summarises the evaluation query set used to test the system. This table typically includes:</p>
<list list-type="bullet">
<list-item><p>total number of queries,</p></list-item>
<list-item><p>thematic categories (progression, assessment, appeals, graduation, enrolment),</p></list-item>
<list-item><p>proportion of high-risk versus low-risk queries, and</p></list-item>
<list-item><p>language distribution.</p></list-item>
</list>
<table-wrap id="T2" specific-use="rules">
<label>Table 2</label>
<caption>
<p>Query Dataset Characteristics</p>
</caption>
<table frame="hsides" rules="all">
<thead>
<tr>
<th align="left" valign="top">Query Category</th>
<th align="left" valign="top">Risk Level</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left" valign="top">Programme Progression</td>
<td align="left" valign="top">Low</td>
</tr>
<tr>
<td align="left" valign="top">Assessment &amp; Exams</td>
<td align="left" valign="top">Low</td>
</tr>
<tr>
<td align="left" valign="top">Registration &amp; Enrolment</td>
<td align="left" valign="top">Low</td>
</tr>
<tr>
<td align="left" valign="top">Graduation Requirements</td>
<td align="left" valign="top">Medium</td>
</tr>
<tr>
<td align="left" valign="top">Appeals &amp; Mitigation</td>
<td align="left" valign="top">High</td>
</tr>
<tr>
<td align="left" valign="top">Disciplinary / Special Cases</td>
<td align="left" valign="top">High</td>
</tr>
</tbody>
</table>
</table-wrap>
</sec>
<sec>
<title>4.7 Interpretation of retrieval performance metrics</title>
<p>Retrieval performance metrics presented in <xref ref-type="table" rid="T3">Table 3</xref> (information retrieval performance) would be useful in evaluating how effectively the system identifies relevant regulatory clauses. The table is typically expected to report:</p>
<list list-type="bullet">
<list-item><p>Top-1, Top-3, and Top-5 accuracy,</p></list-item>
<list-item><p>Recall values across query categories.</p></list-item>
</list>
<table-wrap id="T3" specific-use="rules">
<label>Table 3</label>
<caption>
<p>Information Retrieval Performance</p>
</caption>
<table frame="hsides" rules="all">
<thead>
<tr>
<th align="left" valign="top">Metric</th>
<th align="left" valign="top">Top-1</th>
<th align="left" valign="top">Top-3</th>
<th align="left" valign="top">Top-5</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left" valign="top">Retrieval Accuracy (%)</td>
<td align="left" valign="top">&#8211;</td>
<td align="left" valign="top">&#8211;</td>
<td align="left" valign="top">&#8211;</td>
</tr>
<tr>
<td align="left" valign="top">Recall (%)</td>
<td align="left" valign="top">&#8211;</td>
<td align="left" valign="top">&#8211;</td>
<td align="left" valign="top">&#8211;</td>
</tr>
</tbody>
</table>
</table-wrap>
<p><xref ref-type="table" rid="T3">Table 3</xref> is designed to help assess the semantic retrieval module performance. The findings can thus help inform future regulatory drafting and consolidation efforts at the institutional level.</p>
</sec>
<sec>
<title>4.8 Discussion of response accuracy and grounding metrics</title>
<p><xref ref-type="table" rid="T4">Table 4</xref> (response quality and grounding metrics) presents expert-evaluated measures such as:</p>
<list list-type="bullet">
<list-item><p>regulatory accuracy rate,</p></list-item>
<list-item><p>citation correctness, and</p></list-item>
<list-item><p>hallucination rate.</p></list-item>
</list>
<table-wrap id="T4" specific-use="rules">
<label>Table 4</label>
<caption>
<p>Response Quality and Grounding Metrics (Expert Evaluation)</p>
</caption>
<table frame="hsides" rules="all">
<thead>
<tr>
<th align="left" valign="top">Metric</th>
<th align="left" valign="top">Value (%)</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left" valign="top">Regulatory Accuracy Rate</td>
<td align="left" valign="top">&#8211;</td>
</tr>
<tr>
<td align="left" valign="top">Citation Correctness</td>
<td align="left" valign="top">&#8211;</td>
</tr>
<tr>
<td align="left" valign="top">Hallucination Rate</td>
<td align="left" valign="top">&#8211;</td>
</tr>
<tr>
<td align="left" valign="top">Partial / Ambiguous Responses</td>
<td align="left" valign="top">&#8211;</td>
</tr>
</tbody>
</table>
</table-wrap>
<p>Hallucination rate measures the extent to which the system generates information that is not supported by any source document. A low hallucination rate would indicate that the RAG approach is effectively grounding responses in verified content, whereas a high rate would suggest that the model is still relying too heavily on its generative component, increasing the risk of misinformation.</p>
<p>Citation correctness evaluates whether the references provided by the system accurately point to the relevant sections of the source documents. High citation correctness would imply that the system not only retrieves appropriate information but also links it transparently to its origin, thereby enhancing user trust. Conversely, low citation correctness would indicate mismatches between answers and their cited sources, which could undermine confidence even if the answer itself appears plausible.</p>
<p>Answer accuracy assesses the factual correctness and completeness of the generated response relative to the query. Strong performance on this metric would suggest that the system can correctly interpret and synthesise information from retrieved documents, while weaker performance would highlight limitations in reasoning or comprehension, particularly for complex or multi-part queries.</p>
<p>Grounding completeness measures how fully the response is supported by the retrieved evidence, especially in cases where multiple clauses or documents must be combined. High grounding completeness would indicate that the system successfully integrates all relevant pieces of information, whereas partial scores would suggest that some necessary context is missing, potentially leading to incomplete or oversimplified answers.</p>
<p>Finally, escalation or confidence calibration metrics capture the system&#8217;s ability to recognise its own uncertainty and defer to human intervention when necessary. Effective calibration would be reflected in the system flagging ambiguous or low-confidence cases for review, thereby reducing the risk of misleading outputs. Poor calibration, on the other hand, would result in overconfident responses in situations that require nuanced interpretation, particularly when regulations span multiple clauses or contain inherent ambiguities.</p>
</sec>
<sec>
<title>4.9 Risk handling and escalation performance</title>
<p><xref ref-type="table" rid="T5">Table 5</xref> (risk handling and escalation metrics) evaluates the system&#8217;s governance behaviour through:</p>
<list list-type="bullet">
<list-item><p>correct escalation rate,</p></list-item>
<list-item><p>false automation rate, and</p></list-item>
<list-item><p>unnecessary escalation rate.</p></list-item>
</list>
<table-wrap id="T5" specific-use="rules">
<label>Table 5</label>
<caption>
<p>Risk Handling and Escalation Metrics</p>
</caption>
<table frame="hsides" rules="all">
<thead>
<tr>
<th align="left" valign="top">Metric</th>
<th align="left" valign="top">Value (%)</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left" valign="top">Correct Escalation Rate</td>
<td align="left" valign="top">&#8211;</td>
</tr>
<tr>
<td align="left" valign="top">False Automation Rate</td>
<td align="left" valign="top">&#8211;</td>
</tr>
<tr>
<td align="left" valign="top">Unnecessary Escalation Rate</td>
<td align="left" valign="top">&#8211;</td>
</tr>
</tbody>
</table>
</table-wrap>
<p><bold>Correct escalation rate</bold> measures the proportion of cases where the system appropriately identifies that it cannot confidently or safely provide a fully reliable answer and escalates the query to a human. A high correct escalation rate would suggest that the system is effectively recognising its limitations, particularly in complex, ambiguous, or high-stakes scenarios. A low rate, on the other hand, would indicate that the system is failing to flag cases that genuinely require human judgment, increasing the risk of incorrect or misleading responses being delivered automatically.</p>
<p><bold>False automation rate</bold> captures the proportion of cases where the system chooses to provide an automated response when it should have escalated instead. This is a critical risk metric, as high false automation implies overconfidence: the system is answering queries autonomously despite insufficient evidence, ambiguity, or low certainty. A low false automation rate would indicate safer behaviour, where the system avoids making unsupported decisions and defers appropriately when needed.</p>
<p><bold>Unnecessary escalation rate</bold> measures how often the system escalates queries that it could have handled correctly on its own. A high unnecessary escalation rate would suggest that the system is overly conservative, potentially leading to inefficiencies, increased workload for staff, and reduced user satisfaction due to delays. Conversely, a low unnecessary escalation rate would indicate that the system is making efficient use of automation, handling straightforward queries independently while reserving escalation for genuinely difficult or uncertain cases.</p>
<p>Together, these three metrics provide a balanced view of system behaviour: correct escalation reflects appropriate caution, false automation highlights risky overconfidence, and unnecessary escalation captures inefficiency due to excessive caution. An effective system should aim for high correct escalation, low false automation, and low unnecessary escalation.</p>
</sec>
<sec>
<title>4.10 User-centric evaluation and perceived trust</title>
<p><xref ref-type="table" rid="T6">Table 6</xref> (user experience and trust metrics) gives visibility on survey-based measures including:</p>
<list list-type="bullet">
<list-item><p>User satisfaction score,</p></list-item>
<list-item><p>Perceived trustworthiness, and</p></list-item>
<list-item><p>Query resolution rate.</p></list-item>
</list>
<table-wrap id="T6" specific-use="rules">
<label>Table 6</label>
<caption>
<p>User Experience and Trust Metrics (Student Survey)</p>
</caption>
<table frame="hsides" rules="all">
<thead>
<tr>
<th align="left" valign="top">Metric</th>
<th align="left" valign="top">Mean Score</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left" valign="top">User Satisfaction (1&#8211;5)</td>
<td align="left" valign="top">&#8211;</td>
</tr>
<tr>
<td align="left" valign="top">Perceived Trustworthiness (1&#8211;5)</td>
<td align="left" valign="top">&#8211;</td>
</tr>
<tr>
<td align="left" valign="top">Clarity of Responses (1&#8211;5)</td>
<td align="left" valign="top">&#8211;</td>
</tr>
<tr>
<td align="left" valign="top">Resolution Rate (%)</td>
<td align="left" valign="top">&#8211;</td>
</tr>
<tr>
<td align="left" valign="top">Willingness to Reuse (%)</td>
<td align="left" valign="top">&#8211;</td>
</tr>
</tbody>
</table>
<table-wrap-foot>
<fn><p><bold>Scale:</bold> 1 = Very Poor, 5 = Excellent</p></fn>
</table-wrap-foot>
</table-wrap>
<p>The discussion of <xref ref-type="table" rid="T6">Table 6</xref> will help reveal how trustworthiness is correlated with citation transparency and response verbosity or conversational fluency. This finding will validate the system model&#8217;s prioritisation of traceability over purely natural dialogue.</p>
</sec>
<sec>
<title>4.11 System model limitations revealed by evaluation</title>
<p>The discussion will also critically examine limitations exposed by the metrics and datasets:</p>
<list list-type="order">
<list-item><p><bold>Regulatory ambiguity:</bold> Some regulations are inherently open to interpretation, limiting full automation.</p></list-item>
<list-item><p><bold>Dataset bias:</bold> The query dataset reflects common enquiries and may under-represent rare but critical edge cases.</p></list-item>
<list-item><p><bold>Temporal dependency:</bold> Evaluation results depend on the currency of regulations; performance may degrade if updates are delayed.</p></list-item>
</list>
<p>These limitations are architectural rather than algorithmic and reinforce the need for continuous governance and institutional oversight.</p>
</sec>
<sec>
<title>4.12 Implications for the FoE and broader adoption</title>
<p>From an institutional perspective, the discussion aims to illustrate that the proposed system model is not merely a technical artefact but an operational support mechanism. The evaluation tables collectively will provide indications on how the chatbot will:</p>
<list list-type="bullet">
<list-item><p>possibly reduce routine administrative workload,</p></list-item>
<list-item><p>possibly improve consistency of regulatory advice, and</p></list-item>
<list-item><p>possibly enhance student confidence in institutional processes.</p></list-item>
</list>
<p>The modular design will also enable future extensions, such as integration with LMS or analytics-driven policy refinement. The effectiveness is a theoretical expectation until the pilot phase is complete.</p>
</sec>
<sec>
<title>4.13 Ethical considerations, consent procedures, and data management plan</title>
<sec>
<title>4.13.1 Ethical approval governance</title>
<p>The development and evaluation of the regulatory-support chatbot will be designed to comply with institutional research ethics guidelines and applicable data protection regulations. Because the system processes student queries and institutional regulatory documents, the study incorporates safeguards to ensure that personal data, institutional information, and user interactions are handled responsibly.</p>
<p>Prior to dataset construction and system evaluation, ethical approval would be sought from the relevant institutional research ethics committee. The ethical review would assess the handling of student interaction data, the anonymisation procedures used during dataset preparation, and the mechanisms implemented to prevent the disclosure of personally identifiable information.</p>
<p>The study is designed to minimise ethical risks by ensuring that:</p>
<list list-type="bullet">
<list-item><p>regulatory documents originate from publicly available or institutionally authorised sources,</p></list-item>
<list-item><p>student queries used in the evaluation dataset are anonymised and stripped of personal identifiers, and</p></list-item>
<list-item><p>the chatbot system does not provide binding administrative decisions and instead functions as an informational support tool.</p></list-item>
</list>
</sec>
<sec>
<title>4.13.2 Consent procedures</title>
<sec>
<title>4.13.2.1 Student interaction data</title>
<p>Given that real student queries will be used to construct the evaluation dataset, informed consent procedures will be implemented.</p>
<p>Students participating in the study would be informed that:</p>
<list list-type="bullet">
<list-item><p>their interactions may be recorded for research and system improvement purposes,</p></list-item>
<list-item><p>all collected data will be anonymised before analysis, and</p></list-item>
<list-item><p>participation is voluntary and may be withdrawn at any time.</p></list-item>
</list>
<p>Consent would be obtained through a digital consent form prior to participation. The consent form would clearly describe:</p>
<list list-type="bullet">
<list-item><p>the purpose of the research,</p></list-item>
<list-item><p>the types of data collected,</p></list-item>
<list-item><p>how the data will be stored and processed,</p></list-item>
<list-item><p>potential risks and benefits of participation, and</p></list-item>
<list-item><p>contact details of the research team and ethics committee.</p></list-item>
</list>
<p>Students who do not provide consent would not have their queries included in the research dataset.</p>
</sec>
<sec>
<title>4.13.2.2 Administrative staff participation</title>
<p>Where administrative staff contribute example queries or assist in validating regulatory interpretations, their participation is treated as expert input rather than personal data collection. Staff contributors would be informed that their input may be used for system design and evaluation purposes.</p>
</sec>
</sec>
<sec>
<title>4.13.3 Data anonymisation</title>
<p>All user-generated queries included in the dataset undergo anonymisation before storage or analysis.</p>
<p>The anonymisation process removes or masks the following elements:</p>
<list list-type="bullet">
<list-item><p>student names,</p></list-item>
<list-item><p>identification numbers,</p></list-item>
<list-item><p>email addresses,</p></list-item>
<list-item><p>programme registration numbers, and</p></list-item>
<list-item><p>any other personally identifiable information.</p></list-item>
</list>
<p>Queries are stored as de-identified textual entries, and each query is assigned a random identifier to prevent linkage to individual students.</p>
</sec>
<sec>
<title>4.13.4 Data Management Plan (DMP)</title>
<p>A structured DMP was developed to ensure that the research data are securely stored, responsibly used, and reproducible where appropriate.</p>
<sec>
<title>4.13.4.1 Data types</title>
<p>The project will produce and use several categories of data:</p>
<list list-type="order">
<list-item><p><bold>Regulatory document dataset</bold></p>
<list list-type="bullet">
<list-item><p>university regulations</p></list-item>
<list-item><p>faculty regulations</p></list-item>
<list-item><p>programme handbooks</p></list-item>
<list-item><p>examination rules</p></list-item>
<list-item><p>circulars and notices</p></list-item>
</list></list-item>
<list-item><p><bold>Clause-level regulatory dataset</bold></p>
<list list-type="bullet">
<list-item><p>segmented policy clauses</p></list-item>
<list-item><p>associated metadata</p></list-item>
</list></list-item>
<list-item><p><bold>Query dataset</bold></p>
<list list-type="bullet">
<list-item><p>anonymised student queries</p></list-item>
<list-item><p>synthetic queries generated by experts</p></list-item>
</list></list-item>
<list-item><p><bold>System evaluation logs</bold></p>
<list list-type="bullet">
<list-item><p>retrieved clauses</p></list-item>
<list-item><p>system responses</p></list-item>
<list-item><p>escalation decisions</p></list-item>
</list></list-item>
</list>
</sec>
<sec>
<title>4.13.4.2 Data storage</title>
<p>All research data are stored in secure institutional storage systems with controlled access.</p>
<p>Security measures include:</p>
<list list-type="bullet">
<list-item><p>encrypted storage servers,</p></list-item>
<list-item><p>password-protected access, and</p></list-item>
<list-item><p>restricted access to authorised researchers only.</p></list-item>
</list>
<p>Raw datasets containing potentially sensitive information are stored separately from processed research datasets.</p>
</sec>
<sec>
<title>4.13.4.3 Data retention</title>
<p>Data will be retained for a limited period to support research validation and replication.</p>
<p>Typical retention policy:</p>
<list list-type="bullet">
<list-item><p>anonymised datasets: retained for 5 years,</p></list-item>
<list-item><p>raw interaction logs: retained for 1&#8211;2 years, and</p></list-item>
<list-item><p>temporary processing files: deleted after preprocessing.</p></list-item>
</list>
<p>Retention policies follow institutional data governance guidelines.</p>
</sec>
<sec>
<title>4.13.4.4 Data sharing and reproducibility</title>
<p>To support research transparency and reproducibility, selected components of the dataset may be shared publicly, subject to institutional approval.</p>
<p>The following resources may be released:</p>
<list list-type="bullet">
<list-item><p>anonymised query dataset,</p></list-item>
<list-item><p>clause-level regulatory dataset structure,</p></list-item>
<list-item><p>metadata schema, and</p></list-item>
<list-item><p>system architecture description.</p></list-item>
</list>
<p>However, full regulatory documents may not be redistributed if they are subject to institutional copyright or restricted access policies.</p>
<p>Researchers wishing to replicate the system can reconstruct the knowledge base using publicly available institutional regulations.</p>
</sec>
<sec>
<title>4.13.4.5 Data security and privacy protection</title>
<p>The system is designed to minimise the risk of exposing sensitive information.</p>
<p>Key safeguards include:</p>
<list list-type="bullet">
<list-item><p>removal of personal identifiers from query data,</p></list-item>
<list-item><p>role-based access control for dataset access, and</p></list-item>
<list-item><p>separation of research datasets from operational system logs.</p></list-item>
</list>
<p>Additionally, the chatbot system itself is configured not to store long-term conversation histories unless explicitly required for evaluation purposes.</p>
</sec>
<sec>
<title>4.13.4.6 Data lifecycle</title>
<p>The research data lifecycle consists of the following stages:</p>
<list list-type="order">
<list-item><p>data acquisition (regulatory documents and anonymised queries),</p></list-item>
<list-item><p>data preprocessing and clause segmentation,</p></list-item>
<list-item><p>metadata annotation and vector indexing,</p></list-item>
<list-item><p>system evaluation using the query dataset,</p></list-item>
<list-item><p>secure storage and documentation of datasets, and</p></list-item>
<list-item><p>controlled sharing of anonymised datasets for replication.</p></list-item>
</list>
</sec>
</sec>
<sec>
<title>4.13.5 Limitations and ethical safeguards</title>
<p>Although the system will be designed to support regulatory information access, it is not intended to replace official administrative advice. All responses generated by the chatbot include a disclaimer indicating that:</p>
<list list-type="bullet">
<list-item><p>the response is informational,</p></list-item>
<list-item><p>official confirmation should be obtained from faculty administration for binding decisions.</p></list-item>
</list>
<p>High-risk queries such as appeals, disciplinary matters, or exceptional cases are automatically escalated to human administrators to ensure appropriate governance oversight.</p>
</sec>
<sec>
<title>4.13.6 Compliance with data protection regulations</title>
<p>The study design aligns with principles commonly found in international data protection frameworks, including:</p>
<list list-type="bullet">
<list-item><p>data minimisation,</p></list-item>
<list-item><p>purpose limitation,</p></list-item>
<list-item><p>informed consent, and</p></list-item>
<list-item><p>secure storage of personal data.</p></list-item>
</list>
<p>Only the minimum necessary data required for research evaluation will be collected and processed.</p>
</sec>
</sec>
<sec>
<title>4.14 Summary of discussion</title>
<p>The discussion confirms that the proposed system model, when evaluated using carefully designed datasets and metrics, will potentially achieve a balanced integration of automation and governance. The tables on datasets and metrics are not only evaluative tools but also diagnostic instruments that reveal strengths, limitations, and opportunities for institutional improvement.</p>
<p>Overall, the system model is shown to be technically sound, institutionally aligned, and ethically grounded, making it suitable for deployment within the FoE and adaptable to similar higher education contexts.</p>
</sec>
</sec>
<sec>
<title>5. Conclusion and Future Work</title>
<sec>
<title>5.1 Conclusion</title>
<p>This paper presented the conceptual design, system model, and evaluation framework for an AI-assisted Regulations and Student Support Chatbot tailored to the FoE at the UoM. Unlike generic conversational systems, the proposed chatbot will explicitly be designed for high-stakes regulatory guidance, where accuracy, traceability, and institutional accountability are paramount.</p>
<p>The system model integrates semantic information retrieval, retrieval-augmented response generation, confidence-based validation, and human escalation mechanisms into a cohesive, governance-aware architecture. By grounding all responses in official University and Faculty regulations, the chatbot mitigates the risk of hallucinated or misleading information&#8212;an issue frequently cited in the literature on LLMs in education.</p>
<p>The implementation strategy emphasises modularity and sustainability, enabling the system to be maintained and updated in line with evolving academic regulations. The dataset construction process, based on authoritative regulatory documents and representative student queries, ensures contextual relevance and institutional alignment.</p>
<p><xref ref-type="table" rid="T1">Tables 1</xref>, <xref ref-type="table" rid="T2">2</xref>, <xref ref-type="table" rid="T3">3</xref>, <xref ref-type="table" rid="T4">4</xref>, <xref ref-type="table" rid="T5">5</xref>, <xref ref-type="table" rid="T6">6</xref> present the proposed evaluation framework designed to assess the performance and governance compliance of the system as a first-line student support tool. The framework includes metrics related to retrieval accuracy, regulatory correctness, hallucination rate, and citation correctness, which will be intended to evaluate how effectively the system identifies, interprets, and references relevant institutional regulations. These indicators are included to ensure that responses remain grounded in authoritative sources and aligned with institutional policies.</p>
<p>In addition, the framework incorporates measures for evaluating the behaviour of the risk-aware escalation strategy. Metrics such as correct escalation rate and false automation rate are defined to assess whether high-risk or policy-sensitive queries will be appropriately redirected to human administrators. These measures aim to support the monitoring of institutional boundaries and ensure that automated responses will be limited to suitable contexts.</p>
<p>User-centred evaluation metrics are also included to capture student perceptions of the system. Indicators such as satisfaction, perceived trustworthiness, and intention to reuse are proposed to assess how students experience and interact with the chatbot interface. The inclusion of these measures reflects the design emphasis on transparency, traceability, and the provision of clearly cited regulatory information rather than purely conversational fluency.</p>
<p>Overall, the evaluation framework is intended to provide a structured approach for assessing how a regulatory-support chatbot could operate within the FoE. The framework aims to support future empirical studies that examine regulatory clarity, administrative workload, and the student information experience while maintaining alignment with institutional governance and academic integrity requirements.</p>
</sec>
<sec>
<title>5.2 Limitations</title>
<p>Despite its strengths, the proposed system has several limitations. First, regulatory language is inherently complex and, in some cases, open to interpretation, which constrains full automation. Second, the evaluation dataset, while representative, may not capture rare or exceptional edge cases. Third, system performance is dependent on the timeliness and completeness of regulatory updates; delays in document integration could affect response accuracy.</p>
<p>These limitations are primarily institutional and procedural rather than algorithmic, underscoring the importance of sustained governance and human oversight.</p>
</sec>
<sec>
<title>5.3 Future work</title>
<p>Several avenues for future work emerge from this conceptual framework:</p>
<list list-type="order">
<list-item><p><bold>Functional pilot study</bold></p>
<p>A controlled pilot will be conducted within selected engineering modules to deploy the chatbot and analytics platform in a live academic setting. This phase will focus on:</p>
<list list-type="bullet">
<list-item><p>testing system integration with LMS and institutional workflows,</p></list-item>
<list-item><p>monitoring real-time student interactions with the chatbot,</p></list-item>
<list-item><p>evaluating usability, response quality, and system reliability, and</p></list-item>
<list-item><p>collecting feedback from both students and academic staff.</p></list-item>
</list>
<p>Hypothetically, successful outcomes would include high user engagement, reduction in routine queries handled by staff, and positive user satisfaction scores.</p></list-item>
<list-item><p><bold>Empirical validation</bold></p>
<p>Following the pilot, a rigorous empirical evaluation will be conducted to measure the system&#8217;s impact on student success and decision support effectiveness. This will include:</p>
<list list-type="bullet">
<list-item><p>quantitative analysis of pass rates, grade improvements, and retention metrics,</p></list-item>
<list-item><p>evaluation of predictive model performance (precision, recall, AUC),</p></list-item>
<list-item><p>assessment of escalation metrics (correct escalation, false automation, unnecessary escalation), and</p></list-item>
<list-item><p>comparative analysis using control vs intervention groups (A/B testing).</p></list-item>
</list>
<p>Strong empirical results would demonstrate statistically significant improvements in student outcomes and efficient human&#8211;AI collaboration, thereby justifying broader institutional deployment.</p></list-item>
<list-item><p><bold>Extended multilingual support</bold></p>
<p>Future versions of the system will incorporate structured support for Mauritian Creole, particularly for interface-level explanations, while preserving legal accuracy in English and French regulatory sources.</p></list-item>
<list-item><p><bold>Longitudinal impact studies</bold></p>
<p>Further evaluation over multiple academic cycles will enable assessment of long-term impacts on student retention, administrative workload reduction, and policy compliance.</p></list-item>
<list-item><p><bold>Advanced confidence estimation</bold></p>
<p>Integrating more sophisticated uncertainty modelling techniques will further improve escalation decisions, particularly for interpretative or multi-clause regulatory queries.</p></list-item>
<list-item><p><bold>Integration with institutional systems</bold></p>
<p>Linking the chatbot with existing university systems such as LMS or student information systems will enable personalised, context-aware responses while maintaining strict privacy controls.</p></list-item>
<list-item><p><bold>Regulatory analytics and policy feedback</bold></p>
<p>Aggregated query logs will be analysed to identify recurring areas of confusion, informing improvements in regulatory drafting, student communication, and policy simplification.</p></list-item>
<list-item><p><bold>Cross-faculty and cross-institution deployment</bold></p>
<p>The modular architecture will make the system readily adaptable to the other faculties within the UoM and to similar higher education institutions, enabling comparative studies across disciplines and contexts.</p></list-item>
</list>
</sec>
<sec>
<title>5.4 Final remarks</title>
<p>This work proposes that AI-assisted chatbots, when carefully designed with retrieval grounding, risk awareness, and governance mechanisms, can serve as trusted institutional support tools rather than mere conversational agents. The proposed system offers a conceptual approach to improving regulatory accessibility in higher education, providing a foundation for responsible AI deployment within the UoM and beyond.</p>
</sec>
</sec>
</body>
<back>
<ref-list>
<ref id="B1"><label>1</label><mixed-citation publication-type="book"><string-name><surname>Andrenucci</surname>, <given-names>A.</given-names></string-name>, &amp; <string-name><surname>Sneiders</surname>, <given-names>E.</given-names></string-name> (<year>2005</year>). <source>Automated question answering: review of the main approaches</source>. <publisher-loc>Sydney, NSW, Australia</publisher-loc>, <publisher-name>IEEE</publisher-name>, pp. <fpage>514</fpage>&#8211;<lpage>519</lpage>.</mixed-citation></ref>
<ref id="B2"><label>2</label><mixed-citation publication-type="book"><string-name><surname>Ashok</surname>, <given-names>M.</given-names></string-name>, <string-name><surname>Ramasamy</surname>, <given-names>K.</given-names></string-name>, <string-name><surname>Snehitha</surname>, <given-names>G.</given-names></string-name>, &amp; <string-name><surname>Keerthi</surname>, <given-names>S. R.</given-names></string-name>, (<year>2021</year>). <source>A Systematic Survey of Cognitive Chatbots in Personalized Learning Framework</source>. <publisher-loc>Chennai, India</publisher-loc>, <publisher-name>IEEE</publisher-name>.</mixed-citation></ref>
<ref id="B3"><label>3</label><mixed-citation publication-type="journal"><string-name><surname>Carayannopoulos</surname>, <given-names>S.</given-names></string-name> (<year>2018</year>). <article-title>Using chatbots to aid transition</article-title>. <source>International Journal of Information and Learning Technology</source>, <volume>35</volume>(<issue>2</issue>), <fpage>118</fpage>&#8211;<lpage>129</lpage>. <pub-id pub-id-type="doi">10.1108/IJILT-10-2017-0097</pub-id></mixed-citation></ref>
<ref id="B4"><label>4</label><mixed-citation publication-type="journal"><string-name><surname>De La Roca</surname>, <given-names>M.</given-names></string-name>, <string-name><surname>Chan</surname>, <given-names>M. M.</given-names></string-name>, <string-name><surname>Garcia-Cabot</surname>, <given-names>A.</given-names></string-name>, <string-name><surname>Garcia-Lopez</surname>, <given-names>E.</given-names></string-name>, &amp; <string-name><surname>Amado-Salvatierra</surname>, <given-names>H.</given-names></string-name> (<year>2024</year>). <article-title>The impact of a chatbot working as an assistant in a course for supporting student learning and engagement</article-title>. <source>Computer Applications in Engineering Education</source>, <volume>32</volume>(<issue>5</issue>), <elocation-id>e22750</elocation-id>. <pub-id pub-id-type="doi">10.1002/cae.22750</pub-id></mixed-citation></ref>
<ref id="B5"><label>5</label><mixed-citation publication-type="book"><string-name><surname>Dignum</surname>, <given-names>V.</given-names></string-name> (<year>2019</year>). <source>Responsible artificial intelligence: How to develop and use AI in a responsible way</source>. <publisher-name>Springer</publisher-name>. <pub-id pub-id-type="doi">10.1007/978-3-030-30371-6</pub-id></mixed-citation></ref>
<ref id="B6"><label>6</label><mixed-citation publication-type="webpage"><string-name><surname>Doshi-Velez</surname>, <given-names>F.</given-names></string-name>, &amp; <string-name><surname>Kim</surname>, <given-names>B.</given-names></string-name> (<year>2017</year>). <source>Towards a rigorous science of interpre table machine learning</source>. Arxiv. <uri>https://arxiv.org/abs/1702.08608v2</uri></mixed-citation></ref>
<ref id="B7"><label>7</label><mixed-citation publication-type="journal"><string-name><surname>Duarte</surname>, <given-names>N.</given-names></string-name>, &amp; <string-name><surname>Vardasca</surname>, <given-names>R.</given-names></string-name> (<year>2023</year>). <article-title>Literature review of accreditation systems in higher education</article-title>. <source>Educational Sciences</source>, <volume>13</volume>(<issue>6</issue>), <elocation-id>582</elocation-id>. <pub-id pub-id-type="doi">10.3390/educsci13060582</pub-id></mixed-citation></ref>
<ref id="B8"><label>8</label><mixed-citation publication-type="webpage"><collab>European Commission</collab>. (<year>2019</year>). <source>Ethics guidelines for trustworthy AI</source>. <publisher-name>European Commission</publisher-name>. <uri>https://data.europa.eu/doi/10.2759/346720</uri></mixed-citation></ref>
<ref id="B9"><label>9</label><mixed-citation publication-type="journal"><string-name><surname>F&#248;lstad</surname>, <given-names>A.</given-names></string-name>, &amp; <string-name><surname>Brandtz&#230;g</surname>, <given-names>P. B.</given-names></string-name> (<year>2017</year>). <article-title>Chatbots and the new world of HCI</article-title>. <source>Interactions</source>, <volume>24</volume>(<issue>4</issue>), <fpage>38</fpage>&#8211;<lpage>42</lpage>. <pub-id pub-id-type="doi">10.1145/3085558</pub-id></mixed-citation></ref>
<ref id="B10"><label>10</label><mixed-citation publication-type="book"><string-name><surname>Holmes</surname>, <given-names>W.</given-names></string-name>, <string-name><surname>Bialik</surname>, <given-names>M.</given-names></string-name>, &amp; <string-name><surname>Fadel</surname>, <given-names>C.</given-names></string-name> (<year>2019</year>). <source>Artificial intelligence in education: Promises and implications for teaching and learning</source>. <publisher-name>Center for Curriculum Redesign</publisher-name>.</mixed-citation></ref>
<ref id="B11"><label>11</label><mixed-citation publication-type="book"><string-name><surname>Horvitz</surname>, <given-names>E.</given-names></string-name> (<year>1999</year>). <source>Principles of mixed-initiative user interfaces</source> (pp. <fpage>159</fpage>&#8211;<lpage>166</lpage>). <publisher-name>ACM Press</publisher-name>. <pub-id pub-id-type="doi">10.1145/302979.303030</pub-id></mixed-citation></ref>
<ref id="B12"><label>12</label><mixed-citation publication-type="journal"><string-name><surname>Jiang</surname>, <given-names>M.</given-names></string-name>, <string-name><surname>Gao</surname>, <given-names>K.</given-names></string-name>, <string-name><surname>Wu</surname>, <given-names>Z.</given-names></string-name>, &amp; <string-name><surname>Guo</surname>, <given-names>P.</given-names></string-name> (<year>2022</year>). <article-title>The influence of academic pressure on adolescents&#8217; problem behavior: Chain mediating effects of self-control, parent&#8211;child conflict, and subjective well-being</article-title>. <source>Frontiers in Psychology</source>, <volume>13</volume>, <elocation-id>954330</elocation-id>. <pub-id pub-id-type="doi">10.3389/fpsyg.2022.954330</pub-id></mixed-citation></ref>
<ref id="B13"><label>13</label><mixed-citation publication-type="journal"><string-name><surname>Ji</surname>, <given-names>Z.</given-names></string-name>, <string-name><surname>Lee</surname>, <given-names>N.</given-names></string-name>, <string-name><surname>Frieske</surname>, <given-names>R.</given-names></string-name>, <string-name><surname>Yu</surname>, <given-names>T.</given-names></string-name>, <string-name><surname>Su</surname>, <given-names>D.</given-names></string-name>, <string-name><surname>Xu</surname>, <given-names>Y.</given-names></string-name>, <string-name><surname>Ishii</surname>, <given-names>E.</given-names></string-name>, <string-name><surname>Bang</surname>, <given-names>Y. J.</given-names></string-name>, <string-name><surname>Madotto</surname>, <given-names>A.</given-names></string-name>, &amp; <string-name><surname>Fung</surname>, <given-names>P.</given-names></string-name> (<year>2023</year>). <article-title>Survey of hallucination in natural language generation</article-title>. <source>ACM Computing Surveys</source>, <volume>55</volume>(<issue>12</issue>), <fpage>1</fpage>&#8211;<lpage>38</lpage>. <pub-id pub-id-type="doi">10.1145/3571730</pub-id></mixed-citation></ref>
<ref id="B14"><label>14</label><mixed-citation publication-type="journal"><string-name><surname>Kim</surname>, <given-names>Y.</given-names></string-name>, &amp; <string-name><surname>Baylor</surname>, <given-names>A. L.</given-names></string-name> (<year>2016</year>). <article-title>Research-based design of pedagogical agent roles: A review, progress, and recommendations</article-title>. <source>International Journal of Artificial Intelligence in Education</source>, <volume>26</volume>, <fpage>160</fpage>&#8211;<lpage>169</lpage>. <pub-id pub-id-type="doi">10.1007/s40593-015-0055-y</pub-id></mixed-citation></ref>
<ref id="B15"><label>15</label><mixed-citation publication-type="journal"><string-name><surname>Lewis</surname>, <given-names>P.</given-names></string-name>, <string-name><surname>Perez</surname>, <given-names>E.</given-names></string-name>, <string-name><surname>Piktus</surname>, <given-names>A.</given-names></string-name>, <string-name><surname>Petroni</surname>, <given-names>F.</given-names></string-name>, <string-name><surname>Karpukhin</surname>, <given-names>V.</given-names></string-name>, <string-name><surname>Goyal</surname>, <given-names>N.</given-names></string-name>, <string-name><surname>K&#252;ttler</surname>, <given-names>H.</given-names></string-name>, <string-name><surname>Lewis</surname>, <given-names>M.</given-names></string-name>, <string-name><surname>Yih</surname>, <given-names>W.</given-names></string-name>, <string-name><surname>Rockt&#228;schel</surname>, <given-names>T.</given-names></string-name>, <string-name><surname>Riedel</surname>, <given-names>S.</given-names></string-name>, &amp; <string-name><surname>Kiela</surname>, <given-names>D.</given-names></string-name> (<year>2020</year>). <article-title>Retrieval-augmented generation for knowledge-intensive NLP tasks</article-title>. <source>Advances in Neural Information Processing Systems</source>, <volume>33</volume>, <fpage>9459</fpage>&#8211;<lpage>9474</lpage>. <pub-id pub-id-type="doi">10.48550/arXiv.2005.11401</pub-id></mixed-citation></ref>
<ref id="B16"><label>16</label><mixed-citation publication-type="book"><string-name><surname>Luckin</surname>, <given-names>R.</given-names></string-name>, <string-name><surname>Holmes</surname>, <given-names>W.</given-names></string-name>, <string-name><surname>Griffiths</surname>, <given-names>M.</given-names></string-name>, &amp; <string-name><surname>Forcier</surname>, <given-names>L. B.</given-names></string-name> (<year>2016</year>). <source>Intelligence unleashed. An argument for AI in education</source>. <publisher-name>Pearson</publisher-name>.</mixed-citation></ref>
<ref id="B17"><label>17</label><mixed-citation publication-type="journal"><string-name><surname>Luo</surname>, <given-names>Q. Z.</given-names></string-name>, &amp; <string-name><surname>Hsiao-Chin</surname>, <given-names>L. Y.</given-names></string-name> (<year>2023</year>). <article-title>The influence of AI-powered adaptive learning platforms on student performance in chinese classrooms</article-title>. <source>Journal of Education</source>, <volume>6</volume>(<issue>3</issue>), <fpage>1</fpage>&#8211;<lpage>12</lpage>. <pub-id pub-id-type="doi">10.53819/81018102t4181</pub-id></mixed-citation></ref>
<ref id="B18"><label>18</label><mixed-citation publication-type="journal"><string-name><surname>Nurshatayeva</surname>, <given-names>A.</given-names></string-name>, <string-name><surname>Page</surname>, <given-names>L. C.</given-names></string-name>, <string-name><surname>White</surname>, <given-names>C. C.</given-names></string-name>, &amp; <string-name><surname>Gehlbach</surname>, <given-names>H.</given-names></string-name> (<year>2021</year>). <article-title>Are artificially intelligent conversational chatbots uniformly effective in reducing summer melt? Evidence from a randomized controlled trial</article-title>. <source>Research in Higher Education</source>, <volume>62</volume>(<issue>3</issue>), <fpage>392</fpage>&#8211;<lpage>402</lpage>. <pub-id pub-id-type="doi">10.1007/s11162-021-09633-z</pub-id></mixed-citation></ref>
<ref id="B19"><label>19</label><mixed-citation publication-type="journal"><string-name><surname>Okonkwo</surname>, <given-names>C. W.</given-names></string-name>, &amp; <string-name><surname>Ade-Ibijola</surname>, <given-names>A.</given-names></string-name> (<year>2021</year>). <article-title>Chatbots applications in education: A systematic review</article-title>. <source>Computers and Education: Artificial Intelligence</source>, <volume>2</volume>, <elocation-id>100033</elocation-id>. <pub-id pub-id-type="doi">10.1016/j.caeai.2021.100033</pub-id></mixed-citation></ref>
<ref id="B20"><label>20</label><mixed-citation publication-type="book"><string-name><surname>Power</surname>, <given-names>D. J.</given-names></string-name> (<year>2002</year>). <source>Decision support systems: Concepts and resources for managers</source>. <publisher-name>Quorum Books</publisher-name>.</mixed-citation></ref>
<ref id="B21"><label>21</label><mixed-citation publication-type="book"><string-name><surname>Sharda</surname>, <given-names>R.</given-names></string-name>, <string-name><surname>Delen</surname>, <given-names>D.</given-names></string-name>, &amp; <string-name><surname>Turban</surname>, <given-names>E.</given-names></string-name> (<year>2021</year>). <source>Analytics, data science and artificial intelligence systems for decision support</source>. <edition>11</edition> ed. <publisher-name>Pearson</publisher-name>.</mixed-citation></ref>
<ref id="B22"><label>22</label><mixed-citation publication-type="book"><collab>Unesco</collab>. (<year>2021</year>). <source>AI and education: Guidance for policy-makers</source>. <publisher-name>Unesco</publisher-name>. <pub-id pub-id-type="doi">10.54675/PCSP7350</pub-id></mixed-citation></ref>
<ref id="B23"><label>23</label><mixed-citation publication-type="journal"><string-name><surname>Winkler</surname>, <given-names>R.</given-names></string-name>, &amp; <string-name><surname>Soellner</surname>, <given-names>M.</given-names></string-name> (<year>2018</year>). <article-title>Unleashing the potential of chatbots in education: A state-of-the-art analysis</article-title>. <source>Academy of Management Proceedings</source>, <volume>2018</volume>, Article <elocation-id>15903</elocation-id>. <pub-id pub-id-type="doi">10.5465/ambpp.2018.15903abstract</pub-id></mixed-citation></ref>
<ref id="B24"><label>24</label><mixed-citation publication-type="journal"><string-name><surname>Yin</surname>, <given-names>J.</given-names></string-name> (<year>2021</year>). <article-title>Mindset and individual learning in the workplace: A systematic review and future agenda</article-title>. <source>Economic Studies</source>, <volume>71</volume>(<issue>1</issue>), <fpage>7</fpage>&#8211;<lpage>26</lpage>.</mixed-citation></ref>
</ref-list>
</back>
</article>