Data protection impact assessment: starter template
A starting point for your organisation's own assessment. This is not legal advice. Your data protection officer should review and complete it. Below Threshold has filled in what it can describe about the service; the rest is for your organisation.
1. About this assessment
- Organisation: [name]
- Owner: [name and role]
- Data protection officer consulted: [name, date]
- Date: [date]
- Review date: [date, or when the service changes]
2. Is an assessment needed?
Using an online procurement service to receive supplier submissions is not usually high-risk processing on its own. Many organisations still carry out a short assessment because the service involves a new supplier, cloud hosting and commercially sensitive information. [Record your organisation's screening decision here.]
3. The processing
What the service does: buyers use Below Threshold to check whether a procurement is below threshold, prepare a tender pack, invite suppliers or publish an open opportunity, receive sealed submissions, evaluate them, record the decision and contract, and send outcome letters. Every action is recorded in an audit trail.
Personal data:
- your staff: name, work email, role, sign-in and audit records;
- suppliers' contacts: email address, name and organisation;
- submissions: answers and files, which may include information about suppliers' staff, such as CVs.
Where it is held: see the hosting region and sub-processors on the Below Threshold privacy page.
How long: you set the retention period after a procurement closes (7 years by default). Matters on legal hold are kept until the hold is lifted. Email logs are kept for 90 days and backups for 35 days.
Who can see it: only people in your organisation, according to their role and their assignment to each procurement. Evaluators only see submissions after the deadline, after the lead releases them, and after declaring any conflict of interest. The platform operator has no access to procurements through the application.
4. Lawful basis
[For most public bodies: Article 6(1)(e), public task, under your procurement powers. Confirm with your data protection officer.]
5. Necessity and proportionality
- [Is the data limited to what the procurement needs? Do your questions ask for personal data only where needed?]
- [Have you told suppliers how their data is used? Link to your privacy notice in the tender pack.]
- [Is your retention period justified?]
6. Risks and measures
| Risk | Likelihood and severity | Measures in the service | Your own measures | Remaining risk |
|---|---|---|---|---|
| Someone sees a bid before the deadline | [ ] | Bids sealed until the deadline and the lead's release; each submission encrypted with its own key; every access attempt logged | [ ] | [ ] |
| An account is taken over | [ ] | Two-step sign-in, account lockout, sign-out after 30 minutes idle | [Staff training; leavers removed promptly] | [ ] |
| An evaluator has a conflict of interest | [ ] | Declaration required before seeing bids; a declared conflict needs a recorded decision | [ ] | [ ] |
| A malicious file is uploaded | [ ] | Type checks and virus scanning; infected files quarantined and never downloadable | [Your own endpoint protection] | [ ] |
| Data is lost | [ ] | Daily encrypted backups with a tested restore | [ ] | [ ] |
| Data is kept too long | [ ] | Automatic deletion after your retention period, with legal hold | [Set your retention period] | [ ] |
| Data is transferred outside the UK | [ ] | Sub-processors and safeguards listed on the privacy page | [Check the safeguards are acceptable] | [ ] |
| The hosting provider's staff could access data | [ ] | Encryption at rest; keys held separately from backups | [Accept or reject this residual risk] | [ ] |
7. Sign-off
- Measures approved by: [name, date]
- Residual risks approved by: [name, date]
- Data protection officer's advice: [summary]
- Advice accepted or overruled, and why: [ ]