Philippines staffing research · Published
On this page
Reading public procurement data without overclaiming vendor spend
A review of what federal procurement datasets can and cannot show a small business comparing vendor categories, prices, and spending patterns.
Methodology
This review defines a documentary protocol for using public federal procurement data as context for a small business vendor review; the unit is one vendor category linked to a public award dataset, a contract record, and a stated comparison question. The protocol compares those sources with guidance from USAspending.gov, SAM.gov, and the Acquisition Regulation system, which publish federal award and contracting information rather than private market prices. Inclusion rules are declared before inspection so favorable categories are not selected after the fact. The review reports coverage gaps and label counts, not estimates of a fair market price. It does not provide legal or procurement advice, and any purchasing decision remains with the business owner.
Key Stats
- 4: questions a public award record can answer
- 3: public references used for background
- 0: private price conclusions drawn
Key Takeaways
- Treat a federal award value as a public contract fact, not as the market price a small business should expect.
- Record the agency, period, place of performance, and product category before comparing awards.
- Use SAM.gov and USAspending.gov together so entity identity and award history are not confused.
- State the coverage limits of public data before presenting any vendor benchmark.
Question and scope
This review asks what federal procurement data can tell a small business about a vendor category without implying a private-market price; the population is public award records for one product or service category, and the unit is one award linked to its recipient, agency, period, and place of performance. The question is narrow because public data serves a different purpose than a private quote: it shows what government buyers awarded under their rules, not what a small business should pay. Freeze the category definition before inspection so adjacent products are not mixed in after the fact. Record the data source and the retrieval date beside each result. The award record is the object of study, never proof of a fair price.
| Scope | Public federal awards in one vendor category |
|---|---|
| Unit | One award with recipient, agency, period, and place |
What USAspending covers
USAspending.gov publishes federal award data, including prime awards, subawards, and agency spending; it can show who received an award, which agency obligated funds, the period of performance, and the place of performance. Those fields are useful for understanding the shape of a category and the agencies that buy in it. The data does not show a private company's costs, margins, or negotiated discounts. It also does not prove that an award was typical, because large and small awards may be mixed in one category. Record the award type and the date range before drawing any comparison.
| Shows | Recipient, agency, obligation, period, place |
|---|---|
| Does not show | Private costs, margins, or negotiated discounts |
What SAM and contract data add
SAM.gov provides entity registration and identifying information that helps confirm who a vendor is; contract records can add the solicitation, the contract type, and the place of performance when those fields are published. Together, these sources help a reviewer avoid confusing two companies with similar names or treating a subsidiary as an unrelated vendor. They still do not provide a complete price history, because not every transaction is published at the same level of detail. The protocol links each award to an entity record where possible and flags awards that cannot be matched. Identity confidence should be reported separately from price comparison.
| Adds | Entity identity, contract type, solicitation, place |
|---|---|
| Limit | Not every transaction is published at equal detail |
Why public data cannot set your price
A public award reflects federal requirements, competition rules, and contract terms that may not resemble a small business purchase; the award value may include options, overhead, compliance costs, or a multi-year period that a private quote does not. Using it as a benchmark without those adjustments can create a false sense of overpaying or underpaying. The protocol records the contract type and period so the reviewer can see what the number represents. It does not convert an award into a unit price unless the source publishes a defensible quantity. A category-level comparison is more honest than a precise-looking number built from mismatched records.
| Award value | May include options, overhead, compliance, multi-year term |
|---|---|
| Comparison | Category context only unless quantity is published |
Comparing categories without false precision
Start with a clear category definition and a stated question, such as which agencies buy this service and how awards are distributed; report the number of awards, the range, and the median, and label any amount that is an obligation rather than a payment. Do not combine products with different units or services with different scopes into one average. If the data is too thin, say so instead of widening the category until a number appears. The protocol records every exclusion and the reason. A thin but honest comparison is more useful than a broad one that hides its assumptions.
| Report | Award count, range, median, obligation basis |
|---|---|
| Avoid | Mixed units or widened categories that hide thin data |
Reporting limits to the owner
The owner needs to know what the data supports before it influences a negotiation; state the source, the retrieval date, the category definition, and the fields that were missing. Explain that federal awards are not private quotes and that the comparison is context rather than a price target. If the review finds a possible saving, describe the question to ask a vendor rather than a conclusion to impose. Do not present a public-data benchmark as evidence that a current vendor is overcharging. The honest output is a short list of informed questions and the additional private evidence needed to answer them.
| Deliver | Source, date, definition, missing fields, questions |
|---|---|
| Avoid | Treating an award as proof of overcharging |
Entity identity and subsidiaries
A vendor name in an award record may refer to a parent, a subsidiary, or a joint venture; use the entity identifier and registration record to check which legal entity received the award. Do not assume that two similar names are the same company or that one address proves a relationship. Record the identity confidence beside the award and flag any record that cannot be matched. A subsidiary may negotiate separately from its parent, so combining them can distort a category comparison. Identity work comes before any price discussion.
| Check | Entity identifier, registration, and legal name |
|---|---|
| Flag | Unmatched or ambiguous award records |
Award type and period effects
Award values are not interchangeable across contract types and periods; a firm-fixed-price contract, an indefinite-delivery vehicle, and a cost-reimbursement award describe different commitments. A multi-year award may include options that were not exercised, while a shorter award may include all work in one period. Record the contract type, the period of performance, and whether the amount is an obligation or an outlay. Compare awards only when those fields are similar enough to support the question. A chart that ignores contract type can make two unrelated numbers look comparable.
| Fields | Contract type, period, obligation or outlay |
|---|---|
| Compare | Only awards with similar scope and terms |
The review uses public federal procurement data and guidance only as background. It does not claim that the cited sources endorse this protocol or that their data represents private-market pricing.
Sources
- USAspending.gov: Publishes federal award, subaward, and agency spending data.
- SAM.gov: Provides federal entity registration and identifying information.
- Acquisition.gov: Publishes the Federal Acquisition Regulation and related guidance.
FAQs
Can a federal award value set a fair price for a small business?
No; it is context under federal rules, and a private price requires private quotes and scope details.
Why compare USAspending and SAM.gov together?
USAspending shows award history while SAM.gov helps confirm the identity of the entity that received it.
What if the category has very few awards?
Report the thin coverage and avoid widening the category until a number appears.
Related Research
Plan the next step
Bring one vendor category and its source data to a bounded review of public awards, entity identity, and comparison limits.
Plan the next stepRead the daily blog guides · Explore service workflows · Plan your staffing routine
Take one vendor category, name the public dataset and retrieval date, and separate what the awards show from what they cannot prove.