Toggle menu

DPIA - Preston City Council, DWP and HMRC Digital Economy Act Data Sharing Pilot.

Two arrows in circular shape

Step 1: Identify the need for a DPIA

Explain broadly what project aims to achieve and what type of processing it involves.

You may find it helpful to refer or link to other documents, such as a project proposal. Summarise why you identified the need for a DPIA.

This is a follow-up pilot to the Council Tax Pilot (DEA/D/1-29) that was in operation from March 19 to March 20. This new pilot involves 30 local authorities, DWP and HMRC.

Both this new pilot and the first are and were aimed at:

  • Increasing the management and recovery of debt by utilising HMRC PAYE and Self Assessment (SA) data
  • Identifying and supporting vulnerable debtors.

As the country begins to recover from Covid-19, debt recovery action will recommence.

Thus, the aims of this pilot are to support public authorities in enacting fair debt recovery programmes, supporting those who can't pay whilst managing and recovering debt from those who can pay.

The first pilot involved 29 local authorities supplying a sample of their Council Tax debtors to HMRC, whereupon HMRC returned the associated PAYE and Self Assessment data to the local authorities for them to use in managing and recovering debt (via communication with the debtors and by using Attachments of Earnings (AoE) where appropriate).

The first pilot has now ended and the results are being analysed. Early indications suggest it has successfully achieved a Council Tax debt recovery rate of approximately 20%. This new pilot is again limited to Council Tax debtors.

In building upon the first pilot, there are two areas that can be improved upon in launching this second pilot:

  • the identification of vulnerability, and,
  • the matching rate.

Identification of Vulnerability - In the first pilot, we anticipated that the PAYE and SA information of debtors could indicate their vulnerability. This proved to be erroneous and no determination could be made from either data set. 

Matching Rate - The first pilot's matching success rate was 54%.

Although this was better than expected, the introduction of additional identification information can increase the match rate significantly, thus increasing the debt recovery rate.

Public Authorities -  This second pilot aims to include the following: Local Authorities, comprising 

  • a core from the first pilot, and,
  • a small selection of those who have expressed a new interest.

DWP - Included as the source for:

  • increasing the vulnerability identification, by returning matched debtors in receipt of income-based benefits,
  • increasing the matching rate with HMRC, by adding additional identification data (including NINO to debtors it matches).

The data requested from HMRC is:

  • Address data - to aid communication
  • PAYE data - to aid segmentation of recovery action
  • Self Assessment data - to aid segmentation of recovery action
  • Furlough data - to aid in the identification of vulnerable debtors

Neither HMRC or DWP is to retain the data beyond its matching operations.

Cabinet Office is not to retain the data beyond its collation of the Local Authorities' spreadsheets, its passing of this to DWP and its return of disaggregated information to respective Local Authorities. 

An MOU will be drawn up between all parties (including Preston City Council, Cabinet Office, DWP and HMRC) prior to the data share under Article 28 of the UK GDPR. Here, the process of transferring the data shall be detailed.

Background of the Authority

Preston is a City in the North West of England, granted City status in 2002 and renowned for its Preston Guild celebrations every twenty years.

It has a population of approximately 115,000 people, with residential dwellings of just over 65,000, forever increasing due to the number of new housing developments currently being built.

Historically collection rates were usually around the 96% mark but in more recent years, since 2013 when the national scheme of Council Tax benefit was abolished and replaced with a localised Council Tax Support Scheme, the collection rate has slowly reduced, as Preston introduced a scheme whereby Council Tax Support is calculated on the full amount of Council Tax and a 20% reduction is applied for all working age customers.

This has resulted in collection rates falling to around the 93/94% rate since then. Arrears for the past 5 years amount to £11,537,678.20.

Preston City Councils recovery Policy can be found on the website - Difficulties paying your Council Tax.

An annual Council Tax bill is issued to every chargeable dwelling, requesting instalments over 10 or 12 months, payable by direct debit over 5 monthly payment dates (1st, 7th,15th,21st or 28th) or by cash/cheque on the 1st of the month.

A reminder 1 notice will be issued 7 days after an instalment has become overdue requesting payment to bring the account up to date.

If payment is not made, a summons will then be issued and our court costs are currently £27.00 for the issue of a summons and £26.50 if a liability order is granted.

If, upon receipt of a reminder 1 notice, the account is brought up to date, no further action is taken. However if the account falls into arrears again, a second reminder notice is issued and this advises that payments should be brought up to date and paid on time in future as if they fall behind again, a final notice will be issued and this cancels the right to pay in instalments, meaning the full outstanding balance will be payable.

