In scoping

Corporate & Institutional Boards

Public-company boards. Nonprofit boards. Pension trustees. University trustees. Foundation boards. The private-sector and institutional governance bodies whose decisions produce public consequences — and whose published codes often exceed their actual practice.

Common accountability gaps in this area

  • Published codes of ethics do not always match observed conduct.
  • Director independence can be defined narrowly through technical interpretations of SEC standards.
  • Audit committees sometimes approve what management presents without the staff to test it independently.
  • ESG disclosures sometimes report on policies that exist on paper more than in practice.
  • Pension trustees may approve fee structures that are difficult to explain, to managers whose performance is hard to verify.
  • Nonprofit and university boards sometimes tolerate related-party transactions that a public-company audit committee would reject.

What TASFGA will track

  • Code-vs-conduct audits — published policies tested against observable behavior
  • Director-independence ledger — real independence, not technical compliance
  • Related-party transaction tracking — especially in nonprofit and pension contexts
  • Disclosure quality index — 10-K, proxy, 990, and equivalent filings rated against actual decision records
  • Compensation-outcome pairing — pay vs. the metric the pay was supposedly tied to

Evidence carried over from Focus 1

Residential community associations are corporations. They have directors, fiduciary duties, an audit relationship, and a controlling shareholder during the sponsor's control period — with none of the disclosure architecture that constrains a public-company board. That makes Focus 1 a controlled study of what board governance does when the oversight is removed, and the findings transfer.

  • The control period is a related-party laboratory. While a sponsor or developer controls the board, it sits on both sides of every transaction: it appoints the directors, selects the manager, awards the construction contracts, and determines what the entity will later claim against it. The abuses documented in that window are the same related-party failures that appear in nonprofit and pension governance, with the concealment stripped away.
  • Audit-committee capture, in its purest form. The accountant is typically recommended by the manager, retained by the board, and paid from member funds, and the engagement depends on the manager's referral pipeline across many entities. That is not independence. It is the captive audit relationship a public-company audit committee exists to prevent, operating with no committee at all.
  • Fiduciary duty without an enforcement path. Directors owe duties; members have no practical way to enforce them short of trial-level litigation that is prohibitively expensive and takes years. A duty with no reachable remedy is a disclosure, not a constraint — the same structural problem that makes derivative litigation a poor instrument in the corporate setting.
  • Code-versus-conduct, measurable. These entities publish governing documents that state exactly what the board must do: how it must bid, what it must retain, when it must report, what it must fund. The distance between that text and the record is directly measurable, which is what makes the sector the best available proving ground for a code-versus-conduct audit.

Two of the review practices developed there apply here without adaptation: Audit & Financial Records Review, which tests what an audit opinion does and does not cover, and Procurement Integrity Review, which tests referral economics, affiliate vendors, and the fees an intermediary earns from the counterparties it recommends.

Why this matters

Corporate and institutional boards make decisions that move markets, fund universities, pay pensions, and deliver (or deny) services. Existing oversight — SEC filings, audit opinions, accreditation reviews — can be insufficient for the leverage these bodies hold. TASFGA aims to apply the same planned accountability loop here as everywhere else: find the gap between code and practice, propose a fix, and track implementation.