Refugee Maps All articles
Data & Analysis

Hired Late: Auditing the 90-Day Employment Benchmark Against Monthly Hiring Seasons in Six Arrival Metros

Refugee Maps
Hired Late: Auditing the 90-Day Employment Benchmark Against Monthly Hiring Seasons in Six Arrival Metros

Photo: warehouse workers shift change employment office job seekers, via enterpriseordersolutions.com

The 90-day employment benchmark is among the most frequently cited numbers in American resettlement work. It appears in program reporting, in congressional testimony, and in the shorthand that caseworkers use when describing the first quarter of a new arrival's life in the United States. What the benchmark does not carry with it is a calendar. It says that employment should be reached within roughly three months; it says nothing about whether those three months land in a hiring season or a dead one.

That omission matters because the four sectors that absorb the largest share of newly arrived workers — accommodation and food services, food manufacturing, warehousing and storage, and home health care — do not hire at a constant rate. They breathe with the year. A family that arrives in February in a northern metro and a family that arrives in June in the same metro face materially different labor markets, even though the benchmark applied to both is identical.

This article sets out a reproducible timing audit: not a measure of whether jobs exist, but a measure of whether the calendar gives arrivals a fair shot at reaching them.

What the Benchmark Measures, and What It Leaves Out

The 90-day figure functions as a performance target inside the resettlement system rather than a legal deadline imposed on newcomers. That distinction is frequently lost in public discussion, and it is worth restating plainly: missing the benchmark is a signal about program conditions, not a finding about an individual's effort or capacity. Read that way, the benchmark becomes a diagnostic instrument, and the obvious next question is what conditions the clock is running through.

Employment timelines are shaped by English proficiency, credential recognition, transportation, child care, and employer willingness. They are also shaped by something far more mundane: whether the relevant employers are hiring in the month the arrival lands. A timing audit isolates that last variable so it can be seen alongside the others rather than buried beneath them.

Building the Timing Audit

Data inputs

Three public sources are sufficient to construct the audit. First, monthly refugee arrival counts by state and metro, available from the Office of Refugee Resettlement's arrival data, aggregated into arrival-month shares. Second, monthly hiring indicators by industry from the Bureau of Labor Statistics' Job Openings and Labor Turnover Survey, which reports hires and separations at the national and regional level. Third, annual employment and wage estimates by metro from the Occupational Employment and Wage Statistics program, used to confirm which sectors are large enough in a given metro to matter.

A fourth input, state labor market information releases, can supply metro-level seasonal factors where the federal series are too coarse.

The mismatch ratio

The audit's core construction is simple enough to be run in a spreadsheet. For each metro and each arrival month, take the ninety-day window that follows arrival. Sum the seasonal hiring intensity for the four target sectors across that window, weighting each sector by its share of employment in the metro. Divide by the same sector-weighted sum calculated across the full year. The result is a timing ratio: values below one indicate that arrivals in that month enter a window that is softer than the annual average; values above one indicate a window that is stronger.

The ratio is not a prediction. It is a description of the seasonal shape of demand that a given arrival cohort walks into.

Where the Calendar Bites

In an illustrative build across six metros — Buffalo, Louisville, Houston, Minneapolis–St. Paul, Phoenix, and Columbus — the ratio varies more by arrival month than many practitioners might expect. Northern metros with hospitality-heavy economies show a pronounced trough for arrivals in late autumn and winter, when seasonal food service employment contracts and few large employers are onboarding. Warehousing pulls in the opposite direction in the same metros, with a late-year peak that partly offsets the hospitality decline but concentrates opportunity in temporary and shift-based roles.

Food processing shows a different rhythm again, tied to harvest and production cycles that differ by region: strong late-summer and autumn hiring in the Upper Midwest, flatter patterns in parts of the South. Home health care is the least seasonal of the four and the most turnover-driven, which makes it the most reliable counterweight in off-season windows — and also the sector where wage levels and scheduling conditions most often strain a new worker's household budget.

The practical finding is not that some metros are bad places to arrive. It is that the same metro can be a materially different labor market in March and in October, and that arrival-month composition is therefore a planning variable rather than background noise.

What Advocates and Planners Can Do With a Timing Map

A timing ratio is most useful when it changes a decision. Several uses follow directly from the construction.

Limits of the Method

Three caveats deserve emphasis. The first is ecological: a timing ratio describes a labor market, not a person, and it should never be used to explain or excuse an individual outcome. The second is scale: national and regional JOLTS series cannot fully resolve metro-level seasonality, and state labor market information varies in quality. The third is granularity: arrival counts in smaller metros are small enough that month-to-month ratios should be treated as indicative rather than precise, and multi-year pooling is usually necessary before drawing conclusions.

There is also an ethical dimension to publishing such a map. A layer that identifies where arrivals land and when they arrive can be read as a planning tool or as a targeting instrument. Consistent with the practice outlined elsewhere on this site, the audit should be released at metro scale, with arrival counts binned rather than exact, and without any attribute that could be joined to identifiable individuals.

A Reproducible Recipe

For researchers who wish to run the audit themselves: assemble twelve months of arrival data by metro; pull the corresponding JOLTS hire series for the four sectors; apply each metro's sector employment shares from OEWS as weights; compute rolling ninety-day sums and normalize to the annual mean; publish the resulting matrix alongside the full codebook and the vintage date of every series. Then date the layer, because hiring seasonality itself shifts, and a ratio built on 2021–2023 data should not be read as a description of 2026 without re-running it.

The benchmark will not change because the calendar is inconvenient. But a map that shows where the clock and the hiring season diverge gives caseworkers, planners, and advocates something the benchmark alone never could: a sense of when the door is actually open.

All Articles

Related Articles

The Second Queue: Driver’s License Access as Refugee Settlement Infrastructure

The Second Queue: Driver’s License Access as Refugee Settlement Infrastructure

Funded but Unreached: Mapping Energy Assistance Under-Enrollment in Refugee Arrival ZIP Codes

Funded but Unreached: Mapping Energy Assistance Under-Enrollment in Refugee Arrival ZIP Codes

Where the Paycheck Meets the Fee: Auditing Financial Access in Refugee Settlement ZIP Codes

Where the Paycheck Meets the Fee: Auditing Financial Access in Refugee Settlement ZIP Codes