Details of request “Kubaza niba indangamuntu isimbura iyatakaye yari ifite nomero: 1200280066452093 yarakozwe naho yoherejwe.

Event history

This table shows the technical details of the internal events that happened to this request on Sobanukirwa. This could be used to generate information about the speed with which agencies 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 Sobanukirwa. 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 ATI law, and the way agencies 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
3466  sent  2022-05-23 17:48:03 +0200  waiting_response  2022-05-23 17:48:03 +0200  waiting_response  outgoing  
3470  response  2022-05-24 08:37:25 +0200    2022-05-24 09:59:44 +0200  waiting_response  incoming  
3471  status_update  2022-05-24 09:59:44 +0200  waiting_response  2022-05-24 09:59:44 +0200  waiting_response   
3473  response  2022-05-25 12:48:03 +0200    2022-05-29 11:14:41 +0200  partially_successful  incoming  
3475  followup_sent  2022-05-29 11:13:59 +0200        outgoing  
3476  status_update  2022-05-29 11:14:41 +0200  partially_successful  2022-05-29 11:14:41 +0200  partially_successful   

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 Sobanukirwa 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.