Selection and Reporting of Official Information Act Statistics

Similar documents
Request for document related to coalition negotiations between Labour and New Zealand First

CODE OF PRACTICE Emergency Short-Term Appointments to Positions in the Health Service Executive

CAPABILITY DEVELOPMENT TOOLKIT

Australian Law Librarian

AUDITOR-GENERAL S AUDITING STANDARD 4 THE AUDIT OF PERFORMANCE REPORTS. Contents

CODE OF PRACTICE Appointment to Positions in the Civil Service and Public Service

Dealing with OIA requests involving Ministers

ACTING IN THE SPIRIT OF SERVICE Information gathering and public trust

Part 2 - Audit and Monitoring. Operational Policy

Open Government and Democracy Policy

Substantial collation or research

Access to information, public participation and access to justice in environmental matters at Community level A Practical Guide

A new optional streamlined planning process

Stakeholder Engagement Strategy

State Servants, Political Parties and Elections: Guidance for the 2005 Election Period. Issued by the State Services Commissioner

Our Privacy Principles

Customer Service Strategy

Policy Review Sheet. Review Date: 22/05/18 Policy Last Amended: 22/05/18. Next planned review in 12 months, or sooner as required.

Resource Management Act Survey of Local Authorities

A FRESH APPROACH TO THE LEGISLATION

Provider Risk Assessment and Management

Department of the Prime Minister and Cabinet

Lead Employer Flexible Working Policy. Trust Policy

JOB DESCRIPTION. Assistant Director of Operations (or nominee) Subject to child and adult workforce regulations

LONDON BOROUGH OF BARNET CODE OF CORPORATE GOVERNANCE

JOB DESCRIPTION. 1) Take a lead role in the management and leadership of both services.

TIME OFF TO TRAIN POLICY

Department of the Prime Minister and Cabinet

Register of Apprenticeship Training Agencies - Guidance for Applicants

Flexible Working Policy

Flexible Working Policy

The UK legislation is wholly retrospective and applies to all information held by public authorities regardless of its date.

Flexible Working Policy May 2017

2008 Value-For-Money Audit of the WSIB Appeals Program Executive Summary Report. March 10, Advisory Services

6. Caretaker Conventions: An Overview of New Zealand and Local Government Arrangements

Operating procedure. Managing customer contacts

CANADIAN AVIATION REGULATION ADVISORY COUNCIL (CARAC) NOTICE OF PROPOSED AMENDMENT (NPA): RESPONSIBLE AERODROME DEVELOPMENT

Natural England Standard Access to information responding to requests for information

REGULATORY IMPACT ANALYSIS

Enhancing Identity Verification and Border Processes Legislation Bill 26/10/2016

Customer Advocacy. Complaints Management Policy

The Corporation of the City of London Building Permit Review Internal Audit Report

Marketing Code of Conduct

GD 2016/0082. Council of Ministers. Considerations relating to a single resident record for the Isle of Man

Memorandum of understanding between the Competition and Markets Authority and NHS Improvement

HSE statement on radiation protection advisers

Privacy Notice. The Kind of Information We Hold About You

POSITION DETAILS Business unit Investigations Position number TBA. Location Melbourne CBD Date approved June 2017

Charities you can trust and that provide public benefit.

Public Consultation Guidelines - Electricity, Gas & Water Licences and Electricity & Gas Standard Form Contracts

10 th WORLD CONFERENCE OF THE INTERNATIONAL OMBUDSMAN INSTITUTE WELLINGTON, NEW ZEALAND, NOVEMBER 2012

JC May Joint Committee Final Report on guidelines for complaints-handling for the securities (ESMA) and banking (EBA) sectors

JC June Joint Committee Final Report on guidelines for complaints-handling for the securities (ESMA) and banking (EBA) sectors

W h i t t l e s C h a r t e r e d A c c o u n t a n t s

Trade Effluent. 19 th October 2017

Appendix 2. The Roberton recommendations

