Data of how direct payments are being used by users

Dean made this Freedom of Information request to North Lincolnshire Council Automatic anti-spam measures are in place for this older request. Please let us know if a further response is expected or if you are having trouble responding.

The request was partially successful.

Dear North Lincolnshire Council,

Could you provide any data you hold regarding what direct payments are specifically being used for by users? The more comprehensive and specific this list is, the better. For example, data showing DPs being used for a gym membership would be more useful and insightful than data showing DPs being used for "leisure activities" which would be too broad and nonspecific.

If you require dates to extract this data could you extract it from the last five financial years as follows:

• 2018-2019
• 2019-2020
• 2020-2021
• 2021-2022
• 2022-2023

I appreciate that this data might be quite vast. If this is the case then please prioritise all types of direct payments which are NOT used for personal assistants. This should adequately refine your search to a more manageable size. Does this make sense? Please get in touch if you require further clarification.

Yours faithfully,

Dean

Information Governance Team,

Dear Dean,

Thank you for your request which was received on 17th May. The estimate
response date for your request is the 15th June.

Should you have any queries, amendments or additions relating to this
request, please remember to quote the reference number above in any future
communications.

Yours Faithfully

Information Governance Team
North Lincolnshire Council

Dear Information Governance Team,

I have further refined my request which I have included in full below. I hope this helps.

☆For the attention of Adult Social Services☆

The term data in the heading above refers to the actual activity/service/goods that a direct payment was/is used for and not just the broader category that it falls within. Of course, the broader category can be included as well. Where direct payments are used for personal assistants (PA), these can be excluded from the dataset.

The primary purpose of this request is to receive a full breakdown of how individual users spend their direct payments. The amount of each payment would be very useful but not essential. The total direct payment amount each person receives is useful though and this can be displayed weekly or monthly or whichever is easiest for you.

So, to re-iterate, please provide all data in relation to how direct payments are specifically being used by users aged 24 - 54 and all other age groups can be excluded. The more comprehensive and detailed this list is, the more useful it will be for this FOI request. For example, data showing DPs being used for a gym membership (including how much it costs) would be far more valuable than data showing DPs being used for "leisure activities" which would be too broad; nonspecific and unhelpful.

If you require dates to extract this data could you extract it from either of the following financial years (preferably both):

• 2018-2019
• 2022-2023

I appreciate that this data can be quite laborious at times, especially if extracting the data from a manual trawl of individual care and support plans. It may or may not be easier to consider past audits and current monitoring systems to extract the same data and always remember to keep it within the age parameters of 24 - 54 which should exclude the majority of users.

To compliment the core request, could you kindly send me your direct payments policy including your practice guidance for practitioners. Could you also send me your Care and Support Planning Policy along with your practice guidance for practitioners. Please send any other policies you feel are relevant or related to the policies and practice guidance documents requested above.

Yours sincerely,

Dean

North Lincolnshire Council

2 Attachments

