Example mine record
A fictional illustration of the records to keep under a MUCC code.
Draft for ASMRAF review · Version 0.2 · 14 October 2026
Prepared for the South African launch. This document sets out proposed rules; it does not confirm that staff, services or legal arrangements have been put in place.
1. Fictional example only
This record is entirely fictional. It is not an anonymised real case, certificate, mine approval or payment confirmation. Reference: EXAMPLE-MINE-001. Mine: Example Mine. Launch country: South Africa. Status: Provisional. No real MUCC is issued by this document.
2. Applicant and permissions
Applicant identity: held in the restricted application file, not shown here. Authority to represent the mine: evidence needed. Right to carry out the intended mining activity: evidence needed. Exact location: restricted. Scope of minerals and activities: to be established through the assessment.
3. Evidence and findings
Licence validation: not completed. Site visit: not completed. Labour and safety review: not completed. Assay and chain-of-custody records: none received. Corrective actions: to be determined after assessment. Do not populate these fields with an example that looks like a completed check.
4. Decision and transaction links
Verification decision: not made. Decision-maker and evidence reference: none. Sale and lot references: none. Buyer agreement: none. Payment instruction: none. Recipient payment confirmation: none. Each event needs its own evidence and timestamp before the status changes.
5. Minimum audit fields
For a real case record the event type, mine and transaction references, record version, actor, source, time, finding and reason for any change. Keep private evidence references separate from public descriptions. Reopening a file must show what was actually saved, who saved it and whether a decision is still outstanding.
Before this document is adopted
Use only as a training illustration. Replace example values with evidence in an authorised case workflow, never in the public website.
Proposed accountable role: ASMRAF verification team. Named appointments and an adoption date must be recorded before operation.