In conversations with IR managers at listed mining companies, a number that comes up repeatedly is 40 to 60 hours per quarter spent on disclosure preparation. That includes drafting the earnings press release, preparing the MD&A, and getting through the internal review cycle before external publication. For a mid-cap single-asset or two-asset gold or copper producer, this is not unusual.
The striking part is not the raw hours. It is what those hours are actually spent on. When you break down the quarterly disclosure workload, a substantial portion is going toward producing output that differs from last quarter's equivalent documents by maybe 15 percent of the actual content. The production tables change. The cost variances need new explanatory language. The balance sheet numbers update. But the structure, the policy boilerplate, the commodity price sensitivity language, the hedging program descriptions, the forward-looking statement conventions: those are almost identical to what was published three months ago.
Where the time actually goes
The biggest single time consumer in a quarterly disclosure cycle is not writing. It is coordination and reconciliation.
The IR function at a listed miner is downstream of multiple input streams. Production data comes from the mine site through a reporting chain that may involve a mine manager, a head of operations, and a technical services function before it gets to IR in a form that can be included in external disclosure. Financial data comes from CFO-side accounting in a format that needs to be reconciled to the IR narrative. Legal review of forward-looking language involves at least one additional pass. Executive review typically involves the CEO and CFO at a minimum, each of whom has their own edit preferences.
Each handoff takes time that is hard to measure because it does not look like production time. It looks like waiting. The draft sits in a reviewed state while the IR manager waits for the production data to be confirmed. The production data is confirmed, but then the legal pass raises a question about the guidance language that requires a conversation. The conversation produces an agreed change, which requires re-routing the document.
In a four-person IR function running this process manually, the wait time between handoffs often exceeds the drafting time itself. The disclosure is not late because the writing was slow. It is late because the process between writing and publishing is unmanaged.
The sections worth automating
Not all of the 40-60 hours are equivalent in terms of automation potential. Some categories of work are genuinely judgment-dependent and cannot be systematically accelerated without reducing quality. But a meaningful portion is mechanical and can be handled with a structured drafting tool.
Production metrics tables are the clearest example. The format for presenting quarterly production statistics has been consistent across the resource sector for years. Total ore processed, head grade, recovery rate, payable metal production, prior quarter comparison, prior year equivalent period comparison: the structure is fixed. The numbers need to be populated and verified, but the framework requires no original thinking. A drafting tool that has been configured for your company's specific format can generate the production table in its approved structure with the numbers filled in, leaving the IR manager to verify accuracy rather than assemble from scratch.
Cost narrative is similar in its high-repetition structure. The AISC calculation methodology is standardized (World Gold Council for gold producers, equivalent frameworks for copper and other metals), and the variance explanation follows a consistent pattern. The current quarter's costs were higher or lower than guidance, driven by X and Y factors, with an outlook statement for the following period. The specific X and Y have to be supplied by the IR manager from the mine site data, but the surrounding language framework repeats verbatim quarter after quarter.
Forward-looking statement language and boilerplate disclaimers are essentially frozen text that should not be drafted each cycle. They should be stored, versioned, and applied without redrafting.
What is not worth automating
The sections that require fresh thinking every quarter are the sections that explain why the quarter was different from guidance or different from the prior period in ways that were not fully anticipated.
If a gold producer had unplanned equipment downtime in Q1 that reduced mill throughput, the explanation of that event and its impact on production and AISC needs to be drafted from the actual facts. An AI tool can provide the sentence structure that your company typically uses for these explanations. It cannot tell you what happened at the mine or whether the event is fully resolved.
Capital allocation commentary and guidance revision language are also sections that require direct IR and management judgment. When management is revising production guidance downward by 5 percent due to a permitting delay, the narrative around that revision has to be precise and deliberate. It will be read closely by every analyst covering the stock. The explanation cannot be generated from a pattern; it has to reflect what actually happened and what the company expects going forward.
Fixing the coordination problem
Even if you solve the drafting side, the coordination problem remains unless you address it separately. The most effective change an IR team can make to reduce total cycle time is not faster drafting. It is a structured workflow that makes the handoff sequence explicit and tracks where the document is at each stage.
For most mid-cap listed miners, this means establishing a fixed timeline at the start of each quarterly cycle: when production data must be delivered to IR in a confirmed state, when the first draft is due, when legal review starts and ends, when executive review happens, and when the final document must be locked for the filing and distribution deadline. The timeline is agreed by all stakeholders before the cycle starts, not negotiated under time pressure after the cycle is already running.
This sounds basic, and it is. But the absence of an agreed timeline is the single most common reason that disclosure preparation time runs longer than it needs to. When the mine site knows that production data is needed by a specific date and IR knows when to expect it, the wait time shrinks. The draft can start on time. The downstream review steps are not compressed.
A drafting tool that generates the initial disclosure framework from the prior quarter's approved language, with placeholder fields for the current-period data that need to be filled in, makes the start of the cycle more explicit. The IR manager can see exactly which sections are waiting for input, which inputs have arrived, and which remain outstanding. That visibility does more to reduce cycle time than any improvement to writing speed.
