Explore the build library
consultance.ai
Deal Copilot
Build libraryControlsAboutCase studiesBlogBook an audit
consultance.ai

Systems

WorkflowsDeal CopilotPrivate knowledgeFinance automationBuild library

Company

About usCase studiesBlogContact

Start a conversation

Free AI auditfounder@consultance.ai

Teams

Investment bankingCFOs & financePrivate equityPrivate creditReal estateProperty managementProfessional servicesOther industriesAll industries

Legal

Privacy policyTerms of service

Our approach

Audit the workflow.Build in your environment.Hand over a system you own.
Build something useful © 2026 consultance.ai
Build library/Private Credit Covenant Recompute

Finance and data

Private Credit Covenant Recompute

For private credit PMs and credit analysts: recompute each borrower's leverage and coverage covenants and add backs from the credit agreement, and see which loans are fine, close or in breach.

Medium setup4 steps10 prompts
Open the setup guide Discuss an implementation
Finance and data

Start with the guided setup

Follow the setup below in your own workspace. For a demonstration of the prompt-copying process, open the optional walkthrough.

Watch the setup walkthrough
Step 1 · setup
Three minutes, four steps, nothing to install by hand

Claude sets it up for you. You just paste.

Never used Claude? It is free and takes 30 seconds to open. Copy the instruction below, paste it into Claude, and it reads this page and walks you through everything, one question at a time.

  1. Tell Claude how to talk to you

    One tap. It changes how much Claude explains, and how slowly it goes. You can change it any time.

  2. Copy your setup instruction

    A short instruction plus a link to this page lands on your clipboard. First copy asks for your email once. That unlocks every button across the whole library.

  3. Open Claude in a new tab

    Free account, no card, 30 seconds. This tab stays open so you can come back.

    Open claude.ai
  4. Paste, send, and answer one question

    Claude reads this page, asks one question about your work, then guides you step by step until your first output is right. If anything looks wrong, tell Claude what you see, and it fixes it with you.

▸Prefer the full prompt instead of the link? (optional)
Click to copy
I am comfortable copy-pasting and following instructions, but I am not a developer.
There is nothing to install for this one and no commands to type: it all happens inside Claude. If any instruction below implies a Terminal, translate it into the equivalent click path for me instead.
- Plain English. Define jargon the first time it appears.
- One step at a time, then wait for me to confirm before the next one.
- Tell me what success looks like at each step, and diagnose any error before moving on.

Follow the instructions below with those rules applied.

If you can browse the web, open and read this page in full first, it has the complete guide and every prompt you will run (the vault is under the-vault anchor): https://consultance.ai/library/private-credit-covenant-recompute#the-vault . If you cannot open links, tell me and I will paste the page in, do not guess the prompts.

You are going to help me run the quarterly covenant recompute on my borrower packs, in my own Claude, with my own accounts. Go one step at a time and wait for me after each step.

First question, and only this one: where do the borrower packs and credit agreements live? One loan as a few files I can upload here, or a folder of loans on my computer?

If I say upload: this is a Claude app job. Tell me to make a private Project and select Claude Opus 5.5 in the model picker. Do not give me a Terminal install.
If I say a folder: this is a Claude Code job. Tell me to open Claude Code in that folder, one step at a time, and tell me what success looks like after each step.

Then run the first session drill with me:
1. Paste prompt 01, the shared rules. Ask me which loans I expect to be tight and why, then the test date, the loans in scope, the close threshold and the named sign-off person, one at a time.
2. Run prompt 02 on the fake sample and compare every line to the answer key. If one line does not match, stop and tell me why before we touch real data.
3. Then run the first unit, the pack spread (borrower-pack-spread), on my real loans.
Step 2 · run it on your data

Step 1 set it up. These 10 prompts do the work.

the vault

The 10 prompts

Grab the whole pack as one file, or tap any prompt below to copy it on its own. Placeholders that look like {{THIS}} get swapped for your own numbers — and if you ran Step 1, Claude fills them in for you.

One .md file · all 10 prompts, numbered, in order · nothing left out.
Click to copy
PRIVATE CREDIT COVENANT RECOMPUTE: SHARED RULES
Every unit in this pack follows these rules. They are written here once.

