Difference between revisions of "Fiscal Sponsorship Working Group"

From Code4Lib
Jump to: navigation, search
(add definition of MOU, and expand some initialisms in headings on this page)
(Resources: add link to recording of presentation)
Line 61: Line 61:
* [https://docs.google.com/presentation/d/e/2PACX-1vTgf_wzKP-bi7sl7QcC4ZPHwEQ_qjcHjZFlLDCRZ0dRY96TQ7g-zosBSrvBzMldu5OkgoZe1cfppu2-/pub?start=false&loop=false&delayms=3000 Slides from Code4Lib 2018 presentation]
* [https://docs.google.com/presentation/d/e/2PACX-1vTgf_wzKP-bi7sl7QcC4ZPHwEQ_qjcHjZFlLDCRZ0dRY96TQ7g-zosBSrvBzMldu5OkgoZe1cfppu2-/pub?start=false&loop=false&delayms=3000 Slides from Code4Lib 2018 presentation]
* [https://youtu.be/yFQOOVtFaco?t=124 Recording of Code4Lib 2018 presentation]
* [[FCIG_Report|Report of the Fiscal Continuity Interest Group]]
* [[FCIG_Report|Report of the Fiscal Continuity Interest Group]]

Revision as of 16:04, 28 February 2018


This group is taking on the task of coming to a fiscal sponsorship agreement with DLF/CLIR for ratification by the Code4Lib community.


  • Carol Bean
  • Galen Charlton (vice-chair)
  • Tim McGeary (chair)
  • Coral Sheldon-Hess (contingent)
  • Chad Nelson
  • Morgan McKeehan

Draft Memorandum of Understanding

Draft Memorandum of Understanding

What is a Memorandum of Understanding? How is it different from a contract?

A Memorandum of Understanding (MOU) is a written agreement between parties that formally states their intention to cooperate, and outlines the requirements, roles, and responsibilities of each party in order to clarify how the parties will work together. An MOU is different from a contract in that an MOU is not legally binding or enforceable. For this reason, an MOU can be used to clarify roles and responsibilities in situations in which the parties working together may not be legally recognized as official or separate entities. Therefore an MOU can be used to create a specific agreement and outline terms of cooperation for situations in which a binding contract is not possible.
More information on MOUs is available at the link below.
Article on MOUs vs. Contracts, by Change Lab Solutions, a nonprofit organization that focuses on public health advocacy: https://www.changelabsolutions.org/sites/default/files/MOU-vs-Contracts_FINAL_20120117.pdf

Text of the draft Memorandum of Understanding between CLIR/DLF and the Code4Lib community

(This text version is provided as a convenience; the PDF version should be considered authoritative in case of discrepancy.)

Memorandum of Understanding between CLIR/DLF and the Code4Lib Community

The Council on Library and Information Resources, through its Digital Library Federation program (CLIR/DLF), agrees to act as ongoing fiscal sponsor for the Code4Lib (C4L) Community. Below is a list of responsibilities for each party. CLIR/DLF Responsibilities:

  • Continue supporting the C4L listserv at no cost and providing staff time for collegial service on C4L volunteer committees as appropriate.
  • Serve as banker and contract signatory year to year for C4L and its annual conference. Fiscal sponsorship and liability will only pertain to the national C4L event and central C4L Community initiatives and expenditures. (Regional C4L events remain the responsibility of local organizers.)
  • Collect and hold donations or other payments made to C4L, both within and beyond the conference cycle, using a dedicated payment gateway.
  • Hold C4L funds in a sweep account at Eagle Bank with interest earnings allocated on a monthly basis and maintain a separate internal account code for C4L in which all interest earnings and disbursements are tracked.
  • Attach check requests to each transaction processed and only disburse funds with the approval of the primary contact/chair of the annual conference Local Planning Committee (LPC) or a designated C4L community representative.
  • Provide semiannual reporting of the C4L account balance to the primary contact/chair of the current year’s LPC or a designated C4L community representative and, by request, a copy of CLIR/DLF’s annual audit.

C4L Community Responsibilities:

  • Coordinate and execute the annual conference through a volunteer LPC. This includes:
    • Budgeting for and working with professional conference planners or services
    • Negotiating favorable contracts with conference facilities
    • Managing conference submissions, registration transactions, sponsorships, scholarships, advertising, and facilities logistics
    • Responding to requests and questions from attendees and presenters
    • Paying attention to accessibility, diversity, and inclusion and promoting/enforcing a conference Code of Conduct
  • Steward C4L resources by:
    • Establishing annual conference budget committees to create projections, make prudent financial decisions, and maintain clear records
    • Coordinating all expenditure requests to CLIR/DLF using a standard form and through the chairs of LPCs, a representative from the C4L Journal Editorial Board, or other designated C4L community representative
    • Coordinating transfer of all financial and conference planning documentation from one year’s LPC chair to the next
  • Protect CLIR/DLF from financial losses associated with conference liability by:
    • Choosing venues carefully, with attention to factors that might affect attendees’ safety and willingness to travel
    • Budgeting for and obtaining event insurance for future conferences
    • Budgeting for development of modest C4L financial reserves, to include funds sufficient to contract with next year’s conference planners, make needed down payments, and ultimately cover or offset contingencies such as cancellation penalties agreed to in conference contracts
  • Set conference budgets to support an annual administrative fee of $5,000 to CLIR/DLF, meant to offset costs of accounting, auditing, coordination, and processing of transactions.
  • Maintain a yearly balance of a minimum of $25,000 in the C4L account managed by CLIR/DLF. CLIR/DLF would appreciate but not require acknowledgment as fiscal sponsor on C4L conference materials and websites. In the event that no LPC emerges from the C4L Community in a given year, CLIR/DLF will bear no responsibility to organize the annual conference. Either party may terminate this MoU after good-faith settling of accounts and with adequate notice to prevent disruption of current conference planning.