Details of request “Procurement status and plans for eBrokerage, and/or Visit Charge Processing solutions in 2021 through 2022

Event history

This table shows the technical details of the internal events that happened to this request on WhatDoTheyKnow. 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 WhatDoTheyKnow. 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
9099264  sent  2021-04-21 17:08:34 +0100  waiting_response  2021-04-21 17:08:35 +0100  waiting_response  outgoing  
9104055  response  2021-04-22 09:51:10 +0100    2021-04-22 09:59:40 +0100  waiting_response  incoming  
9104087  status_update  2021-04-22 09:59:40 +0100  waiting_response  2021-04-22 09:59:40 +0100  waiting_response   
9145557  response  2021-04-29 16:08:00 +0100    2021-04-30 14:09:16 +0100  successful  incoming  
9146903  status_update  2021-04-30 14:09:16 +0100  successful  2021-04-30 14:09:16 +0100  successful   
9742412  edit  2021-08-01 03:47:11 +0100         
9742413  edit  2021-08-01 03:47:11 +0100         
9742414  edit  2021-08-01 03:47:11 +0100         
9742415  edit  2021-08-01 03:47:11 +0100         
9742416  edit  2021-08-01 03:47:11 +0100         

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