1. WHERE TO RUN IT
- One borrower's pack: the Claude app, in a private Project. Chat is fine here.
- A folder of borrower packs: Claude Code, opened in that folder.
- Packs that must stay on a managed machine: Claude Code on that machine.
- The same quarter run again next quarter: Claude Code, so the spread and the table land as files.
Model: select Claude Opus 5.5 in the model picker. Use Claude Sonnet 5 only for the first bulk read of a large folder.
Privacy: your materials go only to your own Claude account, never to us. Use Team or Enterprise, or turn model training off, before you add borrower material.

2. BEFORE THE FIRST RUN
Ask the human for these, one at a time. Start with the view: which loans do you expect to be tight this quarter, and why? What decision does this table feed (a watch discussion, a valuation note, a call to a borrower)? Record the answer word for word as THESIS. Then ask for: {{QUARTER_END}} (the test date), {{BOOK}} (the loans in scope), {{CLOSE_THRESHOLD}} (default 10 percent cushion, labelled ASSUMED), and the named person who signs off the table. A missing item gets a plain default, labelled ASSUMED.
The THESIS comes first. A check that does not bear on a covenant status or on the THESIS cannot change a status.

3. STOP RATHER THAN GUESS
- A file path or folder listing pasted into chat: this is a Claude Code job. Say so and stop.
- A truncated or unreadable file: name it, and do not score it.
- A figure needs a document you do not have (an amendment, a certificate, a support schedule): ask once, name the document, mark the figure OPEN.
- Never fill a definition or a level from market standard terms. The agreement as amended is the only source.
A stop blocks only the outputs that need the missing input. Everything else still runs, for that loan and for every other loan.

4. LABELS ON EVERY FIGURE
REPORTED (document, section or page) · CALCULATED (show the arithmetic) · ASSUMED (who set it) · MARKETING (a claim in a management letter or deck: it makes a question, never a number) · NOT IN SOURCE.

5. THREE FLAG TAGS
- CHANGES THE DECISION: a covenant fails, or the status of a loan moves. Only these reach the status column.
- WORTH A QUESTION: only if the answer could move a ratio by more than 0.05x or move a loan across the close threshold.
- EXPLAINED BY CONTEXT: one line under "Checked, normal". Once closed, it stays closed and never returns.
Test every flag against the list in section 6 before you raise it.

6. LOOKS WRONG, IS NORMAL
- An add back that is large but sits inside the agreement's own EBITDA definition and its cap | permitted | not normal when it exceeds the cap or its category is excluded.
- Cash netted below the balance sheet cash | the agreement caps cash netting | not normal when the certificate nets more than the cap.
- The required level changed since last quarter | a step down schedule | not normal when no schedule or amendment supports it.
- A covenant suspended or replaced for this test date (a holiday) | an amendment says so | not normal when no document shows it or it has expired.
- An equity cure amount sits inside EBITDA | the agreement has a cure right | not normal when the count, amount or timing is outside the right.
- The term loan balance fell | scheduled amortization | not normal when it fell by more than the schedule and the revolver rose to fund it.
- Interest expense differs from cash interest | non cash amortization, OID or PIK | not normal when PIK is counted as paid in cash.
- D&A includes amortization of acquired intangibles | part of D&A | not normal only if the definition limits it.
- A ratio differs from the certificate by 0.01x | rounding | not normal beyond that.

7. STANCE
A neutral colleague who has done this many times. The certificate is a claim to check, not a suspect. Do not hunt for problems. Do not take the certificate as proof. A missing document is a question, not a finding.

8. STATUS WORDS
FINE: every covenant passes with a cushion at or above {{CLOSE_THRESHOLD}}.
CLOSE: every covenant passes, at least one below the cushion.
BREACH: a recomputed ratio fails the as amended level on documents read, and the numbers tie.
OPEN: a document needed to compute is missing. Show the ratio on the documents read and the amount at which the answer flips.
UNTIED: the pack's own figures do not tie to each other. No status for that loan until they do. Still show the ratio computed from the pack figures.
Cushion, from the unrounded ratio: leverage 1 minus ratio over limit. Coverage, or a minimum amount such as liquidity, 1 minus minimum over actual. A covenant suspended on this date is NOT TESTED: it sorts last, and FINE and CLOSE look at tested covenants only.
UNTIED is for figures that do not tie to each other. A gap fully explained by the agreement's definition (an add back the definition excludes) is a finding, not UNTIED.
A debt or cash line the pack does not give (NOT IN SOURCE) is treated as nil only if the certificate's own total ties on that basis, and is said so. Documents implied only by numbering (an Amendment No. 2 with no Amendment No. 1 shown) are a question, never a status.
A risk that falls on a later test date (a cure rolling off, a holiday ending) is raised as WORTH A QUESTION with the later date and the figure, and never changes this quarter's status.
A BLOCK (UNTIED) stops that loan's status, never the analysis. Every other check and every other loan still runs. Always print what happens by default if the human does nothing. A document closes an integrity gap. A signed opinion does not.

