AEVOMIND INSIGHTS — PARTNER ACCESS

The Friday export: what sharing data by email costs, and what to give partners instead

21 October 2026 · 9 min read · By the AevoMind team

Two glass structures joined by one broad channel of flowing light, standing for a direct connection between two businesses' systems.

If someone runs an export every week and emails it to partners, you pay twice: in the hours it takes, and in the risk it reaches the wrong person. Sending data by hand is the most common kind of non-cyber breach reported to the ICO. The fix is letting partners see what is true now.

The short answer

If a person in your business runs an export every week and emails it to customers, suppliers or subcontractors, you are paying for that twice: once in the hours it takes, and once in the risk that it goes to the wrong person. Sending data by hand is the most common way personal data goes astray in the UK.

The fix is not a better spreadsheet. It is letting partners get the current answer themselves — a view of their own data, or a documented interface their systems can read — so nothing has to be sent at all.

A machined gold coupling joining two frosted glass tubes end to end, standing for a documented connection built to fit exactly.
A connection built to fit, rather than a file posted over the wall each week.

What the Friday export actually is

It usually starts reasonably. A partner asks for figures, someone obliges with a spreadsheet, and it becomes a standing arrangement nobody revisits. Within a year it is a routine: pull the report, tidy the columns, remove what the partner should not see, attach, send. Then field the replies — can you resend it, is this the current one, why does this row look wrong?

The file is out of date the moment it is sent, there is no record of who opened it, and the person who built the export is the only one who knows how. When they are on leave, the partner waits.

Where personal data actually goes astray

The ICO publishes every personal data breach reported to it. Set aside the cyber attacks for a moment and look at the ordinary, non-cyber incidents: the largest single category is not a hacker. It is someone sending data to the wrong recipient.

The most common way personal data goes astray is someone sending it to the wrong personNon-cyber personal data breaches reported to the ICO during 2025, by incident type
Data emailed to incorrect recipient2,459
Unauthorised access1,507
Failure to redact886
Data posted or faxed to incorrect recipient735
Loss or theft of paperwork588
Failure to use bcc434

Source: Information Commissioner's Office, data security incident trends (dataset Q1 2019 to Q4 2025), Open Government Licence v3.0. Our own count of distinct incident references for 2025 in the non-cyber category, which totalled 10,304; the file holds one row per incident per data type, so rows over-count. Excludes "other non-cyber incident" (1,697) and "not provided" (788), neither of which names a failure. These are breaches reported to the ICO, which is required only where a breach is likely to risk people's rights and freedoms, so they are not a count of all breaches or a rate per organisation.

Show the data
Incidents reported
Data emailed to incorrect recipient2,459
Unauthorised access1,507
Failure to redact886
Data posted or faxed to incorrect recipient735
Loss or theft of paperwork588
Failure to use bcc434

Of 10,304 non-cyber incidents reported during 2025, 2,459 — nearly one in four — were data emailed to the incorrect recipient. Add the posted and faxed equivalents, the failures to redact and the failures to use bcc, and more than four in ten non-cyber breaches are a person sending or disclosing something by hand to the wrong place.

Two cautions on that number, because it is easy to over-read. These are breaches reported to the ICO, not all breaches, and reporting is required only where a breach is likely to result in a risk to people's rights and freedoms. They cover every sector and size of organisation, so they are not a rate per business. What they do show reliably is the shape of the risk: the failure mode is manual handling, not sophistication.

Five glass towers where only one pair is joined by light and the rest trail off unconnected, standing for partners still exchanging files by hand.
Most partners are still connected by hand, with the data trailing off somewhere.

What it costs when it goes wrong

Sending a file to the wrong person is a personal data breach. Under Article 33 of the UK GDPR, a controller must notify the Information Commissioner without undue delay and, where feasible, within 72 hours of becoming aware of it, unless the breach is unlikely to result in a risk to people's rights and freedoms. The ICO's breach guidance sets out how to make that judgement.

Article 32 requires appropriate technical and organisational security for personal data in the first place. And where you are sending the same message to many people at once, the ICO's guidance on bulk communications by email recommends more secure means than a long address list — bulk email services, mail merge or secure data transfer — and proper policies and staff training behind them.

This is general information rather than legal advice. The practical point stands on its own: every weekly export is a repeated opportunity for a single wrong click to become a reportable incident.

The hours, measured

Take an illustrative business sending weekly data to six partners. The export itself is not the expensive part.

