Planned vs Actual Mine Production: Shift Variance Guide

How to Compare Planned vs Actual Mine Production During a Shift

The shift report says 14,200 tonnes. The plan said 18,000.

Your superintendent is already on the radio asking what happened, and your dispatcher is pointing at the screen like it owes him money.

I have been in that room. More than once.

And here is what I have learned: the gap between planned and actual mine production is not the problem. It is not knowing why the gap exists that kills you.

Most teams can tell you they missed plan. Almost none can tell you, within 20 minutes of shift end, exactly where the tonnes went missing and who owns the fix.

This guide walks you through a repeatable, shift-level process to compare planned versus actual production, identify root causes, and escalate before the next shift inherits someone else’s problem.

What You Need Before You Start

Do not skip this. I have watched teams jump straight into reconciliation with mismatched data sources and spend two hours chasing the wrong issue.

Before beginning, confirm that dispatch, GPS, weighbridge, planning, and maintenance data use the same shift boundaries, material classifications, and production definitions.

Everyone also needs to agree on what “production” means. Are you measuring tonnes mined, tonnes hauled to the ROM pad, or tonnes processed? If planning and dispatch use different definitions, the variance report is fiction.

Verification check: Open the dispatch system and planning software side by side. Can you see the same shift, pit, and material type in both?

If one system shows “Day Shift” while the other shows “Shift A” with a 30-minute offset, fix that first.

For operations struggling to connect these systems, see how mining systems integration helps align fleet, maintenance, and enterprise data.

Step 1: Lock the Reporting Scope

Open your mine planning software, whether that is MinePlan, Deswik, Vulcan, or another platform, and select the specific shift.

Then filter the data by pit, block, and material type.

This sounds basic. It is not.

The friction point I see repeatedly is that teams forget to separate ore and waste. They compare total tonnes moved against a plan built around ore targets.

The numbers look acceptable until someone checks grade and realizes that half the reported production was waste that was never part of the ore target.

Your reporting scope should clearly show:

Verification: The reporting scope must match exactly what the short-term planner used to build the shift schedule. Same boundaries, same material categories, and no ambiguity.

Step 2: Pull the Planned Production Data

Export the planned tonnes for the locked scope.

If the planning team still sends shift plans through PDF or email, get those figures into a structured format. A spreadsheet is the minimum. A connected database or planning system is better.

A simple script or API connection can pull planned tonnes by pit, block, and material type without relying on manual transcription.

The main issue to check is whether the plan reflects actual site constraints.

Planned tonnes may assume full fleet availability, no weather disruption, ideal blast fragmentation, and uninterrupted loading. If the plan assumes 100% availability while the fleet is running at 85%, you are comparing actual performance with a theoretical operating condition.

Confirm whether known equipment, workforce, access, and operating constraints were included before the shift began.

Your planned-production table should include:

The plan version also matters. Always preserve the original plan issued at the beginning of the shift. Do not overwrite it when changes are made later.

Step 3: Pull the Actual Production Data

Now retrieve actual production from the dispatch or fleet management system.

The actual dataset should use the same structure as the planned dataset:

One issue to watch is data latency.

GPS, dispatch, and weighbridge records may not synchronize immediately. If actual production is pulled five minutes after shift end, the last few truckloads may still be missing.

Allow an agreed reconciliation buffer or confirm that all final loads have reached the reporting system before calculating the variance.

Verification: The planned and actual datasets should contain matching reporting units. If the plan contains six blocks and the actual report contains four, something is missing.

Do not continue until the structures align.

For a broader explanation of why traditional fleet systems may not provide the full operational picture, see Mining Fleet Management Software vs Mine Operations Intelligence.

Step 4: Calculate Production Variance and Plan Attainment

Merge the planned and actual datasets by shift, pit, block, and material type.

Then calculate the absolute variance:

Production Variance = Actual Tonnes − Planned Tonnes

Next, calculate plan attainment:

Plan Attainment % = Actual Tonnes ÷ Planned Tonnes × 100

For example:

The goal is one variance report, not two people squinting at different screens.

Should the Plan Be Adjusted After a Delay?

This debate needs to be settled before reporting begins.