IN CONFIDENCE. Targeted Review of the Commerce Act: Initation and Financing of Market Studies

1. This Code of Conduct ( the Code ) sets out the standards that are required of IMPRESS representatives.

Produced by The School Employment Advisory Team. Tel:

Guidelines on International Regulatory Obligations and Cooperation

REVIEW REPORT September 20, 2018 Municipality of the County of Kings

Sharwood s Chinese New Year 2019 Hidden Pig promotion - Terms and Conditions

Apprenticeship End-Point Assessment Plan Regulatory Compliance Officer (Level 4)

Redundancy Policy & Procedure

3.1 The policy applies to any customer (see definition in section 6) making a complaint against Thrive Homes.

Privacy Policy PURPOSE SCOPE POLICY. Data Collection

Freedom of Information Policy

ALBERTA OFFICE OF THE INFORMATION AND PRIVACY COMMISSIONER ORDER F October 1, 2018 ALBERTA COMMUNITY AND SOCIAL SERVICES

COMPLAINT MANAGEMENT POLICY

No. Detail Page. CS 25 Organise and deliver customer service 3. CS 26 Understand the customer service environment 5

Transformation Briefing for the Minister of Revenue. November 2017

Information Commissioner of Canada

Health Sector Relationship Agreement. A tripartite framework for constructive engagement in the New Zealand Public Health and Disability Sector

FLEXIBLE WORKING POLICY

Terms of Reference. Quality and Value Audits

Re: Expert Review of Prompt Payment and Adjudication on Federal Construction Contracts

AUDIT & COMPLIANCE REPORT F18-02 City of White Rock Duty to Assist

Service Model Policy and Guidance: Customer Care Guidance 4.0. Quality and Service Integrity (Q&SI)

FSA 2.1 Third Party Verification Audit Guide for Farm Management Groups FINAL for publication 1 June 2018 (1)

NOT PROTECTIVELY MARKED. HM Inspectorate of Constabulary in Scotland. Inspection Framework. Version 1.0 (September 2014)

Redeployment Policy. Human Resources. Contents

Public sector auditing environment. Recent & current issues for WA public sector auditing

Supplementary Analysis Report: State Sector and Crown Entities Reform Bill

Bord Iascaigh Mhara s Customer Action Plan

Performance Management at Rochford District Council December 2011 PERFORMANCE MANAGEMENT AT ROCHFORD DISTRICT COUNCIL

Ontario s One-Call-to-Dig System Targeted Stakeholder Outreach - Summary of Discussions

Arts Council Customer Service Action Plan

Organisational Change

CIVIL SERVICE COMMISSIONERS FOR NORTHERN IRELAND CODE OF PRACTICE

Review of Compliance. Review completed 30 June 2015 Unclassified summary released October 2015

Her Majesty the Queen in Right of Canada, represented by the President of the Treasury Board, 2011 Catalogue No. BT22-89/2012E-PDF ISBN

COMMUNITY EMPOWERMENT (SCOTLAND) BILL

GUIDELINES FOR IMPLEMENTING A PRIVACY MANAGEMENT PROGRAM For Privacy Accountability in Manitoba s Public Sector

THEMATIC COMPILATION OF RELEVANT INFORMATION SUBMITTED BY ARMENIA ARTICLE 10 UNCAC PUBLIC REPORTING

Agreement on Employee Relations at Heriot-Watt University. 1. Vision and Statement of Intent

Board Official. Tuesday 16 October 2018 Paper No. 18/56. Freedom of Information Monitoring Report for the period 1 April 2017 to 31 March 2018

ISME GUIDE TO REDUNDANCY

REPORT UNDER THE OMBUDSMAN ACT CASE RED RIVER PLANNING DISTRICT REPORT ISSUED ON MARCH 22, 2016

Paper 3 of 4: ICT Functional Leadership. Proposal. Executive Summary. Office of the Minister of Internal Affairs