9. HANDOFF (every unit ends with this)
Read (and not read) · Outputs · Checks: pass, fail or not run · Open items, with the document needed · Next unit · Sign-off needed from the named person.
Click to copy
Run the pack on this sample before you use real data. Run units 04 to 09 on both loans (unit 10 on the table you produce). Compare your result to the answer key. If one figure does not match, stop and find out why before you touch real data. One document is missing on purpose, so you see the pack stop on that figure and carry on with the rest. All names are fictional. Amounts are in millions. Test date 30 September 2026, last twelve months (LTM).
THESIS for this sample: "I expect Brightwater to be the tight one. Northgate should be fine." CLOSE_THRESHOLD 10 percent. Sign-off: the credit committee chair.

LOAN A: NORTHGATE PACKAGING
A1 Credit Agreement extract.
Page 4. Consolidated EBITDA means net income plus, without duplication, interest expense, income taxes, depreciation and amortization, and non cash charges including share based pay (that sum is Pre Add Back EBITDA), plus (e) restructuring costs, up to 15 percent of Pre Add Back EBITDA, plus (f) run rate cost savings from actions taken in the period and realized within 12 months, up to 10 percent of Pre Add Back EBITDA. Net Debt means Funded Debt (term loan, drawn revolver, finance leases) less Unrestricted Cash, with Unrestricted Cash netted up to 10.0. Fixed Charges means cash interest plus scheduled principal payments. Fixed Charge Coverage Ratio means (Consolidated EBITDA less unfinanced capital expenditure less cash taxes) divided by Fixed Charges.
Page 9. Section 7.11. Total Net Leverage Ratio (Net Debt over Consolidated EBITDA, LTM) shall not exceed 5.50 to 1.00 for test dates through 30 June 2026 and 5.25 to 1.00 for each test date after that. Fixed Charge Coverage Ratio shall not be less than 1.10 to 1.00.
A2 Compliance Certificate, quarter ended 30 September 2026, page 1. Adjusted EBITDA 42.0. Net Debt 192.0 (Funded Debt 202.0 less cash 10.0). Total Net Leverage 4.57x, required 5.25x. Fixed Charge Coverage 1.83x, required 1.10x. Page 2: "Changes since the prior certificate: none." Signed by the CFO.
A3 Financial statements.
Page 1, LTM to 30 September 2026: net income 8.0. Interest expense 14.0, of which cash interest 13.2. Income taxes 3.0, of which cash taxes paid 2.6. Depreciation and amortization 9.0. Share based pay 1.0. Restructuring charges (plant closure) 4.0. Capital expenditure 7.0, all paid from operating cash. Scheduled principal paid 4.5.
Page 2, 30 September 2026: term loan 175.0 (30 September 2025: 179.5). Revolver drawn 21.0. Finance leases 6.0. Cash 22.0, all unrestricted.
Page 3, management memo: the plant closure was completed in the period and delivers 3.0 of annual run rate savings, all realized within 12 months.
A4 The Q2 2026 compliance certificate: NOT IN THE FOLDER.

