Covenant Compliance and Headroom Tracking

Executive summary

Covenant headroom is the distance between where your financial ratios are today and the level at which they would breach the terms of your credit agreement. Tracking covenant compliance well means measuring that distance in two ways, as an EBITDA cushion (how far earnings could fall) and in dollars (how much debt or how little liquidity you have to spare), and then testing it forward, quarter by quarter, instead of only looking at the last test date.

The size of the prize is time. A company that sees a thin cushion two or three quarters ahead can cut costs, delay spending, or open a conversation with its lender from a position of choice. A company that sees it on the certificate date can only react.

The first move is to read your own credit agreement and write down, in one table, each covenant, its exact definition, its test dates, and its current headroom. This article gives the formulas and the process. It does not replace the document.

Important: this is operating guidance, not legal or financial advice. Every credit agreement defines its own terms, and those definitions often differ from the textbook versions below in ways that change the answer. You must follow your own credit agreement, and you should involve your counsel and, where appropriate, your lender on any question of interpretation, waiver, or cure.

When to use this

Use this guide when:

• You have a term loan, revolver, or other facility with financial maintenance covenants.
• Headroom has narrowed in recent quarters, or you cannot say how wide it is.
• You are planning an acquisition, a large capex program, a dividend, or a restructuring that affects the covenant inputs.
• Earnings are declining, seasonal, or volatile.
• A sponsor or board asks for covenant forecasts, or a lender requires compliance certificates.
• You are preparing for a refinancing or sale and want a clean record of compliance.

Do not use this as a substitute for the agreement itself. If you do not have the final executed credit agreement and all amendments in one place, get them before building any covenant model.

If a breach is already likely or has occurred, speak to your counsel first, and see Liquidity crisis triage for the operating response.

Diagnostic questions

Answer these from your credit agreement, the last compliance certificates, and your forecast.

1. Which financial covenants exist, and are they maintenance covenants (tested on a schedule) or incurrence covenants (tested only when you take an action such as borrowing or paying a dividend)?
2. For each, what is the exact definition of every input? Is debt gross or net of cash, and is any cash netting capped? Which obligations count as debt?
3. What are the test dates and the measurement period (for example, the last four quarters)?
4. What is the required level at each test date, including any step-downs scheduled in the agreement?
5. How is EBITDA defined, and which add-backs are allowed, capped, or require documentation?
6. What is the last reported value, and what was the headroom, in EBITDA terms and in dollars?
7. Who prepares the compliance calculation, who reviews it, and who signs the certificate?
8. When is the certificate due after period end, and when are financial statements due?
9. Does your forecast project the covenant for every future test date, not only the next one?
10. What are the lender notification requirements (for example, notice of a default or potential default), and who is responsible for giving notice?
11. Does the agreement allow an equity cure or other cure right, and what are the limits on use, amount, and timing?
12. Which operating levers change each covenant, and who owns each of those levers?

How to read the answers: if you cannot answer 2 and 5, your headroom calculation is probably wrong. If you cannot answer 9, you are managing covenants backward. If 10 and 11 are unclear, resolve them with counsel before you need them.

Framework: three covenant families and two headroom measures

Most maintenance covenants fall into one of three families. Each constrains a different part of the business.

And two headroom measures that you should compute for every covenant:

• EBITDA cushion: how much EBITDA could fall, in dollars and percent, before the covenant is breached, holding other inputs constant.
• Dollar headroom: how much additional debt could be taken, or how much liquidity could be used, before the covenant is breached, holding other inputs constant.

The two answer different questions. EBITDA cushion tells the operator how much operating underperformance can be absorbed. Dollar headroom tells the treasurer how much room there is to borrow, spend, or pay out. Show both.

For how EBITDA itself moves from period to period, see EBITDA bridge and continuous tracking. Covenant EBITDA is a defined term and may not equal the EBITDA in your management accounts.

The formulas

All the formulas below are generic. Substitute the exact definitions from your agreement. Where your agreement says otherwise, the agreement wins.

1. Leverage covenant

Leverage ratio = Debt ÷ Covenant EBITDA

Debt may be total debt or net debt (total debt minus permitted cash netting). The agreement defines which obligations are included (for example, funded debt, capital leases, letters of credit drawn) and whether cash netting is capped.

EBITDA cushion (dollars):