Candidate Handbook. Version 01.02

Transcription:

ACTING IN THE SPIRIT OF SERVICE: OFFICIAL INFORMATION Selection and Reporting of Official Information Act Statistics AGENCY GUIDANCE Under our commitment to Open Government, the Government has committed to publishing OIA statistics and developing a suite of consistent measures about OIA performance. This guidance is to assist agencies when developing internal policies and practices in relation to selecting, monitoring and reporting OIA statistics, with a view to ensuring consistency between agencies and over time. On 31 January 2017, the State Services Commission (SSC) published the first-ever State services-wide set of OIA statistics covering 110 agencies. This included all departments and statutory Crown Entities subject to the OIA. This first set of data covered the 2015/16 financial year and reported the number of logged OIA requests along with the number and proportion handled within the legislated timeframe. The second set of statistics were published on 5 September 2017 and covered the 2016/17 financial year. This report included OIA volume, timeliness, number of requests published on agency websites and complaints. The SSC intends to continue to publish statistics on a six monthly basis. The scope (range of reported statistics) and reach (number of agencies included) may expand over time. This guidance is in three parts: Part one Publishing OIA statistics on agency websites: outlines the State Services Commissioner s expectations of agencies when it comes to self-publishing OIA statistics. Part two Logging OIA requests: provides guidance and background on which OIA requests are to be logged for the purposes of performance monitoring and reporting. Part three Selecting OIA statistics: suggests a range of OIA statistics agencies can consider for performance monitoring and reporting, both internally and publicly. 1

PART ONE: PUBLISHING OIA STATISTICS ON AGENCY WEBSITES Agency reporting Agencies vary significantly in their size, complexity, stakeholders and core activities. There is also wide variation in the capability of the information systems agencies use to log OIA requests, capture and report OIA statistics. For these reasons, the SSC is currently limiting centrally published agency statistics to: Number of requests that were completed. Number of OIA requests the agency was unable to complete within the legislated timeframe (recognising the legislated timeframe can include extensions). Number of responses to OIA requests that were published on the agency s website. Number of complaints to the Ombudsman that were notified to the agency. Number of OIA final views formed by the Ombudsman against the agency. 1 Agencies are expected to publish these OIA statistics on their websites. The aim is to improve transparency and confidence in the openness of government. The frequency of reporting is to be determined by agencies depending on the volume of requests handled. A minimum frequency of six months is recommended, to coincide with reporting by the SSC. Those agencies with a larger volume of requests are encouraged to publish more frequently than those with fewer. Agencies are encouraged to consider which additional statistics would be of most value for the agency to collect, monitor and report; internally and publicly. Options are discussed in Part 3: Selecting OIA statistics. In particular, agencies are encouraged to consider the value of collecting and regularly reporting at least the following additional statistics: the number of requests received; the number of requests transferred in full; the number of requests withdrawn; the number of requests refused; the number of requests granted in part; the number of requests granted in full; time taken from receipt of request to despatch of the official information or decision to refuse; time taken from receipt to transfer. The first of these provides a measure of current workload. The next five can provide insight into the range of outcomes experienced by requesters as their requests are finalised. The last two provide details of the time taken to process requests. Agencies are also encouraged to provide commentary on their web-published OIA statistics. Agency commentary can provide richer context for the agency than centrally reported statistics can. Commentary could include: events and circumstances that explain variation in statistics over time; explanation of patterns in the statistics, such as the proportion of requests refused or transferred; 1 The Ombudsman concluded that the complaint (or any part of the complaint) was sustained, i.e. the Ombudsman found in favour of the requester and against the agency. This includes all final views, including cases where the Ombudsman has issued a final view in relation to delay deemed refusal. 2

