Why can a public-sector project count as evidence?
Government and public-sector work can count because the Digital Technology route does not care who paid for the work — it cares whether the work is real product or platform engineering and whether you can be shown to have driven it. A national identity platform, a tax or benefits service used by millions, a health-data pipeline, or an open-source tool released by a state agency are all, on their face, exactly the kind of technology the route is designed to recognise.
The endorsement asks you to satisfy the mandatory criterion and at least two of four optional criteria, and public-sector projects often map cleanly onto them: leading the technical build of a significant new service, or making a proven contribution to a field-advancing platform. Scale is frequently on your side — few private companies serve an entire population, and a service adopted across a country is a strong impact story when it is told correctly.
What are the exceptions and nuances?
The nuance is that "public sector" covers a wide spread of work, and not all of it reads as digital technology to an assessor. The recurring risk reported by applicants and advisers is work being judged "not product-led". Routine IT administration, systems integration, procurement management, or configuring off-the-shelf software for a department does not evidence the same thing as designing and building a platform. If your government role was closer to operations or vendor management than to engineering, the project alone will not carry the application.
A second nuance is confidentiality. Some public-sector work is sensitive, and you may not be able to disclose figures, architecture, or internal detail. That constrains how much of your strongest evidence you can actually show, and it is worth planning around early rather than discovering it late. Where you cannot publish specifics, senior recommendation letters that speak to your contribution become disproportionately important.
Because any judgement here is a judgement, be clear-eyed: a public-sector project counts as supporting evidence, not a guarantee of endorsement. It is one signal among several, and it is weighed on substance.
Is your government project strong enough to lead with?
A £200 Fit Assessment scores your evidence and tells you honestly, before you spend £766 in government fees.
How do you actually present a public-sector project?
Present it as product and platform work first, and as government work second. Lead with what was built — the system, the users it served, the technical problem it solved — and only then note that it was delivered inside the public sector. Make the reach concrete: numbers of users, adoption across departments or regions, measurable outcomes, and anything that shows the work mattered beyond the organisation that commissioned it.
Within the evidence pack — a maximum of ten documents, each up to three sides of A4, with your CV and three recommendation letters sitting outside that count — a public-sector project is usually evidenced through a combination: a written description of the platform and your role, public references where they exist, released code or documentation, and letters from senior people who can attest to your individual contribution. Where the work is confidential, lean harder on the letters and on any element that has become public.
What is the common mistake?
The common mistake is describing the project at the level of the department rather than the level of the person. Applicants write that "the team delivered" or "the ministry launched", and the assessor is left unable to see what the individual did. Achievements stated only at team level are one of the most frequently reported reasons applicants are told there is insufficient evidence of individual impact — and public-sector work, with its large teams and collective language, is especially prone to it.
A related mistake is relying on recognition that exists only inside the same public body. If every referee and every proof point comes from within the department, the picture looks internal rather than field-wide. Strong applications attribute specific decisions and components to the applicant by name, and reach for at least some recognition — a citation, an external adopter, a speaking invitation, an open-source following — from beyond the immediate employer. Referees should be senior and, ideally, connected to product-led digital technology, and their letters must say something specific rather than echoing your personal statement.
How does the £200 Fit Assessment help?
The £200 Fit Assessment exists precisely for cases like this, where the answer is "yes, but it depends on how it is framed". You upload your documents, and the assessment scores your profile out of twenty with a component-by-component breakdown — the mandatory criterion, each optional criterion, your letters, your documentation and an integrity-risk adjuster — so you can see whether your public-sector project is carrying weight or quietly failing the product-led test.
You also receive a Talent-versus-Promise route recommendation, a ten-document evidence plan, a letter and referee strategy, a risk register and a gap analysis, plus a forty-five-minute review call to walk through it live. The report is credited in full against any package within fourteen days. It will not guarantee an outcome — nothing honestly can — but it will tell you, before you commit the endorsement and visa fees, whether your government work is an asset to lead with or a story that still needs rebuilding.
Frequently asked questions
Yes. Public-sector or government digital work can evidence significant contribution and impact, provided the technology work is genuine product or platform work and your individual role in it is clear. It is treated as one supporting signal, not an automatic pass — the assessment is about the digital technology you built and the difference you personally made, not the prestige of the department.
Internal government platforms and services can count, provided they are real product or platform engineering rather than routine IT administration or procurement. A citizen-facing service, a shared data platform, or an internal tool used at scale across a department can all evidence impact. The recurring risk is work judged not to be product-led, so the framing must make the build and the reach explicit.
Attribute specific decisions, components and outcomes to yourself rather than to the team or the department. State what you personally designed, built or led, and support it with recommendation letters from senior people who can confirm your individual contribution. Achievements stated only at team level are a common reason applicants are told there is insufficient evidence of individual impact.
Recognition existing only inside your own employer is a recurring weakness, so at least some evidence and referees should reach beyond the immediate department. A referee should be senior and, ideally, connected to product-led digital technology. Letters that are vague, generic, or that mirror your personal statement are a primary reason applications are not endorsed.
Related reading: the 10-document evidence pack, individual impact vs company success, does GitHub count as evidence, recommendation letter rules, who can be a referee and the pain points hub.
Last updated: 6 July 2026. Facts on this page were verified against GOV.UK on 6 July 2026.