Details of request “Our Chance to go back to HK before the 36th months absence is about to expire next April 2022

Event history

This table shows the technical details of the internal events that happened to this request on AccessInfoHongKong. 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 AccessInfoHongKong. 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 details created_at described_state calculated_state last_described_at link
11686  sent    2022-03-17 10:56:05 +0800  waiting_response  waiting_response  2022-03-17 10:56:05 +0800  outgoing  
11827  response    2022-03-24 15:10:13 +0800    internal_review  2023-05-16 09:50:40 +0800  incoming  
11922  status_update  described_state  2022-03-29 18:04:53 +0800  partially_successful  partially_successful  2022-03-29 18:04:53 +0800   
15349  edit metadata  allow_new_responses_from  2022-09-30 11:45:10 +0800         
15350  edit metadata  allow_new_responses_from  2022-09-30 11:45:10 +0800         
15351  edit metadata  allow_new_responses_from  2022-09-30 11:45:10 +0800         
19119  status_update  described_state  2023-05-16 09:50:40 +0800  internal_review  internal_review  2023-05-16 09:50:40 +0800   

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