discussion of differences in categories of requests and the impact on the agency s performance (See Part 3); estimates of the volume of requests for official information that are not logged and reported, the types of requests and the reasons for not logging them. (This can enhance understanding of the total number of requests for official information handled by the agency, not just the volumes reported for performance purposes. See Part 2.) PART TWO: LOGGING OIA REQUESTS Central reporting of OIA statistics has highlighted the potential for variation across agencies regarding the requests for official information that are formally logged as OIA requests. This guidance aims to promote consistency across agencies by recommending which requests for official information are to be logged, tracked and reported upon. This can enhance comparability of OIA statistics between agencies and over time. Underpinning principle Variation in agency size, complexity, work-flows, OIA request types and demand prevent development of precise criteria for specifying which OIA requests are to be logged for the purposes of monitoring and performance reporting. The underpinning principle for deciding which requests should be logged is: A request for official information will be logged when it requires considered application of the provisions of the Official Information Act 1982. For the purposes of performance monitoring and reporting, it may not be appropriate to log routine or straightforward requests that can be met immediately or without need for considered application of the Act. Which requests are not logged will vary depending on the specific context of each agency, but could include: not logging requests for publicly available information; not logging requests where the information is provided immediately and in full. Logged requests can include those where: the request is for information that may need to be withheld, in whole or part; the request is for a large volume of information that needs to be read and reviewed before a decision on release can be made; consultation (internal, with other agencies, or with affected third parties) is likely to be required before a decision on release can be made; the request could impact on the interests of a Minister or Ministers, who may need to be consulted or made aware of the decision that is taken. Each agency is to decide which requests require considered application of the provisions of the Act and are to be logged to enact this principle. 3

Different purposes for OIA statistics This section provides background and context regarding the logging of OIA requests for the purposes of performance monitoring and reporting. OIA statistics can be collected for two purposes. 1. The OIA aims to increase progressively the availability of official information to the people of New Zealand (section 4(a)), with caveats regarding preservation of personal privacy and protection of public interest (section 4(c)). This calls for statistics regarding availability of official information. 2. Commitment 2 of the Open Government Partnership New Zealand National Action Plan 2016-18 calls for a suite of consistent measures about OIA performance, in the context of We will improve government agency practices around requests for official information. This calls for statistics regarding performance, with a view to improving agency practices. Monitoring availability requires that statistics relating to access to official information should be as comprehensive as possible: striving to capture all requests for official information. This is necessary if increases in availability of official information are to be monitored over time. Monitoring performance calls for a suite of statistics that can be used to guide and monitor improvement in practices over time. For this purpose, it is not necessary to capture all requests, but to focus attention on those requests that are most likely to reflect agencies performance in administering the provisions of the Act. The relationship between these two sets of data is illustrated in Figure 1. Figure 1: Logged OIA requests as a subset of all requests All Requests for Official Information This is the universe of all requests for official information. We could seek to estimate the total number of requests for official information in order to evaluate, over time, the extent to which the Act is achieving its aim to increase progressively the availability of information to the people of New Zealand. This is about availability. Logged OIA requests This is the subset of requests that require considered application of the provisions of the OIA. We wish to measure characteristics of these requests in order to monitor and improve agency practices over time. This is about performance. In practice, performance statistics are collated from agency logs of OIA requests. This is why this guidance recommends which requests should be logged, with a view to achieving consistent and comparable OIA statistics across agencies and over time. As noted in Part 1, among other things, agencies are encouraged to self-publish estimates of the volume of requests for official information that are not logged. This can allow estimation of the total number of requests handled by the agency, thus providing insight into the availability of official information and how this is changing over time. 4