Minimum EBITDA to comply = Debt ÷ Maximum leverage
EBITDA cushion ($) = Covenant EBITDA − Minimum EBITDA to comply
EBITDA cushion (%) = EBITDA cushion ($) ÷ Covenant EBITDA

Debt headroom (dollars):

Maximum debt at current EBITDA = Maximum leverage × Covenant EBITDA
Debt headroom ($) = Maximum debt at current EBITDA − Current debt

2. Fixed charge coverage covenant

Definitions vary a great deal. A common generic shape is:

FCCR = (Covenant EBITDA − Unfinanced capex − Cash taxes) ÷ (Cash interest + Scheduled principal)

Some agreements deduct dividends or distributions, some include lease payments in the denominator, and some use different capex definitions. Treat this as a template and adjust to the text.

Cushion in dollars of the numerator:

Minimum numerator = Minimum FCCR × Fixed charges
Numerator cushion ($) = Numerator − Minimum numerator

Because EBITDA is the main driver of the numerator, and other items are held constant, the numerator cushion is also the EBITDA cushion in dollars. Express it as a percent of EBITDA too:

EBITDA cushion (%) = Numerator cushion ÷ Covenant EBITDA

Fixed charge headroom (dollars): how much more in fixed charges (additional debt service, for example) you could absorb:

Maximum fixed charges = Numerator ÷ Minimum FCCR
Fixed charge headroom ($) = Maximum fixed charges − Current fixed charges

3. Minimum liquidity covenant

Liquidity = Unrestricted cash (as defined) + Available undrawn commitments (as defined)
Liquidity headroom ($) = Liquidity − Minimum required liquidity

Check three details in your agreement: whether the cash must be in specific accounts, whether availability is limited by a borrowing base or by another covenant, and whether liquidity is tested only at quarter end or at all times. A liquidity covenant that applies at all times has to be forecast weekly. That is the job of the weekly cash forecast described in the Cash flow operating system playbook, with its 13-week cash flow forecast template and the 13 week cash flow builder.

Worked example (illustrative)

The numbers below are made up to show the method. They are not benchmarks and not from a real company. Dollar figures are in millions. The covenant terms are invented for the example. Your terms will differ.

A company has the following at the test date:

Leverage

• Leverage = 30.0 ÷ 10.0 = 3.0x, against a maximum of 4.0x.
• Minimum EBITDA to comply = 30.0 ÷ 4.0 = $7.5M.
• EBITDA cushion = 10.0 − 7.5 = $2.5M, which is 25.0% of covenant EBITDA.
• Maximum debt at current EBITDA = 4.0 × 10.0 = $40.0M. Debt headroom = 40.0 − 30.0 = $10.0M.

Reading it: EBITDA could fall by a quarter before this covenant fails, holding debt constant. Or debt could rise by $10M, holding EBITDA constant. Remember that these are separate cushions. If EBITDA falls and debt rises at the same time, as happens when a downturn is financed with the revolver, the cushion shrinks faster than either number suggests.

Fixed charge coverage

• Numerator = 10.0 − 1.5 − 1.0 = $7.5M.
• Fixed charges = 2.4 + 3.0 = $5.4M.
• FCCR = 7.5 ÷ 5.4 = 1.39x, against a minimum of 1.20x.
• Minimum numerator = 1.20 × 5.4 = $6.48M.
• Numerator cushion = 7.5 − 6.48 = $1.02M, which is 10.2% of covenant EBITDA.

This is the binding covenant. The leverage cushion is $2.5M of EBITDA, while the FCCR cushion is only $1.02M. The tightest covenant sets the real headroom, and it is often not the one the board talks about.

Minimum liquidity

• Liquidity = 3.2 + 4.5 = $7.7M.
• Liquidity headroom = 7.7 − 5.0 = $2.7M.

Summary table

The fixed charge headroom is 7.5 ÷ 1.20 − 5.4 = 6.25 − 5.4 = $0.85M of additional fixed charges, holding the numerator constant. The cushion that matters for the operator is the $1.02M EBITDA cushion; the fixed charge headroom matters if you are considering new debt or new scheduled principal.

Forward testing: the quarter-by-quarter projection

A covenant that passes today can fail in two quarters even if nothing dramatic happens, because the measurement window rolls. Each quarter, the oldest quarter drops out of the LTM (last twelve months) figure and a new one enters. If the quarter leaving was strong and the quarter arriving is weak, LTM EBITDA falls. If a step-down in the required level is scheduled, the cushion shrinks further at that date.

