Choose a search mode and write queries

GovTribe search pages can support Keyword Search, Semantic Search, or both. The search mode controls how GovTribe reads the text you type into the search bar.

Choose a mode

Start with Keyword Search when exact words, phrases, acronyms, identifiers, or operator-based combinations need to match.

Start with Semantic Search when the idea matters more than the exact wording. Semantic Search is usually better for market exploration, similar work, related concepts, and plain-language research questions.

If a query mixes both needs, choose the mode that matches the most important part of the task. Use Keyword Search when an exact number, code, or name must match. Use Semantic Search when the query is mainly about finding related records or discovering records that may use different terminology.

Note: Keyword Search is the default mode on GovTribe search pages that offer a search-mode selector.

Keyword Search

Keyword Search looks for direct term, phrase, and identifier overlap. It works well when the query is short, specific, or tied to words that should appear on the record.

Use filters instead of the search box when the task is mainly about a structured field, such as a vendor, agency, NAICS or PSC category, date, value, location, set-aside, pursuit status, or award status. A keyword query can mention those ideas, but filters are better when the field itself is the requirement.

For why some filters can include related records, hierarchy matches, or role-specific relationships, see Filter by related records and hierarchies.

Do not use field-scoped syntax such as agency:NASA, boosted terms such as cloud^2, or Lucene words such as AND and OR as operators. GovTribe chooses the searched fields for each page; use filters for agencies, vendors, categories, dates, values, locations, and statuses.

Exact phrases with double quotes

Put quotes around words that must stay together. This is useful for program phrases, source-description language, service names, and uncommon multi-word terms.

• Search "technical peer review" when the words need to appear together.
• Search "site access escorts" when that exact work phrase matters.
• Search "incident management training" when the program or framework phrase should match.
• Search "customer assistance center" when the facility or office phrase is the important part.

Required terms with +

Use + when two words, phrases, or groups must both match. This narrows a query while still letting each side match its own wording.

• Search "cloud migration" + security when both the modernization work and the security context should appear.
• Search "financial management" + audit when the result should include both the function and the review activity.
• Search "health program planning" + support when the phrase needs to appear with service context.
• Search "recruiting" + outreach when both ideas should be present.

Match different terms with |

Use | when any one of several terms or phrases can match. This is the keyword OR operator.

• Search "maintenance" | "repair" | "modernization", not "maintenance" OR "repair" OR "modernization", when any of the phrases can match.
• Search "flight training" | "flight instruction" when either phrase would describe the same need.
• Search dredge | dredging | "floating plant" when related terms may appear in different source records.
• Search "artificial intelligence" | "machine learning" | autonomy when several technology terms could describe the work.
• Search "repair" | "maintenance" | "modernization" when records may use different words for facility work.

Exclude terms with -

Use - to exclude the next term or quoted phrase. Always include at least one positive term or phrase before the exclusion.

• Search cybersecurity -staffing when cybersecurity should match but staffing-heavy results are not useful.
• Search "construction management" -residential when residential projects should be removed.
• Search "data analytics" -training when training records are crowding out analytics work.
• Search "medical transportation" -ambulance when ambulance-only results are not the target.

Group terms with parentheses

Use parentheses when part of the query has several alternatives and another part must still apply. This is useful for compact searches with a shared requirement.

• Search "cyber security" + (training | exercises) when the exact phrase should appear with either supporting activity.
• Search (dredge | dredging | "floating plant") + (electrical | controls | automation) when either dredging term must pair with at least one systems term.
• Search "public health" + (analytics | reporting) when the public-health phrase should appear with either data activity.
• Search (repair | maintenance | modernization) + "airfield" when several facility-work terms could apply to the same place type.

Prefix terms with *

Put * at the end of a term when matching several words that start the same way would help. This can broaden results quickly, so start with a specific root and add other terms or filters if the result set is too broad.

• Search cloud* migration when records may use cloud, cloud-based, or related cloud-prefix wording.
• Search cyber* training when records may use cyber, cybersecurity, or related cyber-prefix wording.
• Search moderniz* facilities when records may use wording such as modernize, modernizing, or modernization.

Fuzzy terms with ~N

Add ~1 or ~2 after a term when a close spelling match may help. ~1 is narrower, and ~2 is broader. Use fuzzy terms sparingly because they can pull in near matches that are not actually relevant.

• Search cloud~1 migration when exact cloud wording misses useful nearby matches.
• Search cybersecurity~1 training when a minor spelling variation may appear in source text.
• Search telematics~1 maintenance when a specialized term may have close spelling variants.

Semantic Search

Semantic Search looks for meaning instead of only matching the exact words in the query. Write the query in plain language, the same way you would describe the work, market, organization, or public need to another person.

Do not use keyword operators in Semantic Search. Instead of "cloud migration" + security -staffing, write secure cloud migration and modernization work that is not primarily staffing.

Describe the work

Use plain work descriptions when the exact title, category code, or source wording may vary.

• Search infrastructure upgrades for public facilities.
• Search predictive maintenance for equipment and building systems.
• Search environmental health and safety support services.
• Search custodial and facility support services for military installations.

Describe the mission or problem

Use mission- or problem-oriented queries when you know what the work supports but not how a record will describe it.

• Search health systems planning and customer support services.
• Search financial statement audit and internal control review.
• Search emergency response and disaster recovery support.
• Search recruiting outreach and applicant support services.

Explore related wording

Use broader descriptions when you want related records that may not share a single phrase.

• Search cultural resources, historic preservation, archaeology, and tribal consultation.
• Search secure data linkage and information-sharing systems.
• Search training and simulator support for operational readiness.
• Search digital transformation and workflow modernization.

Related articles

• Filter by related records and hierarchies: Understand why filters can include records connected through agencies, categories, organizations, contacts, parent records, or sub-award relationships.
• Federal contract awards: Search awarded federal contract records and compare award value, timing, and related organizations.
• Federal contract opportunities: Review federal procurement notices and related source context.
• Vendors: Research companies, recipients, suppliers, and other market participants.
• Saved searches: Return to repeatable searches that support capture tracking and opportunity monitoring.