Skip to content

ABOUT THIS SCREEN


Designed For:

Users of any type of services who have a need or desire to understand contractual service level obligations.

 

Purpose

This screen contains 17 obligations that may be contained in service level agreements. The obligations will be output in a structured format, allowing users to better understand their contractual service level obligations. Each obligation will be broken down into sub-parts, as follows:

  1. 1. Responsible Party
  2. 2. Obligation Summary (may also include a standardized version of the same where relevant)
  3. 3. Consequence Summary (may also include a normalized version of the same where relevant)
  4. 4. Obligation Trigger
  5. 5. Trigger Type
  6. 6. Obligation Type

 

 

Limitations, Assumptions, Details:

This screen has only been tested on service level and related agreements. Some questions are designed to output substantive responses while others will output Yes/No responses. This screen may be limited to provide a single obligation per each obligation type. Standardized outputs will only be provided where a single obligation or consequence exists. Standardized outputs will not consider references to "business days", or similar. See the user guidance associated with each particular obligation for additional details.


ABOUT THE AUTHOR


Maya Lash

Maya Lash

Maya is a Senior Legal Knowledge Engineer at Agiloft, where she leverages her legal expertise to enhance contract lifecycle management through AI-driven features. Prior to joining Agiloft, she worked at Zuva, where she began her career in Legal Knowledge Engineering, focusing on AI for contracts.

 

Before transitioning into LegalTech, Maya practiced as a corporate lawyer, advising startups and high-growth companies on financing, exits, and general corporate matters. During her legal career, she also began exploring ways to integrate AI into legal workflows and is licensed to practice in both Canada and Australia.