Details of request “Bid Tabulation Results for Improvements to Beechcroft Drive & Connecting Streets

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
919752  set_embargo    2024-05-17 09:33:30 -0400         
919753  sent    2024-05-17 09:33:30 -0400  waiting_response  waiting_response  2024-05-17 09:33:30 -0400  outgoing  
919754  public_token    2024-05-17 09:33:32 -0400         
936878  overdue    2024-05-30 00:00:00 -0400         
937244  response    2024-05-30 13:44:20 -0400        incoming  
1232150  embargo_expiring    2025-05-09 00:00:00 -0400         
1237688  expire_embargo    2025-05-17 00:00:06 -0400         
1237718  edit metadata  allow_new_responses_from  2025-05-17 03:45:08 -0400         
1237719  edit metadata  allow_new_responses_from  2025-05-17 03:45:08 -0400         
1237720  edit metadata  allow_new_responses_from  2025-05-17 03:45:08 -0400         
1237721  edit metadata  allow_new_responses_from  2025-05-17 03:45:08 -0400         
1237722  edit metadata  allow_new_responses_from  2025-05-17 03:45:08 -0400         
1237723  edit metadata  allow_new_responses_from  2025-05-17 03:45:08 -0400         
1237724  edit metadata  allow_new_responses_from  2025-05-17 03:45:08 -0400         
1623266  edit metadata  allow_new_responses_from  2026-05-31 03:45:13 -0400         
1623267  edit metadata  allow_new_responses_from  2026-05-31 03:45:13 -0400         
1623268  edit metadata  allow_new_responses_from  2026-05-31 03:45:13 -0400         
1623269  edit metadata  allow_new_responses_from  2026-05-31 03:45:13 -0400         
1623270  edit metadata  allow_new_responses_from  2026-05-31 03:45:13 -0400         
1623271  edit metadata  allow_new_responses_from  2026-05-31 03:45:13 -0400         
1623272  edit metadata  allow_new_responses_from  2026-05-31 03:45:13 -0400         
1623273  edit metadata  allow_new_responses_from  2026-05-31 03:45:13 -0400         
1623274  edit metadata  allow_new_responses_from  2026-05-31 03:45:13 -0400         
1623275  edit metadata  allow_new_responses_from  2026-05-31 03:45:13 -0400         
1623276  edit metadata  allow_new_responses_from  2026-05-31 03:45:13 -0400         
1623277  edit metadata  allow_new_responses_from  2026-05-31 03:45:13 -0400         
1623278  edit metadata  allow_new_responses_from  2026-05-31 03:45:13 -0400         
1623279  edit metadata  allow_new_responses_from  2026-05-31 03:45:13 -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.