Name: Productions Part II: Advanced QC, Warnings, and Modifications
Uploaded: 2026-08-25T18:25:17.499Z
Duration: 1 h 24 min 32 s
Description: Productions Part II: Advanced QC, Warnings, and Modifications

Transcript for "Productions Part II: Advanced QC, Warnings, and Modifications": Hello and welcome everybody. It's good to see you all. My name is Zach Souza. I just wanted to introduce myself and get us kicked off for today's webinar. I'm a customer mark customer marketing manager here at Emerilaw, and today we're gonna be talking productions part two. So if you joined us about a month ago for the first part in this production series, Welcome back. If you're here for the first time, we're happy to have you. Today, we're gonna be talking about advanced QC warnings and modifications. But of course, before we get right into it, I have just a few housekeeping tips to keep you all going. The first piece I wanna call out is that today's session is gonna be recorded. So if you wanted to revisit and relisten to any of this presentation in the future, all you have to do is revisit the same link you used to join us live today. In the future, it will be replaced with an on demand recording of today's session. So keep that in mind. If you run into audio or video, don't forget to turn on light mode. You'll see a toggle button and the ability to turn on light mode below your presentation window. That should solve most AV issues if you do run into them. I'll also call out on the right hand side of your screen. You've got our chat. Feel free to drop in, say hi. Leave a comment. This is where the majority of the session chat is gonna happen today. If you do have a question specifically about today's content that you wanna ask our speakers, I'm gonna direct you to putting those directly into our q and a chat. That is where we can keep everything organized and know which questions already been answered or not answered. So if you want us to get to your question, please go right to the Q and A drop it drop it in drop it in at any point of today's session. We'll try to get to as many of these questions as possible and right back to you all to answer everything that gets submitted. I also want to highlight the docs tab. We've got a number of productions resources listed there for you to take a look, download as so definitely keep an eye on those. We also have a couple of other, resources and links that we're including. One of them I'm gonna shout out is at link to buy tickets for Everlost Summit twenty six. It's coming up really soon, October 27 through the twenty ninth. This is our three day in person conference specifically for our customers, and it is going to be offered at a 10% discount if you use the code webinar. So take that with you. Use the code if you're thinking about coming. If you're thinking about getting certified on the Everlaw platform, we offer an in person certification track at Everlaw. That fills up very quickly and might even be filled up and at least couple of the sessions right now. So take a look, sign up if you're interested in that. It is a good experience and a lot of people walk away, excited to be certified in the day. So before I tip-off to our speakers, I'm gonna kick us off with one poll question and this is to get a sense of our audience and where you all are in terms of, using production. So the first question is what is your current comfort level and familiarity using productions today? So I'm gonna pop that poll question up. It should be live and I will keep it up for a minute or so while I welcome on today's speakers. Great. Thanks, Zach, and hello, everyone. Thank you for joining us today. My name is Mario, and I'm joined by my colleague, Carrie, and we're both on Everlaw's user education team, and we're back for the second of two webinars in our production series. So during today's webinar, we're gonna build on the foundation we created in part one and dive deeper into some of Everlaw's pre and post production functionality. We'll begin by quickly reviewing what was covered in part one for anyone that needs a refresher or wasn't able to join. Then we'll learn about the importance of setting up quality checks or QCs to flag any potential production issues. Next, we'll go over how to interpret and address those production and protocol warnings. Then we'll run our production and talk about how to work with the different document versions. And finally, we'll cover how to modify a completed production, like changing the settings or creating a clawback. Now the goal is by the end of the day, you'll hopefully feel confident catching and fixing any issues before your own productions go out the door, as well as making any adjustments after if needed. Now we'll be demonstrating all of this using a synthetic dataset for the fictional exchange Blockball, which is based on the real world story of the crypto boom and bust in the early twenty twenties. Today's session will be interactive through the use of polls and knowledge check questions, and unlike our previous webinar, you don't need to worry about logging into this Everlaw project yourselves. We'll be sharing our screens throughout the training so you can observe and take notes if you like. At this point, we're gonna hide our videos so you can see as much of the screen as possible. Alright. So let's quickly review the basics of productions that we covered in part one. First, when you produce a document on Everlaw, Everlaw will create a separate new version of that document. This new version will be assigned a unique Bates number that cannot be reused on other documents. On this new version, the images will have a bait stamp along with any other endorsements you might want to add, and any redactions will be fully burdened. The new version will be linked to the original document so you can easily compare the two copies. It is important to note that producing documents does increase the billable size of your database, so you might wanna only give production permissions to a small group of users. Lastly, we highly recommend configuring your production settings ahead of time whenever possible. Those settings are configured in what we call a production protocol. Let's jump over to the Everlaw platform now and check out an existing protocol. Here we go. And here I am on the home page for our blockbulk case. As a reminder, you won't won't be logging into this project today, so you can just focus on watching. To look at our existing protocols, I'll click the data transfer icon in the top toolbar and then choose productions. Now if this is ever grayed out for you and it's not clickable, it means that you don't have the necessary productions permissions and you'll wanna contact your project administrator. So I'm gonna look for a protocol. So I'm gonna go to the protocols on the left. And I'll use these arrows to find the specific one I'm looking for, in this case, the January production protocol. To see the details, I'll click view protocol summary and then click edit over on the right. This takes me to the production protocol wizard and I'm gonna move through these steps pretty quickly since we went over this in the last webinar, but if you wanna see this in more detail, you can check out the production protocols video in the docs tab later. So this first step is where you'll define your production criteria, which is the specific set of documents you want to produce. In this case, we've put those documents into a binder. Next you'll have the option to customize your quality checks. And quality checks are tools that you can use to ensure that your production is following all required elements of your specific ESI protocol. If something is not in line with the protocol, the quality check will give you a warning prior to production with recommended actions to address that warning. Everlaw has some built in standard quality checks and you can also create your own custom checks. We'll be diving deeper into how to create a custom check and review your warnings in just a moment. On the next step, you'll give your protocol a name and identify your base prefixes. After that, you'll specify your image details like endorsements. Next, you'll select your redaction configurations and customizations if needed. And here you can choose which documents you'll be producing native files for. On this step, you'll need to tell Everlaw which documents in your production are privileged which is designated by a specific privilege code. We'll also revisit this later today. Next, you can create additional image placeholder rules if needed. Then you'll configure the metadata fields in your load file. And finally, you can select any additional options like creating a privilege log. I'll review this summary and then click save. Again, that was just a quick refresher, and you can always check out the productions protocol video that's linked in the docs tab today for more information. I'll hand things over to Carrie now to tell us some more about those quality checks I mentioned. Thanks, Margo. I'll go ahead and switch over to a new protocol that we made during part one of our webinar series. So that way, we can go over how to actually leverage the QCs. Everwall has a robust and customizable QC tool. We have a list of some of these prepopulated warnings that will give you, that that we will give you about your protocol in production before you produce your documents. You can also create custom QC checks in your production protocol. This means that you can create checks specific to your case and your organization standards. And then once created, you can even template them and reuse them across future projects. You can create these custom quality checks under the advanced settings tab. And you'll come over to where it says custom quality checks. And then when you're ready to make a new one, just click new custom check. Let's say my team is requiring that we only produce documents coded as responsive. This would be a great time to use that custom QC tool. My first step is to name my QC. I'm gonna go ahead and name it responsiveness check. When I create a custom check, I'm building a search for the criteria that I want my documents to meet. For example, I wanna make sure I'm only producing responsive documents. So I'm gonna click in. I'm going to search for my responsive code. I can then select the severity of my QC, and this is a major one, so I'm gonna go ahead and select that. And then finally, I'm gonna write in a suggested resolution. Because I only wanna produce responsive documents, I'm gonna go ahead and have my suggestion be to exclude from production. And then great. My team also agreed that of those responsive documents, I wanna ensure that they all have an issues code in order to stay organized. So I'm gonna make a second QC, And this one, I'm gonna name issues check. And this time, I want any code within that category, so I'm gonna choose the category instead. And this is just a minor severity. There might be situations where there's exceptions to the rule, so I'm gonna keep it selected as minor. And then my selected my suggested resolution is going to be a second past review. And then I can hit create. Now I can use this on future protocols or update an existing protocol to include in the custom check. In order to add these to my existing protocol, I'm gonna go back to my protocol list. I'm gonna select the protocol I want, and I'm gonna go into edit. So I can do view summary and then hit this edit icon here. I'm gonna click over to the custom quality check tab. And now underneath where we select our options, you can see both of those that I just created. As mentioned, I wanna make sure both of these are included, so I will click one and then the other. At this point, I'm not changing anything else about my protocol, so I'm just gonna click all the way through to save. Before running the production, I am required to review any production warnings selected during that QC process. This ensures my production will meet all of my ESI protocol needs. Here you can see that for this production for this protocol, several things have been flagged. And our warnings are divided into two categories. We have our protocol warnings, and those have to do with the settings or configuration of the protocol. And then we also have production warnings, and those have to do with the documents themselves that are being produced. Warnings can also be classified as major or minor. Protocol warnings can be resolved by changing the protocol configuration or you can ignore them. Under the suggested resolution column, you can select the hyperlink text to easily update your protocol. If you would like, you can ignore the warning just by checking the box on the right hand side. So under my protocol warnings, I have a few things I wanna address here first before running my production. These first two, base number not included in load file and family metadata not included in load file, both of those have to do with the values that weren't added to my load file. So to fix this, I just need to reconfigure that load file and make sure all essential information is included. When I click into the hyperlink text, it brings me directly to that step in the protocol in order to easily make those edits. For this, I'm just gonna go ahead and use the Everlaw defaults since I know that that includes both the Bates numbers and family metadata that's required. From there, I'm gonna go ahead and hit save. And now you'll see that both of those warnings have been removed because they're no longer in effect. You also see one here that's no privilege rule, and that means that no documents are currently set to be withheld for privilege because no privilege rule was set up. This was likely an oversight from whoever created the protocol originally. But for my team, I wanna ensure that all privilege documents are indeed withheld. So I'm gonna go ahead and add this rule. Again, I can click the blue text and jump to that step. I'm gonna switch to withhold documents. And then this is where I'm gonna select to add a new rule. I'm gonna name this rule the privilege rule. Then I want my placeholder text to say privilege. And then I need to designate which documents I want to be withheld. For these, it's those documents coded as privileged. And then I can hit save. And now you can see my rule is here, and I've selected to withhold those documents. I'm gonna go ahead and hit save. And, again, you'll see that those warnings have now been addressed, so they're removed. Under production warnings, I also have a few that I wanna address. Our first one, it looks like I have four documents that have already been produced in Everlaw. For this, I have these four documents that I produced in my January production. That's okay. I do wanna produce them again, so I'm gonna select to include in my production. You'll also see this responsiveness check. This was that custom QC I set up just a moment ago. Let's say that I sent this out, to be reviewed by a member of my team. If I wanna see this document, I can just click the blue text here and then assign it to them. After checking in with this person, I selected to have the resolution be to not produce these documents because they confirmed that it was not a responsive document, so I'll exclude from production. This next one is that issues check. That was that second QC we set up earlier as well. And my resolution for this was to check for an issues code. Again, let's say I sent this out for review and learned that it doesn't have an issues code because it doesn't match any of the issues code currently created in this project, but it is responsive. So I'm gonna go ahead and choose to include it in my production. With each warning, you can select to either resolve it through Everlost suggestion, include it in production, or exclude. Once all options are made, you can then continue to production. But before we do that, let's go ahead and pause for a moment so we can test our knowledge so far. I'm gonna go ahead and show a question and answer up on my screen that you all are gonna use the polls tab in Goldcast to give your best answer. Your question is, your ESI protocol requires you to only produce emails and no other types of documents. Which of these solutions will create the most solidified safeguards to ensure that happens? Is it a, during review work, only search for emails then add those documents to a binder once done and use it as your review criteria? Is it b, set up a custom QC to alert you if any documents that are not emails are trying to be produced prior to running your production? Or is it c, assign a member of your team to double check all document types are correct before running your production? I'll go ahead and give it thirty seconds for everybody to fill out their answer using that polls tab in Goldcast. Alright. Great work, everybody. The correct answer is B. To set up a custom QC to alert you if any documents that are not emails are trying to be produced prior to running your production. While both a and c are workflows that you could follow, creating that custom QC will allow you to see a specific flag on your work as the last step before running your production, which limits human error and ensures that you are alerted to any missteps before they happen. Let's go ahead and jump back in to running our production now. So again, once I've made my decisions regarding all of the warnings for both the protocol and the documents, I'm gonna go ahead and continue to production. I gotta name my production. And after that, I can just click produce, and I'm ready to run. See my production in progress. I can click into this production status, which will bring me to my production card. You can see all of the other productions that I've run, including this one right here. The production card is a summary of the documents in your production. We can see the name of the production as well as the date and the dates range. There are a few different numbers on your card and each one is a hyperlink to a results table in order to quickly view certain document configurations. For example, we can see specific subsets of documents based on certain qualities like a document's endorsement codes, the redactions, our documents that have been withheld, and our placeholders. The large blue number in the middle will take you to see all of your documents post production, which we will click into in just a moment. But let's spend another moment exploring what else we have available in this card. You can also share your production from here as well by clicking this button. And then this three dot menu in the right hand corner gives you some additional options, such as viewing your source documents or the original version of your documents preproduction, modifying your production, or deleting your production altogether. I also wanna point out one other tool related to administrate administration when it within productions, which is the production report export, which is available up here to those with admin permissions on productions. This lets you export a spreadsheet with key information about each of your productions within a project. Note that when you click the export button, the report will download right away, and it's not gonna create an export card on the home page. Let's go ahead now and actually click into the results table to see what our documents look like now that they've been produced. I'm gonna open up my first document here, and you can see that my redactions are burned in. And then I have my Bates number down in the bottom corner. Alright, I'm going to go ahead and pause here and pass it back over to Margo so we can talk a little bit about what it looks like to see the different versions of our documents. Thanks, Carrie. Let my let me get my screen share going again. Alright, so now that we've gone through how to run a production on Everlaw, let's talk a bit more about working with the different document versions. As we mentioned at the beginning, when you produce a document on Everlaw, Everlaw will create a separate new copy of that document, which we call a version. This allows you to keep the original document accessible and unaltered while still being while still being able to create an edited version with Batesam's endorsements and reductions. It also makes it easy to produce a document to multiple parties with different baits prefixes and different reductions if needed. There may be times where it makes more sense to work with just the original document, just the produced version, or both. Let's jump back into the Everlaw platform and talk through when and how to do that. So just a moment ago we saw that you can click on the BigBlue number and this will pull up your final producer versions of the documents. And this is a great option for when you want to do some quality control and see the documents as they will be seen by anyone who receives this production. Now there may be times where you wanna see all of the original documents instead. Maybe you wanna see the full unredacted text and images, or you want to see the documents with all of their original metadata. To pull those up, you can click the three dot menu, and then choose view source documents. This takes us to our results table where I can see all of the original documents and their error law control numbers with the hash symbol. When I click into one of these documents, I'll see the original version with all of the metadata, the transparent redactions, and no base stamps. Now most of the time you'll probably want to compare this original version with the final version that was produced. To do that, over in the context panel on the left, you'll click the versions icon and here we'll see a list of the original document and the produced version. If this document was produced multiple times, we would see all of those produced versions listed out here. I can click on the produced version to see the final form of the document with that Batesamp, the redactions burnt in, and I can easily switch back and forth between the two versions here. And this is a great way to compare versions for a single document, but what if I wanna see all versions for all of the documents in this production? To do that, I'll close this and go back to our results table, and then I'm gonna click into settings. Under grouping, I'm gonna choose to group by versions, and then I'll make sure we're not removing any documents from the group. This adds these little arrows over on the left, and when I click on one, I'll see the produced version of this document appear below the original document. If I want to see the produced versions for all of these docs, I'll click on the column header and then choose expand all. Now over on the right, the produce to column shows me the corresponding base number or numbers for the produced versions of each document. And the produce from column shows me the Everlaw control number for the original document. Now here's a tip. If you're just looking to quickly scan through both versions, you can enable quick review over at the top right, and then use the arrows on the bottom to navigate through the images while keeping track of your place in the list over on the left. I'll close this and the last thing I'll point out here is that you can also filter down these results to a specific version by clicking the funnel icon at the top of the Bates slash control number column. And then you can check the box next to the Bates prefix that you're interested in. And this may be especially relevant if you're producing the same documents multiple times to different parties with different prefixes. When we add this filter, the original documents will still be in this list for context, but they'll be italicized and grayed out and they'll be skipped over when we're moving through these documents in the review window because we filtered this down and we're focusing on the produced versions. Similarly, I could create a filter for the documents with just the, hash prefix if I wanted to see just the originals. Alright. Let's talk about one more really important thing to understand when it comes to working with document versions, and that's how to account for them when you're creating searches. I'll click the magnifying glass at the very top to go to Everlast's search page, and let's say we're doing rolling productions. So we've produced some documents already but our review is still ongoing. In this example, I want to find documents that mention the name Alex Carter, but I don't want to see any documents that have already been produced. To exclude those documents from my results, I'll need to add in the produced search term, which I can find over on the left under document. I'll keep this first part as any production, and then over on the right, I will select produced and original documents. Lastly, I'll use the not operator to negate this term. In doing so, I've ensured that both the original source documents and the produced versions will not be included in my results. And because my review is ongoing, I want to just focus on the documents that mention Alex Carter but have not been produced yet. I want to reiterate that if you forget this step, every law will still warn you if your production includes documents that already have been produced. This search just helps your review process be more efficient, so you and your team don't spend time looking at documents that you've already reviewed and produced. I'll also mention that while for this example, it makes sense to select any production because we want to eliminate all produced documents, you can also use this produced search term to search for documents within a specific production. It's also important to note that, this search criteria that we've built out is applied before the overall search settings. So if you choose to group your results by attachment families that could bring in additional documents. Alright, let's go into another knowledge check. And in this case, I want to look at the final versions of the documents before sharing a production. What is the best way for me to find these documents? Is it a) on the production card click the three dot menu and then choose view source documents, b) on the production card click the big blue number, c) run a search for all documents that have been produced across multiple productions, or d) run a search using the produced search term and specify original docs only. Go ahead and give everyone a moment to think about their answers and respond in the poll. Alright. The correct answer is B. Since we're looking for the final versions of these documents, the best option here is to go to the production card and click that big blue number. This will pull up a results table with all of the final produced versions. Alright. I will hand things back over to Carrie now. Now in a perfect world, once your production is finished, you'll never need to make any changes to it ever again. However, we all know that mistakes might happen during review or production, or the case may have just changed over time. When that happens in most scenarios, you can simply modify your existing production in Everlaw instead of having to entirely delete it and start over from scratch. There are three main reasons you would want to modify a production. One, if you need to change something in the production configuration, such as the bait stamp location on an image, the metadata included in a load file, etcetera. Or two, maybe you need to claw back documents that should have been marked as withheld. Or three, there is a change in the case that requires documents to no longer be privileged. Note that we can modify documents that are currently a part of an existing production. And if you need to add an entire if you need to add or entirely remove documents from productions, you'll need to delete the production and rerun it with the updated set of documents. That being said, if you saved your production protocol, you'll still be able to reuse that same protocol and you won't have to re production protocol, you'll still be able to reuse that same protocol and you won't have to reconfigure every single setting. Another important note is that production modifications are a two step process. First, you'll need to edit the original configuration of the production First, you'll need to edit the original configuration of the production protocol or edit the review work on the original document, depending on your situation. After that, you'll actually run the documents through Everlaw's production tools and create the modified production that then can be shared. Everlaw will use the updated protocol or review work as the instructions for how to change the existing document. Gonna jump back into the platform, back over to productions. One way you might need to modify a production is through an arbitrary set. This will be done by editing the production protocol itself. I hit my three dot menu and then edit. Let's say I need to move the bait stamp to the bottom right corner. Now that I'm in here, I would just go ahead and click in to image details. And then under bait stamp, bait's number, I would just change it to the bottom right corner. This is the only thing I wanna change, so then I'll just go ahead and click through. And then save. Now when I go back to my production card and I hit my three dot menu and I go to modify production, I'll see that there is an option for this arbitrary set. If you want, you can select just a subset if you wanna change only a part of your production. But in this case, I wanna I want to modify all of the documents in my production because it has to do with the bait stamp location. So I can hit save, And then I'm going to name the modification. I'll name this bait stamp modification. And then modify 16 documents. Everlaw creates a new set of modified documents replacing the previously produced version. So when I click in after this is done producing, open one of my documents, and I can see that my bait stamp is now in the bottom right corner as selected. If I ever wanna see the history of my production and any modifications, I can select show production history at the bottom of the card and see previous versions. In those versions, I can see the first one I created earlier right here and then that modification I created just now. Another way you might need to modify the production is within the documents review work directly. For example, let's say I ran my production already. And when I was reviewing my documents, I noticed one of them is privileged, but it wasn't coded as such, so it was accidentally produced. Luckily, with Everlaw, we can perform a clawback. So I'm gonna go ahead and come back to my documents. And let's say it was this first one right here, and I wanted this to actually be coded as privileged. There are a few different ways to get to your document's original version to make changes. You can either, like I did here, find my one document, go to the context panel, go to versions, and then go into the original document. Or, alternatively, from the production card itself, I can go into my three dot menu, and then I can view source documents and find it that way. Either way, once I'm at my source document, this is where I will actually make that change. So I'll go ahead and go over to my coding panel and add the code privileged. And now when I go back to my production card, I go into my three dot menu and I go to modify my production. I'll now see that there is one document available to claw back. I'm gonna follow the same process by clicking in, naming my modification, and modifying my one document. Now I can see it in my production history. And then as soon as it's done waiting to produce, I'll then wanna go ahead and click where it says package to include the modified documents in the production. If I don't click package, then the production won't contain the files that I've modified. There also may be a situation where a modification in the case leads to a document needing to be unprivileged. The process is very similar to clawing back a document. You would go to the source documents, identify it, just remove that code, and then, again, modify your production and rerun it. If you created a withholding rule for a different code, such as confidential, and you need that document to no longer be withheld, you can also remove that code to achieve the same outcome. But either way, once you've made your desired change, just go back into the card, modify the production. It'll be available here. Name it, run it, and package it. If you shared your production originally via email, you can go in and revoke access through the shared email so people no longer have access to an older version of the production. After doing that, make sure to reach out to your new with a new production link to ensure that all parties have the most up to date produced documents. You may need to delete a production if it was run by mistake or if you need to fundamentally change the document set by adding or removing documents. To do this, again, just go to the three dot menu on the production card on the production page and then select to delete production. Be aware that this action is permanent, and deleting a production removes the produced versions of the documents, the images with dates numbers, endorsements, and burned in redactions. However, this process will not affect the original source documents. All your review work like codes, notes, and highlights remain safe on the original file, allowing you to easily correct your production set or criteria and run the production again. We're gonna pause one more time for another knowledge check. And, again, you'll go ahead and use Goldcast to record your answer in the polls tab. After running my production, I realized that my privileged document was accidentally produced in full because it wasn't coded as privileged. How should I solve this problem? Should I go into my protocol and create a privilege log? Should I, b, edit my protocol to create a privilege rule that withholds all documents coded as privileged? Should I, c, go into the produced version of my document and code it as privileged, then rerun my production? Or d, go into my source document encoded as privileged, then run a callback. I'll go ahead and give us thirty seconds to answer that question now. Alright. So the correct answer for this one is D. Go into my source document and code it as privileged, then run a clawback. As a reminder, if you have a document that you neither either need to clawback or unprivilege, you're always gonna wanna make sure to make those edits and changes in the source document itself. That's where you would either apply or remove a code before then running that modification. Alright. I'm gonna go ahead and pass it over to Margo now to recap all we've learned today. Thanks, Carrie. And, yeah, we've learned a lot. So let's look back. We started with a quick refresher on production protocols. Then we talked about how to use standard and custom quality checks to catch potential issues before your production goes out the door. Then we went over how to interpret and act on those warnings. We also talked about how to actually run your production and work with resulting document versions. And finally, we discussed how to modify your production after it's been created like creating a clawback. Now before we wrap things up, we would love to know what's something new that you learned today. Go ahead and type it out in the chat. Give folks a moment to type out their answers. Awesome. Thanks, everyone. So at this point, we're gonna ask that everyone everyone respond to one more poll for us and let us know how confident you're feeling about leveraging productions on Everlaw now. You'll see that in the poll tab, and while you all are responding to that, our team is gonna publish some of the great questions that came in today so you all can see the answers. We'll give folks a moment to respond to the poll. Awesome. It's great to see that folks are generally feeling more confident about using productions on Eberlawn. Now remember, as you're working on productions in your own cases, you can always contact our amazing customer support team for help. Thank you all so much. That's a wrap from us, and we'll pass it back to Zach to close things out. Awesome. Thanks for that great session, team. I just wanna thank everybody behind the scenes answering questions. It's always great to see such an audience come and participate in training like this. We hope it was fun, at least interesting, and helps you feel more confident getting into Eberla and handling some production modifications in the near future. So we hope you take this to heart and can really get to using it soon. On that note, we are gonna run a survey, so there should be a link up on your screen now to take our training survey. Please let the team know how today's session went, what you'd like to see for future training sessions, and the user education team who puts together all this content is always happy to look at and consider your feedback. So if you have a second, we would love to hear what you have to say. Before I move on, I wanted to shout out our next session coming up for future webinars. We're gonna have a two part story builder session. So if you don't know what story builder is, it is Erela's narrative building toolkit. It is designed and meant for you to be to be used throughout the life cycle of a case. So a lot of people might think of putting together a timeline or a statement of facts. And with story builder, it allows you to start planning from day one while review is happening after your review is taking place. So we're gonna break that apart and talk about shaping that case strategy from day one in part one. And then in part two, building stronger cases faster in the deposition prep and transcript analysis piece of that narrative building process. So the the link is in the docs tab. Don't forget to check it out. You can register for both sessions today so that they're on your calendar. And, we hope to see you there soon. That'll be great to see as many of you there as possible. Another shout out, if you are interested in learning more and learning from other users, please join the Everlaw community. There's a button at the top of your screen. If you're not already a member, I highly recommend you checking it out, putting in a a post, asking questions about a specific workflow that maybe you've had challenged with. I'm sure there are members out there who can help you. So I'll put that out as a great resource. And lastly, just one last reminder for Summit. It's gonna be here so soon. We're excited to have so much, so many great speakers, so many, great sessions. So please check it out. With that, thanks, everyone. I will see you very soon. And if I don't see you at the next webinar, hopefully, I see you in person. Great. I will see you all later.