Why have I forgotten most of what I achieved?
Because you were doing the work, not documenting it. This is the single most under-appreciated fact about the Digital Technology endorsement: the people who struggle most with evidence are not the least accomplished - they are the ones who shipped constantly and never kept a record. The one applicant quote that survived our full verification process says it exactly: "I had forgotten a bunch of them. This is why it is great to document your journey."
Read that again, because it reframes the whole exercise. The applicant did not lack achievements. They had a career full of them and simply could not recall them on demand when a blank Stage 1 form asked, in effect, prove you are exceptional. That gap - between what you have actually done and what you can remember doing - is where good applications quietly die. Tech Nation cannot endorse what you cannot articulate, and you cannot articulate what you cannot recall. The fix is not to feel more confident. It is to go digging.
Where is the evidence actually buried?
Every meaningful thing you built left a trace in a system somewhere. Your job is to treat those systems as an archaeological site and excavate them layer by layer. The evidence you think is gone is nearly always still sitting in tools you still have access to - or can regain access to with one email.
- Version control - your commit history, merged pull requests, code review comments and repository contribution graphs. These are dated, attributable proof of exactly what you built and when. A GitHub or GitLab profile is often the single richest dig site an engineer owns.
- Issue and project trackers - Jira, Linear or GitHub Issues tickets you owned, closed, or were assigned as the technical lead. Sprint boards show scope and ownership; incident tickets show that you were the person trusted to fix things when they broke.
- Observability and analytics - dashboards, Grafana panels, before-and-after latency or reliability metrics, revenue or adoption graphs tied to features you shipped. Quantified outcomes turn a claim into a documented result.
- Your inbox and calendar - old email threads announcing a launch, a promotion, an award, a conference acceptance or an invitation to advise. Calendar invites date-stamp talks you gave and panels you sat on. Payslips and offer letters corroborate seniority and salary trajectory.
- Everything public - merged open-source contributions, published articles, conference programmes, podcast appearances, patents, Stack Overflow reputation, npm or PyPI download counts, and press mentions of products you worked on.
None of this is written as evidence yet. That is the point. Archaeology is the step almost everyone skips - they sit down to "write the evidence" from memory, produce a thin list, and conclude they do not qualify. The record was there the whole time.
What is the excavation method, step by step?
Work through five digs in order. Each one feeds the next, and each is deliberately mechanical so that memory does the least possible work.
- Dig one - the timeline. Open a blank sheet and list every role, project and side-venture across your career with start and end dates. Do not judge relevance yet; just get the skeleton down. This is the map that tells you which systems to excavate.
- Dig two - the artefact sweep. For each entry on the timeline, open the corresponding tools and pull the raw traces: export your commit history, list your merged pull requests, screenshot the dashboards, search your inbox by project name. Save everything with its date attached.
- Dig three - the impact pass. Beside each artefact, write the outcome in one line: what changed because of this, and by how much. "Cut checkout latency by 40 per cent." "Owned the migration that let the team ship weekly instead of monthly." Numbers wherever they exist.
- Dig four - the external-signal hunt. Separate the finds that show recognition outside your own employer - a talk, an article, an open-source project others depend on, a press mention - from those visible only internally. Recognition existing only inside your own company is a recurring weakness; external signal is disproportionately valuable.
- Dig five - the shortlist. Rank every find by strength and by how cleanly it attributes to you personally. You are building toward a pack of up to 10 documents, so you can afford to be ruthless: keep only the artefacts that are dated, attributable and criterion-relevant.
How do I map my finds to the endorsement criteria?
Excavation gives you a pile of dated, attributable artefacts. The next task is to sort them against the criteria, because Tech Nation does not reward volume - it rewards coverage. You must satisfy the mandatory criterion plus at least two of the four optional criteria, and every document in your pack should be doing a specific job.
Lay your shortlist across the criteria like a grid. Which finds evidence the mandatory criterion of being a recognised or emerging leader? Which map to innovation, to contributions beyond your direct role, to technical or commercial expertise? An artefact that supports two criteria at once - say, an open-source project that shows both innovation and recognition outside your employer - earns its place twice over. The maximum is 10 documents of up to three sides of A4 each; your CV and your three recommendation letters sit outside that count, so do not waste document slots on things a letter or the CV already covers.
Source: GOV.UK - Global Talent visa (Digital Technology) and Tech Nation guidance. Requirements verified 6 July 2026; always confirm the current position on GOV.UK before applying.
Not sure your finds are strong enough?
Get a written, scored read of exactly what you already have - and precisely which gaps remain - before you commit a penny to government fees.
How do I turn a team effort into individual evidence?
This is where archaeology earns its keep, because the most common way strong applicants fail is by describing achievements at team level. Assessors repeatedly report marking applications down for "insufficient evidence of individual impact" - the work was real, but the applicant wrote "we shipped" and never showed which part was theirs. Endorsement is granted to a person, not a team.
Artefacts solve this in a way that prose cannot. A commit history is authored by you specifically. A design file carries your name as author. An incident you were paged for names you as the responder. A launch email you wrote and sent shows you owned the release. When you can point to a dated, attributable artefact, "we built a payments platform" becomes "I designed and shipped the reconciliation service inside our payments platform, and here is the pull request and the dashboard that prove it." That shift - from the collective to the personal, backed by evidence - is often the whole difference between an endorsement and a refusal.
How far back can I dig - does old work still count?
Dig everywhere, but weight recent finds most heavily. Evidence-recency confusion is a recurring reason applicants report weak assessments: items that fall outside the recent window are given little weight, and a pack built mostly from work six or eight years ago reads as a career in decline rather than a leader still operating at the top of their field. Your excavation should still surface older material - it establishes trajectory and belongs in your CV and personal statement - but the documents you actually submit should lean toward what you have built lately. If your strongest artefacts are old, that is a finding in itself: it tells you the real task is generating fresh evidence now, not just recovering the past.
How does the £99 Fit Assessment help me excavate?
Archaeology is work you can do alone, and much of this method is deliberately designed so that you can. Where the Fit Assessment adds value is judgement: once your finds are on the table, an experienced eye tells you which artefacts are genuinely strong, which criteria you already cover, and which gaps you must still fill before spending £561 on an endorsement fee. The report scores what you have out of 20, maps each artefact to the mandatory and optional criteria, and returns a 10-document evidence plan - a shortlist built from your own excavation rather than a blank template. It is available as a £199 option that includes a one-hour case discussion, a live walkthrough of the report with a human, and your chosen assessment fee is refunded in full if you engage Endorsa for a document-preparation package.
If the assessment shows the digging is more than you want to do alone, that is exactly what the service tiers exist for. Done-with-you (from £2,500) curates and maps your evidence with you and includes support for one endorsement review; End-to-End (£4,500) reconstructs the entire pack from scratch, coordinates your referees and drafts everything, and includes one free reattempt support if the outcome goes against you. The excavation still starts with you - nobody knows your career like you do - but you do not have to interpret the finds by yourself.
Frequently asked questions
That is the normal starting point, not a disqualifier. One applicant who succeeded described the same feeling - that they had forgotten a bunch of their achievements - and the fix was systematic reconstruction rather than memory. You rebuild the record from artefacts you already generated: commit histories, pull requests, tickets, dashboards, old emails, calendar invites and payslips. The evidence exists; it just is not written down yet.
Tech Nation generally expects your evidence to reflect recent activity, and items falling outside the last five years are a recurring reason applicants report weak assessments. Older work can still establish trajectory in your CV and personal statement, but the strongest documents in your pack of up to 10 should sit inside the recent window. Verify current guidance on GOV.UK before you apply.
You may submit a maximum of 10 documents, each up to three sides of A4. Your CV and your three recommendation letters sit outside that count. The task is not to reach 10 for its own sake; it is to satisfy the mandatory criterion plus at least two of the four optional criteria with the strongest artefacts your excavation surfaces.
It can, but only if you can attribute your individual contribution. Achievements stated at team level with no personal attribution are a recurring reason applications are marked as showing insufficient evidence of individual impact. Archaeology helps here: a commit history, a design file authored by you, an incident you were paged for, or a launch you owned turns "we shipped" into "I built".
The Fit Assessment scores what you already have out of 20, maps each artefact to the mandatory and optional criteria, and returns a 10-document evidence plan showing exactly which gaps remain. It is available as a £199 option that includes a one-hour case discussion - a live walkthrough of the report - and your chosen assessment fee is refunded in full if you engage Endorsa for a document-preparation package.
Related reading in this cluster: evidence (the 10 documents), endorsement criteria, recommendation letters, the personal statement and the full pain-point hub. Wider guides: who qualifies and Talent vs Promise.
Last updated: 6 July 2026. Facts verified against GOV.UK on 6 July 2026 - always confirm current requirements before applying.