corrections at statistics sweden
DESCRIPTION
Corrections at Statistics Sweden. Cecilia Westström Communication Department 2010-06-30. Background. ”The shoe problem” 2008 lead to requirement for new process Guidelines produced in 2009 Clarified organisation within Statistics Sweden Communication Department – coordinate handling - PowerPoint PPT PresentationTRANSCRIPT
Corrections at Statistics Sweden
Cecilia Westström
Communication Department
2010-06-30
Background
• ”The shoe problem” 2008 lead to requirement for new process
• Guidelines produced in 2009• Clarified organisation within Statistics Sweden
• Communication Department – coordinate handling• Process Department - receives reports of errors and
analyses reasons
• Our experiences, reactions from users, other statistical offices,...
• Need to adjust guidelines for handling of errors
Principles
• Openness about errors and corrections• Errors should be corrected as quickly as possible• Handling varies depending on the type of product
and how serious the error is• The user's perspective is the determining factor for
assessing the seriousness of the error• Corrections should be visible and give relevant
information
Proposal for handling of errors• Major (significant) errors in our most important products
(CPI, LFS, GDP)• Notify that an error has occurred• Remove the incorrect information• Decision to publish on a certain day at 09:30• Inform important users separately (but at the same time as
information about the error is published !)• Inform internally
• Minor errors in our most important products• Publish at 09:30 but without notification in advance
• Other products• Notify about major errors locally on the website (product page)
• Make corrections as soon as possible
Issues
• Speed versus simultaneity• Simultaneity is important in standard publishing of
statistics and therefore an issue in corrections• Simultaneity is crucial for stock market affecting stat
• Removing the incorrect information quickly versus creating uncertainty among users• We have tried ”remove everything” but now more
restricted
• Informing about ”everything” versus adapting to the needs of users • Push for most important errors, pull for the rest