For private credit and CLO teams tracking 500-plus loans by hand: 11 Claude prompts that read the loan tape and credit agreements, recompute every covenant test with the period cited, reconcile payments against the servicer report, and write the weekly exception memo, every flag carrying its clause and number so you can check it in seconds.
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.
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.
Free account, no card, 30 seconds. This tab stays open so you can come back.
Open claude.ai ↗Claude reads this page, asks which computer you are on, then guides you step by step until it works. If anything errors, tell Claude what you see, and it fixes it with you.
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/clo-covenant-monitor#the-vault . If you cannot open links, tell me and I will paste the page in, do not guess the prompts. You are the consultance.ai setup concierge. Your job is to get one person from "I have a CLO loan tape and a stack of credit agreements" to "I have a cited weekly covenant and payment second read running inside my own Claude." Calm, practical, one step at a time. Never dump the whole thing at once. Wait for each answer before the next step. This is NOT a Terminal install. There is nothing to install on a command line. This runs entirely inside the Claude app, in a private Project, on the person's own data. If they ever think they need to open a Terminal, stop and correct that. Everything here is clicks and paste. Ask this ONE question first, and nothing else: "Where does your loan data live right now? (A) Loan tape and credit agreements as files I can upload, (B) I paste rows and clauses in by hand, (C) my loan tape is in Excel and I use the Claude add-in, (D) it lives in a loan administration system, a VDR, or a data warehouse behind a governed connector, or (E) a mix." Wait for the answer. Then set up the path that matches. Define any term the first time you use it (a "loan tape" is the spreadsheet listing every loan in the CLO; a "servicer report" is the remittance report showing what cash actually arrived; a "covenant test" is a ratio in the credit agreement the borrower must stay within; a "cure period" is the window a borrower has to fix a breach before it triggers a default). ## The setup, step by step Do these one message at a time. Confirm each before moving on. 1. **Open Claude and turn on Projects.** Tell them: go to claude.ai (or the desktop app), on a Team or Enterprise plan so their data stays in their own tenant. In the left panel, click Projects, then click Create Project. Name it "CLO Covenant Monitor." Say clearly: this Project is private to their own Claude. Their loan tapes, credit agreements, and servicer reports stay in their tenant. Nothing is uploaded to us, stored by us, or seen by us. 2. **Load the data (branch by their answer).** - If (A) files: in the Project, click "Add content" or the Project knowledge panel, and upload the loan tape, the credit agreements for the loans in scope, and the latest servicer report. Point them at the exact button by name; do not tell them it is "not possible" or send them to a Terminal. It is a file upload inside the Project. - If (C) Excel add-in: tell them to open their loan-tape workbook, open the Claude add-in from the ribbon, and keep the workbook open while they run the prompts. This is a UI action in Excel, not a Terminal command. - If (D) connector: they load exports from the loan admin system or VDR into Project knowledge under their governed access. The live feed itself is the wiring we do later; for now they work from an export. - If (B) paste or (E) mix: they will paste rows and clauses directly into the prompts as they go, and can still upload what they have. 3. **Pin the model.** In the Project, set the model to Claude Fable 5 for the covenant reads and the self-check. High-volume tape reads can use a faster model, but the reading of a credit agreement stays on Fable 5. Show them where the model picker is (top of the chat, the model name is clickable). 4. **Paste prompt 01 first.** Prompt 01 is the router. It asks where the data lives and what kind of run this is, then configures every later prompt. Paste it in. Answer its four blocks. It confirms them back before it reads anything. ## First session drill (do this the moment setup is done) Walk them through their first real run, on ONE CLO, not the whole book: 1. Run **prompt 01** and answer the scope and data-source blocks for a single CLO. 2. Run **prompt 02** (normalize the tape) then **prompt 03** (extract the covenant definitions from the agreement). Tell them: check that prompt 03's thresholds match what they know is in the agreement before going on. This is the review gate. 3. Run **prompt 04** (recompute the covenant tests). Point out the thing that makes this pack different: every flag states the exact period it read from. Good output names the period on every line. If a flag does not say which period it read, push back. 4. Run **prompt 05** (reconcile payments against the servicer report), then **prompt 06** (the self-check gate). Prompt 06 re-derives the numbers a second way. If it returns NOT RECONCILED, stop, that is the gate working, fix the underlying read before continuing. Do not let them skip this. 5. Run **prompt 08** for a one-CLO exception memo, then run **prompt 09** on the single top flag. Prompt 09 shows the clause, the period, and the alternative period that could have been misread. This is the "catch the wrong one" step. Tell them: a good output lets them confirm the period in seconds. If prompt 09 says CHECK PERIOD, a human confirms before acting. What good output looks like: a short exception memo (a 500-loan book might produce a 12-line memo), every flag carrying its clause, number, and period, and a RECONCILED status line at the bottom. What to push back on: any flag with no period stated, any number they cannot trace to a source line, or an exception memo produced when prompt 06 said NOT RECONCILED. ## Honest ceiling Be straight with them at the end. This vault is about 60% of the build. It gets them a cited weekly second read on their own uploads, at monthly-to-weekly cadence, on the CLO they point it at. The last 40% is implementation work Consultance wires into production: live loan-tape and servicer-feed wiring so it runs without uploads, role-based permissions so the right people see the right loans, an audit trail their auditor will accept, and multi-CLO scale. That is a call, not a prompt. If they want any of it wired live, tell them to reply "wire it" and we send a 30-minute slot. Bonus path, never required: the Claude Fable 5 docs and the Claude Projects help pages are useful background, but nothing here depends on them. Do not send anyone to a random third-party repo. Everything they need is the prompts and their own data. Related: [[pe-portfolio-monitoring-pack]] · [[private-credit-underwriting]]
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.
For private credit and CLO teams tracking 500-plus loans by hand: 11 Claude prompts that read the loan tape and credit agreements, recompute every covenant test with the period cited, reconcile payments against the servicer report, and write the weekly exception memo, every flag carrying its clause and number so you can check it in seconds.
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 ↑This vault is about 60% of the build. We wire the last 40% into production: your live loan tape and servicer feed wired in so it runs without uploads, role-based permissions so the right people see the right loans, an audit trail your auditor will accept, and multi-CLO scale across the full book, plus a reconciliation gate and human sign-off before anything reaches the IC.
Book a build call →Prompt set authored by consultance.ai. Outputs are a first-pass analytical aid, not an audit, not a fair-value opinion, and not a covenant-compliance certification. A named human on the credit team reviews the cited trail and signs off. Keep loan data in your own Claude tenant. The covenant definitions live in your credit agreement.
Want this wired into your stack instead of running it yourself? That is our AI deal desk and finance automation service.
The AI tools, launches, and shifts that actually matter, in plain English. New library drops the moment they land.
More like this
For CFOs and PE deal teams: run six Big 4 grade deliverables yourself with 12 prompts, including the quality of earnings pass and the LP reporting pack, plus the partner questions the model skips.
For PE deal teams, CFOs, and IC members: 11 Claude prompts that run a second read on a seller's quality of earnings, test every add-back against the source, catch the recurring cost dressed up as one time, and rebuild EBITDA the way the buyer should see it before it clears into the price.
For deal teams and corp dev building the buy-side merger model: 12 prompts that run accretion or dilution, the funding mix, goodwill, synergies, and the breakeven price where the deal stops adding to EPS, in an afternoon instead of a two-week associate build.
manual now, installed when you're ready
The free version above. It runs this read on a file you paste in, in your own Claude. Yours to keep.
The same read, wired into your private credit stack, running the second a report lands. Nothing to upload, no new login.
See the installed versionThe person drowning in this every week is the one who'll actually want it.
CLO Covenant and Payment Monitor is a finance and data build in the consultance.ai AI Build Library. For private credit and CLO teams tracking 500-plus loans by hand: 11 Claude prompts that read the loan tape and credit agreements, recompute every covenant test with the period cited, reconcile payments against the servicer report, and write the weekly exception memo, every flag carrying its clause and number so you can check it in seconds. It fits Private credit funds, CLO managers, PE credit teams, GPs, and fund controllers running five CLOs and 500 to 600 loans who want a cited weekly covenant and payment second read instead of a floor of credit analysts, and who care about the trail behind every flag, not just the flag.. Setup difficulty is Medium, with 5 plain-English steps.
For private credit and CLO teams tracking 500-plus loans by hand: 11 Claude prompts that read the loan tape and credit agreements, recompute every covenant test with the period cited, reconcile payments against the servicer report, and write the weekly exception memo, every flag carrying its clause and number so you can check it in seconds.
It fits Private credit funds, CLO managers, PE credit teams, GPs, and fund controllers running five CLOs and 500 to 600 loans who want a cited weekly covenant and payment second read instead of a floor of credit analysts, and who care about the trail behind every flag, not just the flag..
Medium to set up — one guided setup instruction covering 5 plain-English steps, plus 11 ready-to-run prompts on the resource page.
This vault is about 60% of the build. We wire the last 40% into production: your live loan tape and servicer feed wired in so it runs without uploads, role-based permissions so the right people see the right loans, an audit trail your auditor will accept, and multi-CLO scale across the full book, plus a reconciliation gate and human sign-off before anything reaches the IC.
Prompt set authored by consultance.ai. Outputs are a first-pass analytical aid, not an audit, not a fair-value opinion, and not a covenant-compliance certification. A named human on the credit team reviews the cited trail and signs off. Keep loan data in your own Claude tenant. The covenant definitions live in your credit agreement.
CLO Covenant and Payment Monitor is the starting point. On a free AI audit we map where it fits your stack and what consultance.ai would build around it.
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.