Details of request “Building a sunroom

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
385069  sent  2025-05-25 22:55:50 +1000  waiting_response  2025-05-25 22:55:50 +1000  waiting_response  outgoing  
397238  overdue  2025-06-24 00:00:00 +1000         
397480  overdue  2025-06-24 00:00:00 +1000         
397974  overdue  2025-06-24 00:00:00 +1000         
398147  overdue  2025-06-24 00:00:00 +1000         
398366  overdue  2025-06-24 00:00:00 +1000         
398545  overdue  2025-06-24 00:00:00 +1000         
398970  overdue  2025-06-24 00:00:00 +1000         
399167  overdue  2025-06-24 00:00:00 +1000         
400228  overdue  2025-06-24 00:00:00 +1000         
400416  overdue  2025-06-24 00:00:00 +1000         
400634  overdue  2025-06-24 00:00:00 +1000         
401903  overdue  2025-06-24 00:00:00 +1000         
402085  overdue  2025-06-24 00:00:00 +1000         
402625  overdue  2025-06-24 00:00:00 +1000         
402847  overdue  2025-06-24 00:00:00 +1000         
403029  overdue  2025-06-24 00:00:00 +1000         
403387  overdue  2025-06-24 00:00:00 +1000         
404453  overdue  2025-06-24 00:00:00 +1000         
404634  overdue  2025-06-24 00:00:00 +1000         
404953  overdue  2025-06-24 00:00:00 +1000         
405192  overdue  2025-06-24 00:00:00 +1000         
405440  overdue  2025-06-24 00:00:00 +1000         
405794  overdue  2025-06-24 00:00:00 +1000         
406010  overdue  2025-06-24 00:00:00 +1000         
406238  overdue  2025-06-24 00:00:00 +1000         
406498  overdue  2025-06-24 00:00:00 +1000         
407888  overdue  2025-06-24 00:00:00 +1000         
408999  overdue  2025-06-24 00:00:00 +1000         
409159  overdue  2025-06-24 00:00:00 +1000         
409668  overdue  2025-06-24 00:00:00 +1000         
410008  overdue  2025-06-24 00:00:00 +1000         
410300  overdue  2025-06-24 00:00:00 +1000         
410783  overdue  2025-06-24 00:00:00 +1000         
411214  overdue  2025-06-24 00:00:00 +1000         
411462  overdue  2025-06-24 00:00:00 +1000         
412697  overdue  2025-06-24 00:00:00 +1000         
412916  overdue  2025-06-24 00:00:00 +1000         
413213  overdue  2025-06-24 00:00:00 +1000         
413434  overdue  2025-06-24 00:00:00 +1000         
414596  overdue  2025-06-24 00:00:00 +1000         
414817  overdue  2025-06-24 00:00:00 +1000         
415001  overdue  2025-06-24 00:00:00 +1000         
416105  overdue  2025-06-24 00:00:00 +1000         
417350  overdue  2025-06-24 00:00:00 +1000         
417643  overdue  2025-06-24 00:00:00 +1000         
417819  overdue  2025-06-24 00:00:00 +1000         
418032  overdue  2025-06-24 00:00:00 +1000         
419156  overdue  2025-06-24 00:00:00 +1000         
419542  overdue  2025-06-24 00:00:00 +1000         
419726  overdue  2025-06-24 00:00:00 +1000         
420059  overdue  2025-06-24 00:00:00 +1000         
420453  overdue  2025-06-24 00:00:00 +1000         
421490  overdue  2025-06-24 00:00:00 +1000         
421727  overdue  2025-06-24 00:00:00 +1000         
421989  overdue  2025-06-24 00:00:00 +1000         
422296  overdue  2025-06-24 00:00:00 +1000         
422581  overdue  2025-06-24 00:00:00 +1000         
410013  very_overdue  2025-07-25 00:00:00 +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.