Details of request “OLAF probes into MEPs

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
15067  sent  2015-07-10 14:38:41 +0200  waiting_response  2015-07-10 14:38:41 +0200  waiting_response  outgoing  
15543  response  2015-08-03 16:55:38 +0200    2015-08-04 18:20:29 +0200  partially_successful  incoming  
52808  overdue  2015-08-04 00:00:00 +0200         
15566  status_update  2015-08-04 18:20:29 +0200  partially_successful  2015-08-04 18:20:29 +0200  partially_successful   
15567  followup_sent  2015-08-04 18:32:32 +0200  internal_review  2015-08-04 18:32:32 +0200  internal_review  outgoing  
16038  response  2015-08-28 15:39:24 +0200        incoming  
16522  response  2015-09-23 11:58:25 +0200    2015-09-27 14:27:35 +0200  rejected  incoming  
16605  status_update  2015-09-27 14:27:35 +0200  rejected  2015-09-27 14:27:35 +0200  rejected   

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.