Summary

  • Internet Society Board Meeting 196 was scheduled to adjourn at 09:05 UTC on 26 July 2026. Foundation Meeting F36 was scheduled to begin five minutes later, with a new call to order, a new conflict check, separate officer elections and Foundation-prefixed committee appointments.
  • The shared roster is deliberate. The Foundation's current bylaws say Internet Society's trustees are also Foundation trustees unless Internet Society, as sole Member, resolves otherwise. Shared people do not make the corporations or their Boards legally identical.
  • The public architecture contains three decision capacities: the Internet Society Board, the Foundation Board, and Internet Society acting as the Foundation's sole Member. The third includes approval rights over fundamental transactions and the Foundation's annual budget.
  • A decision-capacity receipt would keep the coordination benefit while identifying the acting entity, authority, meeting or consent record, quorum, vote, conflicts, budget or asset owner, implementing officer, dependency and correction state.

Five minutes separated two Boards

At 09:05 UTC on 26 July, Internet Society Board Meeting 196 was due to adjourn in Vienna. The published agenda then tells readers that the Internet Society Foundation Board meeting “immediately follows” and links to a separate page. That second agenda begins at 09:10.

The five-minute interval looks almost too small to matter. No new group had to enter the room. The same trustees could remain in their chairs. The President, finance staff, counsel and governance staff could carry the institutional context from one session to the next. A shared Board is meant to reduce the cost of explaining dependencies twice.

Yet the second agenda does not say that the first meeting merely resumed. Foundation Meeting F36 begins with its own welcome, apologies and declarations of conflict. It schedules a Foundation Board Chair election, a Foundation officer election and Foundation committee appointments. Its proposed committee resolution carries an F2026-X identifier and names committees of the Foundation Board. The agenda then turns to a Foundation update, a CFO report, a Foundation Finance Committee report and the Foundation's Strategic Advisory Committee before a separate adjournment.

The Internet Society agenda had already performed the corresponding acts for a different institution. Meeting 196 opened its own conflict checkpoint, elected the Internet Society Board leadership, proposed appointments to Internet Society committees, heard reports connected to the Internet Society, considered finance and enterprise risk, and explicitly adjourned the ISOC Board meeting before sending observers to the Foundation page.

That is the governance distinction in its most practical form. The people can remain. The meeting must change.

The agendas are not minutes. At the 31 August research cutoff, approved minutes for Meeting 196 and F36 were not yet on the two minutes indexes. The agendas therefore prove the planned decision surfaces and proposed resolution language; they do not prove exact votes, final resolution numbers, attendance changes or recusals. A 31 July announcement establishes the seated roster and the new Chair. It cannot fill the unreported details of either meeting.

The common roster is part of the design

The overlap is not an accidental staffing convenience. The Foundation's current bylaws name Internet Society as the sole Member and say that, unless the Member resolves otherwise, the Member's trustees are the Foundation's trustees. A Foundation trustee ordinarily remains in office while serving as a trustee of the Member. The Foundation's public Board page consequently lists the current Internet Society trustees as its own Board.

The Board Member Agreement is equally direct. It lists the collective work of an Internet Society trustee—mission, CEO selection, strategy, fiduciary and financial oversight, programmes, budgets and Board performance—and then says the trustee performs those same functions as the Internet Society Foundation Board. It repeats the Foundation role among the trustee's individual responsibilities.

Brian Haberman, elected Chair in July, explained the benefit in an August Q&A. The two organizations are separate but their missions are tightly interwoven, he said; a shared Board can see crossovers and dependencies and give leadership a view across both. He called the relationship symbiotic while also saying that each entity has a distinct mission.

That account should be treated as an attributed explanation, not a legal interpretation. The Q&A carries a disclaimer saying its views may or may not reflect official Internet Society positions. Even so, it identifies a real advantage. When one organization supports policy, community and technical work and the other operates as its supporting philanthropic organization, a Board that sees both sides can avoid coordination through incomplete memos and late escalations.

The mistake would be to assume that shared visibility also supplies shared legal capacity. It does not.

One roster can occupy three capacities

The public documents describe at least three paths through which a consequential act can occur.

First, the Internet Society Board directs the affairs of Internet Society. Its bylaws define its quorum and vote, allow unanimous written consent, require minutes, authorize its committees, assign approval of the Society budget and establish the Society's officers and records. Trustees in that capacity serve Internet Society as a whole.

Second, the Foundation Board directs the affairs of the Internet Society Foundation. Its bylaws apply a separate quorum and vote to Foundation Board action, allow a separate unanimous written consent, require Foundation minutes, establish Foundation committees and officers, and require the Foundation Board to elect a Chair at its own Annual Meeting. The Foundation transparency page says trustees serve the Foundation as a whole.

Third, Internet Society is the Foundation's sole Member. The Member has voting rights and may act by written consent filed with the Foundation's records. Its reserved rights include approval of fundamental transactions and approval of the Foundation's annual budget under a procedure determined by the Foundation Board and approved by the Member.

These paths are related but not interchangeable. A Foundation Board proposal can require a Member approval. Internet Society may supply that approval because it is the Member, not because a Foundation Board vote silently counts twice. A common briefing may inform both actions. It should produce two linked records if two capacities act.

The distinction matters even when every person votes the same way. Authority is not identified by the face at the table. It is identified by the office being exercised, the corporation whose affairs are being directed and the record in which the act becomes effective.

The latest approved records already preserve separation

This is not an argument that the two organizations publish one blurred minute book. Their latest approved paired records show the opposite.

Internet Society Meeting 194 was held in London on 18 April 2026. Its minutes identify the Internet Society meeting, list the trustees, conduct a conflict call and move through Society matters: organizational performance, finance, committee work, enterprise risk and Board resolutions. Foundation Meeting F35 was held the next day. Its minutes list materially the same trustees but call the Foundation Board meeting to order again, ask for conflicts again, address Foundation operations, philanthropy, grants, pre-audit finances and co-funds, and record a separate adjournment.

