Funds allocated to each of the "Unboxed: Creativity in the UK" projects
Dear Birmingham Organising Committee for the 2022 Commonwealth Games Ltd,
The Unboxed project has an announced budget of £120 million pounds. I would like to request the amount of money awarded to each of the ten projects that have been funded by the Unboxed festival.
The projects are:
* ABOUT US
* DANDELION
* DREAMACHINE
* GALWAD
* GREEN SPACE DARK SKIES
* OUR PLACE IN SPACE
* POLINATIONS
* SEE MONSTER
* STORYTRAILS
* TOUR DE MOON
For each of these, please list the amount of money requested (if known), and the amount of money awarded by Unboxed.
Yours faithfully,
Jonty Wareing
Dear Mr Wareing
Thank you for your Freedom of Information Act request dated 24 November 2021 which you sent to the Birmingham Commonwealth Games Organising Committee. Your request is currently being considered by the Organising Committee's subsidiary, UNBOXED, and will be dealt with under the Freedom of Information Act 2000 ('the Act').
Please be aware that the Act provides a number of exemptions which may prevent release of the information you have requested. Your request will be reviewed and if any of the exemption categories apply, then the information will not be provided.
We will send you a full response within 20 working days, either supplying you with the information which you have requested or explaining to you why we cannot supply it.
In the meantime, if you have any further queries please do not hesitate to contact me using our FOI enquiries email address at [email address].
Yours sincerely,
Stuart Skelly
STUART SKELLY
Data Protection Officer and Data Protection Legal Counsel
[email address]
Birmingham 2022 Commonwealth Games
One Brindley Place, Birmingham, B1 2JB
www.birmingham2022.com
Dear Mr Wareing
Please find attached UNBOXED’s response to your above FOI request.
Yours sincerely,
Stuart Skelly
STUART SKELLY
Data Protection Officer and Data Protection Legal Counsel
Birmingham 2022 Commonwealth Games
One Brindley Place, Birmingham, B1 2JB
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Email Disclaimer Notice
This e-mail and any files transmitted with it are private and
confidential. If you have received it in error you must not use, copy,
disclose or store the information contained within this email or
attachments. Please notify the sender immediately by using the reply
function and permanently delete what you have received. The information
contained in an email may be subject to disclosure as required by law
including under the Freedom of Information Act 2000 and any legislation
applicable in the United Kingdom with regards to the protection of
personal data. Unless the information requested is legally exempt from
disclosure, we cannot guarantee that we will not provide the whole or part
of an email to a third party making a request for information about the
content of the email. Internet e-mail is not a secure medium. Incoming and
outgoing email messages may be monitored in accordance with relevant
legislation. The statements and opinions expressed in this message are
those of the author and do not necessarily reflect those of the Birmingham
Organising Committee for the 2022 Commonwealth Games Ltd.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Dear Stuart Skelly,
I have attempted to locate the contract award notices for each of the Unboxed funded projects on the government contract finder portal, but I cannot find them.
In your previous response you stated they would be published "in the near future" - six months has passed, and I'm not sure if I am failing to use the correct search terms or if they are still yet to be published.
If the contract award notices have been published could you please provide me with the references or direct links to them?
If they have not yet been published, do you have an estimate on when they may be published?
Yours sincerely,
Jonty Wareing
Your message to [email address] couldn't be delivered.
Stuart.Skelly wasn't found at birmingham2022.com.
request-810474-de2bf. . . Office 365 Stuart.Skelly
Action Required Recipient
Unknown To address
How to Fix It
The address may be misspelled or may not exist. Try one or more of the
following:
• Send the message again following these steps: In Outlook, open this
non-delivery report (NDR) and choose Send Again from the Report
ribbon. In Outlook on the web, select this NDR, then select the link
"To send this message again, click here." Then delete and retype the
entire recipient address. If prompted with an Auto-Complete List
suggestion don't select it. After typing the complete address, click
Send.
• Contact the recipient (by phone, for example) to check that the
address exists and is correct.
• The recipient may have set up email forwarding to an incorrect
address. Ask them to check that any forwarding they've set up is
working correctly.
• Clear the recipient Auto-Complete List in Outlook or Outlook on the
web by following the steps in this article: [1]Fix email delivery
issues for error code 5.1.10 in Office 365, and then send the message
again. Retype the entire recipient address before selecting Send.
If the problem continues, forward this message to your email admin. If
you're an email admin, refer to the More Info for Email Admins section
below.
Was this helpful? [2]Send feedback to Microsoft.
══════════════════════════════════════════════════════════════════════════
More Info for Email Admins
Status code: 550 5.1.10
This error occurs because the sender sent a message to an email address
hosted by Office 365 but the address is incorrect or doesn't exist at the
destination domain. The error is reported by the recipient domain's email
server, but most often it must be fixed by the person who sent the
message. If the steps in the How to Fix It section above don't fix the
problem, and you're the email admin for the recipient, try one or more of
the following:
The email address exists and is correct - Confirm that the recipient
address exists, is correct, and is accepting messages.
Synchronize your directories - If you have a hybrid environment and are
using directory synchronization make sure the recipient's email address is
synced correctly in both Office 365 and in your on-premises directory.
Errant forwarding rule - Check for forwarding rules that aren't behaving
as expected. Forwarding can be set up by an admin via mail flow rules or
mailbox forwarding address settings, or by the recipient via the Inbox
Rules feature.
Recipient has a valid license - Make sure the recipient has an Office 365
license assigned to them. The recipient's email admin can use the Office
365 admin center to assign a license (Users > Active Users > select the
recipient > Assigned License > Edit).
Mail flow settings and MX records are not correct - Misconfigured mail
flow or MX record settings can cause this error. Check your Office 365
mail flow settings to make sure your domain and any mail flow connectors
are set up correctly. Also, work with your domain registrar to make sure
the MX records for your domain are configured correctly.
For more information and additional tips to fix this issue, see [3]Fix
email delivery issues for error code 5.1.10 in Office 365.
Original Message Details
Created Date: 5/6/2022 1:57:35 AM
Sender Address: [FOI #810474 email]
Recipient Address: [email address]
Subject: Re: Your FOI request dated 24.11.21
Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[email address] not found by SMTP
address lookup
DSN generated by: LNXP123MB3692.GBRP123.PROD.OUTLOOK.COM
Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
5/6/2022 local (Exim 4.94.2) (envelope-from
1 1:57:35 foi mstrwdtkhexa.srv.mysociety.org <[FOI #810474 email]>) *
AM
5/6/2022 esmtps
2 1:57:36 mstrwdtkhexa.srv.mysociety.org starling.ukcod.org.uk (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) 1 sec
AM (Exim 4.89) (envelope-from
<[FOI #810474 email]>)
5/6/2022 Microsoft SMTP Server (version=TLS1_2,
3 1:57:37 mailer102.ukcod.org.uk LO2GBR01FT030.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
AM
5/6/2022 Microsoft SMTP Server (version=TLS1_2,
4 1:57:37 LO2GBR01FT030.eop-gbr01.prod.protection.outlook.com LO4P123CA0473.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
AM
5/6/2022 Microsoft SMTP Server (version=TLS1_2,
5 1:57:37 LO4P123CA0473.GBRP123.PROD.OUTLOOK.COM LNXP123MB3692.GBRP123.PROD.OUTLOOK.COM cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
AM
Original Message Headers
Received: from LO4P123CA0473.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:1a8::10)
by LNXP123MB3692.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:137::13) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5206.13; Fri, 6 May
2022 01:57:37 +0000
Received: from LO2GBR01FT030.eop-gbr01.prod.protection.outlook.com
(2603:10a6:600:1a8:cafe::bf) by LO4P123CA0473.outlook.office365.com
(2603:10a6:600:1a8::10) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5206.14 via Frontend
Transport; Fri, 6 May 2022 01:57:37 +0000
Authentication-Results: spf=pass (sender IP is 46.43.39.102)
smtp.mailfrom=whatdotheyknow.com; dkim=pass (signature was verified)
header.d=whatdotheyknow.com;dmarc=pass action=none
header.from=whatdotheyknow.com;
Received-SPF: Pass (protection.outlook.com: domain of whatdotheyknow.com
designates 46.43.39.102 as permitted sender) receiver=protection.outlook.com;
client-ip=46.43.39.102; helo=mailer102.ukcod.org.uk;
Received: from mailer102.ukcod.org.uk (46.43.39.102) by
LO2GBR01FT030.mail.protection.outlook.com (10.152.42.157) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.5227.15 via Frontend Transport; Fri, 6 May 2022 01:57:37 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
d=whatdotheyknow.com; s=2020a.mysociety; h=Content-Transfer-Encoding:
Content-Type:Mime-Version:Subject:Message-ID:To:From:Date:Sender:Reply-To:Cc:
Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender:
Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id:
List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive;
bh=pt2YCEs7Cdd0p03VUawVvxK9UOQN4IutF/Chg3dArOc=; b=DwJJZPjnZbTuyPoRUPikrTG0M
6lMC1tLZgvxqTYLWwBR6KZZjnXT1DczzNnJ9jHgv2E0clQdjRUk6WqzcNQxII+7eQbwWinD/ilEzu
QmIDnOBSPWbHiSWk8Hl1iYjdq9fduImvgqGRponjhJxNXcVfvdEnxGIiHzfTIWWM10rgr+R5abJ44
/X+tOe0f+5d36DIr5erfrz2X9MKnlULusX6QTCuFmUtgTz++sxPlC17nPf2WBEUnK2n9qkMf6mPiU
CSebFZZ0vqZ+w7x9n14yye1LnZGdx2xlOaetOwHur04+GSbWiaay2fUe0iNsQmaxm1WFTM6qiJVIf
Hybn3tExw==;
Received: from mstrwdtkhexa.srv.mysociety.org ([2a00:1098:82:dd::10:1]:49494)
by starling.ukcod.org.uk with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
(Exim 4.89)
(envelope-from <[FOI #810474 email]>)
id 1nmnDs-0008Tf-6S
for [email address]; Fri, 06 May 2022 02:57:36 +0100
Received: from foi by mstrwdtkhexa.srv.mysociety.org with local (Exim 4.94.2)
(envelope-from <[FOI #810474 email]>)
id 1nmnDr-00FCjF-Pw
for [email address]; Fri, 06 May 2022 02:57:35 +0100
Date: Fri, 06 May 2022 02:57:35 +0100
From: Jonty Wareing <[FOI #810474 email]>
To: Stuart Skelly <[email address]>
Message-ID: <[email address]>
Subject: Re: Your FOI request dated 24.11.21
MIME-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Return-Path: [FOI #810474 email]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 96073eca-79ba-43ab-a522-50a25aba167e:0
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 7d627884-bbd1-445e-50ed-08da2f03cb70
X-MS-TrafficTypeDiagnostic: LNXP123MB3692:EE_
References
Visible links
1. https://go.microsoft.com/fwlink/?LinkId=...
2. https://go.microsoft.com/fwlink/?LinkId=...
3. https://go.microsoft.com/fwlink/?LinkId=...
Sent a follow up to Birmingham Organising Committee for the 2022 Commonwealth Games Limited again.
Your message to [email address] couldn't be delivered.
Stuart.Skelly wasn't found at birmingham2022.com.
request-810474-de2bf. . . Office 365 Stuart.Skelly
Action Required Recipient
Unknown To address
How to Fix It
The address may be misspelled or may not exist. Try one or more of the
following:
• Send the message again following these steps: In Outlook, open this
non-delivery report (NDR) and choose Send Again from the Report
ribbon. In Outlook on the web, select this NDR, then select the link
"To send this message again, click here." Then delete and retype the
entire recipient address. If prompted with an Auto-Complete List
suggestion don't select it. After typing the complete address, click
Send.
• Contact the recipient (by phone, for example) to check that the
address exists and is correct.
• The recipient may have set up email forwarding to an incorrect
address. Ask them to check that any forwarding they've set up is
working correctly.
• Clear the recipient Auto-Complete List in Outlook or Outlook on the
web by following the steps in this article: [1]Fix email delivery
issues for error code 5.1.10 in Office 365, and then send the message
again. Retype the entire recipient address before selecting Send.
If the problem continues, forward this message to your email admin. If
you're an email admin, refer to the More Info for Email Admins section
below.
Was this helpful? [2]Send feedback to Microsoft.
══════════════════════════════════════════════════════════════════════════
More Info for Email Admins
Status code: 550 5.1.10
This error occurs because the sender sent a message to an email address
hosted by Office 365 but the address is incorrect or doesn't exist at the
destination domain. The error is reported by the recipient domain's email
server, but most often it must be fixed by the person who sent the
message. If the steps in the How to Fix It section above don't fix the
problem, and you're the email admin for the recipient, try one or more of
the following:
The email address exists and is correct - Confirm that the recipient
address exists, is correct, and is accepting messages.
Synchronize your directories - If you have a hybrid environment and are
using directory synchronization make sure the recipient's email address is
synced correctly in both Office 365 and in your on-premises directory.
Errant forwarding rule - Check for forwarding rules that aren't behaving
as expected. Forwarding can be set up by an admin via mail flow rules or
mailbox forwarding address settings, or by the recipient via the Inbox
Rules feature.
Recipient has a valid license - Make sure the recipient has an Office 365
license assigned to them. The recipient's email admin can use the Office
365 admin center to assign a license (Users > Active Users > select the
recipient > Assigned License > Edit).
Mail flow settings and MX records are not correct - Misconfigured mail
flow or MX record settings can cause this error. Check your Office 365
mail flow settings to make sure your domain and any mail flow connectors
are set up correctly. Also, work with your domain registrar to make sure
the MX records for your domain are configured correctly.
For more information and additional tips to fix this issue, see [3]Fix
email delivery issues for error code 5.1.10 in Office 365.
Original Message Details
Created Date: 6/9/2022 1:36:15 AM
Sender Address: [FOI #810474 email]
Recipient Address: [email address]
Subject: Re: Your FOI request dated 24.11.21
Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[email address] not found by SMTP
address lookup
DSN generated by: CWXP123MB3174.GBRP123.PROD.OUTLOOK.COM
Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
6/9/2022 local (Exim 4.94.2) (envelope-from
1 1:36:15 foi mstrwdtkhexa.srv.mysociety.org <[FOI #810474 email]>) *
AM
6/9/2022 esmtps
2 1:36:16 mstrwdtkhexa.srv.mysociety.org starling.ukcod.org.uk (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) 1 sec
AM (Exim 4.89) (envelope-from
<[FOI #810474 email]>)
6/9/2022 Microsoft SMTP Server (version=TLS1_2,
3 1:36:16 mailer102.ukcod.org.uk LO2GBR01FT027.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
AM
6/9/2022 Microsoft SMTP Server (version=TLS1_2,
4 1:36:16 LO2GBR01FT027.eop-gbr01.prod.protection.outlook.com LO4P265CA0207.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
AM
6/9/2022 Microsoft SMTP Server (version=TLS1_2,
5 1:36:16 LO4P265CA0207.GBRP265.PROD.OUTLOOK.COM CWXP123MB3174.GBRP123.PROD.OUTLOOK.COM cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
AM
Original Message Headers
Received: from LO4P265CA0207.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:318::20)
by CWXP123MB3174.GBRP123.PROD.OUTLOOK.COM (2603:10a6:400:36::11) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5314.12; Thu, 9 Jun
2022 01:36:16 +0000
Received: from LO2GBR01FT027.eop-gbr01.prod.protection.outlook.com
(2603:10a6:600:318:cafe::89) by LO4P265CA0207.outlook.office365.com
(2603:10a6:600:318::20) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5332.11 via Frontend
Transport; Thu, 9 Jun 2022 01:36:16 +0000
Authentication-Results: spf=pass (sender IP is 46.43.39.102)
smtp.mailfrom=whatdotheyknow.com; dkim=pass (signature was verified)
header.d=whatdotheyknow.com;dmarc=pass action=none
header.from=whatdotheyknow.com;
Received-SPF: Pass (protection.outlook.com: domain of whatdotheyknow.com
designates 46.43.39.102 as permitted sender) receiver=protection.outlook.com;
client-ip=46.43.39.102; helo=mailer102.ukcod.org.uk; pr=C
Received: from mailer102.ukcod.org.uk (46.43.39.102) by
LO2GBR01FT027.mail.protection.outlook.com (10.152.42.153) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.5332.12 via Frontend Transport; Thu, 9 Jun 2022 01:36:16 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
d=whatdotheyknow.com; s=2020a.mysociety; h=Content-Transfer-Encoding:
Content-Type:Mime-Version:Subject:Message-ID:To:From:Date:Sender:Reply-To:Cc:
Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender:
Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id:
List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive;
bh=pt2YCEs7Cdd0p03VUawVvxK9UOQN4IutF/Chg3dArOc=; b=t6JJlcraMnba9X7aqmXVyv2kh
cGRN4PR7SDazxDM5+YWV6oIExCTrFCRbVlhg6MaRNLR4FoovNQi63Wqo2BXXN43FvkNXB6EHZroe4
osQjch9a1FXNzvDmuCH/VLQ9Z3RnRah2lw6Wo06GSgwcR54pllTp5Zo03E8GMJkbRsJfprLZSVKQR
IhHvrUXqa8PcJJA6bugMEUL1bFoCvtaf9GNzagkylTjBeJCM5PtoHmJRBQWYlFJnvW03MG3cmdUe/
1eJt+ayN9a0LKEUthPghPRxCyaDZMRqdjg0tN5ewll/19hl9jq3yL7+3InYhwA8sQOEiazn7jW6u7
qNlrIMW5Q==;
Received: from mstrwdtkhexa.srv.mysociety.org ([2a00:1098:82:dd::10:1]:58478)
by starling.ukcod.org.uk with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
(Exim 4.89)
(envelope-from <[FOI #810474 email]>)
id 1nz75s-0003od-2i
for [email address]; Thu, 09 Jun 2022 02:36:16 +0100
Received: from foi by mstrwdtkhexa.srv.mysociety.org with local (Exim 4.94.2)
(envelope-from <[FOI #810474 email]>)
id 1nz75r-002qXX-Mj
for [email address]; Thu, 09 Jun 2022 02:36:15 +0100
Date: Thu, 09 Jun 2022 02:36:15 +0100
From: Jonty Wareing <[FOI #810474 email]>
To: Stuart Skelly <[email address]>
Message-ID: <[email address]>
Subject: Re: Your FOI request dated 24.11.21
MIME-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Return-Path: [FOI #810474 email]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 96073eca-79ba-43ab-a522-50a25aba167e:0
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 68036772-7225-4ccd-3451-08da49b87238
X-MS-TrafficTypeDiagnostic: CWXP123MB3174:EE_
References
Visible links
1. https://go.microsoft.com/fwlink/?LinkId=...
2. https://go.microsoft.com/fwlink/?LinkId=...
3. https://go.microsoft.com/fwlink/?LinkId=...
We work to defend the right to FOI for everyone
Help us protect your right to hold public authorities to account. Donate and support our work.
Donate Now
WhatDoTheyKnow left an annotation ()
We suggest responding via "Actions" and selecting the option to send your follow-up to the main FOI email address for the Birmingham Organising Committee for the 2022 Commonwealth Games Ltd.
The issue appears to be with replying to the email address for individual from the body who last sent a message.