Details of request “Ministerial Submission MS22-00569

Event history

This table shows the technical details of the internal events that happened to this request on Right to Know. 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 Right to Know. 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
240492  sent  2024-03-16 16:41:44 +1100  waiting_response  2024-03-16 16:41:44 +1100  waiting_response  outgoing  
240493  response  2024-03-16 16:42:00 +1100    2024-03-16 16:46:26 +1100  error_message  incoming  
240494  status_update  2024-03-16 16:46:25 +1100  error_message  2024-03-16 16:46:26 +1100  error_message   
241237  response  2024-03-19 15:30:45 +1100        incoming  
247229  response  2024-04-09 10:57:31 +1000    2024-04-09 12:40:54 +1000  waiting_response  incoming  
247237  status_update  2024-04-09 12:40:54 +1000  waiting_response  2024-04-09 12:40:54 +1000  waiting_response   
247238  followup_sent  2024-04-09 12:59:27 +1000        outgoing  
247251  response  2024-04-09 13:46:23 +1000    2024-04-09 14:57:01 +1000  waiting_response  incoming  
247255  status_update  2024-04-09 14:57:01 +1000  waiting_response  2024-04-09 14:57:01 +1000  waiting_response   
247256  response  2024-04-09 14:59:15 +1000    2024-04-09 15:02:32 +1000  waiting_response  incoming  
247257  followup_sent  2024-04-09 15:02:28 +1000        outgoing  
247258  status_update  2024-04-09 15:02:32 +1000  waiting_response  2024-04-09 15:02:32 +1000  waiting_response   
247259  followup_sent  2024-04-09 15:04:38 +1000        outgoing  
249501  overdue  2024-04-16 00:00:00 +1000         
249534  followup_sent  2024-04-16 19:30:28 +1000        outgoing  
251946  followup_sent  2024-04-23 13:11:26 +1000        outgoing  
253224  response  2024-04-29 15:04:09 +1000        incoming  
257305  response  2024-05-10 10:07:17 +1000    2024-05-10 13:32:27 +1000  waiting_response  incoming  
257318  status_update  2024-05-10 13:32:27 +1000  waiting_response  2024-05-10 13:32:27 +1000  waiting_response   
257319  followup_sent  2024-05-10 13:32:50 +1000        outgoing  
258421  very_overdue  2024-05-16 00:00:00 +1000         
260646  response  2024-05-23 09:02:28 +1000    2024-05-23 18:27:44 +1000  waiting_response  incoming  
260685  status_update  2024-05-23 18:27:44 +1000  waiting_response  2024-05-23 18:27:44 +1000  waiting_response   
260686  followup_sent  2024-05-23 18:28:31 +1000        outgoing  
260903  response  2024-05-24 12:51:43 +1000    2024-05-24 13:21:26 +1000  waiting_response  incoming  
260909  status_update  2024-05-24 13:21:26 +1000  waiting_response  2024-05-24 13:21:26 +1000  waiting_response   
260910  followup_sent  2024-05-24 13:23:44 +1000        outgoing  
273899  response  2024-07-12 10:38:41 +1000    2024-07-12 12:41:06 +1000  waiting_response  incoming  
273913  status_update  2024-07-12 12:41:05 +1000  waiting_response  2024-07-12 12:41:06 +1000  waiting_response   
273916  followup_sent  2024-07-12 12:45:27 +1000        outgoing  

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 Right to Know 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.