This guide is for digital leads, programme owners and procurement teams at public bodies, municipalities and state-owned agencies who are deciding what a remote supplier should own. It sits in the industry platform playbooks and links to Netbase's digital transformation consulting service.
In this guide
- Why is a public digital service harder to hand to a supplier?
- Which parts can a remote partner own, and which stay with you?
- How do you test a remote supplier with no public-sector record?
- When should a public body not use a remote partner?
- Where AI fits
- What delivery record exists, and what does not?
- Alternatives: other ways to source the work
- Limits of this guide
- Frequently asked questions
- Next step
Why is a public digital service harder to hand to a supplier?
A public digital service is harder to hand over because the public body cannot hand over its duties. It still answers for who is eligible, how personal data is held, whether everyone can use the service and how decisions can be appealed. A supplier can do the work; the accountability stays with the public body.
Three features make the split different from a private project. Public services have no competitor to fall back on, so a citizen who cannot finish an application online has nowhere else to go. Accessibility is a legal duty in many places: the EU directive on public-sector websites and mobile apps requires an accessibility statement with a feedback route. And published standards, such as the GOV.UK Service Standard with its 14 points, set expectations on open code, reliability and performance data that a supplier must meet as well.
Which parts can a remote partner own, and which stay with you?
The matrix below splits a public digital service into six parts. "Shared" means the partner does the work and a named public officer signs it off.
| Part of the service | Who should own it | Main risk | Move it to the partner when |
|---|---|---|---|
| Policy, eligibility and decisions | Public body; the partner only codes the rules it is given | Rules coded from an unclear policy | Never; keep it in house |
| Discovery and user research | Shared: partner runs interviews and journey maps | Research done without access to real users | The public body arranges user access and joins the sessions |
| Service design and accessibility | Shared: partner prototypes and tests against WCAG 2.2 | Sign-off left to the supplier | A named officer owns the accessibility statement |
| Build and integration | Remote partner, by milestone, in the client's repository | Code or licences the body cannot take back | Source code and IP terms are in the contract |
| Hosting and data | Public body, with partner scripts and runbooks | Data stored where the law does not allow | The body chooses and controls the hosting account |
| Run, support and change | Remote partner under an agreed scope | Silent dependency on one supplier | Response targets, reports and an exit plan are agreed |
The pattern is simple: the closer a part sits to a decision about a citizen, the more of it the public body keeps.
How do you test a remote supplier with no public-sector record?
You test a supplier with no public-sector record by asking for evidence against published public standards rather than for references it cannot give. Each check below maps to a public source, so the answer can be compared across bidders.
-
Ownership of code and IP
Ask who owns the code written for you and which parts are licensed products. The US Digital Services Playbook asks that software and data made by third parties stay under the agency's control.
-
Exit and handover
Ask for a handover plan: repository access, documentation, a runbook and a period of joint running. See our transition and knowledge transfer plan for a template.
-
Accessibility evidence
Ask how the team tests against WCAG 2.2 and who writes the accessibility statement and handles feedback. For a content-heavy public platform, see layered, accessible science stories.
-
Security practice
Ask which controls the supplier runs on its own operations, and which it will build into your service. Our list of security questions for a development partner covers the core set.
-
Hosting you control
Ask whether the service can run in an account the public body owns, in the jurisdiction it chooses.
-
Reporting cadence
Ask how often you will see progress, risks and the backlog, and in which tool.
-
AI under human approval
Ask where AI is used in delivery or in the service, and which person approves each output that affects a citizen.
-
A stop rule
The GOV.UK guidance on discovery says it is not a failure to stop after discovery if research shows that is the best course. Ask the supplier to commit to that exit point in writing.
A supplier that answers all eight with documents, not promises, is a stronger bid than one with references and vague answers.
When should a public body not use a remote partner?
A remote partner is the wrong choice in four cases. The first is work that needs people on site every day or staff with a national security clearance. The second is data that must not be reached from outside the jurisdiction, even for support. The third is a tender limited to suppliers on a framework the partner is not on. The fourth is policy work itself, where the job is to decide rules, not to build software.
In those cases, a remote partner can still help in a smaller role: a second opinion on architecture, a build of an open component, or test support that never touches live personal data.
Where AI fits
AI helps public services most where staff read and sort large volumes of text. Document AI can read an uploaded form or certificate into draft fields for a caseworker to check, and a retrieval-based assistant can answer staff questions from approved guidance with a link to the passage it used. A named officer approves every decision about a citizen, and the model never decides eligibility on its own.
Netbase works with the major commercial and open-source AI tools and models, chosen per project, which also lets a public body keep a model it already approved. The intelligent document processing page describes what Netbase builds.
- In delivered work
Document AI
A document AI platform that reads and extracts business documents; the client is not named and it is not a public-sector project.
- In delivered work
Knowledge assistant
A retrieval-augmented (RAG) knowledge assistant; the client is not named and its sources are not published.
- Available capability
Caseworker triage
Sorting and routing incoming requests for a human caseworker; not yet tied to a published public-sector case.
What delivery record exists, and what does not?
Netbase has no public-sector or e-government project on record, and this page claims none: no government client, tender, framework listing or security clearance. What exists is adjacent delivery. Netbase has delivered projects for clients in travel and hospitality, healthcare, real estate, manufacturing and logistics, and events, and these clients are not named.
Delivery follows a six-step lifecycle: discovery and strategic alignment; team assembly and architecture planning; agile execution with outcome-based milestones; modular and productized components; training, rollout and optimization; and ongoing support and co-building. Governance runs on weekly reviews, KPI dashboards and a dedicated account manager and project manager. Progress is tracked in Jira, Redmine, Trello or GitHub, where the client can check it at any time.
For custom development the client owns the IP created for it, while Netbase productized modules are licensed, not transferred. Most projects run on fixed-price contracts, with milestone-based, monthly team retainer and KPI-linked models also offered; engagement can be project-based, a dedicated team, on-demand support or fully managed delivery. After launch, Netbase runs, maintains and upgrades what it builds, remotely and alongside the client's team, under an agreed support scope with response targets set per contract.
Netbase's security practices include secure code review, TLS in transit and AES at rest, role-based access control, MFA for admin dashboards, vulnerability scanning, penetration testing and disaster recovery. Netbase holds ISO 27001 certification and a SOC 2 Type II attestation for its own operations; neither extends to a client's service or hosting.
Alternatives: other ways to source the work
A remote partner is one of several routes. Choose by who keeps knowledge and control after launch, not by who looks cheapest.
| Route | Choose it when | Watch for |
|---|---|---|
| In-house digital team | The service is core and long-lived, and you can hire | Hiring time and skills the body cannot keep |
| Local integrator on a framework | A framework or on-site work is required | Lock-in to one supplier's platform |
| Shared government platform or building blocks | A common component already exists, such as identity, payments or messaging | Fit with local rules; GovStack publishes reusable building-block specifications |
| Remote partner for build and run | Code, hosting and exit stay under your control | The eight checks above |
| Mixed: in-house lead, remote build team | You have a product owner but not enough engineers | Clear sign-off on design and accessibility |
The healthcare workflow platform requirements guide shows the same split for regulated patient data, and the manufacturing and logistics workflow automation guide shows how to pick the first workflow to automate.
Limits of this guide
- It is a general guide, not legal or procurement advice; check your own accessibility, data and procurement rules.
- It names standards from the UK, the US and the EU as examples; your country may set different ones.
- Netbase has no public-sector record, so the delivery view comes from adjacent registered work only.
Plan the next step with a Netbase consultant
Frequently asked questions
Yes, a remote partner can build and run a government digital service if the public body keeps policy, data control, accessibility sign-off and the right to exit. The partner should work in repositories and hosting accounts the body owns, so the service can move to another team.
A public body should never hand over decisions about eligibility, policy rules or appeals. A supplier can code the rules it is given and build the screens, but a named public officer must own each rule and sign off each change to it.
Ask the supplier to test each release against WCAG 2.2 and to report the results, and keep a public officer as owner of the accessibility statement. Test with real users who rely on assistive technology, arranged by the public body.
No. Netbase has no public-sector or e-government project on record and names no government client. It offers consulting, build and operation as a capability, backed by unnamed delivery in other industries and its own security practice.
Next step
Send us one public service journey and the parts you want a partner to own, and we will review the ownership split with you.
Related services and solutions
AI-enabled digital transformation consulting that ends in a delivery plan Netbase provides digital transformation consulting for mid-market companies that need a prioritized roadmap with a delivery path, not a deck. We rank every change by value and risk, including where AI removes manual work, and the same team builds it. According to CEO Huy Nguyen (David), Netbase has served 500+ businesses across 80 countries since 2012.
Learn More
Enterprise integration hub ready for AI agents: one monitored layer for commerce, ERP and CRM data An enterprise integration hub is a central layer that moves orders, customers, stock and invoices between your commerce, ERP and CRM systems, with monitoring, retries and replay in one place, and scoped APIs that AI agents can call safely. Netbase builds it as a custom layer on the stack you already run, starting from the flows that break most often.
Learn More
Intelligent document processing with AI: from orders, invoices and forms to validated data Intelligent document processing is AI-driven intake that reads orders, invoices and forms, extracts the fields your systems need, validates them against business rules and routes each record to the right queue, with people reviewing anything uncertain. Netbase offers it as a growth capability built on its computer vision and automation work, including a document AI platform for an unnamed client.
Learn More
Work with Netbase remotely
Every Netbase engagement is delivered remotely, so clients in any country and any industry can work with us; Netbase has worked with clients in 80 countries. Contracts and invoices are issued by Netbase JSC, and payment is made by bank transfer to Netbase JSC's company account or PayPal Business. Talk to the CEO, Huy Nguyen (David), on WhatsApp or by email.
Discuss a project
Netbase JSC helps organizations design, build, modernize, and operate digital products and AI-enabled business systems.project@netbasejsc.com
+84 937 869 689
91 Nguyen Chi Thanh, Dong Da, Hanoi, Vietnam
Get in touch
Tell us what you want to build, modernize, or operate.