Can government agencies use offshore developers?

What state contract rules and federal data rules say, with quotes from the primary documents, what work usually can run offshore, and what subcontractors should check first.

Short answer: Government agencies can often use offshore developers through a contractor, but not for every project or every kind of data. Some states bar offshore services in their contracts, and federal rules for tax and criminal justice data require access from inside the US. Work on public websites, code and synthetic test data is the part most often allowed.

The answer depends on 3 things: the state, the data the system holds and the exact words in the contract. This guide shows where the limits come from, quotes the primary documents and ends with a checklist for subcontractors.

Is there one law that bans offshore developers?

No single US law bars offshore developers from all state and local government work. The limits come from 2 places.

State procurement law and contract terms can restrict where services are performed. Federal data rules restrict who can access certain data and from where.

That is why 2 projects for the same agency can get different answers. A public website rebuild may be open to an offshore team. A tax or criminal justice system usually is not.

The IRS Publication 1075 and the FBI CJIS Security Policy are the 2 federal documents that come up most often. We cover both below.

Which states restrict offshore IT work?

Several states write offshore limits into statute, standard terms or IT standards. The table compares 4 state examples and 2 federal data rules, with the primary source for each. It is a sample for planning, not a complete survey of all 50 states.

Examples of state and federal offshore rules for government IT work
RuleWhat it restrictsEffect on an offshore teamSource
New Jersey, P.L. 2005, c. 92State contracts primarily for services must say all services under the contract or any subcontract are performed in the US, unless the Director certifies otherwise and the Treasurer approves.Offshore work on covered service contracts needs a written waiver.NJ Treasury
Maryland, State Finance and Procurement 12-111Bidders must disclose whether they or a subcontractor plan to perform services outside the US, where, and why.Disclosure, not a ban. The agency sees the plan at bid time.Maryland General Assembly
Ohio Standard Terms and Conditions (Rev. 5-22-26)Cabinet agencies will not buy services provided outside the US, or allow State Data to be accessed, tested or stored outside the US, without a signed waiver.Covers both offshore people and offshore data. Waiver needed.Ohio Procurement
Oklahoma OMES Offshore Data Storage StandardState data must be hosted, processed, accessed and disposed of within the US. Offshore support is allowed only on systems that use public data.Public-data systems only. Regulated data stays onshore.Oklahoma OMES
IRS Publication 1075 (federal tax information)FTI cannot be accessed by contractors or subcontractors outside the US, its territories, embassies or military installations.No offshore access to any system holding FTI.IRS
FBI CJIS Security Policy (criminal justice information)State and national fingerprint-based record checks before unescorted access to unencrypted CJI.Offshore staff are kept away from unencrypted CJI in practice.FBI

Each row summarizes the linked primary document. Terms change, so check the version attached to your own solicitation.

What do the federal data rules actually say?

The 2 federal rules attach to the data, not the agency. If a state revenue, benefits or child support system holds federal tax information, Publication 1075 applies to every contractor and subcontractor that touches it.

Section 2.C.7 of Publication 1075 (Rev. 11-2021) says FTI "cannot be accessed by agency employees, agents, representatives, contractors, or sub-contractors located outside of the legal jurisdictional boundary of the United States." It adds that systems holding FTI must be maintained by personnel in the US, which "prohibits foreign remote maintenance, foreign call centers, help desks and the like."

The cloud section is just as direct. Agencies must use vendors where all FTI resides in the US and "all accesses, and support of the systems and services are performed from the United States, its possessions and territories."

The CJIS Security Policy, version 5.9.4, works through people screening. Section 5.12.1 says state of residency and national fingerprint-based record checks "shall be conducted prior to granting access to CJI" for anyone with unescorted access to unencrypted CJI. Newer CJIS versions exist, so ask the state's CJIS Systems Agency which version it audits against.

Sources: IRS Publication 1075, sections 2.C.7 and 3.3.1; FBI CJIS Security Policy v5.9.4, section 5.12.1.

Is data location the same as where people work?

No. These are 2 separate questions, and contracts often answer them in different clauses.

One clause says where data is stored. Another says where services are performed or from where systems may be accessed.

Ohio's terms cover both in one sentence. They bar services "provided outside of the United States" and any contract that lets State Data be "sent, taken, accessed, tested, maintained, backed up, stored, or made available outside of the United States" without a waiver (Ohio Standard Terms and Conditions).

Oklahoma separates them. Its standard requires US data hosting, yet it allows vendors a follow-the-sun model that includes application development, on systems that use public data only (OMES Offshore Data Storage Standard).

So a US-hosted environment alone does not settle the question. Read the place-of-performance clause and the remote access clause as well as the data clause.

What work can usually run offshore?

Where the contract allows it, offshore teams usually work on tasks that never touch restricted data or production systems. Oklahoma's standard draws the line plainly: "Offshore support is only permitted on systems that use public data," and regulated data such as HIPAA, FERPA and CJI "must be supported by onshore resources only" (OMES).

Work that often fits inside that line:

  • Front-end builds and design systems for public websites
  • Accessibility remediation of public pages and documents
  • Application development in non-production environments with synthetic data
  • QA, test automation and regression testing against test environments
  • Documentation and training material with no sensitive data in the source

Work that usually stays onshore: production support, admin access to agency systems and anything that holds FTI, CJI, student records or health records. Our guide to regression testing government web apps shows how test work can run on synthetic data.

What this means for subcontractors

Most offshore teams reach public-sector work as subcontractors to a prime. The prime signs the state's terms and flows them down, so the subcontractor inherits every clause in the table above. New Jersey's rule, for example, reaches services "performed under any subcontract" (NJ Treasury).

Before a prime adds you to a bid, check these points:

  1. Place of performance. Find the clause that says where services may be performed, and whether a waiver path exists.
  2. Data and remote access. Find where data must live and whether access from outside the US is allowed.
  3. Data type. Ask whether the system holds FTI, CJI, student or health records. If yes, plan for onshore staff on that part.
  4. Disclosure. Some states, such as Maryland, ask bidders to list offshore locations. Give the prime that detail early.
  5. Written split. Put the onshore and offshore tasks in the statement of work, so the agency can see who touches what.

Konnex works this way. Agency data stays in US-hosted environments, and our offshore engineers work only on code and synthetic test data. Where a contract requires all work in the US, we say so before the bid.

See our delivery and compliance model, the SLED IT overview and how primes buy from us. For teaming terms, read our post on prime and subcontractor teaming on state contracts.

Quick answers

Is there a federal ban on offshore developers for state and local government?

No single federal law bans them. Federal rules restrict specific data instead, such as IRS Publication 1075 for federal tax information and the FBI CJIS Security Policy for criminal justice information.

Which states restrict offshore IT services?

Examples include New Jersey (services in the US unless waived), Ohio (no offshore services or State Data without a waiver) and Oklahoma (state data stays in the US). Maryland requires bidders to disclose offshore plans.

Can offshore developers work on a system with federal tax information?

Not on the FTI itself. Publication 1075 says FTI cannot be accessed by contractors or subcontractors outside the US and its territories.

Does hosting data in a US cloud region make offshore work allowed?

Not by itself. Some contracts, such as Ohio's terms, also restrict where services are performed and from where data is accessed.

Sources for these answers: IRS Publication 1075, Ohio Standard Terms and Conditions, NJ Treasury.

This is general information, not legal advice. Rules vary by state, agency and solicitation, so read the documents for your own contract and ask counsel.

Sources

Planning a project with an onshore and offshore split? Contact Konnex to talk through the scope.