The Law Center Board shall have the following four oversight roles (or “Owls”). The intention here is to provide an extra set of eyes to catch problems and to ensure the Board fills fiduciary duties while maximizing staff agency and power:

1. Financial Owl (Treasurer) 

• • Communicating with the Financial Circle on a quarterly basis to learn about current expenditures, any changes to the budget, and whether projected revenue is enough to meet the budget. This communication may take place at the Board meeting.

  • Asking staff about any confusing or concerning budget items, expenditures, or transactions, and bringing any unresolved concerns to the Board.

  • Financial Owl is only expected to interfere with self-governance if she believes financial reports show evidence of misfeasance or mission drift.

2. Worker Governance Owl 

• • Reviewing newly adopted proposals and policies.

  • Reviewing Worker Self Direction Nonprofit self-assessment and inquiring into whether worker self-direction is effectively advancing the mission of the Law Center.

  • Discussing any concerning proposals, policies, or governance practices with staff and bringing any unresolved concerns to the Board.

  • Worker Governance Owl is not expected to exert an influence on any particular policy or proposal. They are expected to be knowledgeable enough about policies to be able to notice troubling trends. They are expected to make an inquiry into whether the process being used is functioning in a manner that keeps the organization aligned and the staff fulfilled. Staff is expected to coordinate a yearly evaluation of the governance and share it with the Worker Governance Owl; they are not expected to communicate with the Owl on an ongoing basis.

3. Mission Owl (Activities and Programs) 

• • Reviewing activity updates in Asana on a roughly monthly basis.

  • Ensuring that the Law Center is effectively advancing its mission.

  • Discussing any concerning activities with staff and bringing unresolved concerns to the Board.

  • Mission Owl is expected to be able to describe to other board members the types of strategies the staff is using to forward the mission. They are expected to notice activities that may not be aligned or may jeopardize tax-exempt status. Staff is not expected to communicate with the Mission Owl outside of the Asana updates, and staff does not need to seek approval for specific activities. Mission Owl does not have the power to end a program, but only to call to the board's and staff’s attention how it might jeopardize tax status, alienate funders, or be unaligned.

4. Legal Compliance Owl (Secretary) 

• • Ensuring that the Law Center is operating in compliance with the law by annually reviewing a legal compliance check-list with staff.

  • Ensuring that the Law Center is keeping proper meeting records and following procedures under the California Corporations Code.

  • Fielding complaints and grievances per the Whistleblower Policy.

  • Staff are not expected to communicate with the Legal Compliance Owl unless they suspect misfeasance AND they have reason to believe the internal conflict resolution process is inadequate. Legal Compliance Owl is only to interact with staff in this capacity if she has good reason to believe a law is being broken.

Law Center staff shall use the following processes to keep the Board informed of our work:

1. Verbally report to the Board about our activities at quarterly Board meetings.

2. Give all Board members access to the Google Doc where we list accomplishments on a monthly basis.

3. Give most or all Board members access to Asana so that they have a full window into our activities and proposals. Provide monthly updates on Programs and Operations-related items in Asana so that the Board may read updates on major projects.

4. Ensure that Board members are tagged for all programs in NationBuilder so that they receive all email newsletters.

5. Give the Board access to our Budget Doc, where they can write comments and questions. Staff will update the Board on the budget on a quarterly basis and notify the Board of updates.

See the Board Notice and Approval Matrix (below) for guidance on when staff decisions require board notice, feedback, and/org approval.

(IR)

Note from Simon: This could benefit from an intro "why" paragraph. Maybe link our board training manual.