The quarterly reporting cycle at a mid-cap mining company is one of the more compressed and coordination-intensive processes in corporate IR. Four times per year, data collected from mine operations, processed through several layers of reconciliation, handed to finance, reviewed by legal, approved by the executive team, and ultimately filed with EDGAR on a fixed regulatory timeline. At each stage, something can go wrong that does not become visible until it is downstream in the process.
This is a realistic description of that workflow, including the parts that typically produce the most friction. It is useful for IR managers trying to understand where their own process loses time, and for anyone evaluating where structured automation tools could have the most impact.
Stage one: production data collection and confirmation
The quarterly reporting cycle begins at the mine site well before the quarter ends. Operations teams are running their own reporting cycles to track production against plan. By the time the quarter closes, there is typically a preliminary production summary available from the mine site within one to two days of quarter end.
The preliminary number is not the final number. Metal production figures go through a reconciliation process that can take another five to ten business days after quarter end. Stockpile adjustments, concentrate shipment reconciliation, and lab assay confirmations all contribute to the final production figure that can be disclosed externally. The difference between preliminary and final is often small but occasionally material, and a company that discloses a preliminary number and then revises it within the same disclosure cycle has a credibility problem.
For a single-asset gold producer, this stage is relatively straightforward. For a diversified miner with multiple commodities and multiple processing streams, the reconciliation is significantly more complex. The IR manager cannot begin drafting the production section of the quarterly report until the confirmed production numbers arrive, and the arrival is largely outside their control.
Stage two: financial data compilation
Financial data for the quarterly earnings press release and the quarterly financial statements runs on a parallel timeline to production data. The CFO function closes the quarter's books, which for a small to mid-cap miner typically takes ten to fifteen business days after quarter end. Revenue reconciliation, cost accruals, capital expenditure classification, and intercompany eliminations for companies with operating subsidiaries all contribute to this timeline.
The IR manager needs the financial data to complete the cost section of the quarterly report, including the AISC calculation that requires total cash costs, sustaining capital, and sales volumes. If the financial close is delayed by an accounting question that requires audit committee involvement, the IR timeline compresses downstream. The production data may have been ready for a week, and the IR team is waiting on the financial close to complete the cost narrative.
This convergence problem, where two independent data streams have to be ready simultaneously before drafting can begin, is one of the more common sources of compressed timelines. The draft cannot start until both are confirmed, and neither confirms on a schedule that the IR manager controls.
Stage three: first draft
Once production data and financial data are both confirmed, the first draft of the earnings press release can be assembled. At a mid-cap miner with a relatively stable operation, this draft is structurally identical to the prior quarter's equivalent. The tables update, the numbers populate, the production comparison to guidance gets drafted, the cost variance explanation is written.
A first draft assembled manually from the prior quarter's template typically takes an experienced IR manager one to two full days if they are starting from scratch. With a structured drafting tool and a calibrated language library, the initial draft of the templated sections can be generated in hours rather than days, with the IR manager reviewing and editing rather than assembling from the ground up.
The first draft is inevitably incomplete. Sections that require management judgment, particularly the outlook section and any commentary on guidance revisions, need executive input that is not available until the executive review stage. The first draft contains placeholders for these sections that get filled in after executive review.
Stage four: internal review cycle
The internal review cycle at a listed company is where the most time is lost in a poorly managed process. The sequence is typically: IR draft to legal review, legal review to CFO review, CFO review to CEO review, CEO review back to legal for final check, then back to IR for final assembly before external distribution and filing.
Each pass introduces comments, revisions, and sometimes back-and-forth between reviewers that requires another round. A company without a structured review workflow, where comments are delivered verbally or via email in free-form text, can spend as much time reconciling reviewer edits as was spent drafting the original document.
The management discussion section, which requires the CEO and CFO to sign off on forward-looking statements and guidance language, is the most time-intensive review stage. This is appropriate: the people whose reputations are associated with public guidance statements should be reviewing them carefully. The inefficiency comes from an unstructured process where this review happens under time pressure rather than being staged within a pre-agreed timeline.
Stage five: EDGAR filing and external distribution
The final stage, preparing the EDGAR filing and distributing the press release, has its own technical requirements. Form 8-K filing for an earnings press release has specific requirements around timing relative to the event being disclosed, and the EDGAR submission process requires a specific file format. For companies with annual reports that include inline XBRL tagging, the tagging process adds time and technical complexity to the annual cycle beyond what the quarterly press release requires.
The distribution of the press release via a newswire service, the simultaneous posting to the company website and EDGAR, and the notification to the exchange (for TSX-listed companies) all happen within a tight window that is typically less than one business day. System failures at this stage, a formatting error in the EDGAR submission, a website that takes longer to update than expected, are highly visible failures that create immediate concern among the analyst community.
Where the time goes and what to do about it
Mapped against this workflow, the sources of avoidable time loss fall into three categories. First, waiting for confirmed data that has not been given a firm delivery commitment to IR. Second, first-draft assembly time that is higher than it needs to be because the IR team is reconstructing a document they have built three or four times before. Third, internal review friction from an unstructured comment process and a compressed timeline for executive review.
Each has a specific remedy. Confirmed data delivery: agree deadlines with operations and finance at the start of each quarter, not at the end when it is too late. First-draft assembly: structured drafting tools with calibrated language libraries and prior-period templates that generate the initial framework automatically. Internal review friction: structured workflow that stages reviews in sequence with agreed turnaround times, comment tracking that makes it clear who has reviewed what and what is outstanding.
None of these remedies requires significant technology investment. The structured drafting tool adds the most leverage on first-draft time. The workflow and deadline agreements are pure process, no technology required.
