Details of request 'Will the Legal Dispute between SCC and SW1 be heard in a public court?'

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
660145 sent 2012-12-13 17:10:24 +0000 waiting_response 2012-12-13 17:10:24 +0000 waiting_response outgoing
661202 response 2012-12-17 09:37:54 +0000 waiting_response 2012-12-17 10:05:37 +0000 waiting_response incoming
661368 response 2012-12-17 12:05:41 +0000 incoming
661370 response 2012-12-17 12:08:54 +0000 incoming
661374 response 2012-12-17 12:11:12 +0000 waiting_response 2012-12-17 12:56:00 +0000 waiting_response incoming
675564 followup_sent 2013-01-15 16:32:29 +0000 outgoing
676031 followup_sent 2013-01-16 11:33:28 +0000 outgoing
676033 followup_sent 2013-01-16 11:34:31 +0000 outgoing
676063 response 2013-01-16 11:51:59 +0000 waiting_response 2013-01-16 12:00:55 +0000 waiting_response incoming
677104 response 2013-01-17 15:31:26 +0000 2013-01-18 13:59:47 +0000 partially_successful incoming
677777 followup_sent 2013-01-18 13:59:41 +0000 partially_successful outgoing
677779 followup_sent 2013-01-18 14:01:06 +0000 outgoing
677781 followup_sent 2013-01-18 14:01:43 +0000 outgoing
677954 response 2013-01-18 16:40:46 +0000 waiting_response 2013-01-18 16:53:40 +0000 waiting_response incoming
678723 response 2013-01-21 11:25:16 +0000 waiting_response 2013-01-21 19:22:06 +0000 waiting_response incoming
679616 response 2013-01-22 13:19:04 +0000 waiting_response 2013-01-22 19:27:01 +0000 waiting_response incoming
691791 response 2013-02-11 12:17:24 +0000 rejected 2013-02-11 13:55:42 +0000 rejected incoming
691937 followup_sent 2013-02-11 13:57:11 +0000 outgoing
692227 followup_sent 2013-02-11 17:17:08 +0000 internal_review 2013-02-11 17:17:08 +0000 internal_review outgoing
692228 response 2013-02-11 17:17:18 +0000 internal_review 2013-02-11 17:34:27 +0000 internal_review incoming
692436 response 2013-02-12 09:23:39 +0000 internal_review 2013-02-12 10:23:16 +0000 internal_review incoming
701372 response 2013-02-26 16:06:08 +0000 internal_review 2013-02-26 16:12:17 +0000 internal_review incoming
701384 followup_sent 2013-02-26 16:14:26 +0000 outgoing
701678 response 2013-02-27 09:50:29 +0000 rejected 2013-03-26 15:31:37 +0000 not_held incoming
701716 followup_sent 2013-02-27 10:25:06 +0000 outgoing
715997 followup_sent 2013-03-24 17:38:20 +0000 outgoing
717770 followup_sent 2013-03-26 15:31:03 +0000 not_held outgoing

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.