One approach is to normalize the plan. If a blast delay removes 90 minutes from a 12-hour shift, planned tonnes are adjusted to the actual operating time.

The other approach is to leave the original plan unchanged. This keeps the full production gap visible, including the impact of the delay and the operation’s response.

I lean toward keeping the original plan for shift-level reviews and using a normalized figure for longer-term reporting.

The shift team needs to see the full miss. Monthly reporting needs the context.

Pick one approach, document it, and apply it consistently.

Step 5: Identify the Root Cause

This is where most teams stop too early.

They see “missed plan by 3,800 tonnes” and move on.

That is not analysis. That is arithmetic.

For every material variance, investigate the operational cause.

Equipment Availability

Was the required fleet available during the shift?

Review unplanned failures, maintenance holds, and equipment release times. The cost of unplanned mining equipment downtime extends beyond repair hours because unavailable equipment can affect loading balance and production flow across the shift.

Haul Cycle Performance

Were loaded travel, queue, spotting, or return times longer than planned?

Use dispatch or GPS records to compare actual performance with the modeled haul truck cycle time.

Loading and Fragmentation

Did poor fragmentation reduce digging performance or increase the number of passes required to load each truck?

A rise in excavator cycle time can quickly reduce total tonnes moved.

Operator and Shift Performance

Did the same equipment produce different results under different operating crews?

Operator behavior, shift change delays, road conditions, and compliance with dispatch assignments can all affect production.

Plan Quality

Was the original shift plan realistic?

A missed target is not always an execution failure. The plan itself may have been based on incorrect availability, haul-distance, cycle-time, or dig-rate assumptions.

Verification: For every variance above the agreed threshold, the team should be able to name a specific cause, owner, and next action.

“We missed because of delays” does not count.

Real-time visibility helps teams investigate these causes faster. AIM by HonestDig connects production, fleet, and operational information so teams can see where performance begins moving away from plan.

Step 6: Escalate and Close the Loop

When plan attainment falls below the agreed threshold, take the variance report and root-cause findings into the daily planning meeting.

Do not only report the miss. Propose an action for the next shift.

That action may involve reallocating trucks, changing a loading unit, adjusting the material sequence, repairing a haul road, prioritizing maintenance, or revising the next shift’s target.

Automated alerts can also help. When an important equipment event occurs or plan attainment drops below the threshold, the relevant operations and planning teams should know before the post-shift review.

For complex open-pit mining operations, Guaranteed Production Throughput helps connect planned output with current fleet and operating conditions.

This turns shift reconciliation from a reporting exercise into an operating control process.

Common Reporting Errors to Check First

These errors should be resolved before assigning responsibility to operations or maintenance.

Frequently Asked Questions

Why do planned and actual tonnes differ even when the shift runs smoothly?

Data misalignment is often the cause. Planning and actual-production systems may use different units, shift boundaries, time zones, or material classifications.

Before treating the variance as an operational failure, confirm that both data sources use the same definitions.

How often should planned vs actual mine production be compared?

Every shift.

Weekly or monthly reporting can hide problems for too long. Shift-level comparison allows the operation to respond during the next 12 to 24 hours.

Teams using Predictive Site Resilience can identify deviations earlier and respond before they affect a full reporting period.

What plan attainment percentage should trigger escalation?

Many operations use 90%, but the right threshold depends on site variability, geology, fleet condition, and planning maturity.

The most important requirement is that the threshold is documented, understood, and connected to a defined response.

Can planned vs actual production be tracked in Excel?

Yes, particularly for a single-pit operation with limited material types and data sources.

A structured Excel model can compare exported planning and dispatch data. However, the approach becomes difficult to manage as the number of pits, fleets, materials, and shifts increases.

What causes mine production variance?

Common causes include equipment downtime, longer haul cycles, queueing, poor fragmentation, operator variability, weather, access constraints, material misclassification, and unrealistic planning assumptions.

The Real Question

The question is not whether you can compare planned and actual production at the shift level.

It is whether you can identify the cause quickly enough to change what happens next.

AIM by HonestDig brings planning, dispatch, fleet, and production information into one operational view so mine teams can find the variance, assign ownership, and act before the next shift begins.