A monthly mine plan can appear balanced while its supporting calendars disagree. Payroll, maintenance, shipping, rainfall and customer settlement operate on different rhythms. The useful planning question is where those rhythms create an avoidable collision.
The hidden overlap
Consider an illustrative maintenance shutdown that falls in the same week as a major concentrate dispatch. The shutdown itself may be sensible, yet loading, laboratory support and stock access may also be disrupted. A consolidated calendar exposes these shared dependencies without replacing the detailed plans owned by each department.
Who can change a date
A calendar becomes useful when changes have an owner. Moving a vessel booking should trigger a review of storage and cash requirements; advancing maintenance should notify procurement and the laboratory. Otherwise teams continue to optimise their own dates while the business absorbs the combined consequences in overtime or delayed receipts.
Preserve realistic buffers
Not every activity needs a generous contingency. The stronger approach is to identify events that cannot easily be recovered, such as a scarce specialist visit or a fixed transport window. Buffer those interfaces deliberately. Excessive slack elsewhere can hide weak preparation and tie up materials that could serve another operating priority.
Review the missed connections
After a difficult month, investigate the intersections rather than merely ranking departmental performance. Which changed date failed to reach the next team? Which dependency was absent from the plan? For an owner, this creates a practical improvement record. The calendar becomes an operating agreement that can explain why a seemingly small change affected the wider enterprise.