PART THREE: STATISTICS FOR PERFORMANCE MONITORING A range of possible statistics What follows is a discussion of a wide range of statistics an agency could collect regarding their OIA system. It is a starting point to encourage each agency to: reflect upon its OIA handling as a system: its characteristics and behaviour as well as performance; consider the requesters experience of that system; extend the range of OIA statistics monitored by the agency beyond those related to compliance with the Act and those reported centrally by SSC. With these factors in mind, agencies are encouraged to determine which statistics will be of most benefit for them to collect and monitor. Information flows Upon receipt, a request (which may be considered urgent by the requester) enters the agency OIA system. There are only five ways a request can be finalised and leave that system the request is either: withdrawn; transferred in full to another department, office or agency; granted in full; granted in part; or refused. While a request is under consideration by an agency, in addition to internal consultation, it may be subject to consultation with: the requester, which can result in amendment or clarification; a Minister; another department, agency or third party. Agencies may, under defined circumstances, choose to extend the time limits associated with provision of a decision. Similarly, agencies may choose to charge for supply of the official information. Finally, once a decision has been reached regarding provision of the requested information, this may be notified to a Minister, and the response may ultimately be published on the agency website. This view of an agency OIA system suggests that over any given period of time, an agency could count the number of requests subject to each of these actions, namely the number of requests: received; requesting urgent attention; amended or clarified (within or outside the legislated seven day time frame); transferred in full; transferred in part; consulted another agency or 3rd party; consulted Minister; charged; extended; withdrawn; refused; granted in part; granted in full; notified to Minister; response published on the agency website. 5

Timeliness A second group of statistics relate to timeliness of the agency s responses. From a compliance perspective, over any given period of time, an agency could count the number of requests where: the statutory or extended time-frame to reach a decision on the request was met or not met; the statutory time-frame to transfer a request was met or not met; the statutory time-frame to notify an extension was met or not met; the statutory time-frame to seek amendment or clarification was met or not met. At a more sophisticated level, an agency could measure the elapsed time, in working days (as defined by the Act) for various steps through the process. Such statistics can provide a more comprehensive picture of the distribution of elapsed time through various steps in the process. For example, agencies could measure: time taken from receipt of request to despatch of the official information; time taken from receipt of request to decision regarding release of information; time from receipt to transfer; time from receipt to seeking clarification; time from receipt to notification of extension; duration of extension; time for agency or third party response; time for Minister response; time from decision to release of information. Costs A third group of statistics relate to resources and costs. Agencies could measure: charges ($) collected; cost (labour and materials) of providing the response. Perceptions A fourth group relates to perceptions: requester perceptions of their experience; staff perceptions of their experience. Complaints The final group relates to complaints. Statistics could include the number of complaints: received by the agency; notified as having been submitted to an Ombudsman; for which the Ombudsman expressed a provisional view against the agency; for which the Ombudsman recorded a final view and made a recommendation against the agency. Timing issues For any given period (year, quarter, month, etc.) the number or requests for official information that were received during the period can be counted and reported. During the period, a number of these requests will be finalised. Others, particularly those arriving later in the period, will be incomplete at the end of the period. These will be carried forward for completion in subsequent period(s). Similarly, a number of requests from previous period(s) will be finalised during the current period. Thus, the total number of requests that are finalised during any given period can also be counted and reported. 6

Reporting on requests finalised during each period is preferred for the following reasons. 1. Every request will ultimately be counted regardless of whether it is counted upon receipt or upon finalisation. 2. When a request is finalised, all details regarding the processing of the request by the agency are known and can be reported in full: which actions it was subject to, the timeliness, etc. Classification of requests Agencies are encouraged to consider whether classification of requests might provide useful insights into the behaviour of their OIA system. If requests are classified, agencies can examine their OIA statistics for each category, which can allow patterns to be seen in the data that may otherwise be hidden. This potential insight has to be weighed against the effort and cost associated with collection and analysis of the data. There are several ways requests might be usefully classified to enable more detailed analysis of OIA performance. These include (but are not limited to): channel, gateway and requester category. Each of these is described below. Channel: by what method was the request submitted? Search of website; Phone call; Email; fyi.org.nz; Post; In person; Etc. Gateway: what was the entry point for the request? Website form; Media unit; OIA unit; General enquiries; Etc. Requester category: which category of person made the request? Individual citizen; Corporation; Media/Journalist; Member of Parliament; Political research unit; Interest group; Etc. 7