Details of request “Saving the laneways of Paddington

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
320390  sent  2024-12-03 14:24:44 +1100  waiting_response  2024-12-03 14:24:45 +1100  waiting_response  outgoing  
320391  response  2024-12-03 14:25:12 +1100        incoming  
320601  response  2024-12-04 08:33:08 +1100    2024-12-11 10:43:04 +1100  waiting_response  incoming  
324451  status_update  2024-12-11 10:43:04 +1100  waiting_response  2024-12-11 10:43:04 +1100  waiting_response   
331062  overdue  2025-01-01 00:00:00 +1100         
331272  overdue  2025-01-01 00:00:00 +1100         
332113  overdue  2025-01-01 00:00:00 +1100         
332332  overdue  2025-01-01 00:00:00 +1100         
332603  overdue  2025-01-01 00:00:00 +1100         
332865  overdue  2025-01-01 00:00:00 +1100         
333158  overdue  2025-01-01 00:00:00 +1100         
333666  overdue  2025-01-01 00:00:00 +1100         
334035  overdue  2025-01-01 00:00:00 +1100         
334332  overdue  2025-01-01 00:00:00 +1100         
334580  overdue  2025-01-01 00:00:00 +1100         
335946  overdue  2025-01-01 00:00:00 +1100         
336236  overdue  2025-01-01 00:00:00 +1100         
336670  overdue  2025-01-01 00:00:00 +1100         
337132  overdue  2025-01-01 00:00:00 +1100         
338241  overdue  2025-01-01 00:00:00 +1100         
338438  overdue  2025-01-01 00:00:00 +1100         
338888  overdue  2025-01-01 00:00:00 +1100         
339101  overdue  2025-01-01 00:00:00 +1100         
339311  overdue  2025-01-01 00:00:00 +1100         
339493  overdue  2025-01-01 00:00:00 +1100         
339817  overdue  2025-01-01 00:00:00 +1100         
340200  overdue  2025-01-01 00:00:00 +1100         
340409  overdue  2025-01-01 00:00:00 +1100         
340577  overdue  2025-01-01 00:00:00 +1100         
340745  overdue  2025-01-01 00:00:00 +1100         
340958  overdue  2025-01-01 00:00:00 +1100         
341187  overdue  2025-01-01 00:00:00 +1100         
341425  overdue  2025-01-01 00:00:00 +1100         
341804  overdue  2025-01-01 00:00:00 +1100         
341992  overdue  2025-01-01 00:00:00 +1100         
342216  overdue  2025-01-01 00:00:00 +1100         
342458  overdue  2025-01-01 00:00:00 +1100         
342714  overdue  2025-01-01 00:00:00 +1100         
343065  overdue  2025-01-01 00:00:00 +1100         
347395  overdue  2025-01-01 00:00:00 +1100         
347725  overdue  2025-01-01 00:00:00 +1100         
348166  overdue  2025-01-01 00:00:00 +1100         
348335  overdue  2025-01-01 00:00:00 +1100         
349443  overdue  2025-01-01 00:00:00 +1100         
349657  overdue  2025-01-01 00:00:00 +1100         
349921  overdue  2025-01-01 00:00:00 +1100         
350595  overdue  2025-01-01 00:00:00 +1100         
350924  overdue  2025-01-01 00:00:00 +1100         
351223  overdue  2025-01-01 00:00:00 +1100         
351421  overdue  2025-01-01 00:00:00 +1100         
351648  overdue  2025-01-01 00:00:00 +1100         
351824  overdue  2025-01-01 00:00:00 +1100         
352001  overdue  2025-01-01 00:00:00 +1100         
352291  overdue  2025-01-01 00:00:00 +1100         
352686  overdue  2025-01-01 00:00:00 +1100         
342472  very_overdue  2025-02-04 00:00:00 +1100         

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.