Dated evidence for the markets discussed
World Bank WDI source update and observation years are retained below. Checked 2026-11-22. The method that follows does not infer project demand from these national observations or report unperformed fieldwork.
| Country | Population | GDP (current USD) | Real GDP growth (annual %) | CPI inflation (annual %) |
|---|---|---|---|---|
| Chile | 19,859,921 (2025) | 357,371,159,574.86 (2025) | 2.46 (2025) | 4.21 (2025) |
| Peru | 34,576,665 (2025) | 334,854,659,181.89 (2025) | 3.43 (2025) | 1.53 (2025) |
Scope and analytical object
The analytical object is a proposed mining or mining-adjacent project in Chile or Peru, viewed as a chain of dependencies rather than a single asset. The review should identify whether the investment is exposed to mineral production, toll processing, logistics, equipment supply, water delivery, power availability, construction completion, or a service contract with defined performance obligations.
The scope excludes certification of reserves, reserve classification, engineering compliance, environmental approval, legal sufficiency or financing approval. Those matters may inform the analysis, but they remain external inputs that must be supplied by qualified specialists. The workpaper only tests whether the provided evidence is enough to support a coherent financial and operating view.
The core scope question is simple: what exactly generates cash flow, what exact conditions must occur before cash flow begins, and which of those conditions are already evidenced by records rather than asserted in narrative form.
- Mineral resource exposure: revenue depends on extraction or processing of ore.
- Operator exposure: revenue depends on availability, output, recovery or operating performance.
- Supplier exposure: revenue depends on delivered goods, services, mobilization or milestones.
- Infrastructure exposure: revenue depends on connection, commissioning, utilization or throughput.
- Offtake exposure: revenue depends on buyer acceptance, quality, volume and settlement terms.
Evidence base and record inventory
The review should begin with a record inventory. For Chile and Peru, the analyst should request the project company’s corporate documents, site map, title or concession summary supplied by counsel, permit register, technical report, offtake or customer contract, supplier agreements, utility correspondence, logistics plan, capex schedule, opex schedule, debt or lease documents, and historical operating data if the project is existing.
For a mine or plant, the minimum operating evidence set should include the process flow description, expected throughput logic, recovery assumptions, water balance, power demand, access route description, maintenance plan, staffing plan, procurement list and commissioning schedule. Where the project is early stage, the same categories still apply, but the evidence may be only preliminary and should be labeled accordingly.
For revenue analysis, obtain the actual contract or sale basis, not a summary slide. The analyst needs to know whether cash flow is linked to tonnage, production, availability, take-or-pay usage, lump-sum milestone completion, tariffed services or pass-through reimbursement. The classification determines which stress cases are relevant and which are not.
For Chilean projects, separate local currency operating costs, indexed obligations and dollar-linked receipts or capital items. For Peruvian projects, separate local currency costs and receipts from foreign-currency sales, imported equipment and foreign debt. In both cases, the analysis should retain the original currency and indexation mechanics instead of collapsing them into a single blended assumption.
- Corporate and ownership records.
- Technical reports and process descriptions.
- Permits, applications and conditions pending.
- Offtake, customer and supplier contracts.
- Utility, water and transport correspondence.
- Project budgets, invoices and lender materials.
- Historical production, availability or shipment logs, if any.
Reproducible step-by-step method
Step one is to define the cash-generating unit. Name the asset, the legal entity, the operating counterparty and the revenue mechanism. If the project is a supplier, the unit is the contract package, not the broader mining market. If it is a processor, the unit is throughput and recovery, not the underlying resource itself.
Step two is to build a dependency register. List each dependency with four fields: dependency owner, documentary evidence, failure consequence and replacement path. Typical rows include water source, power connection, road or port access, construction permits, operational permits, environmental conditions, community arrangements, spare parts, reagent supply and buyer acceptance.
Step three is to reconcile the technical path. Compare the process design with the equipment list, capacity assumptions, water and power needs, site layout and logistics path. Every major input should trace to a document, an estimate or a licensed specialist memorandum. Anything that cannot be traced should be marked as unsupported rather than inferred.
Step four is to reconcile the financial path. Match each revenue stream to a contract, pricing basis or observed operating pattern. Match each cost line to a quotation, tariff, wage schedule, utility record or historical invoice. Match each capital item to a purchase order, vendor quote or project budget. The objective is internal consistency, not optimistic completeness.
Step five is to run condition-based scenarios. A base case requires documented dependencies only. A downside case should remove one critical dependency at a time and ask whether the project still operates, delays, downscales or fails. A severe case should combine the most plausible dependency interruptions, but only if each interruption is grounded in the evidence record.
Step six is to produce an issue log. Each issue should state what is missing, why it matters, what document would resolve it and whether the missing item changes the conclusion or only the confidence level.
- Define cash-generating unit.
- Build dependency register.
- Trace technical assumptions to records.
- Reconcile financial model to source documents.
- Test condition-based scenarios.
- Log unresolved issues and decision impact.
Verification and triangulation
The analysis should not rely on one record family alone. Technical claims should be checked against contracts, invoices, site correspondence or utility letters. Contract claims should be checked against model logic and counterparties’ documented obligations. Budget claims should be checked against supplier quotes, historical spend or lender materials where available.
If two records disagree, the analyst should privilege the more specific record unless there is evidence it is outdated. For example, a generic investor presentation should not override a current contract or a later project schedule. A process memorandum should not override a utility letter if the letter addresses actual connection status. Conversely, a draft permit list should not be treated as equivalent to a granted permit.
Triangulation should also test language precision. Terms such as reserved, permitted, connected, commissioned, contracted, secured and available are not interchangeable. The workpaper should confirm which term is used in each source and whether the source actually supports that term.
A finding is stronger when at least two independent record families point to the same conclusion, and weaker when the conclusion depends on a single management assertion without corroboration.
- Technical report versus equipment list.
- Contract language versus cash flow model.
- Utility correspondence versus operating schedule.
- Permit register versus site execution plan.
- Historical logs versus management projections.
Downside analysis and stress logic
Downside analysis should focus on failure points in the dependency chain. The first question is not whether the project is profitable under a broad market shock, but whether it can function if one or more required inputs are delayed, unavailable or more expensive than documented.
The most relevant downside dimensions are price, volume, recovery, timing, logistics, utilities, permits, community stability and counterparty performance. Price stress is appropriate only where the project is actually exposed to market pricing. A fixed-fee supplier with pass-through costs does not face the same stress profile as a producer selling commodity output.
Volume stress should reflect whether output is constrained by geology, plant reliability, feedstock, permitting, transport or demand. Recovery stress should be used only where there is a qualified technical basis for recovery assumptions. Where such evidence is absent, recovery should be treated as unverified rather than stressed numerically.
Timing stress should address commissioning, ramp-up, permit commencement and contract start dates. If the project depends on a sequence of approvals or works, each predecessor should be tested for delay and the downstream effect should be mapped explicitly.
The downside conclusion should separate temporary delay from structural failure. A project that survives only after an unproven rescue assumption should not be treated as robust.
- Market price risk, only if revenue is market-linked.
- Output or throughput risk, only if the asset controls volume.
- Recovery risk, only if qualified technical evidence exists.
- Delay risk from permits, construction or connection.
- Counterparty risk for offtake, supply or service contracts.
Investigation stop conditions
The investigation should stop when additional work would not materially improve the decision because the remaining uncertainty is either outside the scope or not removable with ordinary record requests. Examples include matters reserved to licensed engineering, legal due diligence or public authority review.
The work should also stop if the project’s central cash flow mechanism cannot be identified from the records. If the analyst cannot determine whether the project sells ore, concentrates, services, access, capacity or milestone completion, the model is not decision-grade.
Another stop condition arises when essential dependencies remain undocumented after reasonable follow-up. If water, power, access, permits or offtake cannot be evidenced, the conclusion should remain conditional and the issue log should state that the conclusion cannot be upgraded without those records.
The investigation does not continue simply to force a positive answer. The objective is to determine whether the file supports a coherent risk view, not to manufacture comfort through extra assumptions.
- Unknown cash flow mechanism.
- Unresolved core dependency.
- Missing primary contract or permit record.
- Need for licensed professional judgment beyond scope.
- Evidence gap that cannot be cured by ordinary document request.
Limitations and interpretation discipline
This method is analytical and documentary. It does not certify ore reserves, engineering design, legal compliance, environmental performance or community acceptance. It also does not substitute for site inspection, laboratory testing or specialist sign-off where those are needed.
The method is sensitive to the quality of supplied records. If documents are incomplete, outdated, internally inconsistent or translated informally, the conclusion should be downgraded. A clean model cannot repair weak source evidence.
The analysis should avoid country generalization. Chilean and Peruvian projects can differ materially by region, infrastructure corridor, water regime, local counterparties and permit path. National statistics may help frame the market, but they do not establish project feasibility on their own.
The method also avoids assuming that a national pipeline, sector trend or export outlook implies a project award, supply order or operating success. Project evidence must stand on its own records.
- No reserve certification.
- No legal or regulatory approval conclusion.
- No engineering approval.
- No site substitute for documentary evidence.
- No extrapolation from national averages to a specific site.
Decision workpaper and conclusion template
The decision workpaper should end with a short, testable statement. First, identify the project type and revenue mechanism. Second, list the critical dependencies and whether each is evidenced, partially evidenced or unsupported. Third, state whether the operating chain is coherent enough to model as a conditional project or whether material gaps prevent a decision-grade view.
A supportable conclusion has three parts: the records reviewed, the inconsistencies resolved and the residual issues that do not change the overall view. An unsupported conclusion has the same structure, but it ends with the unresolved issues that do change the view and therefore block upgrade of the conclusion.
The final question is what finding would change the conclusion. The answer should be explicit. For example, a current offtake contract with clear volume and pricing terms, a verified utility connection, or a granted permit may move an issue from unresolved to evidenced. Conversely, discovery that the project lacks a legal right to use the intended water source, that the main contract is nonbinding, or that the financial model relies on a revenue stream different from the actual contract would change the conclusion in a negative direction.
The workpaper should therefore close with a conditional verdict, not a promise: if the records support the dependency chain, the project may be analyzed further on that basis; if they do not, the appropriate finding is that the file remains incomplete for investment-risk purposes.
- Project type and revenue mechanism.
- Dependency status by item.
- Resolved inconsistencies.
- Residual gaps and decision impact.
- Specific evidence that would change the conclusion.
Scope, provenance and professional limitations
Wert-Berater Financial provides independent analytical decision support. We do not provide or arrange financing, broker securities, solicit investments or guarantee returns. Every engagement is subject to scope, data availability, geographic coverage, professional qualifications, applicable local law, regulatory restrictions, sanctions, counterparty and payment-risk review. Market coverage does not imply a local office, licence, professional designation or partnership. Local legal, tax, engineering and regulated professional conclusions require appropriately qualified advisers.
