PERC technical reporting in practice: what good vs weak disclosure looks like on mineral projects

If a mineral project report is difficult to follow, confidence drops quickly. That problem is not always caused by weak geology, weak engineering or weak economics. In many cases, the real issue is weaker disclosure.

That gap matters. If assumptions are unclear, if Modifying Factors are only partly carried through, if risk language stays generic, or if the sections do not line up from resource to mine plan to economics, the report becomes harder to trust. That can slow financing, complicate due diligence and weaken the technical case behind the project.

PERC technical reporting in practice: good vs weak disclosure

This is why PERC technical reporting deserves more practical attention. The real difference is not between knowing the standard exists and ignoring it. The real difference is between disclosure that helps a reader understand the project and disclosure that leaves too much to guess.

Why this matters when your project is under review

Once a project moves toward a board decision, financing process, public release, strategic review or regulator submission, the report stops being just an internal technical document. It becomes part of how other people judge credibility.

At that stage, one question matters more than most: can a technically literate reader follow the logic of the project without filling in the gaps alone?

That is where disclosure quality becomes practical rather than theoretical. For the broader study-stage context, see our step-by-step guide to mining feasibility studies.

What PERC means in practice

PERC is not a shortcut that rescues weak technical work. It is a reporting framework that helps structure how Exploration Results, Mineral Resources and Mineral Reserves are presented so that a reader can understand what is known, what is assumed and what remains uncertain.

In practice, strong PERC-aligned disclosure does four things well:

it makes the technical basis visible;
it explains the assumptions that really drive the project case;
it shows where judgment has been applied;
and it avoids making the project sound more certain than it really is.

Where weak disclosure usually appears

Weak disclosure is rarely one dramatic mistake. More often, it appears in the spaces between disciplines.

Resource assumptions are not clearly connected to the mine plan.
Reserve language sounds stronger than the supporting work behind it.
Processing, recovery, dilution or cost assumptions appear in one section but do not carry through consistently into economics.
Risk sections read like generic boilerplate rather than project-specific analysis.
Historical information is referenced without making its limits clear.
The report is technically correct in fragments, but not coherent as a whole.

If you also work under Canadian disclosure rules, compare this with our article on Top 5 disclosure deficiencies of NI 43-101 technical report. The reporting frameworks differ, but the practical weaknesses often look very similar.

Why Table 1 matters more than many teams think

Table 1 is easy to treat as a compliance appendix. In practice, it is much more useful than that.

Done properly, it forces the team to show whether the key reporting criteria have really been considered. It also forces the more useful question: if something is missing, why is it missing?

That is one reason stronger disclosure tends to feel more balanced. It does not only present what supports the project. It also makes limitations, assumptions and gaps easier to see.

Modifying Factors, study maturity and real project execution

This is one of the most important areas for a mining audience because it is where disclosure starts affecting real project execution.

A report becomes weak when it uses the language of confidence without carrying the supporting logic far enough. That often happens when Modifying Factors are named but not assessed deeply enough, when the reporting language sounds more mature than the project really is, or when the step from resource to reserve feels assumed rather than justified.

This is not just a writing issue. It usually points back to integration. If geology, mine planning, metallurgy, infrastructure, ESG and economics are not aligned, the disclosure will show it sooner or later.

If your project is moving toward a more advanced study stage, our Pre-Feasibility & Feasibility Studies (PFS/FS) page is the most natural companion service page for this topic.

Risk, uncertainty and review readiness

A report does not become stronger because it sounds more certain.

In practice, stronger disclosure handles uncertainty directly. It explains where confidence is lower, where outcomes are more sensitive, and which assumptions could materially change the project case. That includes technical uncertainty, but also permitting, infrastructure, ESG, social context and execution risk.

Weak reports often do the opposite. They compress risk into short generic paragraphs that do not help the reader understand consequence, likelihood or business impact.

That weakens the whole report because risk is not separate from value. It is part of how the project should be understood.

A practical checklist before release

Can a reader follow the logic from geology to mine plan to economics without filling in major gaps?
Are the assumptions that really drive the project case clearly stated and explained?
Does the reporting language match the actual maturity of the project?
Are Modifying Factors and uncertainty handled in a way that fits the stage of work?
Does the risk section say something useful, specific and decision-relevant?
Would an external reviewer see the report as coherent, balanced and defensible?

Conclusion: strong disclosure helps projects move forward

Good technical disclosure is not about making a project look better. It is about making the project easier to understand, easier to challenge and easier to trust.

That matters because mineral projects are judged not only on tonnes, grade, recovery, schedule or economics. They are judged on whether the technical story holds together under scrutiny.

Under PERC, strong disclosure usually looks calm, clear and well-supported. Weak disclosure usually leaves friction behind it: more follow-up questions, more caution in due diligence and more work to rebuild confidence later.

Need a stronger technical report or an independent review?

If your project is moving toward public disclosure, financing, due diligence or regulator review, the technical story needs to be clear, consistent and defensible.