Skip to content

CALC Labor Rates Data Dictionary

This document describes the fields available in the CALC labor category rate endpoints (/api/idvs/{key}/lcats/, /api/entities/{uei}/lcats/). For filtering, ordering, and pagination, see the CALC Labor Rates API Reference.

Overview

CALC (Contract Awarded Labor Category) rates are labor category pricing records sourced from the GSA CALC API. Each record represents a single labor category rate on a GSA MAS (Multiple Award Schedule) contract. The dataset contains approximately 238,000 records.

Primary identifier: uuid (deterministic, derived from the external CALC record ID).

Update Frequency

CALC labor rate data is refreshed daily from the GSA CALC API.

Fields

Field Type Description Source
uuid UUID Deterministic primary key (derived from external CALC ID). CALC / Tango
labor_category String Labor category title. CALC
current_price Decimal Current hourly rate. CALC
education_level String Required education level. CALC
min_years_experience Integer Minimum years of experience required. CALC
experience_range String Experience range description (e.g., "5-7 years"). CALC
security_clearance String Security clearance requirement. CALC
worksite String Work location type. CALC
sin String Special Item Number. CALC
category String Service category. CALC
subcategory String Service subcategory. CALC
schedule String GSA schedule name. CALC
contract_start Date Contract period start date. CALC
contract_end Date Contract period end date. CALC

Expansions (via shape)

  • idv -- Linked IDV details: key, piid, award_date
  • recipient -- Entity details via IDV recipient linkage: uei, display_name
  • business_size -- Business size as structured code/description (e.g., {"code": "S", "description": "Small Business"})

The idv and recipient expansions require Pro tier access. The business_size expansion is available on all tiers.

Data Sources

  • GSA CALC -- Contract Awarded Labor Category API. Provides labor category pricing data from GSA MAS contracts.

Usage Notes

  • Use uuid for unique identification. The UUID is deterministic and stable across data refreshes for the same CALC record.
  • IDV linkage is best-effort. The idv expansion is populated when Tango can match the CALC contract number to an IDV PIID in the awards dataset.
  • Recipient is derived from the IDV. The recipient expansion comes from the linked IDV's recipient entity, not directly from CALC data.
  • These are nested endpoints. Access rates via /api/idvs/{key}/lcats/ or /api/entities/{uei}/lcats/ -- there is no top-level route.
  • Pro tier required. Both the endpoints and the idv/recipient expansions require Pro tier access or above.
Report an issue with this page