Deprecated: Return type of FS_Key_Value_Storage::offsetExists($k) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/runcloud/webapps/dev-ukrn-org-uk/web/app/plugins/advanced-accordion-block/admin/fs/includes/managers/class-fs-key-value-storage.php on line 309

Deprecated: Return type of FS_Key_Value_Storage::offsetGet($k) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/runcloud/webapps/dev-ukrn-org-uk/web/app/plugins/advanced-accordion-block/admin/fs/includes/managers/class-fs-key-value-storage.php on line 317

Deprecated: Return type of FS_Key_Value_Storage::offsetSet($k, $v) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/runcloud/webapps/dev-ukrn-org-uk/web/app/plugins/advanced-accordion-block/admin/fs/includes/managers/class-fs-key-value-storage.php on line 301

Deprecated: Return type of FS_Key_Value_Storage::offsetUnset($k) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/runcloud/webapps/dev-ukrn-org-uk/web/app/plugins/advanced-accordion-block/admin/fs/includes/managers/class-fs-key-value-storage.php on line 313

Deprecated: Return type of FS_Key_Value_Storage::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/runcloud/webapps/dev-ukrn-org-uk/web/app/plugins/advanced-accordion-block/admin/fs/includes/managers/class-fs-key-value-storage.php on line 328

Deprecated: Return type of FS_Key_Value_Storage::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/runcloud/webapps/dev-ukrn-org-uk/web/app/plugins/advanced-accordion-block/admin/fs/includes/managers/class-fs-key-value-storage.php on line 339

Deprecated: Return type of FS_Key_Value_Storage::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/runcloud/webapps/dev-ukrn-org-uk/web/app/plugins/advanced-accordion-block/admin/fs/includes/managers/class-fs-key-value-storage.php on line 350

Deprecated: Return type of FS_Key_Value_Storage::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/runcloud/webapps/dev-ukrn-org-uk/web/app/plugins/advanced-accordion-block/admin/fs/includes/managers/class-fs-key-value-storage.php on line 362

Deprecated: Return type of FS_Key_Value_Storage::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/runcloud/webapps/dev-ukrn-org-uk/web/app/plugins/advanced-accordion-block/admin/fs/includes/managers/class-fs-key-value-storage.php on line 375

Deprecated: Return type of FS_Key_Value_Storage::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/runcloud/webapps/dev-ukrn-org-uk/web/app/plugins/advanced-accordion-block/admin/fs/includes/managers/class-fs-key-value-storage.php on line 389

Deprecated: Return type of Illuminate\Container\Container::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/runcloud/webapps/dev-ukrn-org-uk/vendor/illuminate/container/Container.php on line 1231

Deprecated: Return type of Illuminate\Container\Container::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/runcloud/webapps/dev-ukrn-org-uk/vendor/illuminate/container/Container.php on line 1242

Deprecated: Return type of Illuminate\Container\Container::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/runcloud/webapps/dev-ukrn-org-uk/vendor/illuminate/container/Container.php on line 1254

Deprecated: Return type of Illuminate\Container\Container::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/runcloud/webapps/dev-ukrn-org-uk/vendor/illuminate/container/Container.php on line 1267

Deprecated: Return type of Illuminate\Config\Repository::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/runcloud/webapps/dev-ukrn-org-uk/vendor/illuminate/config/Repository.php on line 141

Deprecated: Return type of Illuminate\Config\Repository::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/runcloud/webapps/dev-ukrn-org-uk/vendor/illuminate/config/Repository.php on line 152

Deprecated: Return type of Illuminate\Config\Repository::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/runcloud/webapps/dev-ukrn-org-uk/vendor/illuminate/config/Repository.php on line 164

Deprecated: Return type of Illuminate\Config\Repository::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/runcloud/webapps/dev-ukrn-org-uk/vendor/illuminate/config/Repository.php on line 175
{"id":376,"date":"2017-08-14T08:31:21","date_gmt":"2017-08-14T08:31:21","guid":{"rendered":"https:\/\/www.ukrn.org.uk\/?p=376"},"modified":"2024-01-17T15:31:08","modified_gmt":"2024-01-17T15:31:08","slug":"better-use-of-data-and-information-sharing-to-identify-customers-in-vulnerable-situations-august-project-update","status":"publish","type":"post","link":"https:\/\/ukrn.srgry.uk\/better-use-of-data-and-information-sharing-to-identify-customers-in-vulnerable-situations-august-project-update\/","title":{"rendered":"Better use of data and information sharing to identify customers in vulnerable situations \u2013 August project update"},"content":{"rendered":"\n

Better use of data and information sharing to identify customers in vulnerable situations \u2013 August project update<\/strong><\/p>\n\n\n\n

Published: August 2017<\/p>\n\n\n

Ofwat and Ofgem, through the UK Regulators Network (UKRN), are working together to explore the potential benefits, opportunities and challenges of sharing data across water and energy, to better identify customers in vulnerable situations. Our work so far has shown us that data sharing is just one part of a wider toolkit that companies working across both sectors can use to identify such customers and help them receive the additional, non-financial, support they need. Companies are already working together on signposting, multi-sign-up initiatives and referrals, but data sharing is not currently wide-spread. You can read more about this work in our previous updates; our January open letter<\/a> and April blog<\/a>.<\/p>\n

Last month, to gain a wider consumer perspective on making better use of data to identify vulnerable customers, we engaged with consumer bodies and regulatory experts via a Customer Voice Forum on LinkedIn. We posed a series of questions and invited informal written responses. We also hosted a roundtable discussion with several consumer bodies to follow up on key points raised in the Forum. Participants focused in particular on the following themes.<\/p>\n