Why is my evidence rejected when my company was clearly successful?
Because the Tech Nation endorsement assesses you, not your employer. A product that scaled to millions of users, a funding round, a household-name logo on your CV - none of it is evidence of your own exceptional talent or promise unless the assessor can see the specific slice of that success you personally produced. This is the trap that catches the strongest candidates: the more impressive the company, the easier it is to hide behind its results and the harder the assessor finds it to isolate your individual contribution.
Two related patterns recur again and again in the reasons applicants and advisers report for non-endorsement. The first is recognition existing only inside your own employer - you were the go-to engineer internally, but nothing outside the building says so. The second is achievements stated at team level without individual attribution, which comes back as the phrase applicants dread: insufficient evidence of individual impact. Both are, at heart, the same failure. The narrative describes what a group accomplished; the criteria demand what one person did.
What is the difference between company success and individual impact?
Company success is the outcome the organisation reports. Individual impact is the decision, design, system or leadership act that is traceable to you by name. The assessor is not sceptical that your company did well; the assessor cannot award your endorsement on its results. The mandatory criterion and the optional criteria are all written about the applicant as an individual - see the endorsement criteria in full - so every claim has to resolve to a person, and that person has to be you.
Consider the honest difference between these two sentences. "Our platform reduced checkout latency by 40 percent and lifted conversion" tells the assessor nothing about the applicant. "I redesigned the checkout service's caching layer, the change that is documented in pull request #2841 and the post-launch dashboard, which reduced p95 latency by 40 percent" ties the same outcome to one named engineer through an artefact anyone can inspect. The result is identical. Only the second version is evidence of individual impact.
Evidence and criteria rules verified against GOV.UK on 6 July 2026. The individual-impact refusal pattern reflects reasons applicants and advisers recurrently report, including Tech Nation's own guidance on recommendation letters.
How do I know if a claim reads at company level?
Apply one test to every sentence in your personal statement and every supporting document: could a colleague copy this claim onto their own application without changing a word? If the answer is yes, the claim describes the company, not you, and it will not evidence individual impact. "We migrated the monolith to microservices" passes to any of the fifty engineers who touched it. "I owned the payments and identity services through the migration, evidenced by the architecture decision records I authored and the commits under my handle" belongs to exactly one person.
Three quick signals that a claim is failing the test:
- The subject is "we", "the team" or "the company". First-person singular is not arrogance here; it is the required grammar of the evidence. Rewrite until the subject of the sentence is "I".
- The outcome has no artefact attached. A number with no document behind it - "improved reliability", "grew the platform" - reads as a claim, not evidence. Every impact statement needs a named artefact the assessor can open.
- The recognition never left the building. An internal promotion, an internal award, a manager's private praise: real, but invisible outside your employer. It must be paired with external, verifiable signals to count.
What counts as an attributable artefact?
An attributable artefact is any document that ties an outcome to you by name. It is the difference between "we shipped" and "here is my commit history". The right artefacts differ by discipline, so name the ones that are true for your actual work rather than reaching for a generic list. These sit inside the pack of up to ten evidence documents, each no more than three sides of A4, alongside your CV and three recommendation letters.
| Discipline | Reads as company success | Attributable artefact for you |
|---|---|---|
| Backend / platform engineer | "The platform now handles 10x traffic" | Merged pull requests under your handle, architecture decision records you authored, the on-call incident review naming you as owner |
| Data scientist / ML | "Our model improved accuracy" | The experiment notebook or model card crediting you, a paper or pre-print listing you as author, the pull request that shipped the model to production |
| Product designer | "The redesign lifted engagement" | Named design files and prototypes, a case study crediting you, before-and-after screens tied to a specific commit or release you led |
| DevOps / SRE | "We hit 99.99% uptime" | A dashboard you built, the runbook or incident post-mortem listing you as author, the terraform or pipeline changes under your name |
| Founder / tech lead | "The company raised a round" | Board materials or a technical roadmap you authored, a talk credited to you, press or filings naming you as founder or technical lead |
| Open-source contributor | "The project is widely used" | Your commit history, maintainer status, a named module, an issue or RFC you drove to resolution |
Evidence rules - a maximum of ten documents, each up to three sides of A4, plus CV and three recommendation letters - verified against GOV.UK on 6 July 2026.
How do I rewrite team-level language into first person?
Work through your material claim by claim with a simple three-part shape: name the thing you owned, state what you personally did to it, then point to the artefact that proves it. Keep the company's outcome - you are not discarding the impressive number, you are attaching it to yourself. Here is the pattern applied to real examples.
- Before: "Our team built a fraud-detection system that saved millions." After: "I designed and shipped the feature-engineering pipeline at the core of our fraud-detection system, documented in the merged pull requests under my handle and the model card I authored; the system it fed reduced fraud losses materially in its first year."
- Before: "The company grew to 40 engineers during my time there." After: "I established and led the platform team from two engineers to nine, set its technical standards in the engineering handbook I wrote, and personally interviewed and onboarded six of the hires."
- Before: "We were recognised as a leader in our sector." After: "I was invited to speak on our approach at [named external conference], and my write-up of the architecture was published on [named external outlet] - both crediting me by name, independent of my employer."
The rewrite is rarely about doing more work; it is about surfacing work you already did but buried under the collective "we". As one applicant put it after digging back through their own history: "I had forgotten a bunch of them. This is why it is great to document your journey." The artefacts usually exist. The task is evidence archaeology - finding them and putting your name back on them.
Not sure which of your claims read at company level?
The £99 Fit Assessment scores your draft out of 20, flags every team-level claim, and returns an evidence gap analysis of the attributable artefacts you are missing.
Do my recommendation letters need to match?
Yes - attribution has to be consistent across the whole application, and the letters are where it most often falls apart. If your personal statement claims you led a piece of work, but your three recommendation letters speak only about the team's success in the same vague terms as your draft, the contradiction is doing your case damage rather than supporting it. Letters that are generic, or that simply mirror the personal statement, are confirmed by Tech Nation's own guidance as a primary reason for non-endorsement.
Brief your referees to do the opposite of the company narrative: ask each to describe a specific thing they personally saw you do, in their own words, with an example only they could give. A senior referee from a product-led digital technology company, writing "I watched her make the call to re-architect the billing system, against internal pushback, and it worked" is worth more than three letters praising the company's growth. The letter's job is to be a second, independent voice confirming your individual impact - not an echo of your statement.
Does this differ between Talent and Promise?
The attribution requirement is the same for both routes; the scale of impact expected differs. For Exceptional Talent, you are evidencing that you are already a recognised leader; for Exceptional Promise, that you are on that path. In both cases the assessor still needs the work traced to you by name - Promise applicants sometimes assume they can lean on the team because they are earlier in their careers, but a Promise application built on collective achievements fails for exactly the same reason a Talent one does. Choose the route honestly, then evidence your own slice of the work at the level that route expects.
How does the £99 assessment catch this before you submit?
The Fit Assessment exists precisely because individual-impact failures are invisible to the person who did the work - you know what you contributed, so your team-level sentences read as fine to you. The £99 report scores your draft against the mandatory and optional criteria out of 20, produces a component-by-component breakdown, and flags every claim that reads at company or team level, mapped to the specific attributable artefact that would fix it. You receive a branded PDF and an evidence tracker via secure download links, and a one-hour detailed report walkthrough - a live walkthrough of the report with a human who has seen these patterns before.
Your chosen assessment fee is refunded in full if you engage Endorsa for a document-preparation package, so it is a diagnosis you do not pay for twice: £99 before you risk £766 in government fees on an application that reads at the wrong level. If the report shows the gap is wide, the sensible next step is having the evidence rewritten properly rather than patching it yourself.
Frequently asked questions
Because the endorsement assesses you, not your employer. A recurring non-endorsement pattern reported by applicants and advisers is achievements stated at team or company level without individual attribution, recorded as insufficient evidence of individual impact. The assessor needs to see what you personally decided, built or led, evidenced by artefacts that carry your name. Verify current guidance on GOV.UK.
An attributable artefact is a document that ties an outcome to you by name: a merged pull request under your handle, a design credited to you, a conference talk listing you as speaker, a dashboard or incident review naming you as owner, or a patent listing you as inventor. It is the difference between "we shipped" and "here is my commit history". Verify current evidence rules on GOV.UK.
Yes. Working in a large team is not a barrier; failing to isolate your slice of the work is. The task is to name the specific component, decision or system you personally owned and to evidence it with artefacts that carry your name, rather than describing the team's collective output. Verify the current criteria on GOV.UK.
The £99 Fit Assessment scores your draft against the criteria out of 20, flags every claim that reads at team or company level, and returns an evidence gap analysis identifying which attributable artefacts you are missing. It is available as a £199 option that includes a one-hour case discussion, a live walkthrough of the report, and is refunded in full if you engage Endorsa for a document-preparation package.
No. The personal statement can claim individual impact, but the ten evidence documents and three recommendation letters must corroborate it. If your statement says "I led" and your artefacts say "we shipped", the assessor follows the evidence. Attribution has to be consistent across the statement, the artefacts and the letters. Verify current requirements on GOV.UK.
Related reading: all applicant pain points, the endorsement criteria, building the ten-document evidence pack, recommendation letters that do not backfire, the personal statement, Talent versus Promise, refused, and your 28-day window and the endorsement success rate.
Last updated: 6 July 2026. Facts on this page were verified against GOV.UK on 6 July 2026.