Quick answer
Standards mapping does not need to start with another spreadsheet. beSirius can compare internal or published requirements, run them against the evidence in a Twin and show what is met, partially met or missing. Each result links back to its source. Your team reviews the proposed matches and the gaps that still need action. The same evidence can then be checked against another standard without collecting it again.
Who this is for: Mining and metals teams working with internal assurance, certification readiness, site assessments and several overlapping standards.
A site has already completed an internal assurance assessment. Its policies, monitoring records, audit findings and site evidence exist. Then another standard arrives.
The usual response is to open both frameworks, compare the requirements line by line, search for the same documents again and build another crosswalk in Excel.
That is the part that can now be automated.
The requirements still need to be interpreted correctly, and a reviewer still decides whether a proposed relationship and its evidence are good enough. But comparing clauses, retrieving existing evidence and showing what remains open does not need to start from zero every time.
Can mining standards mapping be automated?
Yes. Much of the repetitive work can be automated: comparing requirements, retrieving relevant evidence, linking the source behind each result and identifying where something is still missing.
The judgement is different. A person still needs to confirm the site and scope, review ambiguous matches and follow the rules of the standard owner for formal recognition, equivalency, certification or assurance.
What changes when the mapping is automated?
| Without automation | With beSirius |
|---|---|
| Open two standards and compare clauses one by one. | Map internal requirements to criteria in another standard and review the proposed relationships. |
| Search folders, audits and site reports for supporting material. | Insight checks the evidence already held in the Twin against the selected criteria. |
| Copy document names into a crosswalk and then reopen them during review. | Each result links to the source document and passage used in the assessment. |
| Work out manually what looks covered, partly covered or still open. | Requirements are returned as met, partially met or missing for review. |
| Repeat the evidence search when another framework arrives. | Reuse the same maintained evidence where it is relevant to the next standard. |
| Keep follow-up actions in a separate spreadsheet or email chain. | Assign unresolved requirements and corrective actions to the responsible team. |
What is standards mapping in mining?
Standards mapping is a structured comparison of requirements. The source can be a company's own assurance framework or a standard it already uses. The target is the framework it wants to assess against next.
A useful mapping records the clauses being compared, the reason for the proposed relationship and the evidence that may support the target requirement. It should also make uncertainty visible.
Similar wording is not enough. Two standards can both address water management, for example, while asking for different actions, records or outcomes. A group policy can be relevant across several sites without proving that every site implements it in the same way.
Mapping, equivalency and recognition are different
Mapping is the comparison work. Equivalency is a conclusion reached under a defined comparison methodology. Recognition is what a named standard or scheme formally accepts under its own rules.
The Copper Mark, for example, publishes a recognition process and an equivalency matrix that identifies recognised coverage and remaining verification work. An internal or automated mapping should not be treated as a substitute for that process.
See the Copper Mark's recognition and equivalence guidance.
How automated standards mapping works
The mechanics are straightforward. The difference is that the repetitive comparison and evidence search happen against one maintained evidence base rather than in a new spreadsheet for every framework.
Choose the site and the criteria
Set the entity, site or business unit in scope and select the internal requirements or published standard you want to assess against.
Compare the requirements
Map internal requirements to relevant external criteria and keep the clause references and framework versions with the result.
Check the evidence already held
Insight runs the Twin against the selected criteria and retrieves the source material that may support each requirement.
See what is met, partial or missing
Each requirement is returned with its source. The team can see what is supported, what is only partly supported and what still needs attention.
Review the result and assign the gaps
Review the proposed relationship and evidence, then assign unresolved requirements or corrective actions to the responsible team.
Example: IRMA and the Copper Mark RRA
A published benchmark from the Copper Mark and the Responsible Minerals Initiative shows why standards mapping is more than matching similar words.
The benchmark compares other standards against the Risk Readiness Assessment (RRA) 3.0, which underpins the Copper Mark's responsible production criteria. Its October 2024 results include the Standard for Responsible Mining v1.0 from the Initiative for Responsible Mining Assurance (IRMA), using Guidance v1.2 from June 2023.
| RRA criterion | Published result for IRMA |
|---|---|
| 28. Water Stewardship | Equivalent |
| 26. Climate Action | Partially Equivalent |
| 30. Circular Economy | Not Equivalent |
Source: Copper Mark / RMI VSS Equivalency Benchmark, selected IRMA results. These are published benchmark results, not a new beSirius equivalency assessment.
The benchmark considers the objective of a requirement, its level of prescriptiveness and the expected outcome. It is one-directional: it assesses IRMA against RRA and does not report where IRMA may exceed RRA.
That distinction matters for automation. A system can help compare the requirements and retrieve the site's evidence, but it should preserve the direction, versions and basis of the comparison rather than reduce everything to a similarity score.
What the published mapping does not answer
Even where two requirements are equivalent, the site still needs evidence. A relationship between standards does not tell you whether a specific operation has the right policy, record, monitoring result or closed corrective action for the period being assessed.
This is where standards mapping and evidence mapping meet: compare the requirements, then check the site's actual record against the target requirement.
How to map mining standards manually
If your team is still building the mapping by hand, the underlying process is the same. Keeping it explicit is useful because these are also the checks a reviewer should make when software proposes the result.
1. Define the site and assessment scope
Record the entity, location, activities and operating stage. Establish which requirements apply before comparing anything.
2. Lock the framework versions
Keep the edition, date and clause identifier for both source and target frameworks. State the direction of comparison.
3. Compare requirements individually
Use topic headings to organise the work, but compare the actions and outcomes required by each clause. Do not treat shared vocabulary as proof of coverage.
4. Link the evidence
Attach the relevant source and passage, not only the document title. Keep the site, reporting period and document owner with the result.
5. Separate evidence gaps from operational gaps
An evidence gap means the records do not yet demonstrate what is required. An operational gap means the activity, control or result itself is missing. They need different follow-up.
6. Review and maintain the mapping
Check the relationship, the evidence and the conclusion separately. Revisit the affected entries when a framework, site condition or source document changes.
Can existing audit evidence support another mining standard?
Often, yes. The useful question is not whether the document has been used before. It is whether the content is relevant to the new requirement, site and reporting period.
An earlier audit report can point to relevant controls, records, findings and unresolved actions. Before reusing it, check the underlying scope and date, whether the findings were closed and whether the target requirement asks for something more specific.
One water management plan, grievance record or risk assessment can be relevant to several standards. The evidence should stay in one maintained record while its relevance is assessed separately for each requirement.
For formal acceptance, follow the target scheme's rules. The Copper Mark's recognition tools, for example, identify both recognised coverage and additional information or assessment work that may still be required.
What beSirius automates in standards mapping
beSirius keeps the evidence separate from the format. The Twin holds the source material. Insight checks it against the requirement. The same evidence can then be reused where it is relevant to another standard, site assessment or customer request.
Which mining standards can be mapped in beSirius?
beSirius supports internal requirements and published standards and schemes used across metals and mining, including IRMA, Copper Mark, CMSI, TSM, ICMM, ResponsibleSteel, GISTM, ISO 14001 and ISO 45001, among others.
The same mechanic also works when the starting point is your own internal assurance framework: compare the internal requirement to external criteria, reuse the evidence already held and identify what the target framework still needs.
See the standards, schemes, ratings and templates covered by beSirius.
Frequently asked questions
What is standards mapping in mining?
Standards mapping compares individual requirements across two or more frameworks and records where they match, partly overlap or differ. A useful mapping also connects each proposed match to the evidence that may support it.
Can AI automate mining standards mapping?
AI can automate much of the repetitive work, including requirement comparison, evidence retrieval, source linking and gap identification. A reviewer still needs to check scope, ambiguous matches, evidence sufficiency and any formal recognition or certification decision.
What is cross-standard mapping?
Cross-standard mapping compares requirements in one framework with requirements in another so a team can see where existing controls and evidence may be reused and where additional work is still needed.
Can one audit document support several mining standards?
Yes, where its content is relevant to each requirement. Check its site, period, scope and sufficiency separately for every use.
Does automated standards mapping establish equivalency or certification?
No, automated mapping can support internal assurance and preparation, but it does not grant certification, confirm compliance or replace a standard owner's formal recognition or assurance process.
How do I map an internal assurance framework to an external mining standard?
Define the site and framework versions, compare each target requirement with the internal requirements, link the relevant evidence, record full and partial matches, identify gaps and review the conclusions before using them for an external assessment.
Do I need to repeat the mapping when a standard changes?
Review the requirements that changed and the mappings they affect. Keep the previous version and its decisions so the team can see what changed and which conclusions need to be reviewed again.
This article is general information. Formal equivalency, recognition, certification and assurance outcomes are determined under the rules of the relevant standard or scheme.
