Is this the same as what's checked at the annual review?

Related but different angle. The annual review is the founder-facing process — the meeting, the trading evidence, the questions you're asked. This article looks at the internal pattern-matching a case officer is likely trained to apply while forming their own view during and around that process, which shapes how they interpret what you present.

What's the single biggest red flag for a case officer in year one?

Inconsistency is the most commonly cited pattern — numbers, dates, or descriptions of the business that don't match across different documents or between what was said last time and what's said now. A single inconsistency isn't necessarily damning, but an accumulation of small ones changes how everything else in the file is read.

Can a founder who is genuinely struggling in year one still pass review?

Yes, generally, if the struggle is disclosed honestly with a credible explanation and evidence of an active response. Case officers are typically more concerned by hidden or minimised problems than by disclosed ones — a founder who says "revenue is behind plan, here's why and here's what we're doing" reads very differently to one whose numbers quietly don't add up with no acknowledgement.

Do case officers visit business premises or just review documents?

This varies significantly by endorsing body and by case — some rely primarily on documentary evidence and the contact-point meeting itself, others may conduct site visits or request video evidence of operations, particularly if something in the documentary record raises a question. Don't assume either way; ask your endorsing body what their process involves.

Is being behind on financial projections itself a red flag?

Not on its own — being behind plan is common and, on its own, is treated as normal startup reality rather than a compliance issue. What tends to draw closer scrutiny is being behind plan with no clear explanation, no evidence of a response, or a story about why that doesn't hold together under questioning.

What endorsing body case officers are trained to look for in year one

Founders preparing for their first annual review tend to focus, understandably, on what they'll be asked to present — the numbers, the trading evidence, the narrative of the past year. Less understood is what's happening on the other side of the table: the internal pattern-matching a case officer applies while listening to that presentation and reading that evidence, shaped by having done this many times before with many different founders. That perspective is worth understanding, not because it's secret or adversarial, but because knowing what draws attention helps you present a genuinely strong year clearly, instead of accidentally triggering scrutiny you didn't need to invite.

Key rules

Case officers reviewing a founder's first year are typically trained, formally or through accumulated practice, to watch for patterns rather than isolated facts: inconsistency across documents and over time, an inability to answer basic operational questions unprompted, activity that appears concentrated around review dates rather than continuous, and a mismatch between the confidence of the narrative and the thinness of the supporting evidence. None of this is uniformly documented in a single published rulebook — practice varies by endorsing body — but these patterns recur consistently enough in practitioner commentary and general due-diligence norms to be treated as a reliable guide to what's actually being watched for, distinct from the founder-facing checklist of what the review formally covers.

Why the internal view is different from the founder-facing checklist

What the annual review actually checks covers the process from the founder's side — what happens at the meeting, what documents you'll need, what the four substantive tests are. This article takes the other seat: what a case officer, having read hundreds of files across many founders, is likely pattern-matching for while forming their own judgement of your specific file.

This distinction matters because the review isn't purely mechanical from the assessor's side either. A case officer bringing experience across a caseload develops an instinct for what a genuinely-lived first year looks like versus what a staged, review-optimised presentation looks like — and that instinct shapes how much weight they give to the documents in front of them, independent of whether every individual document is technically in order.

Pattern one: inconsistency across documents and over time

The single most commonly referenced red flag is internal inconsistency — not any one number being wrong, but the same fact being described differently in different places. A revenue figure in the trading summary that doesn't match the figure mentioned in the covering narrative. A customer count that was "around 40" at the contact-point meeting and "over 100" in the write-up submitted two weeks later. A description of the product that has quietly changed in ways nobody flagged.

None of these individually proves anything. Founders make honest mistakes, and businesses genuinely evolve fast enough that yesterday's number is stale today. What changes the read is accumulation — a file with one small inconsistency reads as a rushed submission; a file with several reads as a business (or a founder) that isn't being tracked carefully, which itself is a mild signal about operational discipline even before it's a signal about honesty.

Pattern two: inability to answer basic questions unprompted

