Alex Morgan has made a data subject access request. One of the records collected for the response is a routine appraisal written by Alex’s team manager, Jamie Lee. The appraisal names Alex, identifies Jamie as the author, and includes Jamie’s private mobile number on a separate line. Each of those three things has a different relationship to Alex’s request, and the lesson treats them one at a time.
The worked example
The source passage, reference A-014 paragraph 2, reads: “Jamie Lee, team manager: Alex completed the project late. We agreed a revised delivery plan.” A separate line holds Jamie’s private mobile number. The stated facts are that Jamie is Alex’s known manager, that this is a routine appraisal, and that the review has identified no confidentiality or safety concern affecting Jamie’s professional identity. The proposed disclosure is given its own reference, R-014, so that another reviewer can follow the decision without relying on a filename that may later change.
What is Alex’s information
The statement that Alex completed a project late is an assessment of Alex’s performance. The revised plan also concerns Alex. The fact that someone else wrote those sentences is part of the context in which the assessment was made. Before extracting a sentence, the reviewer reads the surrounding record: the appraisal might explain the delay, record Alex’s response, or qualify the manager’s account, and the extract preserves the meaning that the relevant context supplies.
The manager’s name and role
Jamie’s attribution introduces information about another identifiable person. Under the UK framework the reviewer considers the other person’s consent, or whether disclosure without consent is reasonable in the circumstances (Data Protection Act 2018, Schedule 2, paragraph 16). The circumstances of the particular record decide that assessment. In this appraisal Jamie acted as Alex’s known manager, the attribution explains whose assessment Alex is reading, and the stated facts identify no confidentiality or safety concern affecting that professional attribution. Those facts support the candidate decision to include Jamie’s name and role.
The record explains how the conclusion was reached, including the handling of consent. In this worked case consent was not sought, because the reviewer assessed disclosure of the professional attribution as reasonable on the stated facts. The assessment would be revisited if an important fact changed. The ICO’s guidance on information about other people in a SAR sets out the factors.
The private mobile number
The number on the separate line is Jamie’s private contact. It has no stated role in the performance assessment, the revised delivery plan, or Alex’s understanding of the appraisal. The candidate extract therefore contains the manager’s professional attribution and the two sentences about Alex, with the private contact line omitted. The original stays intact in the case record, and the omitted field and the reason for that treatment are recorded.
The distinction depends on context. A contact number used in a disputed exchange with Alex could raise a different issue, and a reviewer would then examine that connection and the competing considerations. The example supplies a reason tied to this particular field.
Changing the facts: a confidential witness
A second record changes the picture. A witness reports seeing Alex leave a server room at 21:10, describes being the only night supervisor, asks for confidentiality, and raises a concern about retaliation. Removing the witness’s name leaves a unique role and a precise event, and Alex may be able to identify the witness from the rota or other records. The reviewer examines that possibility and the evidence behind the stated risk before deciding what information can be supplied.
A possible summary would say that an account reports seeing Alex leave the room at 21:10. That text is labelled as a proposed summary. It changes the form of the source and needs checks for accuracy, meaning and remaining identification. The available facts do not resolve the release decision for this second record, so the assessment stays open.
The decision record
A useful record connects the source, the proposed output, the treatment and the reason, and adds the reviewer identifier, the date and the output version so it can be checked later. For the appraisal it reads as follows.
| Source → output | A-014 paragraph 2 → R-014 paragraph 2 |
|---|---|
| Name and role | Retained. Known manager, routine appraisal, no confidentiality or safety concern identified. Consent not sought; disclosure of the professional attribution assessed as reasonable on the stated facts. |
| Private mobile | Omitted. No stated role in the appraisal. |
| Reviewer · date · version | RV-02 · 15 November 2026 · R-014 v1 (example values) |
When a material fact is unresolved, the record holds the question, the person responsible and the next action. A named owner makes the follow-up accountable; the entry still needs an outcome.
| Open item | Witness record |
|---|---|
| Question | Can Alex identify the witness from the rota or other records? |
| Next action | Examine the rota and the evidence behind the stated risk. |
| Owner | Named reviewer; outcome required. |
| Status | Open. The release decision is unresolved. |
Checking the proposed disclosure
The reviewer opens the exact file proposed for release and reads the appraisal as Alex would receive it: the performance statement and agreed plan remain understandable, the professional attribution matches the decision, and the private contact field received the intended treatment. Related files are then read together, because a filename, email signature or covering note could disclose information that another part of the response removes. Where the review depends on protecting an identity, the inference created by the package as a whole is checked.
The response also needs the applicable supplementary information under the right of access, and the organisation responsible for the case connects the reviewed files to the rest of its response process. Completing a document extract is one part of preparing that response.
Watch the lesson by chapter
- 00:00 The appraisal
- 01:04 The requester and the record
- 02:06 Assessing the manager’s identity
- 03:19 Separating the private contact
- 04:22 Changing the facts
- 05:26 Recording the decision
- 06:32 Checking the proposed disclosure
- 07:37 The outcome and next step
Frequently asked questions
Should the manager’s name stay in an employee DSAR response?
Often it can. A manager who writes an appraisal is acting in a professional capacity, and the attribution tells the requester whose assessment they are reading. Under paragraph 16 of Schedule 2 to the Data Protection Act 2018 the controller considers the other person’s consent or whether it is reasonable to disclose without it, and the ICO’s guidance treats information about someone acting in a professional role as more likely to be reasonable to disclose. In the worked example the known management relationship, the routine appraisal and the absence of any identified confidentiality or safety concern support retaining the name and role. Each record is assessed on its own facts.
Does the employee receive the manager’s private mobile number?
Not in the worked example. The number is the manager’s own personal data, it has no stated role in the assessment or the agreed plan, and it is not information about the requester. It is left out of the proposed disclosure and the omission is recorded with its reason. A number used in a disputed exchange with the requester would raise a different question and would be examined on its own facts.
Do we have to ask the manager for consent?
Consent is one route. The other is a reasoned assessment that disclosure without consent is reasonable in the circumstances, which takes account of the type of information, any duty of confidentiality, the steps taken to seek consent, whether the person can give consent, and any express refusal (Schedule 2, paragraph 16(3)). Whichever route applies, the decision record states how consent was handled.
What if removing a witness’s name still identifies them?
Removing a name does not settle the question when a unique role or a precise event lets the requester identify the person from other records, such as a rota. The reviewer examines that possibility and the evidence behind the stated risk before deciding what can be supplied. A proposed summary changes the form of the source and needs its own checks for accuracy, meaning and remaining identification. In the lesson that record stays open, with a named owner and a next action.
What should a DSAR redaction decision record contain?
A reference for the source passage and for the proposed output, the treatment of each field, the reason for each treatment, how consent was handled, and the reviewer identifier, date and output version. Unresolved questions are recorded with the person responsible and the next action, so another reviewer can follow the decision without relying on a filename that may later change.
Is the reviewed extract the whole response?
No. The response also needs the supplementary information under Article 15(1) of the UK GDPR, such as the purposes of processing, the recipients and the retention period, and the organisation’s own response process connects the reviewed files to the rest of the response. Related files are read together, because a filename, email signature or covering note can disclose what another part of the response removes.
Transcript
00:00 The appraisal
Alex Morgan has asked for personal information held about them. This appraisal is one of the records collected for the response. It names Alex, identifies Jamie Lee as the team manager, and includes Jamie’s private mobile number. We will follow this paragraph through the review and finish with a proposed disclosure and its decision record. The example gives us specific facts: Jamie is Alex’s known manager, this is a routine appraisal, and the review has identified no confidentiality or safety concern affecting Jamie’s professional identity. The source says: “Jamie Lee, team manager: Alex completed the project late. We agreed a revised delivery plan.” A separate line contains Jamie’s private mobile. Each part has a different relationship to Alex’s request. Begin by identifying the information about Alex.
01:04 The requester and the record
The statement that Alex completed a project late is an assessment of Alex’s performance. The revised plan also concerns Alex. The fact that somebody else wrote those sentences is part of the context in which the assessment was made. Keep a record of the source passage and the request it answers. In this example, we use source reference A-014, paragraph two. The proposed disclosure will be R-014. Those identifiers let another reviewer follow the decision without relying on a filename that might later change. Read the surrounding record before extracting a sentence. The appraisal might explain the delay, record Alex’s response, or qualify the manager’s account. Preserve the meaning that the relevant context supplies. Jamie’s attribution introduces information about another identifiable
02:06 Assessing the manager’s identity
person. Under the UK framework, the reviewer considers consent or whether disclosure without consent is reasonable. The circumstances of the particular record determine that assessment. For this appraisal, Jamie acted as Alex’s known manager. The attribution explains whose assessment Alex is reading. The stated facts identify no confidentiality or safety concern affecting that professional attribution. Those facts support the candidate decision to include Jamie’s name and role. The record should explain how that conclusion was reached, including the handling of consent. In this worked case, consent was not sought because the reviewer assessed disclosure of the professional attribution as reasonable on the stated facts. The assessment would need to be revisited if important facts changed. Now examine the mobile number on the separate line.
03:19 Separating the private contact
In this example it is Jamie’s private contact number. It has no stated role in the performance assessment, the revised delivery plan or Alex’s understanding of the appraisal. Our candidate extract therefore contains the manager’s professional attribution and the two sentences about Alex, with the private contact line omitted. The original remains intact in the case record. We record the omitted field and the reason for that treatment. The distinction depends on context. A contact number used in a disputed exchange with Alex could raise a different issue. A reviewer would then examine that connection and the competing considerations. Our example supplies a reason tied to this particular contact field. Consider a second record. A witness reports seeing Alex leave a server
04:22 Changing the facts
room at 21:10. The witness describes being the only night supervisor, asks for confidentiality and raises a concern about retaliation. Removing the witness’s name leaves a unique role and a precise event. Alex may be able to identify the witness from the rota or other records. The reviewer needs to examine that possibility and the evidence behind the stated risk before deciding what information can be supplied. A possible summary would say that an account reports seeing Alex leave the room at 21:10. Label that text as a proposed summary. It changes the form of the source and needs checks for accuracy, meaning and remaining identification. The available facts have not yet resolved the release decision for this second record. Return to the completed appraisal decision.
05:26 Recording the decision
A useful record connects the source, the proposed output, the treatment and the reason. Here it identifies A-014 paragraph two, output R-014, Jamie’s professional attribution and the separate private contact field. The rationale identifies the known management relationship, the routine appraisal context and the absence of an identified confidentiality or safety concern on those facts. It also explains why the private mobile was omitted. Add the reviewer identifier, date and output version so the record can be checked later. If a material fact is unresolved, record the question, the person responsible and the next action. The confidential-witness example remains open. A named owner makes the follow-up accountable; the entry still needs an outcome. Open the exact file proposed for release.
06:32 Checking the proposed disclosure
Read the appraisal as Alex would receive it. Confirm that the performance statement and agreed plan remain understandable, the professional attribution matches the decision, and the private contact field received the intended treatment. Then read related files together. A filename, email signature or covering note could disclose information that another part of the response removes. Where the review depends on protecting an identity, check the inference created by the package as a whole. The response also needs the applicable supplementary information under the right of access. Completing a document extract is one part of preparing that response. The organisation responsible for the case must connect the reviewed files to the rest of its response process. Our appraisal now has a proposed disclosure and an explanation another
07:37 The outcome and next step
reviewer can follow. Alex’s performance information remains, Jamie’s professional attribution remains on the stated facts, and the unrelated private contact field has a recorded treatment. The witness record remains a separate unresolved assessment. That distinction is part of an honest case record. The sources for this lesson and information about SafeRedact are in the description.
How SafeRedact Fits
SafeRedact is browser-based redaction software for data subject access requests. Files never leave your browser: documents are processed client-side, only extracted text and the case's data subject details are sent for AI detection, and no documents are stored on servers. Detection text is never used for training and is deleted within 30 days. You name the data subject whose information should be preserved, and other individuals' personal information is flagged for redaction across every file in the case, including ZIP and Purview PST exports. Every detection is reviewed by a human before anything is exported, and the export package includes the redacted files, a processing summary, an audit trail and a review decision log. Supported formats: PST, PDF, DOCX, XLSX, EML, MSG, HTML, TXT, CSV, JSON, ZIP. A Data Processing Agreement is available and enterprise cases are priced per case, with the price set with you and shown before you download.
Make Every Redaction Decision Once
AI detection flags every identifier in the case. You decide whose it is, with the requester's data preserved and every decision recorded in the exported audit trail. Cases are priced per case, with a Data Processing Agreement available.
Set up your organisationDSAR: The Complete Guide
DSAR Redaction Guide (Pillar) What Is a DSAR? Employee DSAR Redaction ICO DSAR Guidance DSAR Redaction Mistakes DSAR Response Template DSAR Compliance Checklist Automate DSAR Redaction DSAR Redaction Cost DSAR Software Comparison CCPA DSAR Guide US State Privacy Laws DSAR Cost CalculatorSources
- UK GDPR, Article 15 (right of access)
- Data Protection Act 2018, Schedule 2, paragraph 16 (information about other individuals)
- ICO, Information about other people in a SAR (right of access guidance, 8 December 2025)
- ICO, Supplying information to the requester (31 July 2025)
- ICO guidance is reproduced in summary under the Open Government Licence v3.0
This page is informational, not legal advice; the legislation, ICO guidance, and your counsel govern. The people, organisation and references in the worked example are invented. Miriam is SafeRedact’s virtual narrator; her voice and likeness are generated with AI. The lessons are written and checked by SafeRedact.