If a final notice is issued, and the customer is unable to pay the amount in full, a payment arrangement can be made. 

Payment arrangements are encouraged at every stage if a customer is struggling to pay.

If a liability order is obtained, notification of this is sent to the customer and they are asked to provide details of their income and expenditure in order that we may assess the most appropriate form of recovery action moving forward. (We rarely receive these completed forms back.

If we are aware of the customer's employment details, we will set up an attachment on their earnings or request deductions from their benefit. If we have no employment details and no other information advising us of their current circumstances, their account will be passed to one of 3 enforcement agent companies that we use.

If the enforcement agent is unable to contact the customer or obtain payment then they will return the case to the Council for further action.

We then assess the account and circumstances and in some cases we will visit the customer to discuss their circumstances and try and help them moving forward.

Our next course of action would be to apply for a charging order with a view to obtaining an order for sale (OFS on empty properties) or we will apply for bankruptcy. However this is a last resort when we have no other recovery options available.

Preston City Council has identified that customer income-based benefit information from DWP and PAYE and Self-Assessment customer information from HMRC is useful and able to support:

the managing of overall arrears and further developing of recovery procedures, by:

  • identifying customers whose circumstances make them vulnerable and providing appropriate support and appropriate recovery action whereupon they engage with the Local Authority;
  • identifying those in employment and allowing the recovering of individual debts by Attachment to Earnings Orders, where appropriate;
  • identifying forwarding addresses for customers who have moved leaving arrears outstanding;
  • identifying those receiving benefits and allowing the recovering of individual debts by Attachment to Benefits Orders, where appropriate.

This is a significant change from the current process and allows us to take positive action to identify and support vulnerable customers and recover debt from those customers who are not engaging in the process and who have already been informed of the action the Local Authority may take.

Preston City Council, DWP and HMRC are joint data controllers in this pilot using the definition as set out in the Data Protection Act 2018.

Cabinet Office is a data processor using the definition as set out in the Data Protection Act 2018.

Cabinet Office is to be the Data Processor of Preston City Council, DWP and HMRCs data (i.e., the Data Controllers of the pilot).

The purpose of the pilot is to gather evidence that the data shared from DWP and HMRC will increase the identification of vulnerable individuals and increase Preston City Council's Council Tax debt recovery rate.

This DPIA is needed as we will be collecting new information from DWP and HMRC to enable Council Tax recovery which may have a significant impact on the individuals concerned, for example:

  • Financially vulnerable individuals may be identified and offered debt support
  • AoE's may be implemented where the individual will have no choice regarding payment of the debt
  • Individuals may be contacted to discuss the new information provided by the HMRC.

This may also raise privacy concerns as this data was originally collected for the purposes of calculating benefits and Income Tax liability.

Step 2: Describe the processing

Describe the nature of the processing

How will you collect, use, store and delete data? What is the source of the data? Will you be sharing data with anyone? You might find it useful to refer to a flow diagram or other way of describing data flows.

What types of processing identified as likely high risk are involved?


Preston City Council will supply Cabinet Office, DWP and HMRC with the names and addresses of Preston City Council's customers with Council Tax debt, plus supporting identification information, (e.g., NINO, DoB, email address and phone numbers) as a one-off data share. 

DWP and HMRC will match against their data and matching cases will be supplied to Preston City Council with income-based benefits information, PAYE and Self-Assessment data.

The data will be used to enable management and recovery of Council Tax debt, via:

  • Where financial vulnerability is identified, discussions around the use of debt support
  • AOE where employment information has been provided
  • Further discussion with the individual where self-assessment information has been provided.

The data will be stored in a secure folder within Preston City Council and Cabinet Office will send this to DWP via secure Government email. DWP will then send the data to HMRC via secure Government email.

Neither HMRC or DWP is to retain the data beyond its matching operations.

Cabinet Office is not to retain the data beyond its collation of the Local Authorities' spreadsheets, its passing of this to DWP and its return of disaggregated information to respective Local Authorities.

The standard data retention period for the pilot is 12 months.  However, data that is being used operationally to recover debt (e.g., via an Attachment of Earnings, bankruptcy action or supporting identified vulnerable customers) will be retained in line with Preston City Council's data retention policies and deleted in accordance with said policies.

From the information supplied by HMRC, if Preston City Council subsequently has this information confirmed by either the employer or the individual, then that information can be classed as having been supplied via another source (i.e., other than HMRC), then Preston City Council shall be able to retain this data on its systems. However, the data received from HMRC in its raw format shall be deleted at the end of the pilot.

From the information supplied by HMRC, if Preston City Council subsequently has this information confirmed by either the employer or the individual, then that information can be classed as having been supplied via another source (i.e., other than HMRC), then Preston City Council shall be able to retain this data on its systems. However, the data received from HMRC in its raw format shall be deleted at the end of the pilot.

For HMRC, the pilot data will be deleted one year after the data has been shared with Cabinet Office, except where the data is being used operationally and will be deleted once recovery action has been completed.

The data will not be shared with anyone else.

A data flow process

The data flow process for the debt recovery and vulnerability support pilot

Describe the scope of the processing

What is the nature of the data, and does it include special category or criminal offence data? How much data will you be collecting and using? How often? How long will you keep it? How many individuals are affected? What geographical area does it cover?


An overview of the activity under the arrangement and how the data will be used

Preston City Council, will undertake a one-off data share as to a reasonable sample of debtors.

This sample is to be of an appropriate size in relation to Preston City Council (as may include all debtors contained within our Liability Order dataset). There is no limit to this sample size. This sample is to be shared with Cabinet Office.

Cabinet Office will then collate all of the submitted samples from the pilot's Local Authorities into a single document. This collated document will then be passed by Cabinet Office to DWP who will match against their benefits records.

For those records matched, DWP will add income-based benefits data and add corroborative customer information (e.g., NINO and/or DoB) and then forward these records to HMRC. HMRC will then match these customer records against their systems and return the records to Cabinet Office with the associated address, PAYE and/or Self Assessment information.

Cabinet Office will then disaggregate this information and provide the respective samples to each local authority, whereupon Preston City Council shall receive its sample back.

No special category or criminal offence data shall be contained within the sample.

The sample will exclude debtors who are;

  • in receipt of debt support - full or partial;
  • deceased;
  • subject to committal and bankruptcy cases;
  • companies;
  • subject to a current Attachment of Earnings.

A snapshot of data will be taken before being issued to DWP/HMRC for evaluation during and post-action.

Once the data has been returned, Preston City Council will analyse the results from DWP and HMRC and;

For those in receipt of DWP Income-based benefits:

  • Pass to debt support team for action
  • Communicate with the debtor
  • If debtor contacted and vulnerability discussed, support offered (where appropriate) and/or payment plan agreed
  • If no contact, Preston City Council shall continue recovery action.

For those in receipt of PAYE:

  • 14-day letter (as per the first pilot) to be issued to the debtor
  • If debtor contacted, payment plan or vulnerability discussed
  • If no contact, Preston City Council shall progress Attachment of Earnings action.

For those in receipt of S/A:

  • Communicate with the customer noting they are in receipt of S/A
  • If debtor contacted, payment plan or vulnerability discussed
  • If no contact, Preston City shall continue recovery action.

An outline of what types of data will be shared and the data security arrangements to be put in place

Preston City Council will supply Cabinet Office with our sample which contains the following;

  • Full name - Title, First name, Middle name or initials, Surname.
  • Current address and postcode
  • Forwarding address and dates
  • Date of commencement of Liability Order (if applicable)
  • Unique identifier (Future proof)
  • Telephone numbers (where available)
  • Email addresses (where available)

In addition, either DoB or NINO will be provided as a minimum (where available) to assist DWP data matching.

Cabinet Office will collate our sample with the other samples from the Local Authorities involved in this pilot for onward transmission to DWP.

Redacted as related to data security and DWP and HMRC processes.

Persons at Preston City Council receiving and disclosing data are limited to debt analysts and debt recovery officers. 

All such users sign data disclosure agreements before system access is granted. All staff have had DPA and lately GDPR training.

Redacted as related to data security and DWP and HMRC processes.

For any third-party entity or body which provides services to Preston City Council and which has access to its software suppliers and is able to extract data to be used in a search tool available for other councils - Preston City Council shall ensure no data supplied to them under this pilot is available for any other council to obtain.

Describe the context of the processing

What is the nature of your relationship with the individuals? How much control will they have? Would they expect you to use their data in this way? Do they include children or other vulnerable groups? Are there prior concerns over this type of processing or security flaws? Is it novel in any way?

What is the current state of technology in this area? Are there any current issues of public concern that you should factor in? Are you signed up to any approved code of conduct or certification scheme (once any have been approved)?


The individuals reside (or resided) within Preston City Council's boundary and are/were liable to pay Council Tax to Preston City Council but are in arrears.

The individuals will have no control.

Council tax is covered by the Local Government Finance Act 1992 and individuals are required to pay Council Tax and would expect Preston City Council to pursue recovery of their debt.

Children and other vulnerable groups are not included.

There are no prior concerns over this type of processing and security flaws. 

The use of data sharing to manage and reduce debt is well established throughout the debt industry.

There is no new technology in this area for this type of pilot.

There are no issues of public concern to be factored in.

Preston City Council, Cabinet Office, DWP and HMRC are required to adhere to the DEA Code of Practice, DPA 2018 and LGFA 1992 (as amended).

Describe the purposes of the processing

What do you want to achieve? What is the intended effect on individuals? What are the benefits of the processing - for you, and more broadly?


What do you want to achieve?

The pilot is aimed at - Increasing recovery of Council Tax debt from individuals who have not paid and debt support for those individuals identified as financially vulnerable.

What is the intended effect on individuals?

The intended effect on individuals will be for those who are able to pay and choose not to pay is to manage and recover their debt.  For those who are identified as vulnerable, the effect will be to help them via debt support.  It will also be fairer for those who do pay their Council Tax.

What are the benefits of the processing - for you, and more broadly?

The benefits of the processing are:

  • Increased debt recovered
  • Increased in-year collection rate
  • Increased identification of vulnerable debtors, as can be signposted for assistance within or externally of the Preston City Council, where they engage
  • Increase in debt recovery due to knowledge of PAYE and Self-Assessment information
  • Increase in take-up of reliable Attachment of Earnings
  • Reduced failure rate of Attachment of Earnings
  • Reduced need for using enforcement agents as a first port-of-call and the increasing of debt with fees.
  • A fair approach to reducing debt with an ability to pay over a regular period.
  • Improved effectiveness in debt recovery and thus reduced pressure on budgets
  • Those in regular employment will avoid expensive and stressful enforcement agent visits
  • Customers knowing that we have access to HMRC data will encourage earlier take-up in contacting Preston City Council and making arrangements to pay
  • Efficiency savings by reducing time/court hearings on committal or insolvency cases
  • Efficiency savings on not transferring cases to enforcement agents
  • Swifter repayment of debt
  • Identification of individuals with a propensity to pay and take appropriate recovery action
  • Reduced or mitigated problem debt.

Step 3: Consultation process

Consider how to consult with relevant stakeholders

Describe when and how you will seek individuals' views - or justify why it's not appropriate to do so.

Who else do you need to involve within your organisation? Do you need to ask your processors to assist? Do you plan to consult information security experts, or any other experts?

Describe when and how you will seek individuals' views - or justify why it's not appropriate to do so

Individual's views will not be sought for this pilot, Preston City Council already has the power to request employment details from individuals when a liability order has been obtained under Regulation 36 of the Council Tax (Administration and Enforcement) Regulations 1992 and employment details are already held in many cases where an attachment of earnings order has been served.

Consultation is not therefore necessary on this occasion.

Additionally the Digital Economy Act 2017 has undergone a public consultation process.

Who else do you need to involve within your organisation? Do you need to ask your processors to assist? Do you plan to consult information security experts, or any other experts?

Within Preston City Council, the DPO, SIRO, senior decision makers, analysts and Council Tax Collection staff need to be involved.

Processors will be asked to assist.

Security, data protection and analyst experts will be involved and consulted.

Step 4: Assess necessity and proportionality

Describe compliance and proportionality measures, in particular

What is your lawful basis for processing? Does the processing actually achieve your purpose?

Is there another way to achieve the same outcome? How will you prevent function creep? How will you ensure data quality and data minimisation? What information will you give individuals?

How will you help to support their rights? What measures do you take to ensure processors comply? How do you safeguard any international transfers?


The lawful basis is under GDPR Article 6 (e) Public task: the processing is necessary for you to perform a task in the public interest or for your official functions, and the task or function has a clear basis in law.

In making this determination, we have consulted the Information Commissioner Officer website and this section specifically and have completed their online interactive tool.

The legal basis for the establishment and operation of the pilot, and the analysis of personal data within it, is covered by Part 5, chapter 3 of the Digital Economy Act 2017. This provides powers for government departments / organisations to share information 'to take action in connection with debt owed to a public authority or to the Crown' (Chapter 3). 

Section 48(3) of the DEA provides that taking action in connection with a debt owed to a public authority includes identifying debt.

Does the processing actually achieve your purpose?

Yes, the pilot is anticipated to achieve the purpose.

Is there another way to achieve the same outcome?

No other way to achieve the same outcome has been identified.

How will you prevent function creep?

We will avoid function creep by adhering to the remit of this DPIA, DEA business case and the data usage agreement and then performing only the analysis necessary to provide the required level of understanding.

How will you ensure data quality and data minimisation?

We will ensure data quality will be ensured by using well-proven matching routines in the analysis, supported by manual review of the results to check for any error. Should any be found then the analysis will be re-run before any results are made available.

Preston City Council will ensure data is minimised to only the data required to ensure a confident match is made.

Only individuals' names and identification data (minimised) will be supplied to the DWP and HMRC.

What information will you give individuals?

None.

How will you help to support their rights?

Their rights will be supported by ensuring that the processes and data used will be in line with DPA, GDPR and DEA Code of Practice requirements.

Their rights will be supported by ensuring that the processes and data used will be in line with DPA, GDPR, the ICO Code of Practice and DEA Code of Practice requirements.

Individuals may request a copy of their personal information (commonly known as a "data subject access request") by contacting their council.

This enables them to receive a copy of the personal information held and to check that it is being processed lawfully.

Information given to the individual will have taken the form of a Privacy Notice outlining the potential uses that may be made of their data for the purposes of Council Tax collection and in the event of non-payment.

The Privacy Notice will also have included details or reference to details of how to exercise data subject rights under the legislation.

Information given to individual as a consequence of the matching activity will depend on the match data returned by DWP and HMRC, and for those with:

  • Income based benefits
  • PAYE data supplied, they will be informed that an AoE will commence
  • Self-assessment data, they will be informed by letter or phone conversation
  • For those identified as financially vulnerable they will be helped by debt support.

Preston City Council will apply it's fairness principles to the pilot.

What measures do you take to ensure processors comply?

All staff have to comply with the above requirements and also staff are trained in DPA and GDPR requirements.

There are criminal sanctions for unauthorised disclosure of HMRC data.

The staff at each authority receiving, processing and transmitting the data are limited to IT data extractions and data analysts and their immediate managers.  All such users sign data disclosure agreements before system access is granted. All staff have had DPA and lately GDPR training.

Staff at HMRC receiving, analysing and disclosing data are limited to data analysts and processors, within the Knowledge, Information and Analysis team. These staff have been security trained.

How do you safeguard any international transfers?

No international transfers will be required as part of the pilot.

Step 5: Identify and assess risks

Describe source of risk and nature of potential impact on individuals. Include associated compliance and corporate risks as necessary.

Risk 1

Risk - Data is shared with other sections or organisations for which there is no authorisation or legal justification.

Impact - Possibility of information being shared inappropriately

Compliance and corporate risk:

  • Non-compliance with the DPA
  • Non-compliance with sector specific legislation or standards
  • Non-compliance with human rights legislation
  • Non-compliance with the DPA or other legislation can lead to sanctions, fines and reputational damage
  • Public distrust about how information is used can damage the council's reputation
  • Data losses which damage individuals could lead to claims for compensation

Likelihood of harm, Severity of harm and Overall risk

  • Likelihood of harm - Remote, possible or probable - Remote

  • Severity of harm - Minimal, significant or severe - Significant

  • Overall risk - Low, medium or high - Low

Risk 2

Risk - The data being collected may be considered sensitive as it shows employment details including levels of earnings, self employment and income.

Impact - Attachments to earnings that are implemented as a result of collecting information about them and possible customer interaction might be seen as intrusive.

Compliance and corporate risk - Public distrust about how information is used can damage the council's reputation.

Likelihood of harm, Severity of harm and Overall risk

  • Likelihood of harm - Probable

  • Severity of harm - Significant

  • Overall risk - Medium

Risk 3

Risk - Data concerning vulnerable customers may be divulged without authorisation putting individuals at risk.

Impact - Vulnerable people may be particularly concerned about the risks of identification or the disclosure of information.

Compliance and corporate risk: 

  • Non-compliance with the DPA
  • Non-compliance with human rights legislation
  • Non-compliance with the DPA or other legislation can lead to sanctions, fines and reputational damage
  • Public distrust about how information is used can damage the council's reputation
  • Data losses which damage individuals could lead to claims for compensation

Likelihood of harm, Severity of harm and Overall risk

  • Likelihood of harm - Remote

  • Severity of harm - Significant

  • Overall risk - Low

Risk 4 

Risk - Data held may be out of date.

Impact - If a retention period is not established information might be held for longer than necessary.

Compliance and corporate risk:

  • Non-compliance with the DPA
  • Non-compliance with sector specific legislation or standards
  • Non-compliance with human rights legislation
  • Non-compliance with the DPA or other legislation can lead to sanctions, fines and reputational damage
  • Public distrust about how information is used can damage the council's reputation.

Likelihood of harm, Severity of harm and Overall risk

  • Likelihood of harm - Possible 

  • Severity of harm - Significant

  • Overall risk - Medium

Step 6: Identify measures to reduce risk

Identify additional measures you could take to reduce or eliminate risks identified as medium or high risk in step 5

Risk 1

Data is shared with other sections or organisations for which there is no authorisation or legal justification.

Options to reduce or eliminate risk

  • A legal gateway for sharing this information has been established
  • Restrict access to data through system usernames/ passwords
  • GDPR training delivered to all existing staff and incorporated in induction procedures for new staff provided.

Effect on risk - Eliminated reduced accepted - Reduced

Residual risk - Low

Measure approved - Yes

Risk 2

The data being collected may be considered sensitive as it shows employment details including levels of earnings, self-employment and income details.

Options to reduce or eliminate risk

  • Data only used by staff responsible for administering attachment of earnings
  • legislation prescribes deduction percentages depending on income (section 6 of CT (admin and enforcement) regulations 1992.

Effect on risk - Reduced

Residual risk - Low

Measure approved - Yes

Risk 3

Data concerning vulnerable customers may be divulged without authorisation putting individuals at risk.

Options to reduce or eliminate risk

  • Restrict access to data through system usernames/ passwords
  • GDPR training delivered to all existing staff and incorporated in induction procedures for new staff provided.

Effect on risk - Reduced

Residual risk - Low

Measure approved - Yes

Risk 4 

Data held may be out of date.

Options to reduce or eliminate risk

  • Compliance with data retention periods that apply to service

Effect on risk - Reduced

Residual risk - Low

Measure approved - Yes

Step 7: Sign off and record outcomes

Measures approved by - Redacted 8 February 2021 - Integrate actions back into project plan, with date and responsibility for completion.

Residual risks approved by - Redacted 8 February 2021 - If accepting any residual high risk, consult the ICO before going ahead.

DPO advice provided - Redacted 8 February 2021 - DPO should advise on compliance, step 6 measures and whether processing can proceed.

Summary of DPO advice

1. I consider that this DPIA identifies adequate measures to make the personal data processing compliant with the GDPR Principles in Art. 5 1(b) to 1(f).

2. In relation to GDPR Principle in Art. 5 1(a) "Lawfulness, fairness and transparency":

a. The DPIA identifies a lawful basis for the processing.

b. While data subjects might experience adverse effects from the processing this would not make the processing unfair given the substantial public interest in the proper collection of taxes.

c. The Preston City Council privacy notice for council tax refers to "government bodies" as sources of personal data but the examples given do not include DWP and HMRC. I would recommend amending this to refer to HMRC explicitly.

d. A review of letters sent to council tax debtors to consider inclusion of a reference to HMRC might be advisable.

3. I am satisfied that the risk mitigation measures and the assessment of low residual risk is appropriate and the processing can therefore proceed.

4. If the project moves from pilot to business-as-usual the DPIA should be reviewed in light of the pilot outcomes and I would recommend also drawing up a formal information sharing agreement.

Version Control

  • 0.1 - Cabinet Officer (on behalf of XX) - 14.01.2021
  • 1.0 - Cabinet Office (on behalf of Preston City Council) - 26.01.2021 - Revised following clarifications and discussions with Pilot Working Group.
  • 1.1 - Cabinet Office (on behalf of Preston City Council) - 02.02.2021 - Revised following updated pilot plans.
  • 2.0 - Cabinet Office (on behalf of Preston City Council) - 04.02.2021 - Revised following updated pilot plans - removal of HMRC's proposal to retain pilot data.
  • 2.1 - Cabinet Office (on behalf of Preston City Council) - 08.02.2021 - Revised following questions/queries from involved Local Authorities - expected to be the final draft version.

Share this page

Share on Facebook Share on Twitter Share by email