Details of request “Water & Sewer Bills

Event history

This table shows the technical details of the internal events that happened to this request on OPRAmachine. 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.

Be careful! To use this data in an honourable way, you will need a good internal knowledge of user behaviour on OPRAmachine. 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
6872  sent    2018-02-07 14:27:14 -0500  waiting_response  waiting_response  2018-02-07 14:27:14 -0500  outgoing  
6882  response    2018-02-07 16:14:30 -0500    waiting_response  2018-02-11 18:51:38 -0500  incoming  
6958  status_update    2018-02-11 18:51:38 -0500  waiting_response  waiting_response  2018-02-11 18:51:38 -0500   
7068  response    2018-02-14 14:48:42 -0500    waiting_response  2018-02-16 10:16:10 -0500  incoming  
7121  followup_sent    2018-02-16 10:15:36 -0500        outgoing  
7122  status_update    2018-02-16 10:16:10 -0500  waiting_response  waiting_response  2018-02-16 10:16:10 -0500   
7126  response    2018-02-16 12:48:34 -0500    waiting_response  2018-02-16 13:15:39 -0500  incoming  
7133  followup_sent    2018-02-16 13:15:19 -0500        outgoing  
7134  status_update    2018-02-16 13:15:39 -0500  waiting_response  waiting_response  2018-02-16 13:15:39 -0500   
7141  response    2018-02-16 15:46:05 -0500    waiting_response  2018-02-20 11:01:32 -0500  incoming  
7144  status_update  described_state  2018-02-16 16:43:51 -0500  requires_admin  requires_admin  2018-02-16 16:43:51 -0500   
7173  overdue    2018-02-17 00:00:00 -0500         
7167  status_update  described_state  2018-02-20 11:01:32 -0500  waiting_response  waiting_response  2018-02-20 11:01:32 -0500   
7175  followup_sent    2018-02-21 01:27:38 -0500  internal_review  internal_review  2018-02-21 01:27:39 -0500  outgoing  
7256  status_update    2018-02-26 13:10:55 -0500  internal_review  internal_review  2018-02-26 13:10:55 -0500   
7257  followup_sent    2018-02-26 13:33:00 -0500  internal_review  internal_review  2018-02-26 13:33:00 -0500  outgoing  
7289  response    2018-02-27 14:45:17 -0500    waiting_response  2018-02-27 19:50:03 -0500  incoming  
7291  followup_sent    2018-02-27 19:49:18 -0500        outgoing  
7292  status_update  described_state  2018-02-27 19:50:03 -0500  waiting_response  waiting_response  2018-02-27 19:50:03 -0500   
7305  followup_sent    2018-02-28 12:34:23 -0500        outgoing  
7355  response    2018-03-02 14:42:07 -0500    partially_successful  2018-03-02 16:11:44 -0500  incoming  
7359  followup_sent    2018-03-02 16:02:28 -0500        outgoing  
7360  status_update  described_state  2018-03-02 16:11:44 -0500  partially_successful  partially_successful  2018-03-02 16:11:44 -0500   
7371  response    2018-03-05 10:24:27 -0500    partially_successful  2018-03-13 16:07:49 -0400  incoming  
7464  status_update  described_state  2018-03-08 14:01:04 -0500  successful  successful  2018-03-08 14:01:04 -0500   
7565  followup_sent    2018-03-13 16:07:07 -0400        outgoing  
7566  status_update  described_state  2018-03-13 16:07:49 -0400  partially_successful  partially_successful  2018-03-13 16:07:49 -0400   
7585  followup_sent    2018-03-14 13:28:14 -0400  internal_review  internal_review  2018-03-14 13:28:14 -0400  outgoing  
7706  response    2018-03-20 10:15:54 -0400    successful  2018-03-26 11:44:53 -0400  incoming  
7828  status_update  described_state  2018-03-26 11:44:53 -0400  successful  successful  2018-03-26 11:44:53 -0400   

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