I have been working with Tech Nation endorsement applications for six years. Up until this year, my success rate was consistently above 90%. That was not because I had some special knowledge others did not have. It was because what was written in the Notion guide was what assessors actually applied. The guidelines were not always easy to interpret, but once you understood them the process was consistent. You could build a portfolio that met the published criteria and expect it to be assessed against them.

Things have changed. The bar has risen, and that is entirely Tech Nation's right as the endorsing body. They can set the standard at whatever level they consider appropriate.

But what I get increasingly worried about is not the bar. It is the gap that has opened up between what the Notion guide says and what assessors are actually applying. People prepare carefully using the published guidance. They build portfolios that satisfy every criterion as written. And they receive rejections citing standards, thresholds and distinctions that were never in the guidance they prepared from. That gap is what this post is about.

The letters contradiction: the most important thing to understand

What the guidelines require from your referees

The Tech Nation Notion guide sets out what your three referees need to be. Each person needs to be an established expert in digital technology, who has known your work for at least 12 months with detailed knowledge of your achievements, skills, experience and contribution. They need to be able to provide specific examples.

That is a meaningful requirement. Twelve months of detailed knowledge is not something a stranger can provide. Your referees, by necessity, are people who have worked with you, mentored you, invested in you, or collaborated with you. They are part of your professional world.

What assessors look for in those letters

Here is where the contradiction emerges. The standard I consistently see applied in assessments is that letters from your immediate professional network are treated as personal endorsements rather than independent sector-level recognition. A letter that is specific, detailed and evidenced can still be considered insufficient if the assessor reads it as coming from someone too close to the applicant.

These two standards cannot both be satisfied at the same time. Someone who has known your work in detail for more than a year is, by definition, a professional contact. They are in your network. You cannot simultaneously have someone with 12 months of deep professional knowledge of your work AND have them be independent of your professional circle. The guidelines require the first. In practice, the second is what gets scrutinised.

The distinction that appears to matter, based on what I have seen succeed and fail, is the difference between vouching and expert assessment. A letter that reads as "I know this person and I can tell you they are excellent" tends to fail, even when it includes specific examples. A letter that reads as "in my capacity as someone with expertise across this field, I have observed this person's work and it is exceptional relative to what I typically see" tends to succeed. The framing matters as much as the content. But this distinction is never explained in the guidelines, and most applicants and most referees would have no way of knowing it.

The published standard: "Three letters of recommendation from three different well-established individuals acknowledged as experts in the digital technology field, with detailed knowledge of your work over a period of 12 months or more." Each letter writer must "be an established expert in digital technology" and "have known your work for at least 12 months."

What assessors apply in practice: Letters from your immediate professional network are treated as personal endorsements rather than independent sector-level recognition, even when written by someone who meets the published 12-month requirement exactly.

How I'd approach it: Honestly? I am not sure which one Tech Nation wants. Do they want someone who has known your work closely for 12 months, which by definition makes them part of your professional network? Or someone independent of your network, who by definition cannot have detailed knowledge of your work? These two requirements cannot both be satisfied simultaneously. My working approach is to get someone who meets the 12-month requirement and brief them to write in the voice of an expert assessing your standing in the field, not a colleague vouching for you. It does not resolve the contradiction, but it is the best available strategy.

Mandatory criteria: the undocumented thresholds

The bar is sustained, sector-wide recognition, not one or two things

The Notion guide describes the mandatory criteria as requiring recognition as a leader or emerging leader in the digital technology sector. What I consistently see applied in practice is something closer to a pattern of sustained recognition across multiple sources and over time. A single award, a single conference appearance, or a single published piece tends not to satisfy the standard even when it is a strong one. Assessors are looking for a pattern, not an instance.

The types of evidence that appear to satisfy this standard consistently are: coverage in established technology media with editorial credibility, speaking roles at major industry conferences where you were invited rather than applied, recognised industry awards granted to you in recognition of achievement rather than competition entries, and letters from people who can speak to your reputation across the broader field. Each of those on its own may not be enough. Together, they build a picture of sustained recognition.

It is also worth noting that a single strong piece of evidence is rarely enough on its own, even for Exceptional Promise candidates. A single award, a single speaking invitation, or a single published piece tends not to satisfy the sustained pattern the assessment appears to look for. Promise candidates sometimes assume a lower bar means fewer pieces of evidence are needed. What appears to differ is the threshold of the individual pieces, not the expectation of a pattern.

The published standard: "Be recognised as a leader or emerging leader in the field of digital technology."

