Covenant Tracking Software for Real Estate Lenders: A Buyer’s Guide


The best covenant tracking software for commercial real estate (CRE) lenders keeps a complete covenant record for every loan through three mechanisms. It sets up each covenant from the signed loan agreement using that loan’s own definitions.
It runs each scheduled test against the borrower’s reported financials and flags loans nearing an at-risk threshold before the test date. It keeps every test in a history and rolls compliance up across the portfolio. The Office of the Comptroller of the Currency (OCC) lists covenant tracking among credit administration processes in its Comptroller’s Handbook on commercial real estate lending. The test math is simple, and the record is where systems differ.
What Is Covenant Tracking Software?
Covenant tracking software stores the covenants in each loan agreement and runs each test on schedule against the borrower’s reported financials. It compares each result to breach and at-risk thresholds. It also keeps a history of every test and rolls compliance up across the portfolio.
It sits between the loan documents and the credit committee. For covenant types and how lenders respond to a breach, see our guide to covenant compliance monitoring for CRE loans.
Why Covenant Tracking Outgrows Spreadsheets
The math in a covenant test is simple. A debt service coverage ratio (DSCR) test divides one number by another, and any spreadsheet can run it. What breaks at scale is the record, meaning which covenants each loan carries, how each is defined, what numbers each test used, and who reviewed it.
The record also has to show which loans are drifting toward a threshold before the test date. Two pressures expose the gap: volume and evidence.
The Volume Problem
Consider an illustrative book. A lender with 400 income-producing loans and an average of six tested covenants per loan runs 2,400 tests a quarter, or 9,600 a year. Each test needs a fresh operating statement or rent roll, a calculation on that loan’s own definitions, and a review.
Reporting cycles also differ from loan to loan. For stabilized or long-lease properties, the OCC Comptroller’s Handbook says “annual operating statements and rent rolls may be adequate.” Lease-up and multi-tenant properties “could warrant the collection of monthly, quarterly, or semiannual information.”
Mixed frequencies across one book are where calendars slip. A small credit administration team ends up chasing statements on several cycles at once, and some tests run on stale numbers. When each officer keeps a separate workbook, the same covenant gets tested on different definitions across the book.
A VP of asset management or portfolio management needs at-risk loans surfaced before the test date, so the borrower conversation starts early.
The Evidence Problem
Examiners look for the record. The OCC Comptroller’s Handbook lists “covenant tracking” among the credit administration processes of a prudent CRE lending operation. When examiners rate credit administration, they consider “loan covenant monitoring and enforcement.”
The SR 23-5 interagency policy statement on CRE accommodations and workouts dates from June 2023. The Federal Reserve, the Federal Deposit Insurance Corporation, the National Credit Union Administration, and the OCC issued it together. It expects “management information systems and internal controls to identify and track loan performance and risk.”
Under a workout, management should also be able to “monitor the ongoing performance of the borrower and guarantor.” The guidance describes processes and information systems, and each lender picks the tool. A spreadsheet can hold the math, and it struggles to hold the record an examiner asks for.
A chief credit officer needs the portfolio rollup of credit metrics across the book and an exam-ready covenant record for examiners and credit committee.
Why It Matters Now
As a reference point for your own credit policy, the OCC Semiannual Risk Perspective for Spring 2026 says CRE “refinance risk merits continued attention.” Across KBRA’s $344.4 billion rated universe of private-label commercial mortgage-backed securities, September 2026 delinquency was 7.7% ($25.8 billion) and distress was 10.3%.
Must-Have Capabilities: A Covenant Tracking Software Checklist
Score each vendor on the following:
| Capability | Why it matters | What to ask the vendor |
| Covenant setup from the loan agreement | Manual entry from a long agreement is where terms get missed. Extraction should propose covenants with the source page, and a person should review them before anything is saved. | Can you show me where each term came from? |
| Per-loan definitions | The OCC notes “Debt-service coverage calculations for covenant compliance may differ from the DSCR used for underwriting and risk-rating analysis.” Income and expense definitions “should be clearly defined,” and the system has to apply each loan’s own definition to its tests. | How do you handle a DSCR covenant defined on trailing 12-month net cash flow after reserves? |
| Coverage of the common financial tests | The OCC names the most common financial covenants on income-producing loans: debt yield, DSCR, loan-to-value (LTV), loan-to-cost (LTC), and borrower or guarantor minimum net worth or liquidity. Reporting covenants, such as statements and rent rolls due, need tracking too. | Which of these tests run out of the box, and which need configuration? |
| Schedules and frequencies per loan | Lease-up and stabilized assets report on different cycles, and each loan’s calendar has to match its agreement. | Can one loan carry monthly, quarterly, semiannual, and annual tests with their own due dates and reminders? |
| Breach and at-risk thresholds | An at-risk threshold shows the team a loan approaching a limit before the test fails. | Who sets the at-risk buffer, and can it vary by covenant? |
| Test history | Every test with its value, date, status, and reviewer is the covenant record. It’s the evidence an examiner or credit committee asks for. | Can I export one loan’s full test history for an examiner? |
| Portfolio rollup | Credit leaders need compliance status and credit metrics across the book, with stale data flagged. | Can I slice compliance by property type, market, officer, and vintage? |
| Workflow for tasks, waivers, and exceptions | Each task, waiver, and exception belongs on the covenant it affects, with approvals recorded. | Can you show me a waiver moving from request to approval? |
| Data intake and validation | Operating statements and rent rolls arrive in Excel and PDF, and bad inputs produce bad tests. | How does the system catch a misread figure or a missing month? |
| Connection to the rest of the loan record | Underwriting, cash flow history, and maturity dates in one place let you read a covenant trend against the original underwriting. | Can I see a loan’s underwritten DSCR next to its tested DSCR? |
| Reporting for credit committee and examiners | Reports should come from the same covenant record the team works in, with no separate rebuild each quarter. | Which standard reports exist, and how do I build a custom one? |
| Permissions and audit trail | Examiners and auditors want to know who changed a definition or a result, and when. | Is every edit to a covenant, threshold, or test logged with user and time? |
Spreadsheets vs. General Loan Systems vs. Purpose-Built Covenant Tracking
Each category of covenant monitoring software fits a different book. The table below compares how categories and capabilities within each category vary by product.
| Criterion | Spreadsheet tracker | General loan or servicing system | Purpose-built covenant tracking in a portfolio platform |
| Covenant setup | Manual entry from each agreement | Manual entry into covenant fields, where the system has them | Designed around covenant setup, often with extraction and review from the signed agreement |
| Per-loan definitions | Possible, held in formulas and notes in each workbook | Varies widely by system, often a standard calculation | Stores each loan’s definition and applies it to that loan’s tests |
| Test calculation | Flexible formulas, maintained by hand | Strong on payments and balances, often lighter on property-level financials | Runs scheduled tests against reported operating statements and rent rolls |
| At-risk alerts | Conditional formatting, if someone opens the file | Varies by system | At-risk thresholds flag loans before the test date |
| Test history and audit trail | Overwritten or scattered across file versions | Strong on transaction history, covenant history varies | Keeps the covenant record for every test |
| Portfolio rollup | Manual consolidation across workbooks | Strong on balances and core loan data | Compliance status and credit metrics across the book |
| Link to underwriting and asset data | Separate files | Core loan data, limited property operating data | Underwriting, cash flow history, and maturities in one place |
| Cost and effort to start | Lowest, with no license and little setup | Often already licensed, with configuration needed | More setup work up front for covenant inventory and definitions |
| Where it fits best | A small book with few covenants and one owner | Payments, balances, and core servicing records | A larger book with many tested covenants and exam or investor reporting needs |
When a Spreadsheet Is Still Enough
A spreadsheet is enough for a small book with few tested covenants and one person who owns them. If that person can produce any loan’s test history on request, the case for software is weak. The case strengthens when the book grows, owners multiply, or an examiner asks for evidence the workbook can’t produce.
How to Evaluate Covenant Tracking Vendors
The best covenant monitoring software for your book is the one that handles your own agreements well. Run each vendor through the following:
- Inventory your covenants: Count loans, tested covenants, test frequencies, and the owner of each test.
- Bring three real agreements: Include your messiest one, and watch the vendor set it up in the demo.
- Test a definition edge case: Try a DSCR on net cash flow, a step-down, or a cure right.
- Ask to see an at-risk loan: Watch a loan surface before its test date, using a buffer you set.
- Request a full covenant record: Ask for one loan’s complete test history as an export.
- Check data intake: See how borrower financials get in and how the system catches bad data.
- Check fit with your lender type: Banks and credit unions need exam-ready evidence. Heads of portfolio management at private credit and real estate debt funds need investor reporting, covered in portfolio management software for private credit.
- Scope the implementation: Ask about scope, data migration, and which people on your team it needs.
Copy these questions into your request for proposal. Ask every vendor the following:
- Where did each extracted term come from, and who approved it?
- How does the system store a covenant definition that differs from underwriting?
- What happens when a borrower’s statement arrives late or incomplete?
- Can you export one loan’s full covenant record, including inputs and reviewer?
- How are at-risk thresholds set, changed, and logged?
- How do compliance results roll up for credit committee reporting?
- What does implementation require from our credit administration team?
Implementing Covenant Tracking Software
Implementation follows a predictable sequence, and the order matters because each step feeds the next. Plan for the following:
- Inventory and clean up covenants: Reconcile the covenant list against signed agreements and retire tests on paid-off loans.
- Extract from signed agreements with review: Let extraction propose covenants, and have a person confirm each one against the source page.
- Map definitions: Record each loan’s income, expense, and debt service definitions for every test to use.
- Set at-risk buffers in credit policy: Your institution sets the buffers, and the software applies them.
- Run one quarter in parallel: Test the same loans in the spreadsheet and the new system, then resolve every difference.
- Assign owners: Credit administration handles setup and testing. Asset or portfolio management handles follow-up on at-risk loans.
- Retire the spreadsheet: Archive it once the parallel quarter reconciles and owners sign off.
The parallel quarter gives the credit committee a reconciled set of results before anyone relies on the new system. It also exposes definition gaps while the old workbook is still there to check against. Credit administration and loan servicing leads own setup and testing, so involve them in definition mapping and the parallel quarter.
How Built Handles Covenant Tracking
Built is the AI operating system for real estate finance, and covenant tracking sits in its asset management and portfolio management stages.
In Deal Management, covenant tracking defines, tests, and monitors covenants in one place, with breach and at-risk thresholds that surface trouble early. Every test lands in a history with its value, date, and status, and a portfolio-wide compliance signal rolls up to the Action Center. Upload a signed loan agreement, and AI covenant extraction proposes the covenants inside it, each with a confidence score and the source page. Nothing is added to the deal until a person has reviewed it. Portfolio credit metrics roll up debt yield, DSCR, and LTV, spot trends over time, and identify stale or outdated cash flow data. The loan maturity and prepayment dashboard filters by DSCR, LTV, and debt yield eligibility to show which loans qualify for extension before the borrower conversation.
We serve 300+ lender clients, including 14 of the top 25 U.S. lenders, with $400B+ in active real estate finance managed on the platform. Our platform data puts median lender implementation at 81 days.
Request a demo to see covenant tracking on your own loan agreements.
Covenant Tracking Software FAQs
What Is the Best Covenant Tracking Software for Commercial Real Estate Lenders?
The best covenant tracking software for commercial real estate lenders keeps a covenant record for every loan. It sets up covenants from signed agreements using each loan’s own definitions. It runs scheduled tests against reported financials and flags loans nearing an at-risk threshold. It also keeps every test in a history and rolls compliance up across the portfolio for the credit committee and examiners.
What Features Should Covenant Tracking Software Have?
Require covenant setup from the loan agreement with source pages and human review. Add per-loan definitions, schedules for each test frequency, and breach and at-risk thresholds. The system should keep a full test history and roll compliance up across the portfolio with stale data flagged. Round it out with waiver workflow, validated data intake, links to underwriting, and an audit trail.
Can Excel Track Loan Covenants?
Yes. Excel can calculate any covenant test, and it works for a small book with few covenants and one owner. It struggles with volume and evidence. An illustrative book of 400 loans with six tested covenants each runs 2,400 tests a quarter. Excel also has trouble producing one loan’s full covenant record, with inputs, dates, and reviewers, when an examiner asks.
How Is Covenant Tracking Software Different from a Loan Servicing System?
A loan servicing system centers on payments, balances, escrow, and core loan data. Its covenant features vary widely and are often lighter on property-level financials. Covenant tracking software centers on the covenant record, with per-loan definitions, scheduled tests against operating statements and rent rolls, and at-risk thresholds. It also rolls compliance up across the portfolio. The two can run side by side.
Can AI Extract Covenants from a Loan Agreement?
Yes. AI extraction can read a signed loan agreement and propose the covenants inside it. Require two safeguards from any vendor. Each proposed covenant should show its source page and a confidence score, and nothing should be saved until a person has reviewed it. That review keeps the extracted terms tied to the agreement an examiner would read.
Who Should Own Covenant Tracking, Credit Administration or Asset Management?
Both should own it, with a clear split. Credit administration usually owns covenant setup, definitions, and testing because it already receives and verifies borrower financials. Asset or portfolio management owns follow-up on at-risk loans and the borrower conversation. Credit leadership sets the at-risk buffers in credit policy and reviews the portfolio rollup each quarter.

Scott Thissen is VP of Enterprise Sales at Built Technologies, where he leads go-to-market strategy and partnerships with top-tier financial institutions modernizing their construction and real estate lending operations.
Scott brings a unique perspective to lending technology: he combines deep sales leadership experience with hands-on expertise in how AI is reshaping customer conversations and deal dynamics. He’s spent the past year reimagining how sales teams can authentically engage with lenders on AI-driven transformation; moving beyond vendor pitches to genuine problem-solving around operational efficiency, risk, and scalability.
His work at Built focuses on helping his teams be consultative real estate experts for their clients navigating our new technology landscape, while building solutions that actually solve real lending problems. He’s passionate about creating frameworks that enable teams to sell smarter and build deeper customer relationships in an AI-driven world.
Scott lives in Brentwood, Tennessee, with his wife and three kids, and spends his free time running to kids soccer games and ballet recitals.

