Details of request “Group Certificates/PAYG payment summaries of APSC SES staff - FY2013/14, FY2014/15 and FY2015/16

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
21030  sent  2016-12-22 08:27:25 +1100  waiting_response  2016-12-22 08:27:25 +1100  waiting_response  outgoing  
21053  response  2016-12-22 15:29:59 +1100    2016-12-23 08:05:51 +1100  waiting_response  incoming  
21066  status_update  2016-12-23 08:05:50 +1100  waiting_response  2016-12-23 08:05:50 +1100  waiting_response   
21384  response  2017-01-09 14:05:54 +1100    2017-01-25 07:22:00 +1100  waiting_response  incoming  
53742  overdue  2017-01-24 00:00:00 +1100         
21915  followup_sent  2017-01-25 07:21:47 +1100        outgoing  
21916  status_update  2017-01-25 07:22:00 +1100  waiting_response  2017-01-25 07:22:00 +1100  waiting_response   
21927  response  2017-01-25 11:19:07 +1100    2017-01-27 17:39:17 +1100  waiting_response  incoming  
21989  followup_sent  2017-01-27 17:39:07 +1100        outgoing  
21990  status_update  2017-01-27 17:39:17 +1100  waiting_response  2017-01-27 17:39:17 +1100  waiting_response   
22024  response  2017-01-30 08:59:12 +1100    2017-01-31 22:19:55 +1100  waiting_response  incoming  
22104  followup_sent  2017-01-31 22:19:38 +1100        outgoing  
22105  status_update  2017-01-31 22:19:55 +1100  waiting_response  2017-01-31 22:19:55 +1100  waiting_response   
22109  response  2017-02-01 09:26:28 +1100    2017-02-01 19:13:16 +1100  waiting_response  incoming  
22133  followup_sent  2017-02-01 19:13:06 +1100        outgoing  
22134  status_update  2017-02-01 19:13:15 +1100  waiting_response  2017-02-01 19:13:15 +1100  waiting_response   
22856  response  2017-02-20 10:59:24 +1100    2017-02-20 20:35:28 +1100  waiting_response  incoming  
22896  followup_sent  2017-02-20 20:34:40 +1100        outgoing  
22897  status_update  2017-02-20 20:35:28 +1100  waiting_response  2017-02-20 20:35:28 +1100  waiting_response   
55712  very_overdue  2017-02-21 00:00:00 +1100         
22902  comment  2017-02-21 09:25:35 +1100         
22940  response  2017-02-22 09:11:28 +1100    2017-02-24 13:16:52 +1100  waiting_response  incoming  
23060  followup_sent  2017-02-24 13:16:42 +1100        outgoing  
23061  status_update  2017-02-24 13:16:52 +1100  waiting_response  2017-02-24 13:16:52 +1100  waiting_response   
24020  followup_sent  2017-03-22 18:45:23 +1100        outgoing  
24189  response  2017-03-27 16:03:25 +1100    2017-04-17 22:14:33 +1000  rejected  incoming  
24996  status_update  2017-04-17 22:14:33 +1000  rejected  2017-04-17 22:14:33 +1000  rejected   
24997  comment  2017-04-17 22:24:44 +1000         

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.