Details of request “IDOC Report 2019

Event history

This table shows the technical details of the internal events that happened to this request on This could be used to generate information about the speed with which authorities respond to requests, the number of requests which require a postal response and much more.

Caveat emptor! To use this data in an honourable way, you will need a good internal knowledge of user behaviour on How, why and by whom requests are categorised is not straightforward, and there will be user error and ambiguity. You will also need to understand FOI law, and the way authorities use it. Plus you'll need to be an elite statistician. Please contact us with questions.

id event_type created_at described_state last_described_at calculated_state link
75355  sent  2020-04-22 14:02:29 +0200  waiting_response  2020-04-22 14:02:30 +0200  waiting_response  outgoing  
75579  response  2020-04-27 15:03:03 +0200        incoming  
76475  response  2020-05-11 14:27:46 +0200        incoming  
90881  edit  2020-11-12 04:45:15 +0100         
90882  edit  2020-11-12 04:45:15 +0100         
90883  edit  2020-11-12 04:45:15 +0100         
163133  edit  2022-05-12 05:45:13 +0200         
163134  edit  2022-05-12 05:45:13 +0200         
163135  edit  2022-05-12 05:45:13 +0200         
163136  edit  2022-05-12 05:45:13 +0200         
163137  edit  2022-05-12 05:45:14 +0200         
163138  edit  2022-05-12 05:45:14 +0200         

Here described means when a user selected a status for the request, and the most recent event had its status updated to that value. calculated is then inferred by for intermediate events, which weren't given an explicit description by a user. See the search tips for description of the states.

You can get this page in computer-readable format as part of the main JSON page for the request. See the API documentation.