The Cooperation Table Blueprint -- Juan Diego Villacis

Who this is for

You are a program manager at an INGO trying to coordinate multiple actors in a territory. Or a government official who inherited a province full of NGOs doing overlapping work. Or a DFI program officer wondering why your grantees in the same region never talk to each other. Or a consultant hired to "build a coordination mechanism" with no template for what that actually means.

You need a multi-stakeholder platform that produces coordinated execution, not just meetings. This guide gives you the architecture, the sequence, and the operational details.

The model in brief

A Cooperation Table brings 22-23 organizations from 5 sectors into a single governance structure. Participants sign a constitutive agreement committing to a shared Hoja de Ruta (roadmap) with quarterly targets, organized into thematic sub-tables. Accountability comes from automated notifications, a public dashboard, and an escalation protocol. The platform is institutionalized through legal instruments so it survives political transitions and funding cycles.

The six phases

Phase 1

Political Foundation

The platform lives or dies based on who convenes it. Your first move is not stakeholder mapping. It is a political calculation: who has the convening authority to put 22 organizations in a room and keep them coming back?

You need a formal mandate before you convene anyone. A written directive, an official letter, or an executive resolution authorizing the creation of the platform.

In Morona Santiago, this came as a prefectoral commitment that later became a formal decree. In Orellana and Sucumbios, the mandate came through Conservation International's programmatic authority, backed by co-convening letters from provincial governments.

Do not skip this step. A Cooperation Table convened informally ("let's all get together and coordinate") will collapse by month 4.

Every successful table had one senior official who personally drove the process. Not the institution. A specific person with enough authority to clear bureaucratic obstacles, enough credibility to bring indigenous authorities to the table, and enough political interest to sustain effort over 8-12 months.

If no one at the senior level cares enough to stake personal reputation on this platform, you are not ready to build it.

Phase 2

Stakeholder Identification & Convening

Every Cooperation Table draws from the same 5 stakeholder categories. Each provides a different type of legitimacy the platform needs.

Sector	What they bring	Typical count
Public Sector	Administrative authority, budget allocation, regulatory power	5-6 orgs
Indigenous Authorities	Territorial sovereignty, FPIC rights, historical legitimacy	3-5 orgs
Civil Society / NGOs	Technical capacity, donor relationships, implementation experience	6-8 orgs
Academia	Data, research capacity, monitoring expertise	2-3 orgs
Private Sector	Economic activity, supply chain influence	3-4 orgs

Do not send a mass invitation for the first meeting. Convene in sequence:

Government first. Secure their co-ownership before anyone else is in the room.
Indigenous authorities second. Meet on their terms, in their territory if possible. Frame the platform as an extension of their governance, not a competing structure.
Major NGOs third. They have the implementation capacity and donor relationships. Get their buy-in on the roadmap concept before the first plenary.
Academia and private sector last. They fill critical roles but rarely drive the process.

The first plenary session should feel like a formalization of agreements already reached, not a cold start.

The right number

22-23 organizations. Below 18, the platform lacks sectoral coverage for territorial legitimacy. Above 28, decision-making slows and meetings become performative. All three tables landed in this range once the relevance filter was applied.

Phase 3

The Constitutive Agreement

Not an MoU. Not a letter of intent. A formal agreement signed by the authorized representative of every member organization, establishing purpose, structure, governance rules, and commitments.

Name & Scope

Official platform name and territory covered

Objective

One paragraph. What coordination problem this solves.

Member List

Every organization + authorized signatory name and title

Governance Structure

Plenaries, sub-tables, coordination core. Voting protocols.

Hoja de Ruta Commitment

Explicit agreement to participate in building and executing the roadmap

Meeting Schedule

Frequency and format of plenaries, sub-tables, coordination meetings

Duration

Aligned with roadmap time horizon (2-3 years)

Modification Clause

How new members join. How the agreement is amended.

The person who signs must have institutional authority to commit their organization. The prefect or vice-prefect (not the planning director). The federation president (not a technical officer). The NGO country director (not a project coordinator). Getting the right signatory level is half the political work.

A signed constitutive agreement creates three forms of accountability:

Legal: The document can be referenced in administrative and institutional processes.
Social: No signatory wants to be publicly identified as the organization that defected from a 22-organization commitment.
Operational: It provides the basis for tracking execution against the roadmap.

In Morona Santiago, 22 organizations signed. That collective signature produced the first 7 Conservation Agreements (June 27, 2025), delivering solar internet, energy kits, and water purification to Shuar and Achuar communities. The constitutive agreement made those agreements possible.

Phase 4

Building the Hoja de Ruta

The roadmap translates the platform's purpose into specific, time-bound, organization-assigned activities. Without it, the Cooperation Table is a meeting. With it, the Cooperation Table is a governance mechanism.