Method

1. Take the last four reported quarters of covenant EBITDA.
2. Add the forecast for each future quarter, using the same definitions as the covenant.
3. For each future test date, compute LTM EBITDA, projected debt (including scheduled amortization and projected revolver use), and the required level at that date.
4. Compute the cushion in EBITDA and dollars for each test date.
5. Flag any date where the cushion falls below an internal trigger you set in advance (for example, a percentage of EBITDA that your management and sponsor agree to treat as a watch level).

Illustrative forward test

Illustrative numbers, in millions. The last four quarters of covenant EBITDA were 2.6, 2.5, 2.5, and 2.4, for LTM EBITDA of 10.0. Debt is 30.0 and amortizes by 0.75 each quarter. The leverage covenant is 4.0x for the next two test dates and steps down to 3.5x at the third and fourth. Forecast quarterly EBITDA for the next four quarters is 2.0, 2.1, 2.2, and 2.3.

How the LTM figures arise: Q+1 is 10.0 − 2.6 + 2.0 = 9.4. Q+2 is 9.4 − 2.5 + 2.1 = 9.0. Q+3 is 9.0 − 2.5 + 2.2 = 8.7. Q+4 is 8.7 − 2.4 + 2.3 = 8.6.

Reading it: leverage looks stable in a narrow band, from 3.11x to 3.19x, but the cushion falls from 22.2% to 8.9% because the required level steps down at Q+3 while EBITDA is still falling. A report that only showed the current ratio would not reveal this. The date to act on is not Q+3. It is today, because the levers (cost, pricing, working capital, deferred spend) take two or more quarters to move the LTM figure.

Sensitivities

For each future date, show at least three cases: the base forecast, a downside you define, and the EBITDA level at which the covenant breaks (the breakeven). The breakeven is the most useful single number for a board because it states the question directly: is it plausible for LTM EBITDA to fall to this level?

Do not label the downside case with a probability unless you have a basis for one. Say what it assumes, and let readers judge.

Add-back definitions: where covenant EBITDA diverges from management EBITDA

Covenant EBITDA is a defined term. Management EBITDA, board EBITDA, and the EBITDA a buyer would pay for are different numbers, and the difference is usually add-backs. Add-backs are adjustments that increase EBITDA, such as restructuring costs, transaction costs, non-cash charges, or expected cost savings. The agreement decides which are allowed, how they are capped, and what documentation they need.

Things to check in the definition:

• Which categories are permitted. A cost not listed may not be added back even if it was one-time in nature.
• Caps. Many agreements limit certain add-backs (commonly, expected or run-rate savings) to a stated percentage of EBITDA or a fixed dollar amount. Compute the cap on the right base, as the agreement defines it, which may be EBITDA before or after the add-back.
• Look-back and look-forward periods. For expected savings, the agreement may require actions to be taken or committed within a stated period and savings to be realized within another.
• Documentation and certification. Some add-backs need an officer's certificate or supporting schedule.
• Treatment of non-recurring losses and gains. Check symmetry. If gains are excluded as one-offs, losses may need to be treated alike.
• Pro forma adjustments for acquisitions and disposals. The agreement may allow or require adjusting LTM EBITDA for businesses acquired or sold during the period.

Illustrative add-back cap

Illustrative numbers, in millions. Reported EBITDA before add-backs is 8.6. The company proposes add-backs of 2.0 for restructuring and run-rate savings. The agreement caps these add-backs at 20% of EBITDA before add-backs.

• Cap = 0.20 × 8.6 = 1.72.
• Allowed add-backs = the lesser of 2.0 and 1.72 = 1.72.
• Covenant EBITDA = 8.6 + 1.72 = 10.32.

If all 2.0 were allowed, covenant EBITDA would have been 10.6, so the cap removes 0.28. With debt of 30.0, leverage is 30 ÷ 10.32 = 2.91x. A model that ignored the cap and used 10.6 would show 2.83x and would overstate headroom.

Good practice for add-backs

1. Keep a schedule of every add-back, with category, amount, period, supporting evidence, and the clause that permits it.
2. Review the schedule each quarter, not only at the test date.
3. Apply the same definition in the forecast as in the certificate. A forecast that includes an add-back the certificate would reject is a forecast of the wrong number.
4. Do not stretch definitions to create headroom. If an add-back is aggressive, assume the lender and any buyer in due diligence will question it. The quality of earnings report is where a buyer tests the same adjustments.

