A buying-office profile can help you understand observed procurement activity within a defined period. It cannot establish the requirement in every solicitation issued by that office.
Read the profile as a set of dated research observations. Then open the particular opportunity and review its own package before deciding to pursue.
Confirm which office the profile describes
Names can overlap across agencies, sites and organizational levels. Record the office name and identifier used by the source. Distinguish the awarding office from a funding organization or place of performance.
A shared city is not an office identity. The existing NAVSUP Mechanicsburg and DLA Mechanicsburg campaign profiles concern different buying organizations. Do not combine them into one buyer merely because both say Mechanicsburg.
Read the denominator before the percentage
| Profile statement | What must be defined |
|---|---|
| Number of opportunities | Notice types, date rule and whether actions or procurement families are counted |
| Share mentioning a requirement | Search rule, text coverage and the population being searched |
| Typical response window | Which posting and response dates are compared, and how missing or changed dates are handled |
| Common commodity | Classification edition and whether the count covers notices, awards or actions |
| Award activity | Awarding/funding office distinction, financial measure and period |
A percentage over descriptions is not a percentage over fully reviewed packages. A provision title in a notice is not necessarily a populated level requirement.
Use the profile to choose what to inspect
A recurring commodity can suggest which technical examples deserve attention. Repeated access language can suggest preparing an access-review process. A short observed window can motivate earlier internal preparation.
Each remains a research implication, not proof of what the next solicitation will demand. Avoid statements such as “this office always requires Level 2” unless the exact claim has an appropriate source and scope. A handful of examples cannot support “always.”
Inspect a source-linked example
Open one notice from the profile and identify the actual document behind the summary. Compare the buyer identifier, date, work description and cited requirement. If the condition sits in an attachment, a description-only board has a coverage limit.
Use the attachment review guide for that step. Review the current package before treating the observation as operative.
Record the useful next question
A practical output is a short list: which work categories need deeper research, which prerequisites the team should investigate, and which current notices justify a full review. Keep unknowns separate from negative findings.
The existing campaign profiles are dated examples, not a claim that this guide contains a newly refreshed office census. This page offers an educational method and does not launch a buyer-intelligence subscription.
Source definitions: SAM.gov, USAspending data documentation, and the linked campaign source records. Reviewed September 7, 2026.
Related reading
Read what a procurement snapshot can and cannot tell you before interpreting a notice count as market demand.