Most project organisations do not have a documented project controls methodology. They have people who know how things are done, a folder of templates of uncertain parentage, and a quality manual nobody opens. The tier-1 mining houses are different. Over decades, and at costs running well into the millions, they built full project management frameworks: operational procedures governing how capital projects are planned, estimated, scheduled, controlled and closed out.
We spent the better part of two years synthesising that body of practice. The source library ran to more than 550 documents: tier-1 mining frameworks, a complete EPCM procedure suite, the full set of AACE Recommended Practices, and PMI practice standards and guides. The output is 124 operational SOPs across 15 project controls domains. The more valuable output is what the synthesis revealed: beneath different terminology and branding, the world-class frameworks agree on almost everything that matters.
Six patterns stand out.
1. They are procedures, not principles
AACE Recommended Practices tell you what good looks like. PMI standards give you the framework. Both are reference standards, and neither tells a controls engineer what to do on Monday morning. The tier-1 frameworks close that gap. Every procedure specifies purpose, scope, roles and responsibilities, step-by-step method, inputs, outputs and templates. The distance between a standard and a procedure is where most controls functions quietly fail, because knowing what good looks like is not the same as having a repeatable way to produce it.
2. They cover the whole lifecycle, not just the schedule
In our synthesised library, planning and scheduling accounts for 24 procedures out of 124. The rest cover cost control, estimating, earned value, risk, construction management, procurement and contracts, document control, engineering management, site management, operational readiness, and portfolio governance. That proportion is faithful to the source frameworks. Mature organisations treat controls as an integrated system, and they write down the interfaces: how the estimate hands over to the budget, how the schedule feeds progress measurement, how change control binds cost and schedule together. Controls failures concentrate at interfaces. The frameworks know it, and they procedure the handoffs, not just the functions.
3. They classify before they estimate or schedule
Every world-class framework enforces classification systems tied to stage gates: estimate classes with declared accuracy ranges and schedule classes with declared maturity, each mapped to what the project phase can support. The discipline this buys is honesty. A study-phase number carries its accuracy range with it, and nobody downstream can mistake a Class 4 estimate for a control budget. Where classification is absent, precision gets confused with accuracy, and sanctioned budgets inherit study-phase guesswork.
4. They separate progress measurement from progress reporting
The frameworks define how progress will be measured before the project starts: physical measurement rules by commodity, earned value data validation, and independent verification. The party reporting progress is never the sole party measuring it. This is the single most protective rule in the entire body of practice, because self-reported progress fails in one direction only.
5. They put teeth in stage gates
Stage-gate procedures in tier-1 frameworks are not calendar events. Each gate specifies the deliverables required, the maturity each must reach, and who is accountable for the assurance review that tests them, with benchmarking against comparable projects as part of the evidence. A gate that cannot say no is a milestone. The frameworks build gates that can say no.
6. They are maintained
Finally, the frameworks live. They carry version control, ownership and review cycles, and they absorb lessons learned as revisions to procedures rather than entries in a register nobody reads. A framework last touched five years ago is an archive. The organisations that get value from methodology treat it as an operational asset with a maintenance budget.
The gap for everyone else
Mid-tier miners, EPCM contractors and owner's teams face an awkward set of options. Commissioning an equivalent methodology at market consulting rates costs between R1.86 million and R4.96 million for a comparable scope, and takes months. Relying on individual experience is faster and free, and it walks out the door with the individual. The result is that most of the industry runs capital projects on institutional memory, while the frameworks that would prevent the recurring failures sit locked inside the organisations that built them.
That is the gap our SOP library exists to close: the synthesised practice of tier-1 mining frameworks, aligned procedure by procedure to the applicable AACE Recommended Practices and PMI standards, in a form a controls team can deploy directly. Not a summary of textbooks. A distillation of how the organisations that deliver the largest capital projects actually run controls.
The ScheduleIQ SOP Library packages all 124 procedures across the 15 domains, with 12 SOPs available free to evaluate. Visit the ScheduleIQ product page or contact us to discuss deployment in your organisation.