Your message to [email address] couldn't be delivered.
request wasn't found at ig.northlincs.gov.uk.
request-981732-051e8. . . Office 365 request
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/7/2023 7:29:29 PM
Sender Address: [FOI #981732 email]
Recipient Address: [email address]
Subject: Re: Freedom of Information Case FOI2023/00750
Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[email address] not found by SMTP address
lookup
Message rejected CWLP265MB2465.GBRP265.PROD.OUTLOOK.COM
by:
Notification Details
Sent by: CWLP265MB2465.GBRP265.PROD.OUTLOOK.COM

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
6/7/2023 local (Exim 4.94.2) (envelope-from
1 7:29:29 foi mstrwdtkhexa.srv.mysociety.org <[FOI #981732 email]>) *
PM
6/7/2023 esmtps (TLS1.3) tls
2 7:29:29 mstrwdtkhexa.srv.mysociety.org mslb001hexa.srv.mysociety.org TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim *
PM 4.94.2) (envelope-from
<[FOI #981732 email]>)
6/7/2023 Microsoft SMTP Server (version=TLS1_2,
3 7:29:30 mslb001hexa.srv.mysociety.org LO2GBR01FT004.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM
6/7/2023 Microsoft SMTP Server (version=TLS1_2,
4 7:29:30 LO2GBR01FT004.eop-gbr01.prod.protection.outlook.com LO4P123CA0493.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM
6/7/2023 Microsoft SMTP Server (version=TLS1_2,
5 7:29:31 LO4P123CA0493.GBRP123.PROD.OUTLOOK.COM CWLP265MB2465.GBRP265.PROD.OUTLOOK.COM cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM

Original Message Headers

Received: from LO4P123CA0493.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:1ab::12)
by CWLP265MB2465.GBRP265.PROD.OUTLOOK.COM (2603:10a6:400:96::14) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6477.19; Wed, 7 Jun
2023 19:29:31 +0000
Received: from LO2GBR01FT004.eop-gbr01.prod.protection.outlook.com
(2603:10a6:600:1ab:cafe::1e) by LO4P123CA0493.outlook.office365.com
(2603:10a6:600:1ab::12) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6477.19 via Frontend
Transport; Wed, 7 Jun 2023 19:29:30 +0000
Authentication-Results: spf=pass (sender IP is 93.93.130.118)
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 93.93.130.118 as permitted sender)
receiver=protection.outlook.com; client-ip=93.93.130.118;
helo=mslb001hexa.srv.mysociety.org; pr=C
Received: from mslb001hexa.srv.mysociety.org (93.93.130.118) by
LO2GBR01FT004.mail.protection.outlook.com (10.152.42.90) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.6477.19 via Frontend Transport; Wed, 7 Jun 2023 19:29:30 +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=4dj8bgxkfQtu8Jo9v9DuPTrUeJbUFlxqng59Hi6JU+g=; b=BBkkV5/ENHd+uKHStZ6Uu/G770
5kIHvhRhPe4PnV6rowE9zkasyXmNd8XtMSwhcfzD5adIZjDfmb4kC/OHy0nmjMXknrTLoGbRAPeBt
0iQyWngHRBe+BVb/A7oyLD/pYFgIEy7eXpMM6X5XLlzJyF03pu42Stmab3LnCHSQLKcpaF6oQigNR
7++4H0oq3y0hMgmIKSV/XB/X4mqtDvUeNIPJLDEaAy19+FYtZu3pDA45yqT4IUnT4QzMvFGUIlHL5
FySn/M8jOFTVSTemYV2oSrkFn6WgxkN9RnOZDsLK7VS+1pZ57ezgZ0krtJzAaikOpR5Xo8jjQB6Kd
AgOAu5/A==;
Received: from mstrwdtkhexa.srv.mysociety.org ([2a00:1098:82:dd::10:1]:34338)
by mslb001hexa.srv.mysociety.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
(Exim 4.94.2)
(envelope-from <[FOI #981732 email]>)
id 1q6yqX-001ePr-So
for [email address]; Wed, 07 Jun 2023 19:29:29 +0000
Received: from foi by mstrwdtkhexa.srv.mysociety.org with local (Exim 4.94.2)
(envelope-from <[FOI #981732 email]>)
id 1q6yqX-00Dfhv-HB
for [email address]; Wed, 07 Jun 2023 20:29:29 +0100
Date: Wed, 07 Jun 2023 20:29:29 +0100
From: Dean <[FOI #981732 email]>
To: Information Governance Team <[email address]>
Message-ID: <[email address]>
Subject: Re: Freedom of Information Case FOI2023/00750
MIME-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Return-Path: [FOI #981732 email]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 586655ed-2cff-4089-8197-b4c10b7b3da3:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: LO2GBR01FT004:EE_|CWLP265MB2465:EE_
X-MS-Office365-Filtering-Correlation-Id: 8c37d38a-6f12-4b08-2686-08db678d83dd

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 North Lincolnshire Council again.

North Lincolnshire Council

2 Attachments

Your message to [email address] couldn't be delivered.
request wasn't found at ig.northlincs.gov.uk.
request-981732-051e8. . . Office 365 request
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/13/2023 6:33:36 PM
Sender Address: [FOI #981732 email]
Recipient Address: [email address]
Subject: Re: Freedom of Information Case FOI2023/00750
Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[email address] not found by SMTP address
lookup
Message rejected CWLP265MB6816.GBRP265.PROD.OUTLOOK.COM
by:
Notification Details
Sent by: CWLP265MB6816.GBRP265.PROD.OUTLOOK.COM

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
6/13/2023 local (Exim 4.94.2) (envelope-from
1 6:33:36 foi mstrwdtkhexa.srv.mysociety.org <[FOI #981732 email]>) *
PM
6/13/2023 esmtps (TLS1.3) tls
2 6:33:36 mstrwdtkhexa.srv.mysociety.org mslb001sova.srv.mysociety.org TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim *
PM 4.94.2) (envelope-from
<[FOI #981732 email]>)
6/13/2023 Microsoft SMTP Server (version=TLS1_2,
3 6:33:37 mslb001sova.srv.mysociety.org LO2GBR01FT020.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM
6/13/2023 Microsoft SMTP Server (version=TLS1_2,
4 6:33:38 LO2GBR01FT020.eop-gbr01.prod.protection.outlook.com LO4P123CA0628.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM
6/13/2023 Microsoft SMTP Server (version=TLS1_2,
5 6:33:38 LO4P123CA0628.GBRP123.PROD.OUTLOOK.COM CWLP265MB6816.GBRP265.PROD.OUTLOOK.COM cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM

Original Message Headers

Received: from LO4P123CA0628.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:294::6)
by CWLP265MB6816.GBRP265.PROD.OUTLOOK.COM (2603:10a6:400:1fc::7) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6500.21; Tue, 13 Jun
2023 18:33:38 +0000
Received: from LO2GBR01FT020.eop-gbr01.prod.protection.outlook.com
(2603:10a6:600:294:cafe::aa) by LO4P123CA0628.outlook.office365.com
(2603:10a6:600:294::6) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6477.35 via Frontend
Transport; Tue, 13 Jun 2023 18:33:38 +0000
Authentication-Results: spf=pass (sender IP is 93.93.128.121)
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 93.93.128.121 as permitted sender)
receiver=protection.outlook.com; client-ip=93.93.128.121;
helo=mslb001sova.srv.mysociety.org; pr=C
Received: from mslb001sova.srv.mysociety.org (93.93.128.121) by
LO2GBR01FT020.mail.protection.outlook.com (10.152.42.146) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.6477.29 via Frontend Transport; Tue, 13 Jun 2023 18:33: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=4dj8bgxkfQtu8Jo9v9DuPTrUeJbUFlxqng59Hi6JU+g=; b=OUglMySla7NlqnXKYvWtDvXNPn
eCMgkmlMn+p0uOHf2RvztXgTlsJ3Mlpqawh9Bi7VD9Tv72t9AdohviJhXPOOzEKIFfHawmzBy8stB
rl8KmC0EoWWRCp5vi98uCqGkSQurmzJX/YBwaP79Yr+t6C9gb/HCRa4t0J62J0u0xrVVVFXcIBrpn
su4EvAOV7o6zi3iVCYua5W4TDHzeq2VSoakyJbWBq1a+Qx2zCQwICEuUvJIFhK4RhQeCCdPME20pB
95iInRfIldfUH7qIdPy6MI+ZEaj2es57UOiXUHHRPR7OsFVxhOF3W7Bkp+d1hRYalScMcVTivC+5x
VZMreayg==;
Received: from mstrwdtkhexa.srv.mysociety.org ([2a00:1098:82:dd::10:1]:35348)
by mslb001sova.srv.mysociety.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
(Exim 4.94.2)
(envelope-from <[FOI #981732 email]>)
id 1q98pk-005n77-Qm
for [email address]; Tue, 13 Jun 2023 18:33:36 +0000
Received: from foi by mstrwdtkhexa.srv.mysociety.org with local (Exim 4.94.2)
(envelope-from <[FOI #981732 email]>)
id 1q98pk-0094Zt-F8
for [email address]; Tue, 13 Jun 2023 19:33:36 +0100
Date: Tue, 13 Jun 2023 19:33:36 +0100
From: Dean <[FOI #981732 email]>
To: Information Governance Team <[email address]>
Message-ID: <[email address]>
Subject: Re: Freedom of Information Case FOI2023/00750
MIME-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Return-Path: [FOI #981732 email]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 586655ed-2cff-4089-8197-b4c10b7b3da3:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: LO2GBR01FT020:EE_|CWLP265MB6816:EE_
X-MS-Office365-Filtering-Correlation-Id: a8f1b6f0-830c-4722-f30c-08db6c3cb3f0

References

Visible links
1. https://go.microsoft.com/fwlink/?LinkId=...
2. https://go.microsoft.com/fwlink/?LinkId=...
3. https://go.microsoft.com/fwlink/?LinkId=...

Information Governance Team,

1 Attachment

  • Attachment

    Information Disclosure FOI2023 00750.odt

    639K Download

Dear Dean,

I am writing in response to your request for information, that was
received on the 17th May. Please find our Information Disclosure letter
attached.

If we can be of any further assistance with regard to this request please
let us know quoting the above reference number.

Yours sincerely,

Information Governance Team
North Lincolnshire Council