Details of request “Training policy

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
4840  sent  2013-09-09 22:42:47 +0200  waiting_response  2013-09-09 22:42:47 +0200  waiting_response  outgoing  
52041  overdue  2013-10-01 00:00:00 +0200         
5282  followup_sent  2013-10-02 23:08:41 +0200        outgoing  
5373  response  2013-10-07 17:32:04 +0200  waiting_response  2013-10-09 23:20:21 +0200  waiting_response  incoming  
55682  very_overdue  2013-10-22 00:00:00 +0200         
6117  response  2013-11-08 18:31:19 +0100  successful  2013-11-09 18:19:24 +0100  successful  incoming  

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.