FPIC as a Contract: Drafting Free, Prior and Informed Consent into Mining and Infrastructure Deals

Back to Insights

A principle in search of a paragraph

Free, Prior and Informed Consent — FPIC — is one of the most invoked principles in extractive industry governance. It appears in ILO Convention 169, the UN Declaration on the Rights of Indigenous Peoples, the African Commission's resolutions, IFC Performance Standard 7, and a growing number of national mining and land laws. It is cited in due diligence reports, lender covenants, ESG disclosures, and project finance term sheets across the continent.

What it rarely appears in, with any precision, is the actual contract.

In most mining concessions, infrastructure agreements, and host-country deals, FPIC is referenced in a recital or a representation, often in language so general that it commits the operator to almost nothing and gives the affected community almost nothing to enforce. The result is a strange asymmetry: a principle that everyone agrees is fundamental, but that almost no one drafts as if they meant it.

This piece is about closing that gap — treating FPIC not as a slogan but as a set of contractual obligations with triggers, procedures, and consequences.

What FPIC actually requires

Stripped of the human rights vocabulary, FPIC is four obligations bundled together:

• Free. Consent must be given without coercion, manipulation, or undue pressure — including the soft pressure of fait accompli, where consultation happens after permits are issued.
• Prior. Consent must be sought before significant project decisions are made, not after.
• Informed. The community must have access to meaningful information about the project's scope, impacts, and alternatives, in a language and format they can use.
• Consent. A genuine yes-or-no decision, not a consultation that proceeds regardless of the answer.

Each of these can be drafted. Each is also routinely under-drafted.

Where FPIC clauses go wrong

The most common drafting failures fall into four patterns.

Recital-only treatment. FPIC appears in the preamble — "the parties acknowledge the importance of free, prior and informed consent" — and nowhere else in the operative text. Recitals do interpretive work but rarely create enforceable obligations on their own.

Consultation dressed up as consent. The contract requires the operator to "consult with affected communities" or to "engage in good faith dialogue." These are softer obligations than consent. Consultation can be checked off; consent can be refused.

No definition of the consent-giver. The agreement names "the affected community" without identifying the legitimate decision-making body. In practice, this lets the operator choose its counterpart — usually the most cooperative one — which is precisely what FPIC is meant to prevent.

No consequences. Even where consent is required, the contract is often silent on what happens if consent is withheld, withdrawn, or never properly obtained. Without consequences, the obligation has no teeth.

What well-drafted FPIC looks like

A contractual FPIC framework has at least five components.

1. A definitions clause that does work. "Affected Community" and "Legitimate Representative Body" need to be defined with reference to identifiable institutions — customary authorities, elected community councils, or registered associations — and to a procedure for confirming representation when it is contested.

"Affected Community" means the population of [defined geographic area], represented for purposes of this Agreement by [named body], or, where representation is disputed, by a representative body confirmed through the consent verification procedure set out in Schedule [X].

2. A staged consent obligation. FPIC is not a one-time event. Different project phases — exploration, feasibility, construction, expansion, closure — trigger different consent decisions. The contract should identify the phases and the corresponding consent triggers, rather than treating consent as a single up-front milestone.

3. Information and time standards. "Informed" and "prior" are meaningful only if the contract specifies what information must be provided, in what languages and formats, and how much time the community has to deliberate before being asked for an answer. Thirty days is rarely enough for a community to evaluate a multi-decade project.

4. A real decision mechanism. The contract should specify how consent is given or refused — a community assembly with documented attendance and voting, a written resolution from the legitimate representative body, or another procedure agreed in advance. This is the part that is most often missing.

5. Consequences for absent or withdrawn consent. The contract should be explicit about what happens if consent is not given, is given conditionally, or is later withdrawn for material breach. Suspension of operations, renegotiation triggers, and dispute resolution pathways all belong here.

"If Consent is not obtained in accordance with Section [X] before the commencement of [Phase], the Operator shall not commence such Phase. If Consent is materially withdrawn during a Phase as a result of the Operator's breach of its obligations under this Agreement, the Operator shall suspend operations in the affected area until the matter is resolved through the procedure set out in Schedule [Y]."

Why this matters for both sides

For governments and regulators, contractual FPIC closes a recurring enforcement gap. National laws may reference consultation duties, but without contractual hooks, the state often has no clean way to suspend or sanction a project for failures further down the chain. Building FPIC into the concession or host-country agreement gives the state a cause of action it currently lacks.

For operators, well-drafted FPIC is risk management. The most expensive community disputes are not the ones where consent was refused — they are the ones where the operator believed it had consent and discovered, years into the project, that it did not. Clarity at the drafting stage is dramatically cheaper than clarity at the arbitration stage.

For communities, contractual FPIC turns a principle they are told they have into a procedure they can actually use.

A drafting culture worth shifting

The persistent under-drafting of FPIC is not really a drafting problem. It reflects an assumption — sometimes unspoken, sometimes explicit — that consent is a soft obligation, useful for compliance narratives but not meant to be tested. That assumption is increasingly out of step with where investors, lenders, and host governments are heading. Lender requirements are tightening. Litigation and arbitration around community consent are increasing. Reputational and political costs of getting it wrong are rising.

Treating FPIC as a contract — with definitions, triggers, procedures, and consequences — is no longer ahead of the curve. It is the curve.