Details of request “Kommunikationsplan för stadsdelen Sigtuna Stadsängar

Event history

This table shows the technical details of the internal events that happened to this request on handlingar.se. 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 handlingar.se. 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
19  sent  2019-04-24 00:25:37 +0200  waiting_response  2019-04-24 00:25:37 +0200  waiting_response  outgoing  
20  response  2019-04-24 00:27:01 +0200    2019-04-24 00:28:22 +0200  waiting_response  incoming  
21  status_update  2019-04-24 00:28:21 +0200  waiting_response  2019-04-24 00:28:22 +0200  waiting_response   
22  response  2019-04-24 10:28:43 +0200    2019-04-24 15:39:56 +0200  waiting_clarification  incoming  
23  status_update  2019-04-24 15:39:56 +0200  waiting_clarification  2019-04-24 15:39:56 +0200  waiting_clarification   
24  followup_sent  2019-04-24 15:42:02 +0200  waiting_response  2019-04-24 15:42:03 +0200  waiting_response  outgoing  
25  response  2019-04-24 15:49:23 +0200    2019-04-24 17:42:18 +0200  waiting_response  incoming  
26  status_update  2019-04-24 17:42:18 +0200  waiting_response  2019-04-24 17:42:18 +0200  waiting_response   
27  response  2019-04-25 09:10:41 +0200    2019-05-01 23:08:24 +0200  not_held  incoming  
36  status_update  2019-05-01 23:08:24 +0200  not_held  2019-05-01 23:08:24 +0200  not_held   
2110  edit  2019-11-02 03:45:20 +0100         
2111  edit  2019-11-02 03:45:20 +0100         
2112  edit  2019-11-02 03:45:20 +0100         
2113  edit  2019-11-02 03:45:20 +0100         
2114  edit  2019-11-02 03:45:20 +0100         
2115  edit  2019-11-02 03:45:20 +0100         
2116  edit  2019-11-02 03:45:20 +0100         
2117  edit  2019-11-02 03:45:20 +0100         
2118  edit  2019-11-02 03:45:20 +0100         
2119  edit  2019-11-02 03:45:20 +0100         
5252  edit  2021-05-02 03:45:18 +0200         
5253  edit  2021-05-02 03:45:19 +0200         
5254  edit  2021-05-02 03:45:19 +0200         
5255  edit  2021-05-02 03:45:19 +0200         
5256  edit  2021-05-02 03:45:19 +0200         
5257  edit  2021-05-02 03:45:19 +0200         
5258  edit  2021-05-02 03:45:19 +0200         
5259  edit  2021-05-02 03:45:19 +0200         
5260  edit  2021-05-02 03:45:19 +0200         
5261  edit  2021-05-02 03:45:19 +0200         
5262  edit  2021-05-02 03:45:19 +0200         
5263  edit  2021-05-02 03:45:20 +0200         
5264  edit  2021-05-02 03:45:20 +0200         
5265  edit  2021-05-02 03:45:20 +0200         
5266  edit  2021-05-02 03:45:20 +0200         
5267  edit  2021-05-02 03:45:20 +0200         
5268  edit  2021-05-02 03:45:20 +0200         
5269  edit  2021-05-02 03:45:20 +0200         
5270  edit  2021-05-02 03:45:20 +0200         
5271  edit  2021-05-02 03:45:20 +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 handlingar.se 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.