Details of request “Group Certificates/PAYG payment summaries of the Department's 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
22283  sent  2017-02-06 14:41:49 +1100  waiting_response  2017-02-06 14:41:49 +1100  waiting_response  outgoing  
22597  followup_sent  2017-02-15 08:43:13 +1100        outgoing  
22823  response  2017-02-18 09:55:58 +1100        incoming  
22871  response  2017-02-20 12:30:19 +1100    2017-02-20 21:36:41 +1100  waiting_response  incoming  
22898  followup_sent  2017-02-20 21:36:32 +1100        outgoing  
22899  status_update  2017-02-20 21:36:41 +1100  waiting_response  2017-02-20 21:36:41 +1100  waiting_response   
23234  followup_sent  2017-03-01 06:35:20 +1100        outgoing  
53785  overdue  2017-03-09 00:00:00 +1100         
23574  followup_sent  2017-03-12 06:23:48 +1100        outgoing  
23701  response  2017-03-15 13:28:59 +1100    2017-03-15 18:05:37 +1100  waiting_response  incoming  
23727  followup_sent  2017-03-15 18:05:28 +1100        outgoing  
23728  status_update  2017-03-15 18:05:37 +1100  waiting_response  2017-03-15 18:05:37 +1100  waiting_response   
23769  response  2017-03-16 15:50:22 +1100    2017-03-16 20:20:20 +1100  waiting_response  incoming  
23788  followup_sent  2017-03-16 20:20:04 +1100        outgoing  
23789  status_update  2017-03-16 20:20:19 +1100  waiting_response  2017-03-16 20:20:20 +1100  waiting_response   
24366  response  2017-03-30 14:20:33 +1100    2017-04-21 18:45:29 +1000  rejected  incoming  
25179  status_update  2017-04-21 18:45:29 +1000  rejected  2017-04-21 18:45:29 +1000  rejected   
30747  followup_sent  2017-11-24 09:28:34 +1100        outgoing  
30751  response  2017-11-24 11:54:06 +1100    2017-11-24 15:44:37 +1100  waiting_clarification  incoming  
30754  followup_sent  2017-11-24 15:44:24 +1100        outgoing  
30755  status_update  2017-11-24 15:44:37 +1100  waiting_clarification  2017-11-24 15:44:37 +1100  waiting_clarification   
30862  followup_sent  2017-12-01 15:51:05 +1100  waiting_response  2017-12-01 15:51:05 +1100  waiting_response  outgoing  
30865  response  2017-12-01 17:26:15 +1100        incoming  
30948  response  2017-12-08 12:08:21 +1100    2017-12-12 07:47:23 +1100  waiting_response  incoming  
30994  followup_sent  2017-12-12 07:47:16 +1100        outgoing  
30995  status_update  2017-12-12 07:47:23 +1100  waiting_response  2017-12-12 07:47:23 +1100  waiting_response   
30998  response  2017-12-12 11:00:03 +1100    2018-01-12 07:54:13 +1100  waiting_response  incoming  
54185  overdue  2018-01-03 00:00:00 +1100         
31376  followup_sent  2018-01-12 07:54:03 +1100        outgoing  
31377  status_update  2018-01-12 07:54:12 +1100  waiting_response  2018-01-12 07:54:13 +1100  waiting_response   
31459  response  2018-01-16 10:12:41 +1100    2018-01-24 17:15:44 +1100  waiting_response  incoming  
31609  followup_sent  2018-01-24 17:15:16 +1100        outgoing  
31610  status_update  2018-01-24 17:15:44 +1100  waiting_response  2018-01-24 17:15:44 +1100  waiting_response   
31667  response  2018-01-30 21:07:51 +1100    2018-02-07 12:50:23 +1100  waiting_response  incoming  
56008  very_overdue  2018-01-31 00:00:00 +1100         
31766  status_update  2018-02-07 12:50:22 +1100  waiting_response  2018-02-07 12:50:23 +1100  waiting_response   

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.