What triggers a production covenant breach in mine project finance
A rundown of how minimum production covenants are structured, what trips them, and why the reported tonnage number matters so much.
A production covenant in a mine project finance facility usually sets a floor: deliver at least X tonnes of ore (sometimes paired with a minimum waste-movement figure) over a defined period, or the facility steps into default territory. The breach itself is almost never one bad month. It's a pattern the lender's monitoring regime is built to catch, and the thing that trips the wire depends on how the covenant is drafted.
How the covenant is usually built
Most facilities don't test production in isolation. You'll see one of three structures, sometimes stacked:
- A hard minimum tonnage test, measured quarterly or trailing-twelve-month, against the base case in the mine plan or feasibility study.
- A debt service coverage ratio (DSCR) floor, where production shortfall flows through revenue and cash available for debt service rather than being tested directly.
- A variance-to-plan trigger, where the covenant isn't a fixed number at all but a percentage deviation from the schedule in the technical report, reviewed at each reporting date.
The second structure is the one that catches people off guard. A mine can miss its tonnage number by a wide margin for a month or two and still clear DSCR if grade comes in high or commodity price offsets the shortfall. Conversely, a mine can hit plan on tonnes and still trip DSCR if costs blow out. What triggers the breach is usually the combination of a sustained volume miss and a revenue line that doesn't cover it, confirmed over the test period the facility agreement specifies rather than a single bad week on site.
Cure periods complicate the picture further. Most agreements give the borrower a window, often one or two reporting cycles, to remedy a miss before it escalates to an event of default. A lot of near-misses never show up in the headlines because they get cured inside that window. The ones that do escalate are usually the ones where the operator's own production report was already trending down for several periods and the lender's team saw it coming.
Where lender reporting fits in
The whole mechanism depends on reporting cadence. Facility agreements typically require monthly or quarterly production reports from the borrower, often backed by a reserve or technical report update and, on larger facilities, periodic sign-off from an independent engineer. The problem financiers run into is that the numbers come from the party with every incentive to smooth them.
A mine that's a bit behind plan in month four has reason to report a soft miss and a credible catch-up story rather than a hard miss that puts it closer to covenant testing territory. Usually it's rounding, timing of survey cutoffs, and optimistic scheduling of the recovery, the kind of thing that looks fine in any single month and only becomes visible once you line up several months against the plan and see the gap isn't closing.
That gap is exactly why some lenders and asset managers want a volume read that doesn't originate with the operator. Comparing the pit's elevation surface this month against last month gives you a moved-material figure built independently of anyone's monthly report, something you can set next to the mine plan or the covenant test yourself. Pit Progression is built around exactly that: a monthly extraction number and the two elevation surfaces behind it, derived from stereo imagery rather than from the site's own reporting.
What to watch for
If you're tracking covenant risk from outside the site, the early signal usually isn't the covenant test itself. It's the trend in the gap between reported and plan tonnage over three or four consecutive periods. A single period miss with a credible cure plan is normal mine operation. A widening gap that the operator keeps describing as temporary is the pattern that shows up in post-mortems on actual breaches.
Debt service coverage calculations, cure period mechanics, and the specific covenant language all sit inside your facility agreement, and that document, not this post, governs what counts as a breach on your deal. What you can get independently is the underlying volume number the covenant is testing against.
If your monthly reporting package is the only read you have on whether a site is moving the tonnes it says it is, it's worth getting a second number that doesn't come from the operator.