Access Official Technical PDF

Share Summary:LinkedInEmail

Survey data collection at national scale depends on more than distributing a questionnaire. The 2018 Census of State and Local Law Enforcement Agencies (CSLLEA), planned by the U.S. Bureau of Justice Statistics (BJS), shows how a collection can be structured around instrument testing, verification of the agency population and consistent reporting. Although the census concerned law enforcement rather than industrial operations, its staged design highlights practical considerations for technical teams planning complex data-gathering programs.

What the 2018 CSLLEA was designed to capture

The CSLLEA was intended to enumerate publicly funded state, county, local and tribal law enforcement agencies operating in the United States. Eligible agencies had to employ the equivalent of at least one full-time sworn officer with general arrest powers. The scope included both general-purpose agencies, such as municipal and county police departments, and special-purpose agencies, including campus, transportation and natural-resources law enforcement.

BJS had conducted the census regularly since 1986, and the 2018 collection was to be its seventh administration. Its purpose was to establish a national inventory and gather personnel counts and information about agency functions. The resulting information was also intended to provide a sampling frame for future BJS law enforcement surveys.

That combination of current reporting and future reuse shaped the collection’s design. The data were not being gathered only to answer an immediate set of questions; they were also expected to support later surveys. In any large-scale reporting effort, defining how collected information will be used can help clarify which fields need to be included and how the respondent population should be identified.

A two-phase approach to survey data collection

The proposed 2018 CSLLEA had two phases. First, BJS planned cognitive testing of a revised survey instrument with 48 agencies. The test group was organized by agency type—local and county police, sheriff’s offices, and special-purpose agencies—and by size, using a threshold of 100 full-time-equivalent sworn officers. The plan allowed for up to eight agencies in each type-and-size category.

Cognitive testing was intended to examine the revised instrument before the main collection. BJS had reduced the number of items from the 2014 administration while adding questions about limited sworn officers. Testing the revised questions with a range of agency types and sizes provided a defined step before asking the broader population to respond.

The second phase, contingent on positive results from the first, was the main data collection. BJS estimated that as many as 20,000 state, county, local and tribal agencies could be included. The plan therefore treated testing and full deployment as separate stages rather than assuming the revised questionnaire was ready for immediate use.

Verifying the respondent population

Alongside instrument testing, BJS planned to refine its agency universe frame. That work included verifying whether agencies were in service, checking contact information and removing duplicate entries. These tasks address a basic challenge in any census-style collection: the list of potential respondents must be sufficiently accurate for the survey to reach the intended population.

For organizations planning their own data collection, the distinction between the questionnaire and the respondent list is important. A clear instrument cannot compensate for outdated contact details or duplicate records. Similarly, an accurate list does not ensure that questions will be understood consistently. The CSLLEA plan addressed both sides of the process: the survey itself and the frame used to administer it.

What information the main collection would request

The proposed survey covered several dimensions of agency structure and activity:

  • Organization: the level of government operating the agency.
  • Resources: total operating budget.
  • Staffing: full-time and part-time counts for fully sworn officers, limited sworn officers and non-sworn employees.
  • Personnel characteristics: gender and primary job responsibility of full-time sworn officers.
  • Operations: functions performed regularly or as a primary responsibility.

This range was intended to give BJS a general profile of participating agencies, rather than focusing on one staffing category or operational function. The proposed reduction in questionnaire items, alongside the addition of questions on limited sworn officers, also illustrates the need to balance scope with manageability: a collection must cover its objectives while remaining answerable for respondents.

Planning for respondent burden

The notice estimated a 90-minute burden for each of the 48 agencies participating in cognitive testing. For the main collection, BJS estimated about 45 minutes per agency, including follow-up time. At the maximum estimate of 20,000 agencies, the full collection could amount to approximately 15,000 burden hours. Including testing, the estimated total was about 15,072 hours.

These figures were estimates presented as part of the collection proposal, not measured outcomes. They nevertheless show why burden is a planning consideration for large surveys. The notice invited comments on the burden estimate, the practical utility of the information, ways to improve its quality and clarity, and options for minimizing the effort required of respondents—including electronic submission and other technology-based methods.

Practical implications for data programs

The CSLLEA plan offers a structured example for anyone responsible for a large, multi-organization information collection. It connects several planning tasks: define the population, verify the records used to contact it, test revised questions with representative respondent groups, identify the information needed, estimate response effort and consider how the results will support later work.

For industrial automation teams, the same considerations can inform planning for operational surveys or cross-site data requests, provided the questions and conclusions are adapted to the specific application. Before requesting information from multiple facilities or stakeholders, clarify the intended use, check the respondent list, test terminology and account for the work required to provide answers. These are planning principles, not claims about the CSLLEA’s application to industrial systems.

Conclusion

The 2018 CSLLEA proposal demonstrates why effective survey data collection is a coordinated process rather than a questionnaire alone. Instrument testing, population verification, clearly scoped information requests and explicit burden estimates all formed part of the planned approach. For technical decision-makers, the practical takeaway is to plan the data frame and the respondent experience alongside the questions—especially when collected information is intended to support future analysis as well as current reporting.

Access Official Technical PDF

About The Author