The Signature Behind the Seal: Verifying Community Mandates in U.S.–Madagascar Agreements

U.S. funders often reach the same unsettled moment late in partnership design: a grant agreement, receipt form, or change order is ready, and someone asks who is authorized to sign. The question sounds administrative. In community-led work, it is a governance question. A signature can commit a village association to obligations, acknowledge funds, or alter a project scope. Before a U.S. partner treats that signature as evidence of community approval, it should know what authority the signer actually carries.

A signature is a governance claim

When a Malagasy community organization signs with a U.S. funder, the document usually does two things at once. It creates a relationship with the funder, and it represents a decision made inside the community. Those are not the same act. The first is contractual. The second is political and social. A useful due diligence process confirms both without asking the community to perform trust for the funder’s benefit.

The practical risk is not that community partners are careless. It is that outside partners often import assumptions about how authority works. In the United States, a nonprofit’s signatory authority is usually documented through bylaws, board resolutions, and officer titles. In Madagascar, authority may sit with a cooperative board, a community association, a fokontany-level body, a delegated project committee, or a combination of these, depending on the legal form and local practice. Titles alone do not settle the matter. A president may speak for an organization but still need assembly approval for a multi-year commitment. A treasurer may handle receipts but not change project scope. A respected facilitator may carry social legitimacy without formal authority to bind the group.

Consent is not the same as authorization

Individual consent matters. People should agree to participate, contribute land or labor, and be named in project records. But individual consent does not equal collective authorization. A community can support a project in general and still require a specific decision before one person signs a contract on its behalf.

This distinction is especially important for U.S. funders that work through small grants and thin administrative teams. The person who can convene a meeting, translate a proposal, or receive a wire transfer is not automatically the person authorized to approve a budget revision. Confusing access with authority is how well-intentioned partnerships create disputes later.

A sound process separates three questions. First, who has been authorized to act for the community body? Second, what can that person approve without returning to the body? Third, how can the community revoke or replace that authority? The answers should be written down, dated, and attached to the partnership record.

Three lightweight artifacts

Most partnerships do not need a heavy legal apparatus. They need a clear paper trail that the community already recognizes. Three artifacts often suffice.

1. A mandate letter

A mandate letter names the individual authorized to sign or act, identifies the community body granting authority, states the scope of authority, sets any financial or programmatic limits, and gives an effective date and duration. It should also say how the mandate can be revoked. The letter does not need to mimic a U.S. corporate resolution. It should reflect the community’s own decision process and be attested by people who can confirm that the decision was made.

2. A meeting-minute annex

Minutes are often more convincing than a standalone letter because they show the decision in context. Useful minutes include the date, place, agenda item, attendees, quorum or participation basis, the decision reached, and the names and roles of those who will sign. If the community decides by consensus rather than vote, the minutes can record that fact. The key is consistency: the person named in the mandate letter should match the person named in the minutes, and the scope should match the agreement.

3. An authority matrix

A simple one-page matrix prevents routine confusion. It lists who may sign grant agreements, who may acknowledge receipts, who may approve change orders, and who may speak to the funder on program matters. It also sets thresholds. For example, a designated officer may sign receipts for routine disbursements, while a scope change above a stated amount requires a fresh community decision. The matrix should identify a backup signer and explain what happens if the primary signer is unavailable.

Verification that respects the partner

Due diligence becomes corrosive when it is applied as suspicion. It becomes constructive when it is a standard onboarding step, explained in advance and applied to every partnership. U.S. funders can ask for the mandate letter, minute annex, and authority matrix as part of the same package that includes the budget and work plan. Reviewers should check dates, names, scopes, and consistency across documents. If something is unclear, a short clarification call is usually better than a long document request.

Where the partner is a registered legal entity, local counsel can confirm that the signatory matches the organization’s governing documents. Where the partner is a community association without a single legal form, the funder should rely on the community’s own recorded decision and avoid inventing a requirement that has no local basis. Notarization may be appropriate in some cases, but it should not become a default hurdle that favors groups with easier access to town offices.

The partner should keep originals. The funder should keep copies and note where the originals are held. That practice protects community records and gives the U.S. side an auditable file without turning document collection into an extractive exercise.

Contract language that keeps decisions local

Authority terms should be specific enough to be auditable and flexible enough to respect community process. A grant agreement can include the following provisions, adapted to the partnership.

• Community authorization. The grantee represents that the individual signing has been authorized by the named community body under a mandate dated and attached as an annex. A copy of the relevant minutes or resolution is included.
• Scope and limits. The signatory may execute the grant agreement and approve change orders up to a stated amount or percentage. Anything beyond that requires a new written authorization from the community body.
• Revocation and replacement. The community body may revoke the mandate by written notice. The funder will recognize a replacement signer after receiving a new mandate letter and minute annex.
• No implied authority. The mandate does not authorize the signer to waive community rights, transfer community assets, or make commitments outside the agreed project scope.
• Records and access. The partner retains original authorization records and provides copies to the funder for its file. The funder may request clarification but will not treat a request as a reason to bypass the community’s decision process.

These clauses do not remove the need for judgment. They give both sides a common reference point when a receipt, change order, or renewal arrives with a familiar signature.

Change orders deserve the same scrutiny as agreements

Many partnerships document initial authority carefully and then relax when the work begins. That is where risk accumulates. A change order can extend a timeline, shift a budget line, or alter who benefits from a project. If the original signer had authority only for the initial agreement, a change order may require a new decision. The authority matrix should say so plainly.

Receipts are different. They usually acknowledge funds received rather than approve new commitments. A routine receipt can be signed by an authorized financial officer within the matrix. But a receipt should not be used to paper over an unauthorized scope change. Keeping those documents distinct helps the community and the funder maintain a clean record.

A file that is auditable without being intrusive

A practical due diligence file can be short: the mandate letter, the minute annex, the authority matrix, the governing documents if any, and a note on where originals are kept. The file should be updated when leadership changes. It should also record any clarification the funder requested and how the partner resolved it. That record protects the community from having to relitigate its authority with every new program officer.

For U.S. funders, the standard is not whether a signature looks official. The standard is whether the community can recognize the decision behind it. When authority is documented in the community’s own terms, the signature becomes what it should be: a reliable bridge between local decision-making and accountable partnership.