Details of request “ABS view on including 16 and 17 year olds in the Marriage Law Postal Survey

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
28599  sent  2017-08-15 07:13:51 +1000  waiting_response  2017-08-15 07:13:52 +1000  waiting_response  outgoing  
28615  response  2017-08-15 11:45:25 +1000    2017-08-15 11:46:12 +1000  waiting_response  incoming  
28616  status_update  2017-08-15 11:46:12 +1000  waiting_response  2017-08-15 11:46:12 +1000  waiting_response   
29230  response  2017-09-04 15:49:27 +1000    2017-09-04 16:03:12 +1000  waiting_response  incoming  
29232  status_update  2017-09-04 16:03:11 +1000  waiting_response  2017-09-04 16:03:12 +1000  waiting_response   
29233  followup_sent  2017-09-04 16:11:42 +1000        outgoing  
29241  response  2017-09-05 08:03:51 +1000    2017-09-05 08:33:55 +1000  waiting_response  incoming  
29243  status_update  2017-09-05 08:33:54 +1000  waiting_response  2017-09-05 08:33:55 +1000  waiting_response   
29408  response  2017-09-14 15:40:04 +1000    2017-09-15 06:05:03 +1000  partially_successful  incoming  
29409  status_update  2017-09-14 15:42:45 +1000  waiting_response  2017-09-14 15:42:46 +1000  waiting_response   
54097  overdue  2017-09-15 00:00:00 +1000         
29415  status_update  2017-09-15 06:05:02 +1000  partially_successful  2017-09-15 06:05:02 +1000  partially_successful   
29416  comment  2017-09-15 06:06:27 +1000         
29485  followup_sent  2017-09-20 16:21:28 +1000        outgoing  
29545  followup_sent  2017-09-25 12:44:48 +1000  internal_review  2017-09-25 12:44:48 +1000  internal_review  outgoing  
29546  comment  2017-09-25 13:16:23 +1000         
29566  comment  2017-09-26 20:27:48 +1000         
29581  response  2017-09-27 15:01:35 +1000    2017-09-29 15:16:20 +1000  requires_admin  incoming  
29594  followup_sent  2017-09-27 18:04:14 +1000        outgoing  
29596  comment  2017-09-28 06:49:17 +1000         
29630  status_update  2017-09-29 15:14:52 +1000  internal_review  2017-09-29 15:14:52 +1000  internal_review   
29631  status_update  2017-09-29 15:16:20 +1000  requires_admin  2017-09-29 15:16:20 +1000  requires_admin   
29636  comment  2017-09-29 20:35:23 +1000         
29637  comment  2017-09-29 22:38:59 +1000         
29647  followup_sent  2017-09-30 10:22:59 +1000  internal_review  2017-09-30 10:22:59 +1000  internal_review  outgoing  
29648  comment  2017-09-30 10:24:10 +1000         
32569  response  2018-04-13 15:15:51 +1000    2018-04-24 07:10:14 +1000  successful  incoming  
32753  status_update  2018-04-24 07:10:14 +1000  successful  2018-04-24 07:10:14 +1000  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 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.