Picture a Tuesday morning. The SOFR curve repriced 40 basis points overnight
The managing director wants to know, in the next 20 minutes, which of the firm’s 27 portfolio companies are exposed, whose hedges are actually protecting them, and where the next covenant conversation is likely to come from. In most private equity firms, that question kicks off a three-day reconciliation exercise across portfolio company CFOs, external advisors, and a spreadsheet that was last updated six weeks ago.
This guide is for the people who have run that exercise and know it does not scale. It walks through the instruments you are actually tracking, the questions a portfolio-level monitoring view has to answer, the data you need to capture, the cadence that holds up under real rate volatility, and the failure modes that surface when any of those pieces are missing.
Most hedges in PE portfolios are one of three structures. Monitoring them correctly starts with knowing what each one does and what data each one generates.
A swap exchanges floating-rate interest payments for fixed-rate payments over a defined term. In a typical LBO, a borrower pays fixed to a counterparty and receives floating, which neutralizes the floating-rate exposure on a tranche of the underlying leveraged loans. Swaps carry mark-to-market risk in both directions and can accrue liabilities if rates fall materially below the swap rate. The operational data points the monitoring system needs are notional, fixed rate, reference benchmark, effective date, maturity, counterparty, and current fair value.
A cap pays out when a benchmark rate exceeds a defined strike, and costs an upfront premium. Caps are common in private credit and direct lending deals where lenders require some hedging but borrowers want to preserve upside if rates fall. The monitoring system needs the strike, notional, maturity, premium paid, current intrinsic value, and implied value, plus a flag for whether the cap is currently in-the-money.
Zero-cost collars are attractive at the point of execution precisely because they show no line-item outflow. But “zero-cost” describes the day-one premium, not the lifetime economics. If rates drop below the floor strike, the borrower, having sold the floor, owes payments to the counterparty, a contingent liability that never appears at execution.
Monitoring a collar, therefore, means tracking both legs at once, including the fair value of the sold floor, not just the cap leg everyone remembers.
Effective hedge monitoring is not about dashboards. The problem is rarely visibility alone. The problem is whether the data can answer underwriting and covenant questions fast enough to influence decisions.
A live list of every company carrying unhedged floating-rate debt, ranked by unhedged notional, with the specific tranches flagged. This is the foundation question. Every other query depends on it being current.
The fair value of the full hedge book, portfolio company by portfolio company, and summed across the portfolio. This answers how much economic value the hedges carry if the portfolio were re-priced today.
For each portfolio company, the percentage of floating-rate debt actually covered by a hedge, and for how long. A company with $400mn of floating-rate debt and a 70% hedge ratio still leaves $120mn exposed to SOFR moves. If that gap sits in the highest-rate tranche of the capital structure, the hit to interest coverage is disproportionate to the 30% headline number.
A forward-looking view of when each hedge matures relative to the underlying debt, so rollovers can be planned alongside refinancings. A hedge that expires 18 months before the debt matures creates a window of fully unhedged exposure that is easy to miss until it happens.
Across the portfolio, how much of the notional sits with each counterparty. Larger funds with 25 or more hedges often concentrate unintentionally with a single dealer, creating counterparty credit risk that would never survive a formal treasury policy at a bank.
For portfolio companies with thin interest coverage ratio or debt service coverage ratio headroom, how much additional rate movement would push them into breach. A hedge is a buffer; the question is how much buffer is left, not just whether the hedge exists.
Every monitoring question above comes back to the same underlying data. A minimum viable schema captures the fields below for every hedge in the portfolio, refreshed at the cadence discussed in the next section.
|
Field |
Description |
Where it comes from |
|
Instrument type |
Swap, cap, collar, or other |
Hedge confirmation |
|
Notional and strike |
Hedged notional and strike/fixed rate |
Hedge confirmation |
|
Effective and maturity dates |
Start and end of hedge coverage |
Hedge confirmation |
|
Counterparty |
Dealer or bank on the other side |
Hedge confirmation |
|
Linked debt tranche |
Specific tranche of the credit agreement being hedged |
Credit agreement and deal file |
|
Current MTM |
Fair value as of the most recent valuation |
Market data feed or counterparty statement |
|
Coverage ratio |
Hedged notional / floating-rate debt balance |
Derived from debt and hedge data |
|
Covenant sensitivity |
Rate move that breaches ICR/DSCR headroom |
Derived from covenants + hedge assumptions |
|
Accounting treatment |
Hedge accounting designation and effectiveness |
Portfolio company finance team |
If any of these fields live only in portfolio company finance files, the fund cannot answer the monitoring questions without a reconciliation. Pulling them together inside Portfolio Management is what turns a quarterly report into a live view.
Not every question needs to be answered at the same frequency. The cadence should match the volatility of the underlying rate and the decisions each data point supports.
During periods of material rate volatility, daily checks on benchmark moves and the resulting MTM impact are the baseline. A 40-basis-point overnight move should not require a three-day reconciliation to understand. In calm markets, daily can step down to weekly.
Once a week, the team should review portfolio-wide coverage ratios, upcoming maturities, and any hedges that have moved materially in or out of the money.
This is also the right cadence for flagging positions approaching the amortization schedule of the underlying debt, where coverage can decay as notional is paid down.
Every month, the monitoring view should be run through covenant stress tests. How would leverage ratio or coverage covenants look under a parallel rate shock? Which portfolio companies would breach first? This question is only answerable if hedge data, financial covenant data, and financials live in the same system.
Quarterly reviews should cover counterparty concentration, hedge accounting effectiveness tests, and the narrative LPs will want on rate exposure. At this cadence, the work is not about live decisions; it is about the structured record that feeds fund-level reporting.
Funds that do not invest in centralized hedge monitoring tend to fail in a recognizable set of ways. Each of these is a signal that the monitoring setup is not keeping up.
A three-year hedge on a seven-year term loan looks complete at close. Without a rollover calendar at the fund level, the expiry can happen before the refinancing, creating a window of fully unhedged exposure that nobody was tracking.
Quarterly valuations are fine for reporting, useless for decisions. When the fund needs to answer a live question, MTM data that is two months old produces answers that are two months wrong.
Floating-rate debt balances move with amortization, prepayments, and cash sweeps. Coverage ratios that use the original debt balance, rather than the current one, overstate protection. This is especially common in cash-sweeping structures.
Individual deal teams execute hedges with their preferred dealers. Without a fund-level view, the same counterparty can end up with 40 percent or more of the book and nobody notices until a credit event forces the question.
Hedges that fail effectiveness tests create earnings volatility the fund did not model for. Monitoring the accounting treatment alongside the economic exposure avoids this kind of surprise showing up in LP reporting.
The value of a fund-level monitoring view is the ability to stress-test the portfolio in ways no individual CFO can. Four specific scenarios are worth embedding in the monthly rhythm.
A 100 basis point parallel rate shock. What happens to cash interest, coverage ratios, and covenant headroom if the benchmark moves up 100 bps across the portfolio? Which companies break first, and by how much?
An unwind at current MTM. If the fund had to unwind the full hedge book today, what would the cash proceeds or cash outflow be? This matters for both liquidity planning and fair-value reporting.
An early refinancing of a portfolio company. How does the hedge book need to be restructured if a specific portfolio company refinances six months early? What is the cost of unwinding the related hedges, and what is the replacement cost?
A counterparty downgrade or failure. If a specific counterparty is downgraded below an acceptable threshold, how much of the book has to be novated or replaced? This is the scenario funds rarely plan for until it happens.
Termgrid’s hedging feature is built inside the same platform that tracks the covenants and debt data each hedge is attached to. That means a hedge position is never viewed in isolation from the credit agreement it hedges.
Closed deals flow into this monitoring view automatically from Deal Execution, so hedge terms captured at execution stay current without anyone re-entering them. MTM data refreshes at the cadence the fund sets, and coverage, maturity, and counterparty views are available at the portfolio level without any reconciliation work.
The practical outcome is that the Tuesday morning question in the opening of this guide gets answered in the meeting, not over the following three days.
It depends on the volatility of the underlying rate. In stable environments, monthly MTM is typically sufficient. In periods of material rate movement, or during a live refinancing or rate shock scenario, daily or weekly refreshes are a better fit. The monitoring platform should let the fund set the cadence, not the portfolio company reporting cycle.
It depends on the volatility of the underlying rate. In stable environments, monthly MTM is typically sufficient. In periods of material rate movement, or during a live refinancing or rate shock scenario, daily or weekly refreshes are a better fit. The monitoring platform should let the fund set the cadence, not the portfolio company reporting cycle.
No. Any firm with more than a handful of portfolio companies carrying floating-rate debt has meaningful hedge exposure to track. Funds with 10 or more portfolio companies typically discover that Excel starts to break down once counterparty concentration, rollover timing, and scenario analysis are added to the list of things that need to be tracked.
The core inputs are the hedge confirmations from each portfolio company, the underlying credit agreement terms, current market data for MTM, and portfolio company financial data that feeds covenant ratios. A monitoring platform integrates all four rather than requiring the fund team to manually combine them each quarter.
A hedge changes the effective interest expense, which flows directly into interest coverage and fixed charge coverage calculations. If a hedge unwinds or matures, covenant headroom can shift materially even if nothing else moves. Monitoring hedges without connecting them to covenant calculations misses half the picture.
The goal is to reduce, not add, reporting burden on portfolio company finance teams. In a platform-based approach, hedge terms are captured at execution and MTM data flows from market sources, rather than requiring portfolio companies to re-submit data every quarter. That shifts work from reconciliation to analysis.
Zero-cost collars have two legs, a purchased cap and a sold floor, and both need to be tracked. The sold floor creates a contingent liability if rates drop below the floor strike, which is often underweighted in monitoring setups that focus on the cap leg. A complete view tracks both the protection and the obligation the collar represents.
At minimum: a centralized record of every active hedge with the nine fields in the data model above, a monthly MTM refresh, and a defined owner at the fund level. That alone outperforms most quarterly reconciliation processes and provides the base for more frequent cadence and richer scenario analysis as the function matures.
The end-state is not a perfect dashboard. It is a state where the people making decisions about the portfolio have current, structured, portfolio-wide hedge data at their fingertips whenever they need it, without anyone having to reconstruct it from portfolio company files.
In practice, that means hedge confirmations captured at execution, MTM refreshed at a cadence matched to market volatility, coverage and maturity data tied directly to the underlying debt, covenant sensitivity modeled at the portfolio level, and counterparty concentration visible as a first-order metric rather than an emergency discovery.
If the current process depends on quarterly reconciliation from portfolio company CFOs, the fund is one fast rate move away from the scenario that opened this guide. Request a demo to see how Termgrid centralizes hedge monitoring alongside covenants, amortization, and capital structure data for the entire portfolio in one place.
Termgrid
