Back to IR Insights IR Practice

Building a Q&A Bank for Mining Company IR Teams

Any IR manager who has run three or more earnings calls at a mining company will recognize this pattern: the same questions appear, cycle after cycle, with minor variations in wording. What is your guidance for AISC in the back half of the year? How does your hedging book look given the current gold price? Can you walk us through the capital allocation framework? When do you expect the new processing plant to reach nameplate capacity?

These are not bad questions. They are the right questions for investors to ask about a producing miner. The problem is that many IR teams treat each earnings cycle as if those questions are being asked for the first time. Answers get drafted from scratch, go through multiple review passes, and arrive at the legal and IR heads' desks 48 hours before the call. The approved answer from Q3 that would have served perfectly as the starting point for Q4 is either forgotten or buried in an email thread from four months ago.

A structured Q&A bank changes that. Here is how to build one that actually works.

The anatomy of a useful Q&A entry

Most Q&A banks that IR teams try to maintain fail because they store answers in the wrong format. They keep a full verbatim answer that is specific to the quarter it was written. When the same question comes up the next cycle, the answer needs so much revision to update the numbers that it is almost as fast to write from scratch. The bank becomes a historical archive rather than a reusable tool.

A Q&A bank entry that is actually reusable has a different structure. It separates the durable frame of the answer from the period-specific data that has to be updated. For a hedging question, the durable frame is the description of the hedging program structure, the policy rationale, and the company's stated approach to commodity price exposure. The period-specific data is the current hedge book position, the percentage of production hedged, and the mark-to-market as of the reporting date.

If you store the answer this way, updating it for each cycle is a data refresh, not a rewrite. The language structure that went through legal review last quarter can carry forward. Only the numbers change.

Organizing by question type

Mining company Q&A questions cluster into a small number of repeating categories. For a gold or copper producer, the typical categories look like this:

Production performance questions address current-period output relative to guidance, the factors behind any variances (grade, throughput, recovery, unplanned downtime), and the outlook for the remaining quarters. These questions require updated data every cycle but follow a consistent explanatory structure.

Cost questions cover cash cost or AISC per ounce or per pound, the drivers of any cost increase or decrease, and the outlook for operating cost performance. The methodology for calculating AISC under the World Gold Council guidance has been stable, and companies that follow it can maintain consistent answers across cycles.

Capital allocation questions address the split between sustaining and growth capital, dividend or buyback policy, and the company's approach to project development spending. These are among the most durable answer types because the policy framework changes infrequently.

Balance sheet and liquidity questions cover the debt position, covenant headroom, cash runway, and any refinancing activity. For a company with a stable debt structure, the framework answer here changes very little from quarter to quarter.

Growth and development questions address permitting progress, construction timelines, cost-to-complete estimates, and production ramp expectations. These are specific to each company's project pipeline and require more frequent substantive updates.

The review and approval workflow

One aspect of Q&A bank management that gets underestimated is the approval workflow. Answers in the bank are not just working drafts. If an answer is going to be used as the basis for a public statement by an officer of a listed company, it needs to have been reviewed by legal and approved by the IR head and CEO or CFO as applicable.

The implication is that each Q&A bank entry should carry version metadata: who drafted it, when it was reviewed, who approved it, and whether it has been used in a public context. When the entry is updated for the next cycle, the update goes through the same review chain. The approved version is locked. Working drafts are kept separate.

This sounds like process overhead. But consider the alternative: answers drafted under time pressure at the end of a quarterly cycle, reviewed once quickly, used on a live call, and then forgotten. The bank forces a discipline that the ad hoc approach does not.

We are not suggesting that a Q&A bank entry can substitute for legal review of the specific facts at the time of the call. An entry that was accurate and approved in Q2 may not be accurate in Q3 if the underlying facts have changed. The bank is a starting point, not a final answer.

Handling new questions that do not have a bank entry

New questions appear when operating conditions change, when a new analyst initiates coverage with a different analytical framework, or when a macro event makes a question suddenly relevant that was not before. For a copper miner being asked about energy cost exposure for the first time, or a gold producer being asked about its exposure to a specific jurisdictional risk that has just become newsworthy, the bank does not help directly.

The best practice here is to treat the new question as a bank-building opportunity from the moment it is answered. When the IR team prepares the response to the new question in real time, that response should be entered into the bank with full approval metadata as soon as the cycle closes. The next time the question appears, you have a starting point.

Some IR teams maintain a "question log" alongside the bank: a running record of questions asked at each earnings call, broken down by topic area and analyst, with a flag for whether the question already had a bank entry or was addressed ad hoc. Reviewing this log before the next cycle reveals which answer types are still missing from the bank.

How often to update the bank

A Q&A bank for an active producing miner should be reviewed and updated at the start of each quarterly disclosure cycle, not at the end. The window between when preliminary production data becomes available and when the earnings call occurs is typically four to eight weeks. That is enough time to review the existing bank entries, identify which ones need data updates, flag the ones that require substantive review because the underlying facts have changed, and route them through approval before the call prep sprint begins.

Leaving the update to the week before the call creates the same time pressure that the bank was supposed to eliminate. The entries that need the most work because the operating context has changed will also be the hardest to update quickly, and those are precisely the answers where rushing is most likely to produce a problem.

An annual full review of the bank is worth doing separately from the quarterly cycle updates. This is where you remove entries that are no longer relevant, consolidate overlapping entries that address the same question from different angles, and update the policy framework answers that may have shifted due to changes in management philosophy or capital structure.

More from IR Insights