The Friday export, measuredIllustrative business sending weekly data to six partners: hours a week before, and once partners can get it themselves
By emailPartner access
Pulling and formatting the export2.50 hrs0.25 hrs
Checking and redacting before it goes1.50 hrs0.25 hrs
Answering “can you resend it?”2.00 hrs0.50 hrs
Correcting what went out wrong1.00 hrs0.50 hrs

Illustrative inputs, not client data. Totals: 7 hours a week against 1.5. The second column is not zero on purpose — someone still watches it and handles exceptions. Substitute hours you have measured.

Show the data
By emailPartner access
Pulling and formatting the export2.50 hrs0.25 hrs
Checking and redacting before it goes1.50 hrs0.25 hrs
Answering “can you resend it?”2.00 hrs0.50 hrs
Correcting what went out wrong1.00 hrs0.50 hrs

That is 7 hours a week against 1.5: about 5.5 hours back, or 23.8 hours a month — roughly 0.15 of a full-time person at 162.5 hours, which is a month of the ONS median full-time week of 37.5 paid hours. Modest, and it recurs every week for as long as the arrangement lasts.

Look at the third row rather than the first. Answering “can you resend it?” costs more than producing the export, because it is unplanned, it interrupts, and it scales with the number of partners. The method is the one in how many hours automation can save: measure your own cycle, then decide.

A gold valve wheel on a glowing frosted glass pipe, standing for controlling how much data a partner can draw and when.
Control is a tap you can turn down, not a file you cannot take back.

What to give partners instead

There are three options, and most businesses need the first long before the third.

  1. A view of their own data. The partner logs in and sees the current position for their records only. No sending, no version confusion, and the answer to “is this current?” becomes self-evident. This is what a client portal does, and it is covered in client portals for small businesses.
  2. A scheduled, controlled transfer into the partner's own system, rather than an attachment: the job of an integration hub, which is also what stops the same data being re-keyed in two places — see disconnected tools.
  3. A documented interface they can build on. When partners want your data inside their own systems, a public API with partner access gives them keys of their own, limits on how much they can draw, a sandbox to test against, a versioning policy so your improvements do not break their integration, and a record of which partners actually use you.

All three replace “we send them a file” with “they can see what is true now”, and all three leave a record of who read what — see audit trails.

A glass sphere with several narrow channels of light leaving it in different directions, standing for one system serving several partners on its own terms.
One system, several partners, each given its own controlled channel.

Where to start this week

  1. List every recurring export leaving the business: who builds it, who receives it, how often.
  2. Mark the ones containing personal data. Those carry the breach risk, and they are the ones to fix first.
  3. Time one cycle honestly, including the resend requests and the corrections.
  4. Ask each partner what they actually do with it. A surprising number paste it straight into their own system, which means they would rather have a connection than a file.
  5. Fix the noisiest one first, usually with a view rather than an interface.

The test of whether it worked is simple: nobody has to send anything, and nobody asks whether the figures are current.

Frequently asked questions

Is it against the law to email a spreadsheet to a partner?

No. Emailing data is not unlawful in itself. UK GDPR requires appropriate security for personal data, and the risk with email is practical rather than theoretical: it is the single most common kind of non-cyber breach reported to the ICO. If you do send a file to the wrong recipient, you may have to notify the Information Commissioner within 72 hours unless the breach is unlikely to result in a risk to people's rights and freedoms.

What should we give partners instead of a file?

Something that lets them get the current answer themselves: a partner view inside your system, or a documented API with its own keys and limits, so they can read only what belongs to them, only when they need it. For regular machine-to-machine exchange, outbound webhooks mean the partner is told when something changes rather than asking.

We are too small for an API. What is the first step?

Stop the resend requests, which are usually the largest single cost. Give each partner a view of their own data with its own login, so the answer is always current and nobody has to send anything. An API is worth building when partners want to put your data into their own systems, not merely read it.

How do we keep control once partners can reach the data?

Keys per partner rather than a shared login, limits on how much can be drawn and how often, a record of who read what, and a versioning policy so improving your system does not break theirs. Read access to a partner's own records is a smaller risk than a spreadsheet of everybody's records sitting in an inbox.

How do we measure what the Friday export costs us?

Time one cycle honestly: pulling and formatting the data, checking and redacting it, answering requests to resend, and correcting what went out wrong. Multiply the weekly total by 4.33 for a month, then divide by 162.5 to express it as a share of one full-time person. Most businesses have never measured the third item, which is usually the biggest.