Details of request “TDC/1617/193 - Request for Proposal for Solution Architecture Services

Event history

This table shows the technical details of the internal events that happened to this request on FYI. 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 FYI. 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 OIA 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
43687 sent 2017-08-15 15:54:27 +1200 waiting_response 2017-08-15 15:54:27 +1200 waiting_response outgoing
43695 response 2017-08-15 17:13:25 +1200 incoming
43717 response 2017-08-16 09:13:25 +1200 2017-09-06 10:55:40 +1200 waiting_response incoming
44502 status_update 2017-09-06 10:55:40 +1200 waiting_response 2017-09-06 10:55:40 +1200 waiting_response
44688 response 2017-09-12 17:17:04 +1200 2017-09-15 08:46:47 +1200 waiting_response incoming
44769 followup_sent 2017-09-15 08:46:36 +1200 outgoing
44770 status_update 2017-09-15 08:46:47 +1200 waiting_response 2017-09-15 08:46:47 +1200 waiting_response
45106 response 2017-09-28 11:07:13 +1300 2017-09-28 16:06:59 +1300 gone_postal incoming
45151 status_update 2017-09-28 16:06:59 +1300 gone_postal 2017-09-28 16:06:59 +1300 gone_postal
45152 followup_sent 2017-09-28 16:10:21 +1300 outgoing
45153 response 2017-09-28 16:17:05 +1300 incoming
45677 response 2017-10-13 15:37:07 +1300 incoming
46207 followup_sent 2017-10-30 13:47:44 +1300 outgoing
46945 response 2017-11-24 08:37:06 +1300 2018-01-17 10:35:11 +1300 rejected incoming
48467 status_update 2018-01-17 10:35:11 +1300 rejected 2018-01-17 10:35:11 +1300 rejected

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