Offshoring on UK government contracts is sometimes allowed, but never on your say-so. The buyer decides in the contract and its security schedule, and DWP wants approval before any part of the service moves abroad, staff access included. Before you bid, map who works where on which systems, disclose it, and design the seats that touch live data so the buyer can say yes.
Is offshoring allowed on a UK public-sector contract?
There's no single rule. The security.gov.uk supply-chain guidance is written for buyers and says it's the contracting authority's job to identify and manage risk in its procurements and supply chains. Whether your engineers in Poland are acceptable is a call each buyer makes for its own contract.
That guidance splits offshoring into three forms: hosting abroad, access by support staff from abroad, and control of the host by a non-UK country. The policy framework for offshoring OFFICIAL data and services is, in its words, "available on request for departments". You can't read it as a supplier, so the practical move is to ask the buyer's security contact which rules apply to your contract, before the bid.
NHS trusts and councils set their own terms, so read the contract and ask the contracting authority.
Does remote access from Poland count as offshoring?
Three separate questions sit under that word. Answer each one on its own.
Hosting
GOV.UK's multi-region cloud guidance says OFFICIAL data can be stored and processed in overseas cloud regions when the legal, data protection and security arrangements are satisfactory. It covers public cloud and SaaS only, and it excludes SECRET and TOP SECRET. It sets no UK-location requirement for OFFICIAL data and says nothing about buyer-specific rules.
Access
Hosting in the UK doesn't settle it. DWP's offshoring policy for contractors lists staff outside the UK accessing UK-hosted DWP systems or information as offshoring. Under DWP's policy, a Polish engineer logging in to a London-hosted system counts. The multi-region guidance says nothing about remote access, so don't read its hosting freedom as access freedom.
People
The Baseline Personnel Security Standard (BPSS) is the minimum check for people working within and for government, including contractors and suppliers. It covers identity, right to work, employment history and unspent criminal convictions. Lack of UK residency "may not be an automatic bar", and someone who spent six months or more overseas in the last three years needs original supporting documents, such as overseas employment or academic references.
What the standard doesn't settle is how a person with no UK right to work is treated. Ask the buyer. The criminal-record leg is the one that varies by country, and we cover criminal-record checks by country separately. Clearance above BPSS is another question for the buyer. The standard also bars overseas suppliers from SECRET or higher assets, which doesn't touch OFFICIAL work.
What do I have to disclose, and when?
DWP is the worked example here, and it's one department's rule, not a national one. Other buyers will differ, so use it as a pattern to ask about.
At bid, you disclose through the information security questions. After award, you send a change request notice to the contract manager. Either way, approval comes before offshoring starts. The submission covers:
- the service and the offshore locations
- privileged users and network connections
- subcontractors, software development and cloud use
- a technical risk assessment proportionate to the arrangement
If you're the lead contractor, you also tell DWP about your subcontractors' offshoring. A contractor that moves work abroad without informing DWP first is in breach, and DWP acts contract by contract.
So the cheapest time to disclose is the bid. A change request mid-contract means asking permission to alter a service the buyer already scored.
What will the buyer ask about my overseas developers?
Expect questions about access, not just location. The security.gov.uk guidance tells buyers to weigh international staffing against the level of access and the criticality of the service, and to include appropriate vetting for staff based internationally. It also says buyers can ask for a supply-chain map: a full inventory of suppliers, subcontractors and information flows. It lists Cyber Essentials among the accreditations a buyer may require, and Cyber Essentials scope for contractors is worth settling early.
The guidance includes one case study worth copying. Every bidder relied on overseas development teams, so the department required software code review by fully vetted UK-based staff before go-live. That's one mitigation a buyer can require, and it leaves the overseas developers on the work.
Which of my countries need extra data steps?
This is a data-protection question, separate from the buyer's offshoring approval.
UK adequacy regulations cover every EEA country, so Poland, Hungary, Slovakia, Slovenia, Romania and Spain need no transfer mechanism for UK personal data. Serbia sits outside the EU and EEA and isn't on the ICO's adequacy list.
The ICO treats making data accessible to a separate organisation outside the UK as a restricted transfer, so a Serbian engineer engaged through their own company or as a contractor who can see personal data needs a transfer mechanism (the IDTA or the UK Addendum) and a transfer risk assessment. DWP asks for that assessment too when personal data goes to a country without adequacy. The mechanics are in IDTA and transfer risk assessment for Serbia.
None of this bars Serbia. It adds paperwork, and you disclose it alongside the location.
What should I put in the bid?
A staffing and access map: one table that answers all three questions before the buyer asks. Here's an illustration, with an invented supplier. A SaaS company with 12 engineers bids to build a case-management tool for a department. Six engineers are in the UK, four in Poland and two in Serbia.
| Group | Location | Access | Disclose | Ask the buyer |
|---|---|---|---|---|
| 6 engineers | UK | Production, live data, code review | Names, roles, check status | Which checks apply |
| 4 engineers | Poland | Source repository, test data only | Country, systems, privileged or not | Approval before work starts |
| 2 engineers | Serbia | Source repository, test data only | Same, plus transfer mechanism and assessment | Approval; whether Serbia is acceptable |
| Cloud host | Region | Hosting | Region, subprocessors | Whether the region is allowed |
"Privileged" means admin or production access. We'd keep that and live data with the UK six and give the overseas engineers a repository and test data, which mirrors the code-review arrangement in the security.gov.uk case study and gives the buyer a version they can approve. If the contract bars offshoring outright, the same map tells you how many UK seats to price.
What this means for your next UK public-sector bid
The decision is which engineers may touch the system and the data, and you need it before the bid or the call-off, not after. Give that decision to one named owner, usually the CTO, and have them build the map from the bid section and send it to the buyer's security contact before anyone writes the answers. If the contract rules out offshoring, plan UK seats and price them. If the real argument is internal, because your board wants engineering moved abroad, the board's case for offshoring engineering is the next read.
If your plan includes engineers outside the UK
The map shows which seats can sit abroad, and those are the ones you may need to fill once the buyer approves a location. HighCircl places senior engineers in seven countries: Poland, Hungary, Slovakia, Serbia, Slovenia, Romania and Spain. Serbia is the one outside the EU and EEA, which matters for the data steps above. Matching takes 72 hours, so the seat needn't hold up the bid. Whether a given engineer may work on a government contract is the buyer's decision, so ask for it first. You can hire senior nearshore engineers.
FAQ
Can offshore developers work on UK government contracts?
It depends on the buyer and the contract. DWP's offshoring policy requires its approval before any offshoring begins, and defines it as any arrangement where part of the service may occur outside the UK. Other buyers set their own terms, so ask the contracting authority.
Does a developer working remotely from Poland count as offshoring?
In DWP's policy, yes, where they access UK-hosted systems or information. For other buyers, check the call-off terms and the security schedule.
Do my developers need BPSS?
BPSS applies to people working for government, including contractors and suppliers. The contract or the buyer says which roles need it. Whether someone based abroad can complete it isn't settled in the standard, so ask the buyer.
Is Serbia treated differently from Poland?
For data transfers, yes: Poland is covered by UK adequacy regulations and Serbia isn't, so a Serbian engineer engaged through their own company or as a contractor who can see personal data needs a transfer mechanism and a risk assessment. The offshoring approval is a separate step, and Serbia isn't barred.
Can OFFICIAL data be stored outside the UK?
Yes, in public cloud and SaaS, when the legal, data protection and security arrangements are satisfactory. Not for SECRET or TOP SECRET.
Sources
- security.gov.uk: Tackling security risk in government supply chains
- GOV.UK: Offshoring policy for DWP contractors, a guide
- GOV.UK: UK government baseline personnel security standard, version 7.0
- GOV.UK: Multi-region cloud and software-as-a-service
- ICO: International transfers, a guide
- ICO: Is the restricted transfer covered by adequacy regulations?
