Short pieces on NAV triggers, fund covenants and what it takes to keep a register live: what has arrived, what is stale, what is in breach and what changes as a result. Each one is a two or three minute read.
Due soon, overdue, blocked and by whom, near covenant, deteriorating fast. Five lists in a fixed order that turn the whole thesis into one screen, each row traceable to the documents behind it.
Read the postSame inputs, independent output, nothing changes for the teams processing the book. After four weeks you compare. And why a monitoring tool should be priced per fund, with a floor, never per seat.
Read the postForty-seven covenants, 61 tests, 112 baskets and 418 defined terms out of one scanned facility in 27 minutes, with 1,003 of 1,014 citations verified by machine. What the AI got wrong, and how we knew.
Read the postNAV moves 10%, the limit should move, and instead it moves in a spreadsheet or not at all. A proposal with its rationale, a sampled review, one-click approval, an audit trail. Internal only; no amendment needed.
Read the postHeadroom, due dates, exposure and state changes are deterministic code, always. Reading, ranking, flagging and drafting are model-assisted, with a check before anything downstream depends on them. The table, and the reasons.
Read the postEvery figure traces to a page in a stored document and every write is audited. Second-line functions cannot adopt a tool that produces numbers they cannot defend to internal audit or a regulator, however good the numbers are.
Read the postEvery desk reconstructs market terms from memory and a few recent deals. The distribution of every basket, cure and blocker across your own closed deals is a query once the corpus is in a register.
Read the postLLM extraction from prospectuses and ISDA schedules works. What it does not give you is a register that stays live: a fresh NAV arriving, a test re-running, a threshold moving, a breach routed to the right desk.
Read the postIncurrence asks "may they?" on demand. Maintenance asks "are they, still, this quarter?" on a schedule. Why private credit monitoring is a calendar with a calculation attached, and syndicated tooling is the reverse.
Read the postVanilla NAV decline over 1, 3 and 12 months is the backbone. The variance is where template-based monitoring quietly fails: flow adjustment, cure periods, floors tied to audited year-end, adviser-change and cross-default clauses.
Read the postThreshold schedules, basket stacking, defined-term chains, grower baskets, restated sections and cross-references that leave the document. The six failure modes we test against, and what to ask a vendor to show.
Read the postThe same notice produces four defensible answers depending on the basis, and two people in the same team will disagree without knowing they disagree. The basis has to be an explicit, stored, auditable choice.
Read the postA review that slipped is not harmless because nothing broke. The desk was pricing exposure off old information. Why staleness needs its own population, its own metrics and its own owner in the committee pack.
Read the postIncurrence capacity is the question that keeps returning and never has a stored answer. What a capacity table looks like, why it needs a history, and why it is a credit signal months ahead of the maintenance tests.
Read the postMost books can tell you a covenant passed. Very few can tell you what the test was run against, or that it has not been run since March. Days-stale is a first-class risk metric, not a data-ops footnote.
Read the postDocuments get read hard once at close, then filed. Every question afterwards, capacity, headroom, permitted payments, sends someone back to a PDF. The problem, framed without naming a product.
Read the postA NAV decline trigger takes an hour to negotiate and then lives for a decade in a PDF nobody re-reads. The risk is not the term. It is that nothing connects the term to the calendar.
Read the post