LOAN B: BRIGHTWATER DENTAL PARTNERS
B1 Credit Agreement extract.
Page 4. Same Consolidated EBITDA, Pre Add Back EBITDA, Net Debt (cash netted up to 10.0), Fixed Charges and Fixed Charge Coverage definitions as A1, except clauses (e) and (f) read: (e) restructuring and integration costs and (f) run rate synergies from Permitted Acquisitions, together not exceeding 15 percent of Pre Add Back EBITDA, calculated before giving effect to clauses (e) and (f).
Page 9. Section 7.11 as originally signed: Total Net Leverage Ratio shall not exceed 5.00 to 1.00. Fixed Charge Coverage Ratio shall not be less than 1.15 to 1.00. Section 7.12: the Sponsor may cure a breach by an equity contribution, up to two cures in any four quarters. The Cure Amount counts as Consolidated EBITDA for that test date.
B2 Amendment No. 1, dated 14 May 2026, page 2. Section 7.11 is replaced: Total Net Leverage Ratio shall not exceed 5.50 to 1.00 for each test date through 31 December 2026 and 5.25 to 1.00 after that. All other terms unchanged.
B3 Compliance Certificate, quarter ended 30 September 2026, page 1. Adjusted EBITDA 40.0. Net Debt 204.0 (Funded Debt 218.0 less cash 14.0). Total Net Leverage 5.10x, required 5.50x. Fixed Charge Coverage 1.57x, required 1.15x. No cure used. Signed by the CFO.
B4 Financial statements.
Page 1, LTM to 30 September 2026: net income 5.0. Interest expense 16.0, of which cash interest 15.5. Income taxes 2.0, of which cash taxes paid 1.8. Depreciation and amortization 8.0, including 1.4 of amortization of acquired intangibles. Share based pay 1.0. Restructuring and integration costs 3.5. Run rate synergies from the Hartwell clinics, a Permitted Acquisition closed on 3 February 2026: 4.5. Capital expenditure 6.0, unfinanced. Scheduled principal paid 5.0.
Page 2, 30 September 2026: term loan 200.0 (30 September 2025: 205.0). Revolver drawn 15.0. Finance leases 3.0. Cash 14.0, all unrestricted.

ANSWER KEY
LOAN A (pass direction)
Pre Add Back EBITDA 8.0 + 14.0 + 3.0 + 9.0 + 1.0 = 35.0. Restructuring 4.0 is under its cap 5.25 (15 percent of 35.0): PERMITTED. Run rate savings 3.0 is under its cap 3.5 (10 percent of 35.0): PERMITTED. Consolidated EBITDA 42.0, ties to A2 (gap 0.0).
Funded Debt 175.0 + 21.0 + 6.0 = 202.0. Cash 22.0 netted only up to 10.0. Net Debt 192.0 (trap answer: netting all 22.0 gives 180.0 and 4.29x).
Leverage 192.0 / 42.0 = 4.57x. Required 5.25x, because 30 September 2026 is after the 30 June 2026 step down date. Cushion 1 minus 4.571 over 5.25 = 12.9 percent.
Fixed Charge Coverage: (42.0 minus 7.0 minus 2.6) / (13.2 + 4.5) = 32.4 / 17.7 = 1.83x. Minimum 1.10x. Cushion 1 minus 1.10 over 1.83 = 39.9 percent.
Status FINE. Gap to the certificate: none. Nothing CHANGES THE DECISION and nothing is WORTH A QUESTION.
Checked, normal (EXPLAINED BY CONTEXT, all five): cash netted at 10.0 against 22.0 on the balance sheet, because the agreement caps it; required level 5.25x against 5.50x earlier, a step down; restructuring and run rate add backs large but inside the definition and the caps; term loan down 4.5, scheduled amortization; interest expense 14.0 against cash interest 13.2, non cash amortization.
Missing document: the Q2 2026 certificate. Headroom trend against last quarter is OPEN. Everything else above still runs.

LOAN B (breach direction)
Pre Add Back EBITDA 5.0 + 16.0 + 2.0 + 8.0 + 1.0 = 32.0. Claimed (e) plus (f) 3.5 + 4.5 = 8.0. Cap 15 percent of 32.0 = 4.8. Permitted 4.8, excess 3.2. Consolidated EBITDA 36.8, against 40.0 on the certificate (gap 3.2). Trap answer: a cap taken on the adjusted 40.0 gives 6.0, EBITDA 38.0 and 5.47x, which looks like a pass.
Funded Debt 200.0 + 15.0 + 3.0 = 218.0. Cash netted up to 10.0. Net Debt 208.0, against 204.0 on the certificate (gap 4.0).
Leverage 208.0 / 36.8 = 5.65x. Required 5.50x (Amendment No. 1, page 2, which replaced the original 5.00x for test dates through 31 December 2026). Cushion 1 minus 5.652 over 5.50 = minus 2.8 percent. BREACH, CHANGES THE DECISION.
Cure on the agreement's terms: EBITDA needed 208.0 / 5.50 = 37.82, so a Cure Amount of 1.02. Section 7.12 allows up to two in four quarters and none is used on B3, so a cure is open. This is a condition, not a reason to soften the status.
Fixed Charge Coverage: (36.8 minus 6.0 minus 1.8) / (15.5 + 5.0) = 29.0 / 20.5 = 1.41x. Minimum 1.15x. Cushion 18.7 percent. FINE.
The certificate shows compliance at 5.10x while the recompute on the agreement's own definitions shows 5.65x: the certificate overstates EBITDA by 3.2 and nets 4.0 too much cash. CHANGES THE DECISION, severity HIGH. Only the borrower's corrected certificate or a waiver closes it. Default if nothing is done: Brightwater stays at the top of the table as BREACH and nothing is sent.
Checked, normal (EXPLAINED BY CONTEXT): interest expense 16.0 against cash interest 15.5; D&A includes 1.4 of acquired intangible amortization; run rate synergies from a Permitted Acquisition are a permitted category and only the cap bites; term loan down 5.0, scheduled amortization; Amendment No. 1 is in the folder, so 5.50x is the right level.
Thesis check: the THESIS said Brightwater is the tight one. Confirmed, and tighter than the certificate shows. Northgate is fine.
Table order: Brightwater (minus 2.8 percent) first, Northgate (12.9 percent) second.

