The Private Credit Modelling Test: What You Actually Build

Open a finished private credit modelling test and a marker's eye does not go to the leverage multiple first. It goes to whether the numbers tie. A model that balances, sweeps correctly and lands on a leverage and coverage figure a lender could actually defend beats a prettier model that does not, every time. That ordering, mechanics before polish, is most of what this test is actually about, and it is worth knowing before you open the spreadsheet.

The reason is structural, not aesthetic. An LBO model and a credit model share the same skeleton — revenue, margin, working capital, a debt schedule — because both are trying to see what a company's cash flow can support. An LBO model then asks what equity earns if the plan works.

A credit model never gets there. It stops at leverage, coverage and a covenant test, because the question was never how well the plan could go. It was whether the business still pays you back when it does not. Build toward that from the first cell and every later decision, what detail earns its place, how much time the downside gets, answers itself.

The build order, and what a test usually hands you

Five pieces, built in this order, because each one feeds the next: the operating case, the debt schedule with its sweep, the interest calculation and its circularity, the covenant tests, and the downside. Skip the order and you spend the clock rebuilding something you already had right once.

Most timed tests do not ask you to build all five from a blank sheet. A pack usually hands you the historical accounts, the proposed capital structure and the pricing on each tranche. What you build is the projection, the mechanics that turn it into a debt schedule, and the two or three ratios the recommendation turns on.

Row five is the row that decides the test, and it is the row most candidates run out of time to reach. The rest of this article is about building the first four fast enough that row five gets the time it needs.

The operating case: only what moves the decision

Three drivers you can defend beat twelve you cannot. Revenue growth, margin, and the working-capital and capital-expenditure assumptions that turn EBITDA into free cash flow. The bridge from EBITDA to cash available for debt service is the fastest thing to have memorised before you sit down, because every later number runs through it.

What does not earn its place: a detailed exit, a returns page, or a working-capital schedule broken into line items you were not asked about. A projection with three drivers you can explain out loud beats one with twelve nobody has time to test.

The debt schedule and the cash sweep

The debt schedule is where the operating case turns into leverage, coverage and, eventually, a recommendation. It does not much matter whether the structure holds a straightforward senior term loan or a blended unitranche facility — the schedule works the same way either way. Get the order of operations inside it wrong and every ratio downstream inherits the error, so it is worth building this piece slowly even when the clock is short.

Mandatory amortisation, first and non-negotiable

Mandatory amortisation comes out first, on schedule, whatever the business's cash flow looks like that year. It is a fixed obligation, not a function of performance, and it reduces the balance before anything else touches it. Only after that is any excess cash applied through the sweep. Reverse the order, and a bad year quietly shows the sweep repaying debt that mandatory amortisation should have absorbed first, which flatters exactly the period where the model should be showing strain.

The sweep, in seniority order

The sweep itself runs in order of seniority. The revolver gets repaid first, out of whatever cash is left after mandatory items, since it is the facility a business draws on and repays most often. Once the revolver is clear, each term loan is swept in turn, from most senior to most junior, and each junior tranche's sweep is calculated net of what the more senior tranches already took that period.

Build the schedule in any other order, senior and junior swept together, or junior first because its margin is higher, and the junior tranche's ending balance is wrong even when every individual formula in the sheet is correct.

The share of cash actually applied is rarely the whole amount. A hundred per cent sweep is the simplest case to model and the least realistic one. Documents commonly cap the sweep at a portion of available cash flow, and it is common for that cap to step down as leverage falls, so a business that is delevering successfully keeps more of its own cash rather than sweeping every spare pound into the term loan indefinitely.

That step-down is a negotiated feature, not a fixed rule, and treating a specific percentage as a universal market number is a mistake worth avoiding out loud in the room.

The shape is also the cleanest illustration of why the covenant test and the debt schedule are not two separate exercises: the same leverage ratio that determines compliance is often the number that sets how much of next year's cash the sweep actually takes.

The circular reference, and the two clean ways to break it

Here is where most candidates lose time, and it is worth being precise about why. Interest expense is usually calculated on the average of the beginning and ending debt balance. The ending balance depends on how much the sweep repaid that period. The sweep depends on free cash flow. Free cash flow depends on net income, and net income depends on interest expense. The loop closes on itself, and Excel cannot solve it in one pass.

There are exactly two clean ways to handle this, and knowing both, and which one suits the clock you are on, is the whole skill.

• Turn on iterative calculation. Excel has a setting, in its formula options, that lets it recalculate a circular formula repeatedly until the numbers stop moving. Turn it on, cap the number of passes at a sensible ceiling, and the average-balance version of the model resolves itself.
• Build a circularity toggle. A single cell holding a one or a zero, wired into the interest formula so that a zero temporarily removes the circular term entirely. Build the rest of the model with the toggle off, so nothing else breaks while you are still debugging it, then switch it on once the schedule is otherwise finished.

Both are standard technique and neither is wrong. What actually separates a good outcome from a bad one under a clock is a third option nobody mentions until they are already stuck: calculate interest on the beginning balance instead of the average. The loop never forms, because the beginning balance was already fixed at the start of the period. It costs a small amount of precision and it costs nothing else.

Whichever route you take, build it once and move on. A candidate who spends twenty minutes perfecting the circularity has spent twenty minutes not building the downside, and the downside is worth more.

Covenant tests, period by period

Once the debt schedule runs, the covenant test is close to free. A maintenance leverage covenant is tested every period against the same EBITDA and debt figures the schedule already produces, so the test itself is one row: this period's leverage, against the level the document allows, with the gap between them carried as headroom.

