Training Your AI Model
How to update your AI model for document recognition
Audience
- Admins or technical resources
Prerequisites
- User set up in Azure AI
- An existing AI model
- EscrowTab admin account
- Using/plan to use EscrowTab when uploading packages (AI model not available with Elsi)
Overview
This will go over how to create an AI model based on a universal template and then add your own document types to train it to your company’s liking. As well as configure EscrowTab document types to ensure they are connected for post prep groups.
Step-by-Step Instructions
Follow these steps to complete the workflow.
- Navigating to Azure AI
- Go to https://contentunderstanding.ai.azure.com/documentintelligence/studio and scroll down to the bottom and click on Custom classification model. If you are prompted to log in, use your Microsoft credentials.

- Choosing your project
- Filter through with the below and click on the Project Name that is your company name
EscrowTab (Production) >> rg-else-webapp-centralus >> docprep-central

3. View your model
To order your documents by type, click the icon show below

This will organize the view by type and list the documents that were used to train it below.
4. Add a new document type
To add a new document type

Names need to be unique. If you would like to upload a different version of the same document you can use ## to differentiate. For example, if you had a typical Compliance Agreement as well as a different version that a branch used, you can have a Compliance Agreement type and a Compliance Agreement ## BranchName type. EscrowTab will recognize both types when AI intelligence is ran and only show the name before the ## separator.
You can have multiple ## separators for any specific document type.

5. Adding documents
You can drag and drop files or browse to add them and they will show under the Unlabeled type
You can select multiple files or one and then click on it and choose which type it should be a part of

Before you can train the model, there will need to be at least 5 sample documents per type
Please refer to the below for best practices on uploading documents
6. Training the new model version
Once document types and data are uploaded, you can train the new model version by clicking the Train button in the right corner. The Train button will be greyed out if there are any document types with less than 5 examples or if there are any unlabeled documents.
The model name follows the name convention of ProjectName.x.x.x; if it does not follow that format it will not work in EscrowTab. EscrowTab will pull the model with the highest version ending in .0 for production.

Training the model is not instant, you can check the status of it by going to the Models side bar. If it has a status of “succeeded” it means that the model is complete.

7. Testing the model
Go to Test and make sure to pick the correct model.

You can now test the model on EscrowTab or in Azure AI under Test. To successfully test in Azure AI, upload the file or files and then click Analyze options and set Split to Auto.

8. Updating Types in EscrowTab
After the model has successfully updated on EscrowTab, you may need to link up Document types. This will ensure that you can use any new added document types in post prep with groups

In EscrowTab navigate to My Account and Types. If you see any Document Types like the below, you will need to sync it

Click on the + icon and then pick the dropdown list. After saving, it should be synced

Tips and Common Pitfalls
Key tips to training documents
- Use clean copies from FileScan – not scanned or printed in PDF
- No signed documents or handwriting on the examples
- No blank pages; if there is a blank page remove it
- You need at least 5 examples, more is recommended if documents can vary by page number or can vary in look
- For examples, it’s good to have some variations with number of signers
- To match a document the AI is looking at the general outline of document and page length; so it’s helpful to get variety with examples varying with number of signers
- Once you've updated a model to EscrowTab you should also test on EscrowTab to confirm that documents are being