This is one of the more reliable tells practitioners describe, and it's specific to the live contact-point meeting rather than the paper file. A founder who has genuinely been running their business for a year can typically answer basic operational questions fluently and specifically, without needing to check notes: How many customers do you have right now? What did your biggest customer pay you last month? Who on your team handles X? What's your current burn rate?

A founder who hesitates, gives vague or evasive answers, or seems to be reading unfamiliar figures for the first time during the meeting is raising a different kind of flag than a wrong number would — it suggests distance between the founder and the day-to-day reality of the business, which cuts directly against the genuine entrepreneur substance the whole route depends on. See the genuine entrepreneur test, decoded for the underlying standard this connects back to — the annual review isn't a separate test from that standard, it's a re-check of it a year on.

A founder who can talk about their business off-script for ten minutes without missing a beat is showing something no document can — that they actually live in this business day to day.

— General practice observation, not a published rule

Pattern three: activity that looks concentrated around review dates

This is a subtler pattern, but one that experienced reviewers reportedly learn to notice: a business whose visible activity — new contracts, social media presence, hiring, press mentions — clusters suspiciously close to the review date, with long quiet stretches in between. A genuinely continuously operating business tends to leave a more evenly distributed trail: incremental progress, ongoing communications, steady (even if slow) customer activity spread across the year, not a burst of visible motion in the weeks before a scheduled check-in.

This doesn't mean founders should manufacture visible "proof of life" evenly across the calendar — that would just be a more sophisticated version of the same problem. It means the underlying operational rhythm of a genuinely active business naturally produces evidence spread across time, and founders who keep ongoing records (monthly notes, regular invoicing, a running log of decisions and pivots) as a normal habit — not as review preparation — end up with exactly that kind of evidence without having tried to construct it.

Pattern four: narrative confidence outpacing evidence thinness

A polished, confident narrative delivered with thin supporting documentation is, somewhat counterintuitively, treated with more suspicion by experienced reviewers than a modest narrative backed by solid evidence. Confidence is easy to perform; contracts, bank statements, and invoices are not. When the story being told is more impressive than what the paperwork can support, that gap itself becomes the thing under scrutiny — not because ambition is bad, but because the gap is exactly what a staged or exaggerated account would also produce.

Know exactly where your application stands.

Get your free AI assessment in 90 seconds.

Get your assessment

What this means practically for founders

None of these patterns are traps designed to catch honest founders. They're the natural tells of the exact thing the review exists to filter for — a business that has stalled, been abandoned, or was never really being run by the person claiming to run it. A founder genuinely doing the work has, without trying, almost everything needed to avoid triggering any of these patterns.

Keep records as you go, not retrospectively. A running, dated log of decisions, numbers, and changes — kept because it's good practice, not because a review is coming — naturally produces the evenly-distributed, consistent evidence trail reviewers are looking for.
Know your own numbers cold. Before any contact-point meeting, be able to state your core metrics from memory, not from a slide. If you can't, that's worth fixing before the meeting, not during it.
Disclose problems before you're asked about them. A founder who raises a shortfall or a pivot unprompted, with an explanation, controls the narrative. A founder whose problems are discovered by the reviewer does not.
Keep your story consistent across documents, deliberately. Before submitting anything, check your trading summary, your narrative write-up, and what you plan to say at the meeting all agree on the same core numbers.
If you've had a genuinely quiet stretch, say so and explain it. A slow quarter with a credible reason (a key hire fell through, a pivot took longer than planned) reads as ordinary startup reality when disclosed. The same quiet stretch, discovered rather than disclosed, reads as concealment.

Sources and further reading

Key takeaways

Case officers pattern-match across a caseload, not just against a single file — inconsistency, hesitation, and suspiciously clustered activity are recurring tells, not published rules.
Inability to answer basic operational questions unprompted at the contact-point meeting is one of the most reliable signals of distance between a founder and their business.
Evidence that clusters around review dates, rather than being spread continuously across the year, invites more scrutiny than it avoids.
A confident narrative unsupported by proportionate documentary evidence draws more suspicion than a modest, well-evidenced one.
Disclosed problems read as normal startup reality; discovered problems read as concealment — the difference is almost entirely about who raises the issue first.