ABARE Client Satisfaction Survey, Year Ending April 2001
Contents
I. Data Processing, Estimation, and Analysis
I1 Follow-up activities
What steps will be taken to ensure the expected response rate is achieved? (I1)
Note. Should detail what follow-up procedures are planned (such as, reminder letters, telephone follow-up of non-respondents, non-contacts, and refusals); and when and how many follow-ups will be attempted.
If the selected farm does not respond reserves are contacted until success is obtained. Sample allocation in each cell will automatically rotate through primary selections then through the reserve pool for that cell. This rotation will continue until the required quota for that cell is obtained.
Return to top
I2 Performance measures
What data collection and processing performance measures have been defined? (I2)
Note. This item is concerned with processes which are in place to ensure that the timetable deadlines will be met, for example, tracking non-contacts and refusals, responses received by date, percentage of data captured by date, percentage of data edited by date, and the like.
Completed data will be scrutinised. No follow up of non-respondents is planned. Analysis will commence as soon as all data have been entered
Return to top
I3 Data entry and coding
What quality control procedures will there be for data entry and coding? (I3)
Note. Examples of quality control procedures include: clerical scrutiny of forms, on-line edits, and the like.
Clerical scrutiny of form and on-line editing as a part of data entry process to ensure the codes are legal.
Return to top
I4 Outliers
Will outliers be identified, and, if so, how will they be handled? (I4)
Note. This item refers to the treatment of unusual or suspicious responses. It outlines treatment for responses which are found to be correct, and for responses which are found to be incorrect.
No outliers will be identified. There will be no outliers because the data sought by this survey is only attitudinal i.e. the level of satisfaction with service provided.
Return to top
I5 Aggregation of data
Will data be aggregated into statistical tables, and if so what are the estimation formulae for the principal output data items?
(I5)
Note. Should include: how adjustments for outliers, imputation and frame undercoverage factors have been incorporated into estimation formulae; the variance formulae for variances that are to be published; and the weighting strategy.
Simple aggregation, figures reported will be per cent of respondents.
Return to top
I6 Non-sampling error
What allowances will be made for potential sources of non-sampling error in estimation? (I6)
Note. Should include: allowances to be made for non-response (such as imputation procedures, analysis of non-respondents); allowances to be made in estimation for frame deficiencies (eg. use of new business provisions); and other allowances to be made for other potential sources of non-sampling error in estimation.
Return to top
I7 Analysis of results
What statistical data analysis techniques will be performed? (I7)
Note. Examples of statistical data analysis techniques include: significance testing, regression analysis, factor analysis and the like.
Simple tabulation, graphs.
Return to top
I8 Availability of results
How will the results of the survey be explained / presented to the major users? (I8)
Note. If applicable, should include: tables; analyses; unit record data; cautionary advice to assist users in interpreting the data (eg suppressing data due to high sampling variability, presenting data in the right context especially in cases of low response rates or low participation rates); and graphs.
Graphs, discussion of key results.
Return to top
I9 Systems Testing
How have the data processing, aggregation and dissemination systems been tested? (I9)
Note. This item is concerned with the testing of systems to reduce non-sampling error.
Data are processed and analysed using systems that were thoroughly tested some years ago. Minor modifications to the processing system are often made. They are tested by applications developers initially and users of the systems subsequently.
Return to top
-->
