Name: Smarter Standards. Less Maintenance. Scale with Agiloft Astra
Uploaded: 2026-10-03T10:46:09.455Z
Duration: 22 min 1 s
Description: Smarter Standards. Less Maintenance. Scale with Agiloft Astra

Transcript for "Smarter Standards. Less Maintenance. Scale with Agiloft Astra": our webcast. Crystal, take it away. Thank you, Jennifer, and hello to everybody. Thank you for joining today. My name is Crystal Ventura. And as Jennifer mentioned, I am Agiloft innovation attorney. I have nearly fifteen years of in house experience, so I truly understand how corporate, legal, and contracting teams face real business pressures in contracting where you have to balance providing actionable guidance that properly addresses risk while maintaining consistency and meeting internal stakeholder expectations. And I've also been in the position that many of you might be in right now where you're looking to bring AI into your company and you needed to add real value. So my mission at Agiloft is to work with our product and engineering teams, to build one of the most accurate and effective AI contracting tools on the market, and I'm excited to demonstrate where we are. Today, I'll be pride... Providing an overview of Agiloft Astra and sharing some exciting updates with you all. So before we dive in, let's see here my screen. If you're new to Agiloft and not familiar with our platform, we have two products. So we have our contract life cycle management solution. We're a long time leader in the CLM space and Astra, which is our AI powered contracts review, negotiation, and analysis tool. So Astra is a web based application that provides presignature contracts review tools to support your negotiations, including an accompanying Microsoft word add in and in-depth post signature analytics. Today, we'll be in the realm of the presignature functionality in Astra, and I'm going to go over some of the great new features we recently released. And when I say recently, I mean, they were released this past Friday, so you all have a front row seat to the latest and greatest. What we've been focusing on is making our standards in the system smarter, which will lead to simpler reviews, more efficient reviews. So four of the main components of this latest release, there are others, but these are the four main ones, was that we added fallbacks. So this is something that our clients have been requesting for a long time, and I know how important it was in, you know, my contracting work. You wanna have your preferred position that the AI is looking at, but also acceptable fallback or backup negotiation positions. We also have the elements library where we have one central location to manage reusable contract standards in one place. We have the document viewer plus an AI confidence score. So that's in our web app where you can review the AI's findings right next to a view of the contract in the web app. You don't have to go out and look at the separate Microsoft Word document. And then multi instance redlining. So as you're running your screen, which we'll look at today, this will allow you to resolve, repetitive issues in one screen of the document. Today's focus is going to be the elements library. So we'll walk through how Astra helps teams manage elements centrally, which leads to review with flexibility and, completing your reviews with greater confidence. So we're gonna see the elements library in action, exploring how these reusable elements can be searched, updated, and applied across screens. Okay. So to start, we're starting in the web app, and this is where we land on the Astra homepage. It brings you to the Astra assistant. We're not gonna look at this today, but it is an interactive AI chat interface that's similar to general AI tools you may use in daily life. But this assistant allows you to request detailed analytics about your uploaded contract documents. So for today's purpose, we are going to navigate over to screens. And a major benefit with Agiloft versus just running your agreements and legal questions through general AI tools is that Asterisk foundation is in its screens, which are used to scan or screen your contract documents against the specific guardrails your team has established. So while you'll still have the benefit of AI analysis and suggestions, Astra's results incorporate your institutional contracting judgment. Screens essentially power the AI with the same institutional knowledge that informs the provisions of your company's legal playbook. And if you're thinking my company doesn't have a playbook, don't worry. The screens functionality in Astra is perfect for you because you'll develop screens that incorporate the decisions that your team has been making and the knowledge your team has gained for years. And you'll finally have that institutional knowledge documented without having to manually draft and maintain a playbook, which is a huge win. So how do screens work? Screens are comprised of elements, and there are two types of elements. There are standards and there are questions. So a standard is a structured contract review requirement. As you can see right there in this screen, we have 26 standards and five questions. We're in the SaaS services buy side playbook. So we're first gonna be looking at a standard. If I click on, let's see here. If I click on data liability cap, we're going to be giving the AI a rule. Right? So here, the rule is the contract should specify the claims related to data privacy or security are either uncapped or subject to a secondary higher liability cap. So the tool is gonna be scanning to see if the contract meets that rule. And you'll see there I'm pointing to the little gavel. The gavel indicates that that card is a standard. And then we also are able to add more context. And so here in the context, we give it a little more information about the secondary cap, and then we also give it really important information where we say, hey. Do not consider insurance obligations when evaluating this requirement. So that's what standard looks like. And then we have another standard here. We can look at governing law. So, again, we can tell the tool... Tell the AI, this is what we prefer. Right? The rule is that the governing law in this in this agreement or all our agreements will be Delaware governing law. But here you see that while we do have that rule, if you look at the card on the left, you'll see that we also have two fallbacks. So this is the new fallbacks functionality. As you're probably all familiar with, you may really want Delaware law, but you're not always going to get it. Right? So companies typically have, fallback jurisdictions. In this case, our first fallback is New York. New York government law is acceptable. And if we can't get the parties to agree to New York, we will agree to, begrudgingly agree to my home state of California. So we have those two fallbacks as well. Okay. And then now we're gonna go and take a look at questions. So questions, in contrast to the standards, questions are open ended. It's an open ended inquiry that you're asking the AI to go and fetch you an answer, right, and give you more context about that question in the contract that you're reviewing. So here, I clicked on the question for website terms reference, And it's just a very simple question. Are there any references in this agreement that I'm reviewing to terms or policies available on the vendor's website? It's very common in staff agreements to have, clickable links to additional terms and conditions or policies. And, again, we're able to give the AI more context, and so we tell it, look for .com references, look for URLs, here are the types of policies or t's and c's that might be common in a SAS agreement that it should be on the lookout for. And then that little icon there, the chat bubble indicates that it is a question versus the gavel to in... Indicate that it's a, a standard. So you've seen the elements in a screen. Now let's go back to the screens page and access our elements library. So you see that's a new tab. And this is a library housing all of the elements we have in this Astra Workspace that we're working in. So it means that those standard in... Standards and questions that we saw in the staff screen we were just looking at, they're all housed here, along with the standards for all other screens in our workspace. So if I type in website here, I will see that, website terms reference. Right? That's the question that we were looking at indicated by that chat bubble. Also, the type there, that category tells me it's a question, and it'll show me that it's in one screen currently. So I click on that. It's that staff services by side playbook that we were just reviewing. So, again, all, standards or questions, all elements that you've built, in a screen will copy over to the new elements library. But also any stand alone elements that you create, will appear here as well. You can see in the top right corner, there is a button, to add a new element. And so if we were to go there, you can add a new standard question and that will appear in the library as well. And then you can later pick that standalone standard, or question to put in one of your screens. Okay. So now let's look at building a screen. So we will go back, to the screens tab, And we have a variety of options to build a new screen. We won't dive into those today, but some things to keep in mind if you play around with Astra, you can copy from a community screen that we have. And then these are pre generated screens, and they're a really good starting place. Or you can generate from your own contract, which is an awesome place to start if you don't already have a playbook. You can use your template and the the tool will help you glean information from there to build your standards. But today, we're gonna build from scratch, and we just looked at a comprehensive SAS screen. But let's say I have the CIO calling about a particular vendor's, data protection and breach obligations. That's probably not a good sign and, she'll want a quick response. So I can create a targeted screen to scan just for those data related provisions using elements I already have from the comprehensive SAS screen, which will all be in the elements library. So I'll go ahead, create a new screen. I'll name it SAS data protection, and breach obligations. And I could add a description as well if I want to indicate to users how and when this should be used. And I'll just go ahead and save that. And now I could manually craft a new element, to add to this screen. But as we discussed, I know that the elements I need are already in that screen we've already created. So instead, I'm gonna browse the library, which will pull up my elements library. And I know that I'm looking for, elements related to data, so I'll search for data. And I'm just gonna pick anything that's applicable to this scenario. So we're gonna click, data breach notification and data privacy liability. Let's see. Data privacy compliance and the data liability cap. So we will go with those four for now, and I will add them to the screen. And voila. Now I have a tailored screen that I can run on a particular vendor SaaS agreement to efficiently and quickly respond to my, CIO's request. Now you can order the cards as I just showed there, for your own viewing of the screen, but it it doesn't make a difference to the AI. Okay. So now we'll take a look at adding elements to an existing screen. So for this, we'll go and find a new, a new screen, a new playbook, and we'll go to the buy side NDA playbook. And when I open it, I see that it has five standards and no questions. And I know that I wanna, add a question to determine the defined purpose of the NDA. I know that my NDA template has purpose as a defined term that the parties are to fill out. So I'm going to click new elements, and I'm going to, browse the library. And I already have a... An element here, a question for purpose definition. So I'll go ahead and select that. And while I'm at it, I'll add our favorite governing law as well. Okay. So the system has now added those two elements, and I'll move governing law up to the top. And now you'll see I have six standards and one question. There's my purpose definition. Again, very simple question. What scope is covered by this agreement? And asking the AI to re... Review the defined purpose. K. And finally, let's go and make a global update to one of our elements. And this is really where the elements library structure shines. So let's say we recently had an uptick in working with vendors based out of Idaho, and our legal team has determined that while not preferred, Idaho governing law is permissible as a third and final fallback option in any agreements we have with these Idaho based vendors. So, I'm in the buy side NDA playbook screen. I can find the governing law, standard, and I could go here and add a third fallback. So, again, very simply, governing law must be Idaho in this fallback. Now if I go, to save this, you'll notice that it will warn me that this particular element is used in multiple screens because if I were to save this, it will update the element everywhere it appears and every screen where it's present. Right? And it lists for me those screens. So I don't wanna do that here. You don't wanna make changes that could affect everything unless you intend to do that. Right? So more common scenario is if you're the Astra admin, you're probably gonna come here to the elements library. You're gonna search for that element that you're trying to update. Here, I just searched for Delaware. Right? And I found that standard, and I'll edit it here. So I can go into edit. Like, again, same process. Add the third fallback. K. I'm gonna put Idaho. Governing law must be Idaho. And, again, we get that same warning, but this time, I'm okay with that. I do want it to be updated in the elements library and everywhere that element is used. So we'll accept the change. Now we'll go back to screens, and we'll go pick up that screen once again. And you'll see now, that that third fallback is present. It's been added. And if we were to look at the other screens that were mentioned, it would be there as well. Okay. So the last stop of our demo will be running our screen on a contract document. So I've opened a NDA in Microsoft Word, and I'm going to go to my Agiloft add in, and then I'm going to select the buy side NDA screen that we were looking at. These are all the screens in my workspace, and then I will select run screen. Okay. So you'll see in this side pane that the results show me I have a failure of one standard, but I'm interested in governing law right now. And so I'll just open that up, and I see that it passed a fallback. So it highlights the language for me, and I see that the governing law is California. So it's telling me that it passed my fallback number two. Did not pass my preferred position of Delaware nor did it pass my first fallback of New York. However, it did pass my second fallback of California. Because of that, it will give me a red line. It's going to suggest New York because since it passed fallback two, it's going to suggest the next highest preferred position, which in this case would be fallback one. So if I wanted, I could, add that red line and change this. I can, click apply changes and select New York as the governing law. But since it's telling me that fallback two is approved, I can also just use that. So I'll stick with that. Also now going down to that question that we asked, so what is the purpose? You'll see the question there and it's just highlighted it for me. There's the defined, definition of purpose. And then it also provides an AI answer where it tells me that the purpose is for the parties to explore this potential business relationship. Okay. So, as a recap, today, we learned how Astra now helps you centrally manage your contract review, which is huge. So these workspace level standards and questions can be created, searched, updated, and applied across a number of screens as we saw. And that's a real win for efficiency and accuracy. We hope that you've been inspired to create and run screens of your own, which you can do for free with our free tier. Kind of unique, there's no limited time trial and no credit card required. You can just go to Agiloft.com and sign up, for Astra. And if you are a CLM customer, you can message us about enabling Astra access. And that's it. So I thank you all for joining today, and thank you to CCBJ for hosting. If you've asked a question and we haven't responded to you, we will. If you leave any feedback or you ask for us to contact you, we will reach out. So thank you very much, and have a great day.