What assessors apply in practice: A pattern of sustained recognition across multiple sources and over time. A single award, talk or article tends not to satisfy it, even though the guidelines do not define what constitutes a sustained pattern.

How I'd approach it: Build a body of evidence that shows a pattern, not a single instance. Multiple types of recognition across different sources, spread over time, appear to carry more weight than one strong piece of evidence.

National recognition and the wider sector question

One of the more frustrating patterns I have seen is how local ecosystem contributions are treated versus wider sector recognition. An applicant with a significant role at an EU national-level accelerator had that contribution noted as useful to the local startup ecosystem but not as evidence of recognised leadership in the wider digital technology sector.

The problem is that the guidelines do not define what "wider" means. They do not say recognition must be international. In fact, the Tech Nation guidance explicitly lists national awards as eligible evidence for some criteria. If national recognition counts for awards, it is not obvious why a significant national-level role does not constitute sector recognition. For applicants from smaller tech ecosystems, national recognition can genuinely represent more influence in their field than a peripheral role at a large organisation in a major tech hub. But the practical standard that appears to be applied is one of sector-wide visibility that goes beyond your immediate geography, even though that standard is never stated.

The published standard: The Notion guide lists national awards as eligible evidence for some criteria. No geographic threshold is stated for mandatory criteria recognition.

What assessors apply in practice: A national-level role in a smaller tech ecosystem can be treated as local rather than sector-wide, even though the guidelines never define what sector-wide means or at what geographic level recognition must operate.

How I'd approach it: If your recognition is primarily national, supplement it with anything that demonstrates reach beyond your immediate geography, even modestly. International speaking invitations, coverage in publications read outside your country, or engagement with global communities in your field all help signal sector-wide rather than local visibility.

Media coverage: when does an interview count?

The Notion guide says media coverage counts as evidence. The published language is: published material in professional or major trade publications or major media about the applicant related to their work in the digital technology sector. A journalist interviewing someone, founder or employee, about their work, their technical decisions and their contribution to the sector is, on the face of it, exactly that.

The question applies equally to founders and employees: what is the difference between an interview that counts and one that does not? An employee quoted extensively in a piece about a product they led is being recognised for their contribution. A founder interviewed about their company and their work is discussing exactly that. Both are, on the published definition, media about the applicant related to their work in digital technology. The guidelines draw no distinction. The assessment sometimes does.

What I have seen in practice is that a body of coverage, even across real publications and genuine speaking invitations, can be characterised as PR activities for the applicant's profile rather than sector recognition. In other words: personal branding. The question the guidelines never answer is where that line sits. Most people who are genuinely recognised as leaders in digital technology build visibility through exactly these activities. They appear in industry media, they speak at events, they are present in their professional community. The difference between that being sector recognition and it being PR activity for your own company is not defined anywhere in the guidance.

The phrase recognised major technology media also appears in assessments as a threshold without ever being defined in the guidance. There is no list of qualifying outlets. There is no minimum readership or visitor count stated, unlike the conference guidance which specifies audience size. Applicants have no way of knowing whether a specific publication meets the threshold before they submit.

The published standard: "Published material in professional or major trade publications or major media about the applicant related to the applicant's work in the digital technology sector."

What assessors apply in practice: A portfolio where most media is in an interview format, whether founder-led or employee-led, can be read as a pattern of promotional effort rather than organic sector recognition of the individual. The guidelines draw no such distinction between interview formats.

How I'd approach it: I genuinely do not know where the line is between an interview that counts and one that does not, for founders or employees. The published standard suggests it should count. Whether it does in practice appears to depend on the overall pattern of your media portfolio, the specific publication, and whether the piece reads as recognition of you as an individual rather than coverage of your company or employer.

OC1: the innovation criteria

Where is the line between innovation and building on established concepts?

For founders and senior employees, the Notion guide requires evidence of innovation or product development, proof of the product in the market, and associated traction through revenue. Traction is explicitly part of the published criteria. A genuinely novel concept with paying users is, on the face of the guidance, what OC1 is designed to capture.

Commercial success alone does not demonstrate innovation, and the OC1 versus OC3 distinction is real. Revenue and user growth belong in OC3. But a founder arguing innovation through a genuinely novel product that is live and in demand is arguing something the guidelines appear to support. The gap is the undisclosed standard that this also needs to be validated by someone outside the company.

