Final TANF Rule as published in the Federal Register 4/12/1999
Final TANF Rule as published in the Federal Register 4/12/1999
Final TANF Rule as published in the Federal Register 4/12/1999
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>Federal</strong> <strong>Register</strong> / Vol. 64, No. 69 / Monday, April <strong>12</strong>, <strong>1999</strong> / <strong>Rule</strong>s and Regulations<br />
and recommended that States be<br />
allowed different sampl<strong>in</strong>g schemes<br />
b<strong>as</strong>ed on local conditions, e.g., different<br />
sample sizes for <strong>the</strong> different monthly<br />
strata. It claimed that <strong>the</strong> proposed<br />
sampl<strong>in</strong>g specifications effectively<br />
created a de facto stratification by<br />
month. However, it believed that States<br />
ga<strong>in</strong>ed no advantage by <strong>the</strong><br />
stratification. Its recommendation, it<br />
believed, would be especially helpful<br />
for States us<strong>in</strong>g monthly samples and<br />
would help with work flow and data<br />
process<strong>in</strong>g issues.<br />
Response: States have considerable<br />
flexibility <strong>in</strong> design<strong>in</strong>g <strong>the</strong>ir sampl<strong>in</strong>g<br />
plans, <strong>in</strong>clud<strong>in</strong>g design<strong>in</strong>g strata to<br />
accommodate local conditions. With<strong>in</strong><br />
that flexibility, however, <strong>the</strong> sampl<strong>in</strong>g<br />
specifications require that a State select<br />
about one-twelfth of <strong>the</strong> m<strong>in</strong>imum<br />
annual sample size each month <strong>in</strong> <strong>the</strong><br />
fiscal year. (One-twelfth of 3000 is about<br />
250 families.) This m<strong>in</strong>imum size is<br />
important <strong>in</strong> order to ensure an<br />
adequate number of families for<br />
calculat<strong>in</strong>g a monthly work<br />
participation rate, <strong>as</strong> required by statute.<br />
Comment: One commenter stated that<br />
<strong>the</strong>re is no re<strong>as</strong>on, <strong>in</strong> <strong>the</strong>ory or logic, to<br />
<strong>as</strong>sume that systemic random sampl<strong>in</strong>g<br />
is <strong>as</strong> good or better than simple random<br />
sampl<strong>in</strong>g. (The sampl<strong>in</strong>g specifications<br />
<strong>in</strong> <strong>the</strong> NPRM suggested that <strong>the</strong> former<br />
w<strong>as</strong> <strong>the</strong> preferred approach.)<br />
Response: We had suggested<br />
systematic random sampl<strong>in</strong>g <strong>in</strong> <strong>the</strong><br />
NPRM because most States had used<br />
that method <strong>in</strong> select<strong>in</strong>g samples for <strong>the</strong><br />
AFDC–QC program. However, we agree<br />
that simple random sampl<strong>in</strong>g is an<br />
acceptable method for select<strong>in</strong>g <strong>the</strong><br />
State’s <strong>TANF</strong> and MOE samples. There<br />
are a wide variety of methods that could<br />
be used to select monthly samples.<br />
These methods <strong>in</strong>clude both simple<br />
random sampl<strong>in</strong>g and stratified random<br />
sampl<strong>in</strong>g.<br />
Comment: One State suggested that<br />
we work with States to develop a more<br />
workable approach to sampl<strong>in</strong>g. For<br />
example, <strong>the</strong>y suggested that it might be<br />
useful to permit States to oversample <strong>in</strong><br />
<strong>the</strong> first two months of <strong>the</strong> quarter and<br />
undersample <strong>in</strong> <strong>the</strong> third month, given<br />
<strong>the</strong> strict requirements for <strong>the</strong><br />
submission of timely data.<br />
Response: Annual participation rates<br />
are b<strong>as</strong>ed on monthly work<br />
participation rate samples. To <strong>as</strong>sure a<br />
reliable annual work participation rate,<br />
we believe that <strong>the</strong> samples for each<br />
month need to be sufficiently large to<br />
calculate a re<strong>as</strong>onably precise monthly<br />
estimate. Therefore, we believe it is<br />
re<strong>as</strong>onable to require States to select<br />
1 ⁄<strong>12</strong>th of its sample each month. Months<br />
<strong>in</strong> which a sample is relatively small<br />
(i.e., less than 1 ⁄<strong>12</strong>th <strong>the</strong> annual required<br />
sample size), adversely impact <strong>the</strong><br />
calculation of <strong>the</strong> annual work<br />
participation rate.<br />
Comment: Two commenters appeared<br />
to believe (although we had not<br />
specified this <strong>in</strong> <strong>the</strong> NPRM) that it w<strong>as</strong><br />
permissible to report aggregate data by<br />
sampl<strong>in</strong>g, and one commenter<br />
recommended that we permit this.<br />
Response: The statute at section<br />
411(a)(1)(B) refers to sampl<strong>in</strong>g for<br />
disaggregated c<strong>as</strong>e-record <strong>in</strong>formation. It<br />
does not provide specific authority to<br />
sample aggregate data. B<strong>as</strong>ed on <strong>the</strong><br />
comments, however, we have<br />
determ<strong>in</strong>ed that it would be appropriate<br />
to allow sampl<strong>in</strong>g for some aggregate<br />
nonexpenditure data elements.<br />
(Expenditure data is never reported<br />
b<strong>as</strong>ed on sampl<strong>in</strong>g.) We have amended<br />
paragraph (a) of this section to reflect<br />
this option. We also <strong>in</strong>dicate <strong>in</strong> <strong>the</strong><br />
<strong>in</strong>structions to section three of <strong>the</strong><br />
<strong>TANF</strong> Data Report (Appendix C) and<br />
section three of <strong>the</strong> SSP–MOE Data<br />
Report (Appendix G) those data<br />
elements that may be reported b<strong>as</strong>ed on<br />
sampl<strong>in</strong>g.<br />
Section 265.6—Must States File Reports<br />
Electronically? (§ 275.6 of <strong>the</strong> NPRM)<br />
The NPRM proposed to require that<br />
States file all quarterly reports<br />
electronically, b<strong>as</strong>ed on format<br />
specifications that we would provide.<br />
Comment: We received comments<br />
from States and national organizations<br />
on this provision.<br />
Several commenters expressed<br />
general support for <strong>the</strong> proposed<br />
requirement (e.g., say<strong>in</strong>g ‘‘<strong>the</strong> law does<br />
not expressly require electronic<br />
report<strong>in</strong>g, but it will greatly facilitate<br />
<strong>the</strong> analysis of data.’’), and most States<br />
that commented believed that <strong>the</strong>y had<br />
<strong>the</strong> capacity to report electronically.<br />
However, some expressed concern<br />
that circumstances might occur that<br />
would prevent a State from report<strong>in</strong>g<br />
electronically <strong>in</strong> a timely manner or<br />
would prevent electronic report<strong>in</strong>g of<br />
some, but not all, data. They<br />
recommended that <strong>the</strong> f<strong>in</strong>al rule allow<br />
alternative report<strong>in</strong>g methods and give<br />
States <strong>the</strong> flexibility to report data <strong>in</strong><br />
whatever format is fe<strong>as</strong>ible for <strong>the</strong>m,<br />
given <strong>the</strong> vary<strong>in</strong>g levels of automation.<br />
In addition, a few States commented<br />
that <strong>the</strong>y had problems with <strong>the</strong> current<br />
electronic report<strong>in</strong>g process and<br />
software.<br />
Response: As we said <strong>in</strong> <strong>the</strong> NPRM,<br />
State representatives supported<br />
electronic submission of both recipient<br />
and f<strong>in</strong>ancial data <strong>in</strong> our pre-NPRM<br />
external consultation meet<strong>in</strong>gs, and we<br />
believe all States have electronic<br />
report<strong>in</strong>g capability (<strong>as</strong> evidenced by<br />
<strong>the</strong>ir use of electronic report<strong>in</strong>g under<br />
17867<br />
previous programs). We cont<strong>in</strong>ue to<br />
believe that electronic submission of<br />
reports will reduce paperwork and<br />
adm<strong>in</strong>istrative costs, be less expensive<br />
and time consum<strong>in</strong>g, and be more<br />
efficient for both <strong>the</strong> States and <strong>the</strong><br />
<strong>Federal</strong> government.<br />
We would take <strong>in</strong>to account any<br />
cat<strong>as</strong>trophic events or one-time-only<br />
circumstances that prevented a State<br />
from fil<strong>in</strong>g its reports electronically, on<br />
a timely b<strong>as</strong>is, but we see no re<strong>as</strong>on to<br />
change <strong>the</strong> f<strong>in</strong>al rule or give States<br />
general authority to submit reports <strong>in</strong> a<br />
variety of formats.<br />
If a State h<strong>as</strong> <strong>in</strong>itial problems <strong>in</strong> us<strong>in</strong>g<br />
<strong>the</strong> report<strong>in</strong>g processes and software<br />
that we will make available, we are<br />
committed to work<strong>in</strong>g with <strong>the</strong> State to<br />
resolve <strong>the</strong>se problems.<br />
Comment: A few States po<strong>in</strong>ted out<br />
that <strong>the</strong>re w<strong>as</strong> no b<strong>as</strong>is <strong>in</strong> <strong>the</strong> statute for<br />
<strong>the</strong> electronic report<strong>in</strong>g requirement.<br />
One State recommended that we delete<br />
<strong>the</strong> provision from <strong>the</strong> rule and issue<br />
<strong>in</strong>structional material separate from <strong>the</strong><br />
regulations.<br />
Response: We agree that this<br />
requirement does not appear <strong>in</strong> <strong>the</strong><br />
statute. However, for <strong>the</strong> re<strong>as</strong>ons stated<br />
above, we believe that it will not be an<br />
onerous adm<strong>in</strong>istrative requirement, is<br />
programmatically justified, and is<br />
with<strong>in</strong> our authority to regulate.<br />
Therefore, we have made no change <strong>in</strong><br />
§ 265.6.<br />
Comment: One commenter <strong>as</strong>ked<br />
what efforts are underway to ensure<br />
compatibility of <strong>the</strong> proposed software<br />
with <strong>the</strong> many different systems States<br />
are us<strong>in</strong>g.<br />
Response: As a part of <strong>the</strong> ETDR, we<br />
provided States with a data report<strong>in</strong>g<br />
system, <strong>in</strong>clud<strong>in</strong>g file layout and<br />
transmission specifications. States with<br />
a variety of systems and file structures<br />
were able to provide <strong>the</strong> specified data<br />
<strong>in</strong> <strong>the</strong> format required. We plan to<br />
modify this system to capture <strong>the</strong> data<br />
required <strong>in</strong> <strong>the</strong> f<strong>in</strong>al rule. States will be<br />
able to enter data and create<br />
transmission files us<strong>in</strong>g our pc-b<strong>as</strong>ed<br />
software. It <strong>in</strong>corporates a free-form<br />
capability to help prevent any future<br />
system <strong>in</strong>compatibility problems.<br />
Section 265.7—How Will We Determ<strong>in</strong>e<br />
If <strong>the</strong> State Is Meet<strong>in</strong>g <strong>the</strong> Quarterly<br />
Report<strong>in</strong>g Requirements? (§ 275.7 of <strong>the</strong><br />
NPRM)<br />
and<br />
Section 265.8—Under What<br />
Circumstances Will We Take Action To<br />
Impose a Report<strong>in</strong>g Penalty for Failure<br />
To Submit Quarterly and Annual<br />
Reports? (§ 275.8 of <strong>the</strong> NPRM)<br />
We are discuss<strong>in</strong>g <strong>the</strong>se two sections<br />
toge<strong>the</strong>r because, <strong>as</strong> <strong>the</strong> commenters