The two records sit on different institutional sites under different numbering systems. Foundation resolutions use an F prefix. Foundation committee appointments say that the Foundation Board is making them. A grant authorization identifies Foundation money and a Foundation programme. These are not cosmetic differences. They make it possible to reconstruct which body acted without guessing from the subject matter.

The current bylaws reinforce the record boundary. Each Board has its own meeting, action, consent and minutes provisions. Each has its own corporate officers and record custody. Each has its own indemnification article. The Internet Society text asks, in the relevant circumstance, whether a person reasonably believed an act was in the Society's best interests. The Foundation text asks the corresponding question for the Foundation.

No inference of a conflict follows from that distinction. Separate corporate interests can be aligned. The Foundation is a supporting organization of Internet Society, operates for its benefit and advances compatible charitable purposes. The important point is narrower: alignment is a relationship between two identified interests, not a licence to stop naming them.

Shared context can conceal the moment authority changes

A back-to-back meeting is efficient precisely because almost nothing visible needs to change. That efficiency creates a documentary risk even where the underlying governance is sound.

A trustee may have no conflict in a Society strategy discussion but a Foundation-specific issue when a grant, vendor, supported organization or restricted fund comes before the second Board. Repeating the conflict call is not ritual. It gives the person a new opportunity to assess the matter against a different corporate interest and transaction set.

Quorum presents a similar problem. The rosters may be identical, but the acting body still needs its own call to order, attendance state and vote. A trustee who steps out between meetings can change the arithmetic. A resolution approved in one capacity cannot be located merely by pointing to a room in which the same majority later sat.

Budgets add the third capacity. The Internet Society Board approves the Society's own budget. The Foundation Board determines a procedure for the Foundation budget, while Internet Society as Member holds an approval right. A statement that “the Board approved the budget” leaves the reader unable to tell whether the necessary act was a Foundation Board approval, a Member approval, an Internet Society budget decision, or more than one of these.

Officers can also wear two hats. The current public materials identify one President and CEO serving both organizations, and finance and legal personnel appear in both meeting records. Shared personnel can be operationally sensible. An instruction still needs to say whether the officer is implementing an Internet Society Board act, a Foundation Board act or a Member consent. Otherwise later custodians may know what management did but not which corporate authority made it executable.

A decision-capacity receipt

The public record already contains most of the components. The improvement is to join them without merging them.

A decision-capacity receipt should begin with one mandatory field: capacity. The value should be Internet Society Board, Internet Society Foundation Board or Internet Society as sole Member. Beside it should sit the legal entity and the corporate interest to which the act belongs.

The receipt should then identify the controlling authority—a bylaw, articles provision, committee charter, contract, policy or Member right—and the record that exercised it. That record could be a meeting number, an F-prefixed Foundation resolution, an Internet Society resolution or a Member written-consent identifier. If two acts depend on one another, neither should borrow the other's identifier. They should link.

Time and state belong in separate fields. Proposed language is not approval. Approval is not necessarily effectiveness. Effectiveness is not implementation. A later correction should supersede the earlier state rather than silently replacing it.

For the decision itself, the receipt should capture the separate quorum, vote and conflict or recusal record. It should name the budget, asset or programme owner and the officer charged with implementation. If one organization's decision depends on advice, a service, funding or consent from the other, the receipt should identify that dependency and its state.

This need not expose closed deliberations. A receipt can state that the source briefing is confidential, legally privileged or access-restricted. It need not publish a grant applicant's private data, legal advice, personnel assessment or security-sensitive payment details. The public layer can prove who acted and under which authority without publishing everything they saw.

Nor does the model require two performances of the same presentation. A common staff paper can be delivered once. Trustees can ask questions that inform both institutions. A joint strategy session can reduce duplication. What cannot be joint by implication is the resulting corporate act. If both Boards decide, there should be two decision entries connected to the common evidence. If the Member also approves, there should be a third.

What the evidence does not show

No reviewed source shows that Internet Society and the Foundation have treated one vote as three. No source establishes a missed conflict declaration, defective quorum, invalid budget, hidden transfer, commingling of assets, self-dealing, tax failure or breach of fiduciary duty. The back-to-back agendas and paired minutes provide positive evidence of separation, not a discovered violation.

The shared roster is not proof that trustees lack independence. The structure is stated in the bylaws, and the Member retains power to resolve otherwise. A separate roster might change the trade-off between coordination and organizational distance, but this Article does not establish that it is necessary or superior.

The use of a singular “Board” in a press release is also not a merger instrument. Public communications often compress two aligned roles into one phrase. The governing records resolve the legal question more precisely. The appropriate response to shorthand is a better link to the two records, not an accusation against the people named in it.

The useful standard is therefore modest: one roster may see the whole relationship; every act should still reveal one capacity. Internet Society and its Foundation have already built much of that separation into agendas, minutes, resolutions, committees and bylaws. A capacity receipt would make the handoff between them as visible as the alignment that joins them.

Sources

  1. Internet Society amended and restated bylaws
  2. Internet Society Foundation bylaws
  3. Internet Society Foundation Articles of Incorporation
  4. Internet Society Board Member Agreement
  5. Internet Society Foundation transparency and governance
  6. Internet Society Board Meeting 196 agenda
  7. Internet Society Foundation Meeting F36 agenda
  8. Internet Society Board Meeting 194 minutes
  9. Internet Society Foundation Meeting F35 minutes
  10. Internet Society Foundation Board resolutions
  11. Internet Society and Foundation announce the 2026 trustees
  12. Q&A with Board Chair Brian Haberman