The Notion guide does not say OC1 requires independent third-party validation of your innovation claims. Yet in practice, self-described innovation without any external confirmation tends to be insufficient. What appears to help is a patent, an innovation or R&D grant from a recognised body, an innovation award, or editorial media coverage that describes the innovation rather than simply reporting what you say about it. But I want to be clear: this is all inference, because the guidelines do not define what third-party validation means or what forms of it they accept.

There is a further complication. The guidelines present innovation and product development as alternatives, with market traction as supporting evidence. In practice, having strong innovation credentials without market validation does not appear to be sufficient either. I have seen an applicant with an innovation award rejected on OC1 because the product was still at MVP stage with no revenue. The innovation credential was there. The market validation was not.

The published standard: "Evidence of innovation or product development, proof of product in market and associated traction through revenue." Paying customers are explicitly part of the published evidence for founders.

What assessors apply in practice: A distinction between genuine innovation and application of existing tools that is never defined in the guidelines. Where that line sits, and what evidence is sufficient to cross it for a founder without a patent, is not disclosed.

How I'd approach it: Be as specific as possible about what makes your approach genuinely novel, not just better or more convenient. What problem could not be solved this way before? What technically enables this that did not exist or was not combined this way before? Revenue and traction support the product-market fit claim, but the innovation argument needs to stand separately and explicitly.

OC4: research contribution

Sustained track record is the standard, but it is never defined

OC4 requires research contribution to the field. The Notion guide does not define how many papers, over what period, with what level of citation or reach. In practice, a small number of recent papers tends to be considered insufficient as a sustained track record. First-authored papers at major international conferences have been rejected as too recent and with limited adoption and reach. The number of papers, the period over which they span, and their adoption by other researchers all appear to be assessed, without any of those thresholds being disclosed.

GitHub engagement as a research metric

Assessors appear to use GitHub stars and engagement as a proxy for whether research has been adopted by the field. This is not mentioned in the Notion guide at all. Applicants submitting strong academic work have no way of knowing that their repository's public engagement may be scrutinised as part of the assessment. If your research has an associated codebase, its public engagement is worth paying attention to before you apply.

The published standard: "At least one peer-reviewed article or published academic paper in a relevant field." The guide states a minimum of one paper.

What assessors apply in practice: A sustained track record of research contribution with sufficient reach and adoption. Three first-authored papers at major international conferences have been rejected as insufficient. The minimum number for Promise versus Talent is never defined. None of these thresholds appear in the guidelines.

How I'd approach it: The gap between what is published and what is applied here is real and I cannot give you a precise number because Tech Nation has not published one. From what I have seen, multiple papers over an extended period with evidence of reach beyond the submission itself (citations, downloads, GitHub engagement, other researchers building on your work) positions better than a cluster of recent papers. If you are building toward OC4, spread your research activity over time and document the adoption of each piece.

The timing question

The guidance updated to say activities done too close to the application date will not be considered. It does not define "too close." The safe working assumption, based on what I have seen rejected, is that the most recent activity in your portfolio should be at least eight months before your submission date. Activities from six or seven months before submission have been rejected as too recent. Any activities you are building now cannot be submitted for at least eight months, and the overall portfolio needs to show a pattern over time rather than a cluster of things you did specifically to apply.

The inconsistency problem

None of the above would be as significant if it were consistently applied. In my experience, it is not. I have worked with applicants who were rejected with profiles substantially stronger than others I know to have been endorsed in the same period. The gap between what the guidelines say and what assessors apply varies, and what satisfies the standard for one assessor does not always satisfy it for another.

This does not mean the route is impossible. It means that preparing only against the published guidelines is not enough. The portfolio needs to go beyond the technical minimum because you do not know which undocumented standards will be applied to your specific application. And a first rejection, with a clear proforma, is often more useful than a successful application would have been, because it tells you precisely where the gaps are.

One more thing worth saying. Tech Nation is the endorsing body. Tomorrow they could decide to only endorse people who have won specific named awards, as PACT does for film and TV. That is their right. The issue is not the standard they set. It is that when the standard changes or goes beyond what is published, applicants are not told. They prepare against a document that no longer fully describes how they will be assessed. That is the gap this post is about.

The practical takeaway. For every piece of evidence, ask: is there independent verification beyond my own claims? Does it show a sustained pattern rather than a single instance? Is the recognition sector-wide rather than local or internal? Can I show what happened after, not just what I did? These are the questions that appear to be applied even when they are not published.

Want an honest read on where your tech portfolio stands? Book a 30-minute coaching session. We go through your activities against both the published guidelines and the patterns I see in practice, so you know where the real risks are. £99.
Book a session →