As per a study by the Institute for Supply Management, a typical Fortune 1000 company manages anywhere between 20,000 to 40,000 active contracts at any given time. Additionally, there are legacy contracts to add to the number. Keeping track of all of these contracts can be a nightmare if done manually. Using Natural language processing [...] Read More →
Welcome to the Brightleaf CEO blog series on Legacy Contract Migration/Extraction. Explore why your business needs to extract and migrate its legacy contracts. Companies that are embarking on getting a handle around their contracts, tracking the salient terms and data points, creating templates for contract types and clause libraries, workflows, etc. often ask Brightleaf similar [...] Read More →

Obligations and rights in a contract! Typically, in a contract, there is no specific section with says “Obligations”. Obligations and rights are strewn throughout the contract. Obligations typically say things like “Party will do…”, “Party shall do…”. Rights are typically outlined as “Party has the right to audit….”, “Customer may extend the agreement…”, “Customer is entitled to terminate […]

Read More →

Not sure where to start?  We’ve curated the best legacy contract migration/data extraction practices to get you started It’s important to cover the best practices, partially covered in the previous blogs. 1.     Decide which contracts you want to migrate 2.     Decide what data points you want to report on across a set of these legacy contracts 3.     Set […]

Read More →

The larger the company, the more the contracts – that is a given. The larger the company, the more divisions. The larger the company, the more these divisions work in silos. All companies run on contracts – buy-side and sell-side. When moving to a new enterprise or contract management lifecycle system no one wants to […]

Read More →

Again, a frequently asked and pertinent question This is the fifth of a ten-part series on contract migration and related data extraction, which will help your legal teams gain a better understanding of the information included in all of your contracts. The first reaction is that EVERY document and EVERY data point needs to be […]

Read More →

This is the fourth of a ten-part series on contract migration and related data extraction, which will help your legal teams gain a better understanding of the information included in all of your contracts. This is the most asked, if not, assumed (as yes) question! And a very pertinent one. AI Software is a necessary condition […]

Read More →
As part of the legacy contract migration/data extraction series of blogs, here is the 3rd one of the series. Can I extract and track my business-specific information? But of course! In fact, 30-40% of the information Brightleaf extracts is our clients’ business-specific information. To give an example, for a Class 1 Railroad company, we extracted [...] Read More →

The first part of the series covered, what is legacy contract migration and why do I need to do it? Here we will discuss the next/second question that is asked very often too, what attributes do I extract and ingest into a CLM during the legacy contract migration process into a CLM? There is no […]

Read More →

To kick off the series, let us first start with the simplest question – What is legacy contract migration and why do I need to do it? You are looking to install a Contract Lifecycle Management (CLM) system to get a handle on your contracts, what good is having a great CLM without any data? […]

Read More →
What is contract intelligence? Contract intelligence is the process of learning and utilizing knowledge gathered using AI-assisted contract analysis to transform contracts and agreements into valuable business assets. It empowers you to have contract visibility and take actionable insights from your contracts. It not only helps in providing transparency but also in monitoring key performance [...] Read More →

When people plan a contract management system, their immediate concerns tend to focus on finding their contracts and reporting on standard metadata, including contract owner, contract status, and renewal date. A centralized repository takes care of the first need. Configured reports set up for specific contract metadata address the second need. But beyond standard contract […]

Read More →