A run that flags a normal item, takes the trap answer, or guesses the missing document has failed.
Click to copy
<unit name="tools-setup">
Follow the shared rules in prompt 01.
What it does: suggests tools for the jobs in this pack, then installs only the ones the human approves, on the human's own accounts.
Use when: after prompt 02 passes, before the first real run. Skip it if upload or paste is enough.
Needs: the "Needs" lines of every unit in this pack, and the systems the human already uses: the folder or data room where borrower packs arrive, the mailbox the certificates come in by, and the loan administration or portfolio system that holds the balances.
Method:
1. See what is already connected. In Claude Code, run `claude mcp list`. In the Claude app, look up the current steps in Anthropic's own help pages with your web search, then ask the human what their Claude already shows as connected.
2. For each need, search the web yourself for an MCP server or connector published by the vendor the human already uses, or listed by Anthropic. Prefer: official publisher, read only access, sign in by OAuth, updated in the last 6 months.
3. Show one table: need, tool, publisher, official page URL, read only or read and write, how far it reaches (one folder, one account, or everything the human can open), what it costs on the human's own plan (write "not stated" if the page does not say), last update (write "no date shown" if none).
4. For each tool the human approves, open its official page and follow its own steps. There are three kinds:
   A server with a command or URL on its page: copy the command word for word. Never write one from memory. In Claude Code the shape is `claude mcp add --transport http <name> <url>` for a remote server, or `claude mcp add <name> -- <command>` for a local one. Use `--scope project` when the tool is for this folder only.
   A connector added in the Claude app (no command): give the human the steps from the official help page, as written there. Claude Code can then use connectors added to their claude.ai account.
   An official page with no command, URL or steps, or steps behind a login: mark it ASK VENDOR, and write the one question to send the vendor contact or admin. Use UPLOAD for that need until it is answered.
