In this chapter
The purpose of this chapter is to describe the additional procedures and assumptions used to move from the time estimates presented in Chapter III, but displayed again in Exhibit 9 below, to a proposed, updated staffing standard. The chapter concludes with a proposed, updated staffing standard and a comparison of it to the existing standard. Table 4.1. Exhibit 9: Minutes Required to Complete Child Support Processes
There are five steps to building a staffing standard from the time estimates presented in Exhibit 9 above. They are summarized below. Step 1 Count or estimate the number of completed processes displayed in Exhibit 9. This considers the total number of completed processes in calendar year (CY) 1999 for each County participating in the focus groups. Step 2 Multiply the average time estimate for each process by the number of processes completed to determine staffing needs. For example, say County X established 100 support orders administratively last year and it takes 5 hours on average to establish an administrative order. By multiplying 5 hours by 100 support orders, we find 500 hours of staff time per year are needed to achieve this outcome. This is repeated for each process within a function and for each County participating in the focus groups to develop the total number of hours of staff time by function. Step 3 Adjust for time not spent directly on processes (e.g., staff meetings) and convert hours into FTEs by considering holidays and other non-work time. Step 4 Relate hours needed to caseload by function. For example, if 3 FTEs are needed to perform all establishment processes and there are 900 cases without orders, the staffing standard is 300 non-ordered cases per FTE. Step 5 Make additional adjustments for supervisors and managers and other support functions (i.e., fiscal, customer service and ACSES liaison). Most of the counts of processes were taken from summing the outcomes displayed in Monthly Management Report 410 (MM-410) for calendar year 1999. The data source and assumptions for each process are discussed in greater detail below by function. In the discussion, we use the following conventions: For this function, the major process is intake. In Exhibit 9, which lists the processes considered in the focus groups and time logs, intakes were broken down by IVA status, foster care, and other statuses. Although “new” cases are recorded separately for IVA/IVE and NIVA/NIVE on the MM-410 report, a new case does not necessarily mean “intake” for NIVA/NIVE cases. A closed IVA/IVE case may be reopened as NIVA/NIVE case and counted as a “new” NIVA/NIVE case. To circumvent this problem, we considered two different definitions of “intake.”
The two different counts result in negligible differences. Thus, we use the first definition for intake and make no distinction between IVA/IVE and NIVA/NIVE intakes (Activities 1 and 2). Using this definition will also make it less burdensome to calculate in subsequent updates. The existing management reports do not discern between Foster Care, Interstate and Medicaid intakes, although separate time estimates were developed in the focus groups and time logs for these classifications (Activities 3, 6 and 7). Since these are subgroups under either IVA/IVE or NIVA/NIVE “new” cases, those under NIVA/NIVE would be subject to the same problem of former IVA/IVE cases reopening as NIVA/NIVE. Furthermore, because the amount of time required to perform a Foster Care intake (96 minutes), Interstate intake (100 minutes) and Medicaid Intake (119 minutes) are somewhat less, but close to the amount of time required to perform NIVA/NIVE and IVA/IVE intakes (131 and 129 minutes, respectively), we use the umbrella categories, NIVA/NIVE and IVA/IVE. In effect, this overestimates the time required for intake, but for the purposes of developing a staffing standard, we would rather err on the high side of the estimate. The remainder of the activities performed in the intake function are: non-cooperation and good cause (Activities 4 and 5 from Exhibit 9, respectively). The numbers of non-cooperation and good cause determinations are not recorded by county. They are only recorded on Colorado’s submission of form OCSE-157. There were 424 determinations of non-cooperation and 57 determinations of good cause during Federal Fiscal Year 1999. Because of the small State number and the lack of County-specific numbers, good cause is not included in the derivation. Non-cooperation, which also may occur in the establishment function, is considered at that stage of case processing rather than inferring how many non-cooperation determinations occur in intake relative to the establishment function. Table 4.2. Number of Completed Intake Processes[a]
The average amount of time for locating an address (Activity 8) is multiplied by the “verified locates: addresses” for IVA/IVE, NIVA/NIVE and FAD cases on page 3 of the MM-410. The average amount of time for locating assets (Activity 10) is multiplied by the “verified locates: assets” listed on the same page of the MM-410. The MM-410 information is captured for CY1999. Table 4.3. Number of Completed Locate Processes
The focus groups and time logs captured time estimates for 11 establishment processes, several of which are variations of order establishments. This included several sub-categories of establishment: (a) paternity and financial order establishment; (b) judicial and administrative process; and (c) responding and initiating interstate. With the exception of paternity and order establishments, and to a limited degree APAs, these distinctions are not made in any monthly management reports. Page 3 of the MM-410 provides counts for order establishments and paternity establishments. The former is by number of orders and the latter is by the number of children. Both counts are listed for IVA/IVE, NIVA/NIVE and FAD separately. For the purposes of developing a staffing standard, all three counts for each activity are totaled for CY1999. Existing management reports do not tell us which orders are established administratively and which are established judicially. The MM-410, however, does list the number of APAs on page 3. We assume the difference between APAs and order establishments are judicial orders. (This adjustment accounts for Activities 11, 12 and 15 in Exhibit 9.) We use the ratio of APAs to judicially established orders to apportion the number of paternities into those established through APA and those established judicially. Responding and initiating interstate establishments (Activities 13, 14 and 16) are not available on any existing management reports, so no distinction regarding interstate status is made. Nevertheless, we do not believe this is a necessary distinction because the time difference in establishing interstate and intrastate orders appears to be negligible. Case management has no measurable outcome. It includes follow-up telephone conversations with parents and enforcement technicians in other Counties and States whenever necessary. It also includes reviewing monthly and weekly reports (e.g., monthly caseload listings). It is considered in Step 3 along with other staff time not spent directly on processes. As discussed earlier, non-cooperation (Activity 18 of Exhibit 9) is not available in any monthly management report by county; however, the total for the State is provided in form OCSE-157. This number is attributed to each county by its respective share of the total State caseload. The number of case closures (Activity 19) is from the MM-430 rather than the MM-410, which has been the data source for all activities discussed thus far. Similar to most of the counts, they are listed separately by IVA/IVE and NIVA/NIVE status and are totaled for CY1999. Because case closure is also an enforcement function, only a share of them are assigned to establishment. They are assigned in the same ratio as court actions, which is discussed later. Genetic testing is not considered in this step for two reasons. First, the number of genetic tests performed (Activity 20) is not provided in any existing management report. Second, the focus groups considered genetic testing as part of establishing a paternity order. The final establishment process (Process 21 in Exhibit 9) is court hearing preparation. Court orders filed for IVA/IVE, NIVA/NIVE and FAD cases, which are listed on page 3 of the MM-410, are used to count this process. However, because a court hearing preparation is also an enforcement function, we prorated the number of establishment court orders filed by using the ratio of estimated judicially established orders to the number of total orders established. Table 4.4. Number of Completed Establishment Processes
There are nine enforcement activities displayed in Exhibit 9. The first two activities listed, income withholdings (Activity 22) and review and adjustment (Activity 23), have counts available from page 7 of the Monthly Monitoring Report. Enforcement Case Management. Similar to establishment case management, enforcement case management (Activity 24) has no measurable outcome, thus is considered in Step 3 along with other staff time not directly spent on processes. It includes staff time dedicated to monthly management reports such as the MW-530 (caseload listings) and EM-100 Credit Reporting Agency Notification reports. Case Closure. Case closure (Activity 25) under the enforcement function includes the remainder of the total case closures that are not included as an establishment function. Number of HIPs. Medical support (Activity 26) is typically sought in conjunction with income assignment, thus the same count available for income assignments from the Monthly Monitoring Reports is applied. Number of Non-Cooperations. Non-cooperation (Activity 27), which is not available at the County level, but estimated from State data in the establishment function, is not considered in the enforcement function. All non-cooperation cases are assumed to occur in establishment. Number of Administrative Enforcement Activities. Most administrative enforcement activities (Activity 28) consist of reviewing reports generated by the state (e.g., license suspension) and are included in the add-on for enforcement case management in Step 3. Number of Court Hearing Preparations. Since this is also an establishment process, the difference between the total number of court filings and the amount applied to establishment are considered enforcement. Number of Contempts. The number of contempt citations filed by county is recorded on page 7 of the Monthly Management Reports.
Number of Interstate Actions. The number of completed interstate actions is based on the total number of initiating reciprocal actions reported on page 3 of the MM-410. Table 4.5. Number of Completed Enforcement Processes
No additional assumptions were necessary to complete Step 2 with the exception of dividing the total number of orders established in Grand County between administratively and judicially established orders. The number of APAs in Grand County exceeded the number of orders established, so we assumed that all orders were established administratively in Grand County. Nonetheless, the number of APAs in Grand County could have exceeded the number of order establishments because it included modifications. No additional adjustment was made for this. County IV-D directors and supervisors were asked about the number of paid holidays and vacation time. Most of the counties have 11 paid holidays and two to three-weeks of paid vacation. In developing the staffing standard, we assumed 11 paid holidays and three-weeks of paid vacation. County IV-D directors and supervisors also were asked how many hours staff spend in meetings and training. The responses varied widely among Counties and even among teams within the same County. As a result, we assumed 80 hours per year, which was toward the high-end of the estimates. We made an additional adjustment for vacancies. The vacancy rate averaged 8 percent in the counties participating in the focus groups. As evident in Exhibit 10, when all factors are considered, we estimate that there are 1,630 available work hours per year per FTE to work directly on processes. (This is approximately 86 percent of total paid time.) The Virginia Staffing Standard assumes 1,372 staff hours available per year before vacancies[23]. Since Virginia’s vacancy rate is also 8 percent, this further reduces the total number of hours per year available to work directly on processes in Virginia to 1,210 hours (58 percent of total hours available). This is considerably less than what is shown in Exhibit 10 for Colorado, but Virginia did not separate out the extensive establishment and enforcement case management that was captured in the Colorado focus groups. If Virginia has excluded case management time from its calculations, the estimate of available work time would be higher. Table 4.6. Exhibit 10: Estimated Work Hours per Year Available to Perform Processes
The time logs also provide some indication of the proportion of time available to directly work on processes and that information supports our higher estimate of available work time. For the three sites recording time logs, the proportion of time spent working directly on processes was calculated at 67 percent, 87 percent, and 88 percent. We assumed that intake and locate technicians could work 75 percent of their time directly on processes. For establishment and enforcement technicians, we assumed 1,630 hours per year available to work directly on processes, but added hours for daily and monthly case management, which amounted to about three to four hours per day. The specific amounts added are based on the hours per day required for establishment and enforcement case management (Activities 17 and 24). There were no additional assumptions necessary for fiscal and customer service staff because they are related directly to caseload. Caseloads were derived from the MM-410 reports for CY1999.
The caseload for each function was divided by the total number of minutes required to complete each of the processes within that function, which was calculated in Step 2. This was done individually for each county that participated in the focus groups. We used an average for all the counties as the staffing standard. Other functions considered in this task are fiscal activities, customer service and ACSES liaison. In this step, we also add supervisors and managers and address the small county add-on. Fiscal Activities. Staffing for fiscal activities is based on information from the focus groups. Since no measurable outcomes for fiscal activities exist, we developed a caseload standard directly. Our approach was to take the number of ordered cases divided by the average number of hours per day (converted to FTEs) spent on fiscal activities. As shown in Appendix E, the number of ordered cases per fiscal FTE averages 2,040 cases and ranges from 1,299 to 2,424 ordered cases per fiscal FTE. Customer Service. As discussed earlier, customer service is one of the most difficult functions to define precisely. It is particularly difficult in the smaller counties where customer service is entangled with intake, establishment and enforcement processes. To add further difficulty, it is similar to fiscal activities in that there are no measurable outcomes. As a result, we developed a caseload standard similar to fiscal activities. To do that, we used total caseload because some customer activities (e.g., Denver County’s staff person dedicated to handling walk-ins) may involve spending time on ordered and non-ordered cases. As evident in Appendix E, the number of cases per customer service FTE averages 1,869 cases and ranges from 848 to 3,194 cases per customer service FTE. Due to the wide range, we discussed the issue with the MIG Advisory Group. They recommended using 1,500 cases per customer services FTE, which is closer to the median shown in Appendix E. ACSES Liaison. Per the recommendation of the MIG Advisory Group, an additional adjustment for the ACSES Liaison was added to the standard later. An e-mail was sent to the ACSES County Users Group requesting they send estimates to project staff about the average amount of time spent on ACSES Liaison duties. Some of the ACSES Liaison duties include the following:
Four counties responded to the survey. The number of cases per ACSES Liaison FTE equivalent they reported were 8,915; 116,408; 9,778; and 15,576, respectively. We eliminated the highest estimate to arrive at an average number of cases of 11,423. We rounded this number to 11,400 cases per ACSES Liaison. Supervision and Management. Assumptions about management and supervision are based on (a) existing staffing levels for those positions, (b) experiences at other child support offices, and (c) a discussion with the MIG advisory group. The recommended staffing levels for supervision and management are: Small County Add-On. We found little evidence in our work to justify a small county add-on. With the exception of customer services, the time estimates for the processes showed no major departure by county size. With respect to customer service, smaller counties had a higher ratio of cases to customer service hours in the focus groups. (That pattern was not evident in the time logs, however.) When presented with this issue, the MIG Advisory Group recommended a limited small county add-on: the minimum number of staff for a county would be 1.0 FTE. That is, if the staffing formula resulted in a staff level of 0.5 FTE, the number would be increased to 1.0 FTE. The basis for this recommendation is that it would be difficult to fill a part-time position. Exhibit 11 summarizes the staffing standard developed in this chapter. It provides three options: For comparison purposes, the existing standard is also displayed in the exhibit. The effects of these proposed staffing standards on Counties are also displayed in Appendix G. Table 4.7. Exhibit 11: Proposed Staffing Standards
[23] Omni Systems Inc. Staffing Standards Analysis of the Virginia Department of Social Services Child Support and Enforcement Program, Report to the Virginia Department of Social Services, Jasper, Georgia (December 29, 1995) page 9.
Download FREE Adobe Acrobat® Reader™ to view PDF files located on this site.
OCSE Home
|
Press Room
|
Events Calendar
|
Publications
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||