Cure rights and equity cure: the concept

When a financial covenant is breached, the agreement determines the consequences. A breach is typically an event of default, which may give the lender the right to accelerate repayment, charge default interest, block further draws, or demand fees, subject to the agreement's own grace periods and cure provisions. What actually happens depends on the agreement and on the lender's response. The paragraph below is a conceptual description only, not advice.

Some agreements, particularly where there is a financial sponsor, include an equity cure right. In concept, it lets the owners contribute new equity (or in some agreements, subordinated capital) within a stated period after the compliance certificate is due, and treats the contribution as if it improved the covenant calculation, so a failed test can be deemed to be passed. Agreements usually place limits on how it works. Common limit types, to be confirmed in your own text, include:

• How often it can be used, for example, a maximum number of times over the life of the facility or within a number of consecutive quarters.
• How much can be contributed, often limited to the amount needed to cure, and sometimes capped.
• How the money is counted, for example, as additional EBITDA in the affected quarter (which then also counts in later LTM periods) or as a reduction of debt, depending on the agreement.
• Whether the proceeds must be used to repay debt, or can stay in the business.
• Timing, because cure rights are usually available only within a short window after the certificate date.

Illustrative cure arithmetic

Illustrative numbers, in millions, and a deliberately simple version of one possible mechanic. Debt is 30.0 and maximum leverage is 4.0x, so minimum covenant EBITDA is 7.5. Suppose LTM EBITDA at the test date is 7.2. Leverage is 30 ÷ 7.2 = 4.17x, a breach, and the shortfall in EBITDA is 7.5 − 7.2 = 0.3.

• If the agreement treats a cure contribution as additional EBITDA, a contribution of 0.3 brings covenant EBITDA to 7.5 and leverage to 4.00x. The test is passed with no headroom.
• If the agreement instead treats the contribution as a debt reduction, the debt must fall to 4.0 × 7.2 = 28.8, so the contribution must be 1.2. The same breach costs four times as much to cure under this mechanic than under the first.

The point is not which version is common. It is that the mechanic in your agreement changes the cost of a cure materially, and the cure usually leaves headroom at zero at the next test date.

Three operating lessons follow:

1. Know in advance whether you have a cure right, what it costs under your agreement's mechanic, and who must approve a contribution (sponsor, board, investors).
2. A cure is not headroom. It repairs a test date. It does not repair the earnings problem that caused the breach, and the next test may fail for the same reason.
3. Alternatives exist, such as an amendment or waiver negotiated with the lender, an asset sale, or a debt paydown from other sources. These involve your lender, advisers, and counsel. The choice is not an accounting question.

Lender communication: timing and content

Most lenders prefer to hear about problems early, and most credit agreements include notice obligations. The details of your obligations are in your agreement. The general discipline is below. Where it conflicts with your agreement, the agreement controls, and your counsel should advise on notice, privilege, and wording.

When to talk

What a good lender conversation contains

1. The facts: current covenant levels, headroom, and the forecast for each test date, using the agreement's definitions.
2. The cause: what moved, in operating terms, supported by an EBITDA bridge.
3. The plan: the actions under management's control, who owns each, and the dates.
4. The ask, if there is one: a waiver, an amendment, a reset, or nothing at this stage. State what you propose and why.
5. The reporting offer: the information you will provide and how often, such as a monthly covenant forecast or the weekly cash forecast.

Credibility is built on consistency. A lender who has seen accurate forecasts every quarter trusts a bad-news forecast more than one who has only seen good news. That is an argument for the discipline of forward testing even when headroom is wide.

Do not wait for the certificate date to decide what to say. Do not present a number to a lender that you have not tied to the agreement's definitions. Do not rely on informal comfort without checking whether the agreement requires waivers or amendments in writing.

Step-by-step: building a covenant headroom tracker in four weeks

Week 1: Extract and define

1. Read the credit agreement and all amendments. Owner: CFO with counsel. Output: a clause-referenced summary of each financial covenant, test dates, required levels and step-downs, notice obligations, and cure rights.
2. Write the definition of each input (debt, EBITDA, add-backs, fixed charges, liquidity) in plain language with the clause number. Owner: controller. Output: definitions table.
3. List current add-backs with support. Owner: controller. Output: add-back schedule.

