18F is a fee-for-service organization. Federal law requires that any agreement between agencies be recorded in some manner.


18F uses two mechanisms to record its agreements with other agencies: Interagency Agreements (IAAs) and Memorandums of Understanding (MOUs).

  • IAA is our shorthand for using the Treasury Department’s standard form 7600A and 7600B, along with terms and conditions, a statement of work, and financial terms to record the agreement.
  • An MOU is a single document to record work done by 18F for OCSIT. Since 18F is part of OCSIT, this agreement is between 18F/OCSIT and the GSA-CFO to allow the transfer of funds from the OCSIT appropriation to 18F for work to be done. Team Ops provides a template for your use.


TTS Policy for Beginning Billable Work

18F does not work without a signed, executed agreement in place. Please review the TTS Policy for Beginning Billable Work to see the full policy.

TTS Policy and Process for GSA Chief Information Officer FITARA Review

18F complies with FITARA and follow the TTS Policy and Process for GSA Chief Information Officer FITARA Review.

For more information about how we do business, see our account management policy.

What are the contents of an IAA?

An IAA is made up of:

  • 7600A General Terms and Conditions: This form records an estimated amount and agreement period. Neither the amount nor the agreement period may be exceeded by the cumulative 7600Bs issued under the 7600A. However, this amount and period are merely estimates.

  • 18F standard terms: This document is attached to all 7600As. It contains multiple provisions, with the two most important being our commitment to open source work and our communication clause informing clients that we may blog about them.

  • 7600B Order Requirements and Funding Information: This form records the actual amount obligated1 in the agreement by the client agency and a period of performance for the specific project. The funding information for each agency is recorded, including the expiration of the funding appropriation. This information is vital to ensuring the agreement meets applicable appropriations laws. There can be multiple 7600Bs under a 7600A, but the total cost of the 7600Bs cannot exceed the estimated amount on the 7600A, nor can the period of performance exceed the end date in the 7600A.

  • Statement of Work (SOW): This document is an attachment to the 7600B and describes the need of the client for 18F’s services and the actual deliverables that will be provided by 18F. These deliverables are specific while adhering to agile principles. Team Ops has multiple templates drafted for use by product leads.

  • Financial information: This is an attachment to the 7600B and describes items 18F can bill to the client in every agreement. It is boilerplate language.

Agreements Kanban Board

The agreements team maintains an Kanban board for agreements in the DC office. Every weekday, a member of the agreements team posts a image of the board in #iaa, as well as providing a visual representation of the status of each category on the board.

How do I get an IAA or MOU completed?

Follow the steps below. The process usually takes 30 days, and largely depends on how quickly the client provides the required information; you complete a statement of work; and the Office of General Counsel (OGC) reviews the agreement. Some agreements can take as few as 10 days, while others take up to 90 days.

The information below provides more detail than we typically give clients. Team Ops maintains a client-facing agreements site that presents a simpler process.


  1. A project clears approval through Business Unit Qualification process.
  2. Complete a cost estimate.
  3. Revise and edit the Statement of Work with the client.
  4. Ask the client to complete the IAA Form Preparation Survey. A PDF of the survey is available if the client cannot complete the Google Form. This form must be submitted by the client before moving to the next step.


  1. The project lead submits the IAA Request Form, which includes a link to the cost estimate, period of performance, statement of work (if drafted), and basic client data.
  2. Team Ops receives the form and: - Creates a file folder with all appropriate templates - Emails the folder to the project lead - Emails the client lead specified to start collecting any additional information required.

Agreements Build

  1. Team Ops edits the statement of work and highlights any changes with the project lead.
  2. The project lead contacts the Director of Infrastructure if any infrastructure is being used.
  3. The final agreement package is assembled (IAA: 7600A, standard terms, 7600B, statement of work, financial information) and shared with client for approval. Team Ops will move to the next phase even without approval from client to keep pace moving.

18F Approvals

  1. The Director of Infrastructure and Agreements Lead approve the agreement.

GSA OGC Approval

  1. Team Ops submits the completed agreement package to OGC.
  2. OCG makes edits. The project lead apprised of edits and accepts or rejects edits.
  3. OGC approves the edited documents.

18F Executive Director Approval

  1. 18F Executive Director approves the agreement.

External Signature

  1. Team Ops sends the approved agreement package to the client agency for signature.
  2. The client returns the signed agreement to Team Ops.

Internal Signature

  1. Team Ops obtains the TTS Commissioner’s signature.
  2. Team Ops obtains the GSA CFO signature.


  1. Team Ops distributes the signed agreement to the client and project lead. The project is moved to the appropriate column on the staffing kanban board.
  2. Team Ops loads the agreement into the 18F and GSA systems for billing purposes.
  3. Team Ops contacts the project lead to create a Tock project to record hours for the agreement.


For information about in-process or signed agreements, see the 18F Master Agreements Report and our account management policy.