Using a SAR in a telecom dispute

Start with the factual gap

Do not send a 30-item shopping list unless each item serves a purpose. Ask: what fact can the provider currently assert without showing the record? If the dispute is whether an order was accepted, seek order status history, decisioning data, confirmation records and signature metadata. If it concerns a callback, seek call recordings, CRM notes and callback tasks.

Useful telecom data categories

The document may contain personal data without the whole document being disclosable

Subject access is about personal data. A provider may lawfully supply extracted personal data rather than every internal document in original form, subject to the UK GDPR/DPA framework and exemptions. When challenging missing material, explain which personal data appears absent and why you believe it exists.

Transaction-specific records matter

Where a provider says no agreement was signed but its own disclosure records a signature timestamp, or says an application was declined despite an internal acceptance status, ask for the underlying transaction-specific audit. A generic blank agreement or current policy does not answer what happened in the individual order.

Preservation and retention

Providers can have lawful retention periods and some operational records may be routinely deleted. A SAR does not impose indefinite retention. If a live dispute depends on records you reasonably believe exist, request them promptly and consider sending a focused preservation request explaining the dispute and categories of evidence in question.

Use the disclosure to build a contradiction map

Compare external statements with internal records. Date each conflict and ask the provider to reconcile it. Avoid assuming that every inconsistency proves misconduct; some fields can refer to different stages of a process. The value comes from forcing precise explanation.

Ask for data categories that answer a disputed fact

Do not confuse a copy of a document with access to the personal data inside it

The right of access concerns personal data. A provider can sometimes satisfy the right without handing over an entire internal document exactly as stored, particularly where other people’s information or exemptions are involved. If something important appears missing, identify the personal data you say has not been supplied, for example, the status history of your order or the note recording why your account was closed.

Transaction-specific data is often more valuable than generic terms

A blank copy of today’s credit agreement does not prove what was presented in your checkout. A generic cancellation policy does not prove why your particular order was cancelled. A current training script does not prove what an adviser told you. Ask for records linked to your account, order, call or decision.

Metadata can matter: timestamps, event types, status transitions, user/team identifiers and decision codes can explain a chronology even where there is no single narrative note.

Internal codes need interpretation

An “ACCEPT”, “SUCCESS” or “CLOSED” field can refer to a specific processing stage rather than the whole transaction. Do not overstate the meaning of a code. Ask the provider to define the field, identify the system that generated it and explain what happened immediately before and after.

This makes contradiction analysis stronger: you are testing meanings against the audit trail rather than assuming that one label wins the dispute.

If records are said to have been deleted

Ask what category of record it was, the applicable retention period, when deletion occurred and whether any related personal data remains elsewhere. A lawful retention policy can mean records no longer exist; a SAR does not create an indefinite preservation duty.

Where litigation or a live complaint is reasonably contemplated, a separate focused preservation request can put the organisation on notice of the evidence categories in dispute. That is not the same legal right as a SAR, so keep the requests conceptually separate.

A SAR response can expose more questions than it answers

Create a three-column schedule: external statement, internal record, question requiring reconciliation. This is especially useful where the provider’s final response says one thing but account notes or system events show another.

Missing SAR data and the telecom complaint are parallel issues

If the provider fails to provide personal data properly, that can become an information-rights issue with its own ICO route. But continue the substantive telecom complaint using the evidence you already have. Do not let a SAR dispute unnecessarily freeze billing, fault, credit-file or ADR action.

Evidence checklist before you send the SAR

• Define the date range.
• Identify account/order/phone numbers needed to locate records.
• State the disputed fact each category relates to.
• Keep a copy of the request and proof of receipt.
• Track any ID clarification and the response deadline separately.
• When the response arrives, preserve the original files and metadata before reorganising them.