What earns marks here is not the arithmetic. It is knowing what the leverage figure is actually built from, since the same ratio that determines compliance also, as the section above showed, often sets the sweep percentage and can step pricing up or down. Get the EBITDA definition wrong and three separate numbers in the model inherit the mistake at once.

The mechanics behind headroom, the maintenance-versus-incurrence distinction, and how much room the market typically allows are covered in full in the covenant guide. Inside the model itself, the only thing that matters is that the test updates automatically as the downside changes the inputs above it, which is exactly what the next section is about.

The downside case is the whole point

Most candidates build a beautiful base case and run out of clock before the case that actually decides the deal. The fix is not to spend less time on the base case. It is to build the downside so it costs almost nothing once the base case exists.

The trick is structural: never build the downside as a second model. Build it as a set of toggled assumptions sitting on top of the same operating case, the same debt schedule and the same covenant test. Change revenue growth, margin and one working-capital assumption in a handful of cells, and the sweep, the leverage figure and the covenant line all move on their own, because they were already wired to those cells.

Done this way, a downside costs the time it takes to decide what stress to name and type three or four numbers into a row of assumption cells. What it does not cost is a second debt schedule, a second sweep, or a second circularity fix, because there is only ever one of each.

Choosing the stress, and what a good one actually contains, has its own answer already: the case study guide walks through a worked downside with the arithmetic shown, and it belongs there rather than here, because that is the article about the exercise itself. What belongs here is the mechanical point: build the toggle first, and the analytical work that guide describes becomes something you have time to do properly.

What a marker checks first

Ask anyone who reviews these tests for a living what they look at first and the answer is rarely the leverage multiple. It is whether the model ties out. If a closing balance sheet does not balance, or a debt schedule's ending balance in one period does not match its opening balance in the next, nothing downstream of that error can be trusted, no matter how sensible the number looks.

That does not mean building a full three-statement model. The case study guide is right that a full balance sheet with working-capital detail is exactly the kind of scope that eats a timed test for no reward.

What it does mean is that even the shortest cash flow projection deserves one identity: cash plus net debt reconciles to where the model started, with a single line that flags to zero when it does not. That line costs a handful of cells and it is the first thing a marker's eye goes looking for.

After the tie-out, the order is roughly: does the sweep actually apply in seniority order and net of mandatory amortisation, are leverage and coverage computed off an EBITDA figure you could defend rather than the sponsor's number taken on trust, and did the model land on an actual recommendation. A clean build with no answer at the end scores worse than a rougher one that finishes.

Time allocation: the on-site against the take-home

The format follows the recruiting calendar, and the sensible build changes with it. A three-to-four hour on-site test and a two-to-three day take-home are not the same exercise at smaller scale. They ask for different amounts of the same thing.

On an on-site test, the beginning-balance shortcut from earlier is not a compromise, it is the correct choice. Nobody marking a three-hour build expects average-balance precision on the interest line, and every minute spent getting there is a minute not spent on the recommendation.

A take-home earns the opposite judgement. With two or three days on the clock, an interviewer reasonably expects the sweep to run properly, the circularity to be handled rather than avoided, and the downside to read as its own piece of analysis with its own paragraph of reasoning, not a single toggled row with nothing said about it. The mechanics do not change between formats. The amount of polish a marker is entitled to expect does.

Where the clock actually gets lost

None of the mistakes below are about knowing less than the person next to you. They are about spending the same knowledge in the wrong order.

• Over-building the operating case. A revenue build with twelve drivers takes three times as long to debug as one with three, and it rarely changes the recommendation. If a driver would not move leverage by a meaningful amount, it is detail that cost you the recommendation rather than detail that earned it.
• Chasing precision on the circularity. An average-balance interest calculation, correctly toggled and converging cleanly, is not worth more than a beginning-balance shortcut that gets the same model finished twenty minutes earlier. The extra precision buys almost nothing a marker will notice; the twenty minutes buys a downside case that would otherwise not exist.
• Getting the sweep order wrong and rebuilding it. Sweeping tranches together, or junior before senior, produces numbers that look plausible right up until someone checks them against the seniority the term sheet actually describes. Fixing it after the fact costs more time than building it correctly the first time would have.
• Treating the downside as a second model. Copying the base case into a new tab and changing formulas by hand is slower than wiring three or four assumption cells to the model that already exists, and it doubles the number of places a mistake can hide.

Every one of these is a build-order mistake, not a knowledge gap, which is exactly why the order in the next section is worth following literally rather than adapting on the fly.

A build order and a checklist you can actually run

Build in this order, every time, regardless of format:

1. The operating case. Three drivers you can defend, run through to cash available before financing.
2. The debt schedule. Mandatory amortisation first, the sweep in seniority order, one tranche at a time.
3. Interest. Beginning balance if the clock is short; average balance with a toggle or iterative calculation if it is not.
4. The covenant test. One row, off the leverage figure the schedule already produces.
5. The downside. A handful of toggled assumptions on the same model, never a second file.

Before you call it finished, run the checklist a marker actually runs:

• Does the closing balance sheet, or at minimum the cash-and-debt identity, tie to zero in every period.
• Does the sweep apply net of mandatory amortisation and in the right seniority order.
• Is the EBITDA behind leverage and coverage one you could defend if asked what is in it.
• Does the covenant line move when the downside assumptions change, or did it get left wired to the base case by mistake.
• Is there an actual recommendation at the end, with a number attached to it.

The bottom line

A credit model is not judged on how much of it you built. It is judged on whether the part you built ties out, sweeps correctly, and lands on a leverage and coverage figure you could defend under a bad year.

Build in order, break the circularity the cheap way when the clock is short, and spend the time that buys you on the downside rather than on the base case. That is most of what a marker is actually looking for.