5. Install one at a time. Then make one small read only test call and show the result. Then go to the next tool.
Rules: use only the human's accounts, keys and credits. Never ask for a key in chat. Use the tool's own sign in, or an environment variable the human sets. Start every tool read only. If the tool has no read only setting, connect it with a user or role that can only view, or tell the human it can write and let them decide. If it reaches further than this job needs, say so before they approve it.
<trap>A server that is not from the vendor, asks for write access or broad scopes, or sends documents to a third party for "processing". Leave it out, even when it is free.</trap>
Stop: no official page means do not install it. Mark that need UPLOAD and carry on. A need whose data lives in a document, not a system (a credit agreement, an amendment), is UPLOAD from the start. Every other unit still runs.
Output: the table, what was installed, each test result, and the handoff. Next: borrower-pack-spread.
</unit>
Click to copy
<unit name="borrower-pack-spread">
Follow the shared rules in prompt 01.
What it does: turns each borrower's pack into one standard layout, and ties the pack to itself before anything is recomputed.
Use when: the packs for the quarter are in. Run once per loan, or once over the folder.
Needs: per loan, the compliance certificate, the financial statements (income statement, balance sheet, debt schedule) and any covenant schedule the borrower sent.
Method:
1. List the documents each loan has and the ones it should have: credit agreement, every amendment and waiver the certificate mentions, the prior certificate. Mark each missing one.
2. Spread each loan into one layout, every line labelled REPORTED with document and page: net income, interest expense and cash interest, income taxes and cash taxes, D&A, non cash charges, each add back the borrower claims under the borrower's own label, funded debt by tranche, finance leases, restricted and unrestricted cash, capital expenditure split financed and unfinanced, scheduled principal paid.
3. Make the period LTM. If the pack gives four quarters, add them. If it gives year to date, build LTM as year to date plus prior year end less prior year same period, and show the arithmetic. If it gives neither, mark the period OPEN.
4. Tie the pack to itself: statement net income and cash and debt to the certificate, the parts to their totals, the units (thousands against millions). Record every difference.
<trap>A single quarter, or a quarter times four, used as LTM. Also thousands mixed with millions across two documents. Both produce a ratio that looks plausible and is wrong.</trap>
Stop: a loan with no financial statements cannot be spread. Mark it OPEN and name the document. Every other loan still runs.
Output: one spread per loan, a document inventory, the tie list, then the handoff. Next: covenant-terms.
</unit>
Click to copy
<unit name="covenant-terms">
Follow the shared rules in prompt 01.
What it does: extracts, from the credit agreement and every amendment in date order, the terms that decide each covenant on this test date.
Use when: the spread is done, and the agreement and amendments are in the folder.
Needs: the credit agreement and every amendment, waiver and consent for the loan.
Method:
1. Read the agreement first, then each amendment in date order. Later text replaces earlier text only where it says so.
2. For each financial covenant, record the level for this test date and the schedule it comes from, as amended. Record the section and page.
3. Record the Consolidated EBITDA definition: its starting point, each add back category, each cap, what the cap is measured against, whether caps are separate or shared, and any time limit.
4. Record the Net Debt definition (which debt counts, the cash netting limit), the Fixed Charges definition, and any other tested covenant (liquidity, interest coverage).
5. Record holidays, springing triggers, equity cure terms and how many cures the pack shows as used. If the earlier certificates are missing, write uses left as UNVERIFIED and do not guess.
<trap>Reading the original level or definition when an amendment replaced it, or the reverse. Also taking the level that applied last quarter when the schedule steps down on this test date.</trap>
Stop: if the credit agreement is missing, no terms exist for that loan. Its status is OPEN and no market standard terms are used. If an amendment the pack mentions is missing, take the terms from the documents you have and mark the amended term OPEN.
Output: one terms sheet per loan with a clause cite on every line, then the handoff. Next: ebitda-addback-recompute.
</unit>
Click to copy
<unit name="ebitda-addback-recompute">
Follow the shared rules in prompt 01.
What it does: rebuilds Consolidated EBITDA exactly as the agreement defines it, and tests each add back the borrower claims.
Use when: terms and spread are done.
Needs: the spread and the terms sheet for the loan.
Method:
1. Build Pre Add Back EBITDA from the definition's own starting lines, using the spread.
2. For each claimed add back, ask in order: is the category in the definition, is it supported by a document in the pack (a borrower memo or schedule in the statements counts as support, REPORTED, and is a question only if the definition asks for more), is it inside any time limit.
3. Apply each cap against the base the definition names. Where the base is the figure before the capped items, use that figure and not the borrower's adjusted EBITDA. Where several add backs share one cap, apply it to the total.
4. Mark each add back PERMITTED, PERMITTED UP TO THE CAP (give the amount and the excess), NOT PERMITTED (the category is excluded), or NEEDS DOCUMENT (the support is not in the pack).
5. Show Consolidated EBITDA on the agreement's terms beside the certificate's figure, and the gap.
<trap>A cap measured against the borrower's adjusted EBITDA instead of the base the definition names. It makes the cap larger, lets more through, and a loan that fails looks like a pass.</trap>
Stop: an add back marked NEEDS DOCUMENT is computed both ways, with and without it. If the status differs between the two, the loan is OPEN and the output names the document and the amount at which it flips. Everything else still runs.
Output: the add back table and the EBITDA gap per loan, then the handoff. Next: covenant-recompute.
</unit>
Click to copy
<unit name="covenant-recompute">
Follow the shared rules in prompt 01.
What it does: computes each tested covenant on the agreement's terms and lines it up against the borrower's certificate.
Use when: EBITDA is done.
Needs: the spread, the terms sheet, the EBITDA recompute and the certificate.
Method:
1. Net Debt: add the debt the definition counts, then net cash only up to the limit.
2. Leverage: Net Debt over Consolidated EBITDA, to two decimals. Take the required level for this test date from the terms sheet.
3. Coverage and any other tested covenant, on the definition's own numerator and denominator, with the arithmetic shown.
4. Cushion for each covenant (shared rules, section 8). If a covenant fails and the agreement has a cure right, show the cure amount that would restore it, the uses left, and say it is a condition and not a reason to soften the status.
5. If a covenant is suspended or replaced on this test date, name the document, show the ratio for information, mark the covenant NOT TESTED, and test the replacement.
6. Put the borrower's certificate beside every line (EBITDA, Net Debt, ratio, required level) and show each gap.
<trap>Netting all balance sheet cash when the agreement caps netting, and using last quarter's required level after a step down. Either one can turn a failing loan into a passing one.</trap>
Stop: a required level that depends on an amendment not in the pack is OPEN, with the ratio shown. Every other covenant and loan still runs.
Output: a covenant table per loan, then the handoff. Next: waiver-and-amendment-trace.
</unit>
Click to copy
<unit name="waiver-and-amendment-trace">
Follow the shared rules in prompt 01.
What it does: ties every waiver, consent, amendment and concession on a loan to the document that granted it.
Use when: the covenants are computed.
Needs: the certificate, any cover letter or management note, and every amendment, waiver and consent in the folder.
Method:
1. List every concession the pack mentions or relies on: waivers, consents, holidays, cures used, level changes, definition changes.
2. For each one, find the document, its date, what it changes, which test dates it covers and when it ends.
3. Check that the concession covers this test date, and was not already used up.
4. A concession claimed in a letter with no document stays MARKETING. It makes a question and no figure.
<trap>A waiver for one test date applied to the next, or a change described in a covering email that the agreement does not recognise as an amendment.</trap>
Stop: a concession with no document is OPEN. Name the document. Covenants that do not rely on it still run.
Output: a concession table (concession, document, date, covers, ends, status), then the handoff. Next: headroom-table.
</unit>
Click to copy
<unit name="headroom-table">
Follow the shared rules in prompt 01.
What it does: writes the one table the portfolio manager reads first.
Use when: units 04 to 08 are done.
Needs: all earlier outputs and the THESIS from prompt 01.
Method:
1. Open with two lines: what the THESIS expected, and what the recompute shows. Say plainly where they agree and where they do not.
2. Write the table, one row per loan and covenant, with a last column for the change in cushion against the prior certificate (OPEN when the prior certificate is not in the pack, and that is the only figure it blocks), sorted by cushion, smallest first: loan, covenant, required level, borrower reported, recomputed, cushion, status, the clause or page behind the figure.
3. Under the table, list flags with their tags. Test each against the normal list before it is raised. CHANGES THE DECISION flags carry a severity. Explained items go in one "Checked, normal" line each and stay closed.
4. List open items with the document needed, then what happens by default if the human does nothing.
5. Mark the table DRAFT. Only independent-recheck releases it.
<trap>Sorting by borrower name or by the certificate's ratio. The portfolio manager reads the order, so the order is by recomputed cushion.</trap>
Stop: a loan with status OPEN or UNTIED still appears, with its computed ratio and the document needed. It is not left out.
Output: the draft table, flags, open items, default action, then the handoff. Next: independent-recheck.
</unit>
Click to copy
<unit name="independent-recheck">
Follow the shared rules in prompt 01.
What it does: re-derives the key figures from the raw documents, then compares them to the table, and releases it or blocks the loans that do not tie.
Use when: the draft table exists. Do this in a fresh conversation if you can. If you cannot, label the recheck SAME SESSION and say it is less independent.
Needs: the raw documents (certificate, statements, agreement, amendments) and the draft table. Do not read the table until step 3.
Method:
1. For each loan, from the raw documents only, work out Consolidated EBITDA, Net Debt, the leverage ratio and one coverage ratio. Show the arithmetic.
2. Work out the required level for the test date from the amendment schedule.
3. Now read the table. Compare each figure. A difference over rounding (0.01x on a ratio, 0.05 on an amount in the pack's own units) is a BREAK.
4. Check the status word for each loan follows from the shared rules, and that the order follows the cushion.
5. A BREAK stops the status of that loan only. Mark the loan UNTIED, show both figures, and release every other loan.
<trap>Reading the table first and confirming it. Work out your figures before you look at the table.</trap>
Stop: if a raw document is missing, that loan's recheck is OPEN. State what happens by default (the loan stays as shown in the draft, marked unverified).
Output: the recheck figures, any BREAK with both numbers, the released table, then the handoff with the sign-off needed from the named person.
</unit>

From a working build to an operating system.

For private credit PMs and credit analysts: recompute each borrower's leverage and coverage covenants and add backs from the credit agreement, and see which loans are fine, close or in breach.

Path A · free

Run the build independently

The setup rail and every prompt above are free and stay free. The cost is your time, and the risk of wiring it wrong on live data.

Back to the prompts
Path B · done with you

Connect it to your operation

The pack recomputes one quarter from the documents you give it. We wire the rest into your environment, with borrower data staying in it: packs and agreements pulled in as they arrive, the spread and recompute run on each quarter, and an evidence trail your committee and auditors can follow. Reply "wire it" for a 30 minute slot.

Book a build call
data safety

Before you use live numbers

  • • Run last quarter's numbers first. Live data is not a test bed.
  • • Nothing here uploads to us. It runs in your own Claude account, on your own machine.
  • • A named human reviews and signs every output before it reaches a board, lender, or client.
  • • Mask account numbers and names to the minimum the task needs.
the fine print

Straight answers on ownership

Prompt set authored by consultance.ai. Document review support, not legal advice and not a default determination; the credit agreement and your counsel govern, and a named person owns every breach call. Borrower files stay in your own Claude account; we never see them. The worked example is synthetic.

Bring this workflow into your operation.

Book a build callBack to the library

Want this wired into your stack instead of running it yourself? That is our AI deal desk and finance automation service.

Newsletter

New builds, as they ship

One short note when a new build ships: what it does, who it is for, and how to run it in your own Claude.

Free. Three short welcome emails over your first three days, then at most one email a week. Unsubscribe in one click.

More like this

Related builds

All builds
Finance and data
Finance and data

Family Office K1 Tie Out

For family office controllers and CFOs: Claude reads each K1 and capital account statement, ties it to its entity in your book, and returns a cited exceptions list. Not tax advice.

Setup guide
Finance and data
Finance and data

Month End Close AI Agent Team

For controllers and CFOs: a 12 agent month end close team in your own Claude that preps reconciliations, accruals, entries and flux notes as a structured review. You approve every ledger post.

Setup guide
Finance and data
Finance and data

Ramp Claude Connector Setup Guide

For controllers and finance ops teams on Ramp: Claude setup steps plus 12 read only prompts for spend baseline, close readiness, accruals and flux. Replaces the manual Ramp export to Excel.

Setup guide
Get the free kitBook a call

Share with your workflow owner.

Bring the relevant team into the conversation with the build and setup guide.

Forward by email
in one line

What is Private Credit Covenant Recompute?

Private Credit Covenant Recompute is a finance and data build in the consultance.ai AI Build Library. For private credit PMs and credit analysts: recompute each borrower's leverage and coverage covenants and add backs from the credit agreement, and see which loans are fine, close or in breach. It fits Private credit portfolio managers, credit analysts and heads of credit who receive a compliance certificate and financials from each borrower every quarter and need to know which loans pass, which are close and which fail on the credit agreement's own definitions. Setup difficulty is Medium, with 4 plain-English steps.

What does Private Credit Covenant Recompute do?

For private credit PMs and credit analysts: recompute each borrower's leverage and coverage covenants and add backs from the credit agreement, and see which loans are fine, close or in breach.

Who is Private Credit Covenant Recompute for?

It fits Private credit portfolio managers, credit analysts and heads of credit who receive a compliance certificate and financials from each borrower every quarter and need to know which loans pass, which are close and which fail on the credit agreement's own definitions.

How hard is Private Credit Covenant Recompute to set up?

Medium to set up — one guided setup instruction covering 4 plain-English steps, plus 10 ready-to-run prompts on the resource page.

How would consultance.ai build this out?

The pack recomputes one quarter from the documents you give it. We wire the rest into your environment, with borrower data staying in it: packs and agreements pulled in as they arrive, the spread and recompute run on each quarter, and an evidence trail your committee and auditors can follow. Reply "wire it" for a 30 minute slot.

What are the licensing terms?

Prompt set authored by consultance.ai. Document review support, not legal advice and not a default determination; the credit agreement and your counsel govern, and a named person owns every breach call. Borrower files stay in your own Claude account; we never see them. The worked example is synthetic.

Connect this build to your workflow.

Discuss how Private Credit Covenant Recompute fits your systems, controls, and team. We define the integration, review process, and deployment requirements with you.

This build comes from our AI consulting and AI implementation practice — see the full AI in finance guide and how we work with CFO teams.

Book an audit