Many thanks to Dylan Piatt and Zach Swaziek for their help with this. Feedback always welcome at asojourn@umn.edu.
Data+code are available here: https://docs.google.com/spreadsheets/d/1RN1XJLIpU12QUwMpkF0DNiV8fkeqdHbWHta2sRfEZT4/edit#gid=651560 and https://github.com/paulgp/GoogleTrendsUINowcast
Understanding changes in national and state-level initial unemployment insurance (UI) claims has value to markets, policymakers, and economists. Initial claims measure the number of Americans filing new claims for UI benefits is one of the most-sensitive, high-frequency official statistics used to detect changes in the labor market. However, official federal data on UI claims comes out at a weekly interval and at a lag. While last week was a record-setting week, this week’s UI numbers doubled that record, with the largest rise in new unemployment claims in U.S. history, due to widespread quarantines. In advance of each week’s release, we constructed harmonized news-based measures of UI claims in a state over various sets of consecutive days. We also build a daily panel on the intensity of search interest for the term “file for unemployment” for each state on Google Trends. Changes in search intensity predict changes in initial claims. We forecast state and national UI claims using the estimated daily model. These models are new and partially validated.
Understanding changes in national and state-level initial unemployment insurance (UI) claims can have value to markets, policymakers, economists, journalists, and the public, especially in times of rapid change. Initial claims measure the number of Americans filing new claims for UI benefits is one of the most-sensitive, high-frequency official statistics used to detect changes in the labor market. However, official federal data on initial claims come out at a weekly interval and at a lag. The U.S. Department of Labor aggregates reports from state unemployment-insurance systems for weekly release of advance estimates on each Thursday, which covers the prior Sunday to Saturday week. They revise these estimates over the following week, so official estimates are released 18 days after each week starts and 12 days after it ends. Statistics on unemployment, employment to population ratios, and labor force participation come out monthly, usually two to three weeks after the reference period ends. To facilitate a more-current view of changes in the labor market, we aim to forecast official UI initial claims statistics.
Below, we describe a model we used to forecast initial claims nationally and by state for the week ending Saturday, March 28. The first (advance), official estimates was released this morning (4/2/2020). Last Thursday’s report of 3.3 million new claims in the week ending March 21 devastated the prior record since records started in 1967, due to widespread quarantines to try to flatten the curve of COVID-19 critical cases. This week’s estimate broke that record again with 6.6 million new claims filed.
Some state agencies reported partial information on new claims to the press, due the staggering growth in UI claims. The first part of our approach gathers and harmonizes the reported numbers across press reports to construct news report measures of UI claims in a state over various sets of consecutive days. The Data section provides more details.
The second part of our approach imputes states’ UI claims harnessing data from Google Trends. We construct a daily panel dataset of the intensity of search for the term “file for unemployment” for each state. We regress this measure on the set of day-states where we have constructed a growth rate in UI claims using news reports, and use this to forecast initial claims for all states based on the estimated daily model and the panel of Google trends data.
For the week ending March 21, the model yields initial national UI claims (seasonally adjusted) of 5.1. Our confidence intervals range from 4.6 to 5.6 million. Relative to the advance estimates from the state, this number is high. Further below, we discuss reasons for this, mainly related to seemingly low UI numbers from states which had had news reports suggesting much higher numbers. This discrepancy is likely due to overwhelmed UI offices in these states.
For the week of 3/22-3/28, we use the estimated relationship from 3/15-3/21 between Google Trends interest and UI claims to predict initial claims. Our model implies a prediction of 6.3 million UI claims, seasonally adjusted, with a 95% CI of 5.7 million and 6.8 million for the week of 3/22-3/28.
Extrapolating Google Trends data from 3/29-3/31 forward to the end of the week, we project 5.8 million UI claims, seasonally adjusted, with confidence intervals of 5.3 and 6.4 million.
We predict large variation across states and the table in the Appendix describes, for each state, the estimated claims level based only on extrapolation from news reports, the Google Trends change and the forecast claims level based on the model combining news reports and Google Trends information. These state estimates are not seasonally adjusted.
We are greatly helped by many states reporting various UI claims statistics over the course of recent weeks. We gather and harmonize the various reported numbers across articles to construct a dataset of “reports.” News articles report fact statements that tend to describe the number of claims for a given set of consecutive dates (from start date \(S\) to end date \(E\)) based on information from state officials. For example, an article might say, the State received 10,394 claims on Monday and Tuesday. Since reports vary over what periods that they report data (some report over a 4 day span, some over a one day span), we reconcile these differences by using a “report-level” dataset, wherein each reported fact statement is treated as an observation. For each report, we construct the per-day average claim, and call that our claim measure \(C\). We found reports for all 50 states and the District of Columbia and constructed report-level here: https://docs.google.com/spreadsheets/d/1RN1XJLIpU12QUwMpkF0DNiV8fkeqdHbWHta2sRfEZT4/edit#gid=651560
For estimation, we then link this to the average of the daily Google Trends data for that particular spell.
We pull data from http://www.google.com/trends, a Google product that aggregates search volume by geography. Many papers have used this previously as measures of activity – one example is Stephens-Davidowitz (2014).
The data is unusually reported. To quote Google:
Search results are normalized to the time and location of a query by the following process: Each data point is divided by the total searches of the geography and time range it represents to compare relative popularity. Otherwise, places with the most search volume would always be ranked highest. The resulting numbers are then scaled on a range of 0 to 100 based on a topic’s proportion to all searches on all topics.
More specifically, to quote Seth Stephens-Davidowitz:
It (Google Trends) takes the percent of all searches that use that term; then divides by the highest number. So if 1 percent of searches include coronavirus in City A and 0.5 percent of searches include coronavirus in City B, city B will have a number half as high as City A.
We pull a dataset of all fifty states (as well as Washington DC and the national trend (“USA”)), collecting an index of the relative search volume for “file for unemployment.” A crucial feature of the Google Trends API is it is only possible to compare five locations per search. To elide this issue, we pull data for California plus four states, and continuously renormalize each state by \(\max{Index_{s}}/\max{Index_{CA}}\). This way, all states are relative to California (and now some of the index measures will be larger than 100.), and comparisons can be made both across time and geographies.
We pull data for all states, as well as the national trend, from February 1st to March 28th (the latest that the data is currently available). We plot the relative indices for select states below, and see that similar to the UI growth in our news data, there is also substantial differences across states in the growth of the search term. Additionally, the weekend effect is quite noticeable, with far more search activity on the Monday after a weekend and the Friday before.
Finally, we consider the relationship between these two measures. For the purposes of estimation, we focus on estimating only with reports that ended by 3/21. That way we are able to use news and official reports for the week of 3/22-3/28 as validation for our empirical model, as we discuss at the end.
With the claims reports as data points, we construct a growth measure, relative to each state’s average of initial claims in the four prior weeks, ending Saturdays 2/22-3/14. We consider the change in the Google Trends index between the 3/15-3/21 week and the day of the week average from the last four weeks (2/22-3/14). We then plot these two measures to consider how correlated the change in Google Trends search intensity is with UI growth.
##
## Call:
## lm(formula = ui_norm ~ hits_norm, data = report_UI_GT_data %>%
## filter(epiweek(week_end) <= 13), weights = baseline_ui)
##
## Weighted Residuals:
## Min 1Q Median 3Q Max
## -358.50 -56.43 1.08 58.60 502.82
##
## Coefficients:
## Estimate Std. Error t value Pr(>|t|)
## (Intercept) 1.537745 0.158805 9.683 <2e-16 ***
## hits_norm 0.038520 0.003644 10.570 <2e-16 ***
## ---
## Signif. codes: 0 '***' 0.001 '**' 0.01 '*' 0.05 '.' 0.1 ' ' 1
##
## Residual standard error: 115.4 on 249 degrees of freedom
## Multiple R-squared: 0.3097, Adjusted R-squared: 0.307
## F-statistic: 111.7 on 1 and 249 DF, p-value: < 2.2e-16
We find a strong relationship between the two variables, with an adjusted \(R^{2}\) of 0.307 when we weight observations by the states’ baseline UI claims. We use this estimated model and observed Google Trends changes to predict unemployment claims for the states lacking news-based estimates.
Finally, we want to forecast the single statistic of weekly national initial claims. We do this in a very simple way, predicting the level of UI growth based on our model and the daily Google trends data, and then converting into predicted UI claims numbers. We sum these predicted measures across states for each week. For seasonally-adjusted numbers, we then scale up 3/15-3/21 by 0.833, and 3/22-3/28 by 0.876, per U.S. DOL practice.
For the week of 3/15-3/21, we predicted 5.1 million UI claims, with a 95% CI of 4.6 million and 5.6 million for the week of 3/15-3/21.
For the week of 3/22-3/28, the figure of Google Trends interest above shows that Sunday, March 22, the first day that will be included in the report, was 500 percent higher than the prior Sunday and Monday 250 percent higher than the prior Monday. Google Trends interest continued to be high throughout the week, suggesting that significant new UI activity. Combining this information with our model implies a prediction of 6.3 million UI claims, with a 95% CI of 5.7 million and 6.8 million for the week of 3/22-3/28.
We additionally report the non-seasonally adjusted numbers below as well.
Week | Predicted UI Claims (millions) | Lower Bound | Upper Bound | Predicted UI Claims (millions) | Lower Bound | Upper Bound |
---|---|---|---|---|---|---|
3/15-3/21 | 4.2 | 3.8 | 4.6 | 5.1 | 4.6 | 5.6 |
3/22-3/28 | 5.5 | 5.0 | 6.0 | 6.3 | 5.7 | 6.8 |
3/29-4/4 | 5.5 | 5.0 | 6.0 | 5.8 | 5.3 | 6.4 |
4/5-4/11 | 4.5 | 4.1 | 4.9 | 4.7 | 4.3 | 5.1 |
4/12-4/18 | 4.2 | 3.8 | 4.6 | 4.4 | 4.0 | 4.8 |
Based on the advance reports from the states, we can evaluate how we did in our forecasts. We’re able to do this in two ways – comparing our estimates to the advance estimates, and using a hold-out sample.
For the week of 3/15-3/21, there are initial advance reports of UI claims at the state level that reported on March 26. We compare the model’s predictions for that week relative to the advance numbers, and find that for many states the model did quite well. However, for certain states, particularly California and New York, it was substantially over. This discrepancy may be due to overwhelm of UI administrative systems in those states.
We can also look at the revised numbers reported on April 2nd and see how we do relative to those:
Since we only use the week of 3/15-3/21 to estimate the model, we can also use the news reports from 3/22-3/28 to assess how well the model does. This is our leave-out sample, and hence will give us a sense of how stable the relationship is.
The model does remarkably well, with an adjusted \(R^{2}\) of 0.7.
The model does remarkably well, with an adjusted \(R^{2}\) of 0.6721.
We can now also check how we did by comparing to advance estimates:
Finally, to minimize the role of congestion concerns by averaging across weeks, we consider how the model did at predicting the sum of the advance estimates, i.e. the total of the two sets of advance estimates between 3/15-3/28.
and scaled by labor force as of February 2020:
As a check, comparing to the advance + revised:
We predict large variation across states and the table below describes, for each state, the estimated claims level based only on extrapolation from news reports, the Google Trends change and the forecast claims level based on the model combining news reports and Google Trends information. These state estimates are not seasonally adjusted.
State | Google Trends Change from 2/22-3/14 | Advance Official UI Claims | Revised Official UI Claims | Predicted UI Claims | Google Trends Change from 2/22-3/14 | Advance Official UI Claims | Predicted UI Claims | Revised + Advance Official UI Claims | Predicted UI Claims |
---|---|---|---|---|---|---|---|---|---|
AK | 8 | 7,847 | 11,028 | 11,712 | 7 | 14,523 | 11,526 | 25,551 | 23,238 |
AL | 34 | 10,892 | 12,618 | 39,647 | 69 | 80,186 | 58,379 | 92,804 | 98,027 |
AR | 55 | 9,275 | 14,733 | 35,601 | 119 | 26,944 | 59,261 | 41,677 | 94,862 |
AZ | 16 | 29,348 | 23,761 | 50,382 | 38 | 89,064 | 69,378 | 112,825 | 119,760 |
CA | 20 | 186,333 | 382,466 | 716,570 | 29 | 878,727 | 828,145 | 1,261,193 | 1,544,715 |
CO | 48 | 19,774 | 22,395 | 45,740 | 55 | 60,784 | 49,610 | 83,179 | 95,349 |
CT | 22 | 25,100 | 82,176 | 47,233 | 22 | 33,182 | 46,810 | 115,358 | 94,043 |
DC | 34 | 14,462 | 16,354 | 11,779 | 76 | 14,868 | 18,517 | 31,222 | 30,297 |
DE | 50 | 10,776 | 12,172 | 12,948 | 109 | 18,987 | 21,340 | 31,159 | 34,288 |
FL | 25 | 74,313 | 30,445 | 93,282 | 71 | 227,000 | 159,028 | 257,445 | 252,310 |
GA | 25 | 12,140 | 107,001 | 89,594 | 63 | 132,386 | 142,151 | 239,387 | 231,745 |
HI | 80 | 8,815 | 11,183 | 39,938 | 114 | 48,861 | 51,588 | 60,044 | 91,527 |
IA | 43 | 40,952 | 54,461 | 53,680 | 61 | 58,453 | 64,965 | 112,914 | 118,645 |
ID | 24 | 13,586 | 15,085 | 17,353 | 64 | 32,240 | 28,082 | 47,325 | 45,435 |
IL | 45 | 114,114 | 132,838 | 230,425 | 64 | 178,133 | 283,070 | 310,971 | 513,495 |
IN | 68 | 59,755 | 30,865 | 74,248 | 131 | 146,243 | 117,313 | 177,108 | 191,561 |
KS | 42 | 23,563 | 17,545 | 34,079 | 72 | 54,739 | 46,711 | 72,284 | 80,790 |
KY | 77 | 49,023 | 23,817 | 77,819 | 132 | 112,726 | 114,754 | 136,543 | 192,573 |
LA | 68 | 72,438 | 55,602 | 51,870 | 119 | 97,830 | 76,271 | 153,432 | 128,141 |
MA | 24 | 148,452 | 182,023 | 112,892 | 23 | 181,062 | 111,337 | 363,085 | 224,229 |
MD | 34 | 42,981 | 47,225 | 58,187 | 81 | 83,536 | 95,159 | 130,761 | 153,346 |
ME | 105 | 21,459 | 21,783 | 28,683 | 136 | 23,535 | 34,735 | 45,318 | 63,418 |
MI | 71 | 128,006 | 90,359 | 161,719 | 183 | 311,086 | 326,397 | 401,445 | 488,117 |
MN | 12 | 115,773 | 165,877 | 50,506 | 22 | 109,896 | 60,554 | 275,773 | 111,060 |
MO | 27 | 42,246 | 48,699 | 56,782 | 77 | 96,734 | 99,494 | 145,433 | 156,277 |
MS | 47 | 5,519 | 8,294 | 18,795 | 104 | 30,946 | 31,083 | 39,240 | 49,878 |
MT | 82 | 15,349 | 19,469 | 24,623 | 112 | 19,540 | 30,555 | 39,009 | 55,178 |
NC | 26 | 94,083 | 73,597 | 46,921 | 47 | 170,881 | 61,966 | 244,478 | 108,888 |
ND | 45 | 5,662 | 9,640 | 9,961 | 130 | 12,591 | 19,807 | 22,231 | 29,767 |
NE | 45 | 15,700 | 6,192 | 13,210 | 84 | 24,572 | 19,113 | 30,764 | 32,323 |
NH | 89 | 29,379 | 27,624 | 20,656 | 118 | 27,454 | 25,309 | 55,078 | 45,965 |
NJ | 26 | 115,815 | 158,254 | 148,465 | 37 | 205,515 | 173,906 | 363,769 | 322,372 |
NM | 18 | 18,105 | 20,953 | 11,605 | 25 | 28,182 | 13,049 | 49,135 | 24,653 |
NV | 136 | 92,298 | 57,253 | 156,692 | 140 | 71,419 | 159,871 | 128,672 | 316,563 |
NY | 30 | 79,999 | 316,791 | 349,194 | 52 | 366,403 | 458,830 | 683,194 | 808,024 |
OH | 35 | 196,309 | 213,288 | 149,580 | 42 | 272,129 | 163,540 | 485,417 | 313,120 |
OK | 37 | 21,926 | 24,519 | 31,828 | 64 | 44,970 | 43,046 | 69,489 | 74,874 |
OR | 56 | 30,054 | 63,829 | 102,625 | 77 | 42,502 | 124,948 | 106,331 | 227,573 |
PA | 49 | 377,451 | 136,519 | 315,082 | 65 | 405,880 | 370,083 | 542,399 | 685,165 |
RI | 40 | 35,847 | 32,200 | 24,897 | 35 | 28,067 | 23,185 | 60,267 | 48,082 |
SC | 42 | 31,826 | 29,656 | 42,353 | 81 | 64,856 | 62,737 | 94,512 | 105,091 |
SD | 75 | 1,761 | 3,434 | 5,454 | 94 | 6,645 | 6,332 | 10,079 | 11,786 |
TN | 30 | 38,077 | 36,300 | 40,950 | 84 | 94,492 | 72,294 | 130,792 | 113,244 |
TX | 15 | 155,426 | 144,542 | 204,735 | 33 | 275,597 | 271,998 | 420,139 | 476,732 |
UT | 15 | 19,690 | 23,245 | 15,681 | 19 | 28,560 | 16,765 | 51,805 | 32,447 |
VA | 17 | 46,277 | 42,200 | 40,915 | 36 | 114,104 | 55,390 | 156,304 | 96,305 |
VT | 87 | 3,784 | 14,136 | 21,942 | 178 | 14,443 | 37,675 | 28,579 | 59,617 |
WA | 13 | 129,909 | 161,868 | 116,292 | 24 | 187,501 | 140,930 | 349,369 | 257,222 |
WI | 18 | 51,031 | 100,410 | 85,883 | 26 | 110,724 | 97,329 | 211,134 | 183,212 |
WV | 34 | 3,536 | 24,086 | 20,759 | 47 | 14,166 | 24,489 | 38,252 | 45,248 |
WY | 63 | 3,653 | 5,271 | 13,080 | 97 | 4,675 | 17,472 | 9,946 | 30,552 |