The Liaison Is Not a Mailbox: Seven Contract Questions for U.S. Partners Naming a Malagasy Point Person

In many U.S.–Madagascar partnerships, the local liaison begins as a convenience. A trusted translator, a cooperative member, a regional coordinator, or a respected community figure agrees to be the point person. The role is rarely written down in detail because everyone assumes the expectations are obvious. They usually are not. The liaison may hold information, shape access, interpret community sentiment, and influence how funds and decisions are perceived. That makes the role too important to leave to informal understanding.

For U.S. partners, the task is not to inflate the liaison into a formal officer if the partnership does not need one. It is to decide what the role actually is and to write the terms accordingly. The following seven questions can be used in proposal design, grantee due diligence, or contract negotiation.

1. What authority does the liaison actually hold?

A liaison may convene meetings, relay information, coordinate logistics, represent a community organization, or approve activities. Those are different roles with different risks. The agreement should state whether the liaison can speak for the community, request data, make purchases, sign documents, approve budget changes, or commit the partnership to any action. If the liaison is a connector rather than a decision-maker, say so. If the role carries delegated authority, identify the limits and the person or body that retains final approval. U.S. partners should also confirm that the community or grantee organization has authorized the liaison to act in that capacity.

2. How will the liaison be compensated, and by whom?

Unpaid liaison work is a common weak point. It can exclude people who cannot afford to volunteer, create hidden dependence, or concentrate influence among those with independent means. The terms should specify whether the role is salaried, stipended, or reimbursed for expenses; who pays; how often; in what currency; and through what banking or mobile-money channel. If the liaison is paid by the U.S. partner but accountable to a community organization, the agreement should explain how that dual relationship is managed. Compensation should not be tied to outcomes in ways that reward pressure on community members or discourage honest reporting.

3. What language access will the role provide—and require?

The liaison should not become the sole linguistic gatekeeper for the partnership. Terms should identify which documents, meetings, and decisions require translation or interpretation, into which languages, and at whose cost. If the liaison interprets during community meetings, the agreement should set expectations for accuracy, confidentiality, and consent. Where possible, budget for independent interpretation at key moments so that community members are not dependent on one person to be heard. Language access is part of benefit-sharing: it determines who can participate meaningfully.

4. What conflicts of interest must be disclosed—and how often?

A liaison may be a cooperative member, a local official, a supplier, a family member of a grantee, or a participant in another initiative. Those relationships are not automatically disqualifying, but they should be known. The agreement should require written disclosure at selection, at least annually, and whenever circumstances change. It should also identify when the liaison must recuse from a decision and who receives the disclosure. U.S. partners should keep a simple conflict-of-interest register and treat it as a governance document, not a personal accusation.

5. What reporting duties are reasonable?

The liaison should know what information is expected, in what format, on what schedule, and for what purpose. Reporting duties might include meeting notes, community feedback summaries, activity updates, or coordination logs. They should not turn the liaison into an informal surveillance agent. Reports should flow to the appropriate partnership committee, and community members should have a channel to review or supplement them where feasible. Reporting time should be recognized in compensation and workload. A short, clear template is usually better than an open-ended request for updates.

6. To whom is the liaison accountable?

Dual accountability is common and should be explicit. A liaison may report operationally to a Malagasy grantee or community organization while coordinating with a U.S. partner. The terms should clarify the reporting line, the escalation path, and how disagreements are resolved. Community accountability matters as well. The agreement should identify how community members can raise concerns about the liaison's conduct, how those concerns are reviewed, and how the liaison responds. A grievance channel that runs only through the liaison is not a grievance channel.

7. How will the role be reviewed, renewed, or ended?

The liaison role should have a term, a review process, and an exit path. Terms can address performance review, community input, renewal, records handover, contact lists, and replacement. If the role ends, the partnership should be able to continue without losing institutional memory or leaving community contacts stranded. A clear exit clause protects the liaison as well as the partnership.

The clause protects the relationship

A well-drafted liaison clause does not make a partnership bureaucratic. It makes the human side of the partnership legible. U.S. partners should ask these questions before a name is proposed, then write the answers into the agreement in plain language. The point is not to distrust the liaison. It is to make sure authority, compensation, language access, disclosure, reporting, accountability, and exit are understood by everyone involved—especially the community the role is meant to serve.