Monitoring and Control of Staff and Payments | ||||
|
The great majority of the workforce employed in the census (particularly the fieldworkers) are unfamiliar with census work, and must learn it from scratch. Naturally, people recruited for this work are unskilled; they learn the necessary skills during the census, or more precisely, at the end of the Census. Census recruits possessed a range of abilities and experience and were from all over the country; they were recruited to what they were aware was temporary and one-time work. |
on the other, make it indispensable to maintain close and strict supervision and control over all employees. |
computer system. | ||||||||||||
System in the Census | ||||||||||||
systems: | ||||||||||||
|
all actions at all three stages of the census (drop-off, pick-up, clean-up). These records made it possible to monitor and follow up the enumerator's work, and the output and quality of the enumeration. |
|
attendance records, etc. The system allowed us to monitor and control these tasks. |
| ||||||||||||||||||||||||||||
Regional Office (RO) staff and monitoring worker performance at both RO and Sub- Regional Office (SRO) level for compliance with instructions. Similarly, ROs had responsibility for SROs in their region. | ||||||||||||||||||||||||||||
|
dropped off and picked up) at all levels: from EA level, the responsibility of an enumerator; via section level, the responsibility of a supervisor; via sub- regional level; the responsibility of a sub-regional director; via regional level, the responsibility of a regional director; to nationwide level at Census Headquarters in Jerusalem. Ongoing monitoring reports enable immediate detection of problems and, thus, enable quick response and strict adherence to schedule. It should be noted that, during the census, we detected cases of enumerators who were unable to keep to schedule; we were able to increase the pace of enumeration through reinforcement with additional enumerators. |
can be found below. |
|
EAs by difficulty of enumeration. Examples of distinctions between easy-to-enumerate EAs vs. hard-to-enumerate EAs are: EAs with communications problems due to language, detached villas vs. apartment blocks, an area where there are dogs in most of the dwellings, an area with a hostile population. The objective was to give enumerators incentive to enumerate in difficult areas by suitable financial reward. EAs were classified by three grades of difficulty -- regular, special and exceptional. The grade of difficulty was determined by a computer program according to weighting of different parameters recorded in the field (by the regional and sub-regional offices). In some cases, the computer's decision to award extra payment increased enumerator motivation; problems arose in other cases, however, when, the computers decision was not always automatically accepted in the field, and authorization from Headquarters to change the grade of difficulty was requested in order to compensate the enumerator with higher pay. |
|
contract State workers, and piece-work workers. Enumerators were piece-work workers and received their wages according to their outputs, i.e. the number of questionnaires dropped off, the number of questionnaires picked up, and the number of solutions they furnished for non-residential buildings. All other workers worked under monthly salary contracts. |
were based on ongoing records in the ERB and subsequently checked and corrected during and after enumeration. The output reports also included data such as the enumerator's personal details, the EA grade of difficulty, and the distance of the EA from the enumerator's place of residence (more or less than 15 km). Personal information provided by enumerators when hired allowed the transfer of payments direct to bank accounts as soon as the census was finished. About 90% of enumerators received payment during the month the census was completed (December 1995). |
| ||||||||||||
paper: | ||||||||||||
Copyright © 1997-1999 The State of Israel. All rights reserved.
See "Terms of Use" for the conditions
under which this service may be used.
![]()
![]() |
![]() |
![]() |
![]() |