U.S. flag

An official website of the United States government

How to contribute

If you are familiar with the process of contributing to TechFAR Hub and understand the guidelines, you may jump to the contribution instructions provided below on this page. If this is your first time contributing, we recommend you read this page carefully.

Why Contribute to TFH?

Our goal with the TechFAR Hub is to compile the best resources available to help government contracting and program professionals succeed with digital services contracts. While the TechFAR Hub includes productive best practices and content from trusted sources, we recognize there are many ways to structure contracts and the methods available to individual teams are constrained by the reality of their operating conditions.

It is our hope that TechFAR Hub may offer guidance and best practices that contracting and program teams can adapt to their own unique conditions. And when teams do adapt material to their specific circumstances, we hope they consider sharing it back with the broader community through contribution to the TechFAR Hub.

What Types of Contributions Are Accepted?

We are interested in any content updates, case studies, best practices, samples and templates that exist to enable improved delivery of digital services. While the USDS hosts the TechFAR Hub, we see ourselves as part of a broader community that is constantly learning and experimenting. As a community member, we hope to curate and amplify all information that may help practitioners solve problems and produce better contracting outcomes.

Specifically, we believe this comes from demonstrated use cases where specific techniques have yielded validated learning. Validated learning means that a technique was attempted in the real world, and the results of that attempt can provide utility to others who may wish to try it. Validated learning is agnostic to the success or efficacy of the technique; even a technique that did not produce the desired outcomes can be useful, provided that retrospective analysis identifies why the desired outcomes were not produced.

We will not limit contributions to specific contract actions. Process improvements, unique interpretations of standard practice, and flexibilities found within the existing Federal Acquisition Regulations are strongly encouraged. This is especially the case if they can be replicated across the government, or provide validated learning that can inform future modifications to a given technique.

It is presumed the guidance within the TechFAR Hub may not be the only guidance appropriate for a given scenario. Or, it may be at odds with certain local practices, or become out of date as new policy and guidance is released. Should you encounter such scenarios, contributions to annotate, qualify, or suggest updates to such content are highly encouraged.

Below are some examples of content contributions.

Case Studies

Case studies are a great way to contribute validated learning to the TechFAR Hub. They do not have to be long; in fact, we encourage brevity and have created a short template to guide your contribution. The template focuses on the problem you solved, the challenges that you faced in solving it, and how your solution was applied and justified by policy, law or regulation.

Policy and Guidance

Are you aware of any new policy or guidance that informs how digital service contracts should be designed, awarded and administered? Please let us know by providing a link to the artifact and brief context about how it informs digital service contracts.

Templates & Samples

Templates and samples are great ways to support replication of your techniques in the real world. A template or sample can consist of an acquisition strategy, solicitation, quality assurance plan, scope of work, or evaluation strategy. Please ensure that you remove any mission sensitive or proprietary business information from your contributions.

Contract Solutions & Vehicles

Have you or your agency executed a multi agency or multiple award contract that others can use for streamlined acquisition? Contribute it to the TechFAR Hub along with instructions about who can use it and how they can use it. Examples include government wide acquisition contracts, interagency contracts, and enterprise-wide indefinite delivery contracts.

What is the Process of Contributing to TechFAR Hub?

Anyone can suggest a change or contribute new content to TechFAR Hub, however you as the contributor are responsible for ensuring that what you contribute is permissible under any agency procedures that may be relevant.

There are three ways to contribute:

  • Open a ticket and let us know what you think should be changed
  • If you're at USDS, read the how to update documentation and create a pull request
  • Click the blue "Help improve this site" at the bottom of every page of this site

We are always interested in contributions of examples, case studies, new policies, and useful material from around the web, so please do let us know if you see any places for updates, changes, or additional resources.

What Happens After I Contribute Content?

A team from the USDS Procurement Community of Practice will review your submission for technical accuracy, appropriateness, and duplication. When recommending changes to existing text, we will ensure that suggested changes do not conflict with current law, policy, or regulation. We may accept changes as additions to the content, and identify these additions as user generated or “original research” to convey that it should be internally validated before used in formal contract actions.

Make sure to provide contact information along with your submission, so that we may contact you if any clarification is required.


  • Tools, Templates & Samples

    Use these artifacts to get a head start on your work.

  • Case Studies

    Learn from the good work of your peers, or contribute your own!

  • Learning Center

    Advance your career by building new skills.

  • Contract Solutions & Vehicles

    Don’t reinvent the wheel before checking out these ready-made solutions.