Week 2: Calculate and reconcile

4. Reproduce the last two compliance certificates from the ledger and check they tie. Owner: controller. Output: a calculation that matches what was reported.
5. Compute current headroom in EBITDA and dollars for each covenant. Owner: FP&A. Output: headroom summary.
6. Identify the binding covenant, the one with the least cushion in EBITDA terms.

Week 3: Project forward

7. Build the quarterly projection for each test date using forecast EBITDA, debt balances including scheduled principal and projected revolver use, and the required level on each date, including step-downs.
8. Add the breakeven EBITDA for each date, and a downside case that you define.
9. Link liquidity covenants to the weekly cash forecast, so a liquidity test that applies at all times is checked weekly.

Week 4: Operate

10. Set internal watch levels and escalation triggers, agreed with the CEO or sponsor. Owner: CFO.
11. Assign an owner for each lever that moves a covenant input: pricing and cost (EBITDA), working capital (liquidity), capex timing (FCCR), and so on.
12. Put the covenant forecast on the monthly close checklist and in the board pack. Owner: FP&A.
13. Agree the lender-communication protocol with counsel: who gives which notice, by when, and with what content.

Templates

Covenant register

Add-back schedule

Forward test grid

Monthly covenant review agenda

1. Headroom by covenant, today versus last month (5 min).
2. Forward test: next four test dates, base and downside (10 min).
3. Add-back changes and support (5 min).
4. Levers: owner, action, expected effect, date (10 min).
5. Lender communication: anything due or advisable (5 min).

Metrics and KPIs

Setting internal watch levels. Do not borrow a "safe" cushion percentage from a blog or another company. Set it from your own volatility: look at how much your quarterly EBITDA has moved from forecast over recent periods, and require a cushion comfortably larger than that, agreed with your sponsor or board. Revisit it each quarter. Where a covenant is binding on a step-down date, set the watch level against that date, not today.

Common mistakes

1. Using management EBITDA instead of covenant EBITDA. Symptom: your number differs from the certificate. Fix: use the defined term, with its caps and exclusions.
2. Testing only the next date. Symptom: surprises when the window rolls or a step-down arrives. Fix: project every test date.
3. Ignoring step-downs. Symptom: stable ratio, shrinking cushion. Fix: show the required level by date.
4. Holding debt constant in downside cases. Symptom: downside cushion looks fine. Fix: let the revolver and amortization move with cash flow.
5. Forgetting that cash netting may be capped or restricted. Symptom: net leverage overstated in the model. Fix: apply the agreement's netting rule exactly.
6. Reporting one headroom measure. Symptom: the board sees dollars but not tolerance for earnings decline, or the reverse. Fix: show both.
7. Treating the tightest covenant as the same one every time. Symptom: leverage gets attention while FCCR is closer to the line. Fix: rank by EBITDA cushion.
8. Add-backs without support. Symptom: add-backs approved quickly, questioned in diligence or by the lender. Fix: schedule, clause, and evidence.
9. Assuming a cure right is available and cheap. Symptom: no plan if the test fails. Fix: read the limits and compute the cure under your own mechanic.
10. Late or informal lender contact. Symptom: the first conversation happens after the certificate is due. Fix: a protocol agreed with counsel and triggered by forecast, not by the failure.
11. Treating liquidity covenants as quarter-end only. Symptom: an intra-quarter dip no one saw. Fix: check the test frequency, and forecast weekly if it is continuous.
12. A model that nobody else can reproduce. Symptom: only one analyst knows how the certificate is calculated. Fix: a documented definitions table and a review step.

AI prompt assistance

AI can help summarize documents, check arithmetic, and draft analysis. It cannot interpret your credit agreement for you, and it should not be relied on for legal conclusions. Provide the actual clauses, check every figure against the ledger, and have counsel confirm any interpretation. Do not paste confidential agreements into tools your organization has not approved for that data.

1. Extract covenant terms into a register.

I will paste the financial covenant section and definitions from our credit agreement. List each financial covenant with its clause number, the formula as written, each defined term it uses, test dates, required levels and step-downs, and any cure right. Quote the clause text for each definition. Do not summarize beyond the text. If a term is ambiguous, list it as a question for counsel.

Check: compare each extraction to the clause. Treat every ambiguity as a question for counsel.

2. Compute headroom and breakeven.

