U.S. Cost Pressure by Location

Burden • Change • Offset

Update Cadence

Refresh Policy And Run Status

CostPressureIQ is maintained with repeatable ingest pipelines that update geographic coverage, score snapshots, and component-level diagnostics. This page describes how update cycles work and surfaces recent ingestion outcomes.

Current Pressure Pulse

Current Context With Its Own Source Dates

Non-scored

Pulse observations are refreshed independently of the annual baseline. A source failure retains its last verified observation with a stale label instead of changing the score or filling a gap with an estimate.

National CPI-U

336.94 CPI-U index (1982-84=100)

+3.7% from the comparable prior period

Source: U.S. Bureau of Labor Statistics, CPI
Source date: 2026-09 • Resolution: National monthly CPI-U context

Pulse Run Status

Failed

Last run started 2026-10-18 and finished 2026-10-18.

County/state covered-job wage and state residential-electricity changes are shown on source-labeled location cards, including inherited geography when applicable.

Current State

Live Source Snapshot

Snapshot Date

2024-12-31

Methodology

v1.1-acs5-2024

Scored Geographies

34,160

Current Context

Separate From Score

Electricity, wage, and CPI signals retain their own source dates.

States

51 scored snapshots from 52 loaded locations.

Counties

3,136 scored snapshots from 3,213 loaded locations.

Cities

30,973 scored snapshots from 31,254 loaded locations.

Latest Successful Refresh

Most Recent Completed Run

Source

current_pressure_pulse

Started

2026-10-15

Records Upserted

3,376

Run History

Recent Ingestion Runs

Ingestion runs capture source-specific pipeline status, record volumes, and error counts. This log is provided for transparency around data freshness and operational health.

current_pressure_pulse

Started 2026-10-18 • Finished 2026-10-18

Failed

Records read: 17,762

Records upserted: 3,325

Records errored: 1

Protected run details were recorded. Public reporting exposes source period, coverage, resolution, and status without disclosing operational configuration.

current_pressure_pulse

Started 2026-10-17 • Finished 2026-10-17

Failed

Records read: 17,762

Records upserted: 3,325

Records errored: 1

Protected run details were recorded. Public reporting exposes source period, coverage, resolution, and status without disclosing operational configuration.

current_pressure_pulse

Started 2026-10-16 • Finished 2026-10-16

Failed

Records read: 17,762

Records upserted: 3,325

Records errored: 1

Protected run details were recorded. Public reporting exposes source period, coverage, resolution, and status without disclosing operational configuration.

current_pressure_pulse

Started 2026-10-15 • Finished 2026-10-15

Succeeded

Records read: 22,762

Records upserted: 3,376

Records errored: 0

Protected run details were recorded. Public reporting exposes source period, coverage, resolution, and status without disclosing operational configuration.

current_pressure_pulse

Started 2026-10-14 • Finished 2026-10-14

Succeeded

Records read: 22,761

Records upserted: 3,376

Records errored: 0

Protected run details were recorded. Public reporting exposes source period, coverage, resolution, and status without disclosing operational configuration.

current_pressure_pulse

Started 2026-10-13 • Finished 2026-10-13

Succeeded

Records read: 22,761

Records upserted: 3,376

Records errored: 0

Protected run details were recorded. Public reporting exposes source period, coverage, resolution, and status without disclosing operational configuration.

current_pressure_pulse

Started 2026-10-12 • Finished 2026-10-12

Succeeded

Records read: 22,761

Records upserted: 3,376

Records errored: 0

Protected run details were recorded. Public reporting exposes source period, coverage, resolution, and status without disclosing operational configuration.

current_pressure_pulse

Started 2026-10-11 • Finished 2026-10-11

Succeeded

Records read: 22,761

Records upserted: 3,376

Records errored: 0

Protected run details were recorded. Public reporting exposes source period, coverage, resolution, and status without disclosing operational configuration.

current_pressure_pulse

Started 2026-10-10 • Finished 2026-10-10

Succeeded

Records read: 22,761

Records upserted: 3,376

Records errored: 0

Protected run details were recorded. Public reporting exposes source period, coverage, resolution, and status without disclosing operational configuration.

current_pressure_pulse

Started 2026-10-09 • Finished 2026-10-09

Succeeded

Records read: 22,761

Records upserted: 3,376

Records errored: 0

Protected run details were recorded. Public reporting exposes source period, coverage, resolution, and status without disclosing operational configuration.

Cadence Policy

How Content Refresh Works

Geographic coverage is refreshed when source location datasets are updated and normalized into canonical state, county, and city route structures.

Cost pressure snapshots are recomputed after ingest runs so Cost Pressure Score and component pressure outputs remain synchronized with the latest available source windows. The current loaded methodology is v1.1-acs5-2024.

When source gaps occur, fields degrade transparently to INSUFFICIENT_DATA or retain the last verified pulse record rather than introducing speculative estimates.

Operational credentials remain private. Public pages report source dates, geographic resolution, coverage, and any fallback rather than environment readiness.

Content Path

Use Fresh Data In Context

After confirming refresh health, move through state, county, and city pages to compare outcomes at each geographic level, then validate interpretation assumptions with methodology and source documentation.