Description Specific and measurable. "Establish 3 community monitoring stations in the buffer zone of Yasuni by Q2 2027." Not "promote environmental monitoring."
Responsible org(s) Named. Not "the platform" or "to be determined."
Sub-table Which thematic group owns this activity.
Timeline Quarterly milestones within the 2-3 year horizon.
Status Pending / In Progress / Completed / Delayed.
Dependencies What must happen before this activity can start.

How many activities

Orellana: 79. Sucumbios: 93. A roadmap with fewer than 40 is probably too vague. More than 120 is listing tasks, not strategic activities.

Do not build the roadmap in a plenary. Build it in sub-table working sessions where 6-10 organizations with relevant expertise propose, debate, and assign activities. Then bring the compiled roadmap to a plenary for validation and formal adoption.

The building process takes 2-3 months of sub-table sessions. Do not rush it. A roadmap that organizations helped build is a roadmap they will execute. A roadmap handed to them by a consultant is a document they will ignore.

Phase 5

Accountability Infrastructure

22 organizations committed to 79-93 activities over 3 years. Without tracking infrastructure, you will discover non-compliance at the annual review. By then, it is too late.

1. The Progress Dashboard

A visual tracking system showing the status of every activity by province, sub-table, and quarter. Every stakeholder sees at a glance which activities are on track and which are delayed. Public visibility is the strongest compliance mechanism in multi-stakeholder platforms.

2. The Notification Engine

Automated email reminders sent to the responsible organization as deadlines approach. Reminder at 30 days. Second reminder at 7 days. Escalation notice when the deadline passes. This replaces manual follow-up that burns out coordination staff and creates political friction.

3. The Escalation Protocol

Automated notification to the responsible organization
Flagging in the dashboard (visible to all)
Discussion in the next sub-table session
Escalation to the coordination core
Formal communication and reporting in the plenary

No penalties need to be punitive. Social accountability among 22 peer organizations is powerful enough. The goal is to make non-compliance visible, not to punish it.

Phase 6

Institutionalization

Every multi-stakeholder platform that dies is killed by the same thing: the project ended, the administration changed, or the champion moved on. If the platform has no institutional life independent of its founding conditions, it will not survive.

Institutionalized through a prefectoral decree: a formal legal instrument establishing the platform as a permanent function of the provincial government. This means:

The platform is part of the government's organizational structure, not a project component
Budget allocation for coordination can be included in the annual budget
A new prefect cannot dissolve the platform without issuing a new decree
The platform has legal identity for interinstitutional agreements

The equivalent in other countries: gubernatorial executive order, provincial ordinance, or regional assembly resolution.

Institutionalization Checklist

0 / 6

Constitutive agreement signed by all member organizations

Roadmap formally adopted as a shared execution instrument

Platform referenced in at least one government planning document

Coordination function assigned to a permanent institution (not the project team)

Legal instrument (decree, ordinance, resolution) establishing the platform as permanent

Multi-funder or co-financing structure to avoid single-donor dependency

Timing

Do not wait until the project's final year. In Morona Santiago, the decree was pursued from the first year. Start the legal and political groundwork in Phase 1 and maintain it in parallel with Phases 2-5.

What will go wrong

I have built three of these. Every one hit problems. Here is what to expect.

The government will try to control the agenda.

Provincial governments often see the table as "their" platform. They push to chair every meeting, filter communications, sideline challengers.

Counter: Establish co-governance from the constitutive agreement. Rotating facilitation. Minutes distributed by the secretariat, not the government.

Indigenous authorities will be skeptical.

They have been invited to hundreds of "coordination" meetings that produced nothing. They will resist being positioned as "one of five sectors" when they hold territorial sovereignty.

Counter: Meet with indigenous leadership separately before the first plenary. Acknowledge their governance structures (life plans, consultative assemblies) as co-equal inputs, not subordinate to the platform.

NGOs will protect their turf.

Organizations with donor-funded projects will resist if they see the table as a threat to their autonomy or donor relationships.

Counter: Frame the table as a visibility mechanism, not a control mechanism. Coordination through the roadmap increases their reporting value to donors.

Activity status will go stale.

Even with automated notifications, some organizations will not update for months.

Counter: Monthly updates are a fixed responsibility of the technical coordinator. Use sub-table sessions to validate status in person.

Political transitions will test everything.

Elections happen. Prefects change. New officials arrive with no institutional memory.

Counter: This is why the decree matters. When the new official arrives, 21 other organizations are still committed. The social cost of abandoning the platform is higher than continuing it.

Attendance will drop after month 6.

The first 2-3 meetings are well-attended because they are novel. By month 6, only committed organizations show up.

Counter: Sub-tables with focused agendas maintain engagement better than plenaries with generic updates. Only call plenaries when there are real decisions to make.