Using these inputs (pasted) and these formulas (pasted from our definitions table), compute leverage, FCCR, and liquidity, the EBITDA cushion in dollars and percent, the dollar headroom, and the breakeven EBITDA for each covenant. Show each calculation step.

Check: recompute one covenant by hand and tie inputs to the ledger.

3. Build the forward test grid.

Here are the last four quarters of covenant EBITDA, the quarterly forecast for the next four, the debt schedule, and the required covenant level by test date (pasted). Compute LTM EBITDA, leverage, and the EBITDA cushion for each test date. Show how each LTM figure is built. Flag any date where the cushion falls below the watch level I specify.

Check: verify the LTM roll arithmetic and that step-downs are applied on the right dates.

4. Draft a lender update outline.

Draft an outline, not final wording, for a lender update using the headroom figures I paste: the facts, the cause, the plan with owners, any ask, and the reporting offer. Do not include any statement about legal rights or obligations.

Check: counsel and the CFO review before anything is sent to a lender.

Implementation guide

Governance: the CFO owns covenant compliance and the certificate. The controller owns definitions, inputs, and the add-back schedule. FP&A owns the forward test. The CEO, sponsor, or board sets watch levels and approves any request to the lender. Counsel owns interpretation, notice, and cure questions.

What to expect: the first reproduction of past certificates often finds small differences between management numbers and the defined terms. Resolve those before projecting anything. Once the forward grid exists, keep it live: update it each month with actuals, and re-run it whenever the forecast changes or you contemplate a transaction.

Downloadable assets

The register, add-back schedule, and forward test grid above are designed to be copied into a spreadsheet. For a quick calculation of cushion and breakeven from your own inputs, use the covenant headroom calculator. Remember that the calculator uses generic formulas, and your agreement's definitions control.

Related resources

• Cash flow operating system playbook: the weekly process that keeps liquidity covenants visible.
• 13-week cash flow forecast template: forecasting liquidity week by week.
• EBITDA bridge and continuous tracking: explaining what moved EBITDA, the first question a lender asks.
• Working capital playbook: releasing cash and protecting liquidity.
• Rolling forecast vs. annual budget: the forecast cadence that feeds forward covenant tests.
• Quality of earnings report before you close: how add-backs and adjusted EBITDA are tested in diligence.
• Liquidity crisis triage: the operating response when a breach or a liquidity shortfall is likely.

Frequently asked questions

What is covenant headroom?

Covenant headroom is the margin between your current financial ratio and the level at which it would breach your credit agreement. It is usually shown two ways: an EBITDA cushion, meaning how far earnings could fall, and a dollar figure, meaning how much more debt you could take or how much liquidity you could use before the covenant is breached.

How do you calculate covenant headroom for a leverage covenant?

Divide debt by the maximum leverage ratio to find the minimum EBITDA needed to comply, then subtract that from current covenant EBITDA to get the EBITDA cushion. For dollar headroom, multiply maximum leverage by covenant EBITDA and subtract current debt. Use the debt and EBITDA definitions in your own credit agreement.

Why should covenants be tested forward?

Covenants should be tested forward because the measurement window rolls each quarter and required levels may step down, so a passing ratio today can fail later even without a sudden drop in earnings. A forward test shows the cushion at every future test date, which gives you time to act before a certificate is due.

What is an equity cure?

An equity cure is a right, in some credit agreements, to contribute new equity within a set period after a failed test so that the covenant calculation is treated as improved. Limits on frequency, amount, timing, and how the money is counted vary by agreement, and a cure does not fix the underlying earnings problem. Read your own agreement.

When should you tell your lender about a covenant problem?

Check your credit agreement for notice obligations first, because some require notice of a default or potential default within a stated time. Beyond that, many companies raise a projected breach as soon as forecasts show it, with the facts, cause, and plan. Take advice from your counsel on timing and wording before contacting the lender.

How this works in a System of Performance

Covenant headroom is only useful if the inputs behind it, such as the debt balance, add-backs, capex timing, and weekly liquidity, stay connected to the definitions in the agreement and to the decisions made to protect it. Those inputs usually sit in the ledger, the treasury workbook, and a lawyer's summary, so each quarter begins with a reconciliation exercise. A Performis routine can take on a recurring job like this, with the scope and fit agreed with you: it works from the records your team supplies, prepares the work for your named reviewer, and keeps each approval on record. To see how your own numbers look, bring it to us as a launch partner.