Saturday, 31 October 2026

Alert debt:the liability that never shows up on the balance sheet

 

Ask a bank CEO what an analyst costs and you'll get a number in seconds. Ask how many alerts are open right now, and how old the oldest one is, and see how long the answer takes.

That second number is a liability. It just doesn't sit on the balance sheet, so nobody prices it.

I call it alert debt: the open, ageing alerts and reviews your controls created and your team hasn't worked yet. Like any debt, it's fine in small amounts and dangerous once it compounds. And it compounds quietly, because every alert that ages makes the next one look normal.

Here's what the interest looks like when a regulator collects it.

In Ireland, the Central Bank found that faults in the configuration of Coinbase Europe's transaction monitoring system left 30,442,437 transactions, about 31% of its transactions in that period and worth over €176 billion, not properly monitored over 12 months. Strictly, that's monitoring that never ran rather than alerts sitting in a queue. The accounting is the same. Completing the monitoring took almost three years and led to 2,708 suspicious transaction reports to the FIU. Then came a €21,464,734 fine, confirmed by the High Court in January.

In the UK, the FCA's Final Notice to Starling Bank describes a customer base that grew from about 43,000 in 2017 to about 3.6 million in 2023, with financial crime controls that "failed to keep pace with its growth." When the bank raised its own financial crime risk rating to red in late 2022, the notice records a backlog of high-risk customer reviews and customer screening alerts as part of the picture. The penalty was £28,959,426.

I read both notices the same way. Volume grew faster than the system built to work it. That's a growth decision, and growth decisions sit with the CEO.

In the UAE, the bill can also carry a person's name. In June, CBUAE fined a foreign bank's branch AED 20 million for "significant, repeated failures" in its AML, CFT and sanctions framework, and fined its Head of Compliance and MLRO AED 300,000. The release doesn't mention a backlog, and I'm not claiming one. My point is narrower. If your MLRO is carrying a queue the business never funded, you've moved firm risk onto one person and booked it as a saving.

My line in the sand: alert backlog belongs in the board pack every month, reported by age. Count shows how busy the team is. Age shows what you owe.

More analysts aren't automatically the fix, and next Wednesday's issue is about exactly that. The fix starts with seeing the debt. At FluxForce, our AI agents investigate each alert and prepare the case, so your analysts make the call faster and every decision leaves evidence an examiner can replay.

Does your board see alert backlog by age, or not at all?


Sources

  • Central Bank of Ireland, enforcement action against Coinbase Europe Limited, 6 November 2025: press release
  • FCA, Final Notice to Starling Bank Limited, 27 September 2024: final notice (PDF


Monday, 5 October 2026

Before you question an employee’s performance, look at the stability around them.

 

Before you question an employee’s performance, look at the stability around them.

Early in my career, I joined an NBFC.

Within a few months, my manager changed. Then my role changed. Then my manager changed again.

Every couple of months, I was adjusting to a new manager, a new role and new expectations.

At the time of my confirmation, feedback was sought from a manager who had worked with me for only two months. He wanted feedback from my previous two managers, but both had already left.

I left the organisation after nine months.

We expect employees to be stable, but rarely ask whether management has given them the stability to perform.

When the manager, role and expectations keep changing, it becomes difficult to build consistency in performance.

Before questioning an employee's performance, ask:

Have we given them enough stability to perform?

Because performance isn't created by the employee alone.

The manager, the role, the expectations and the consistency around them matter just as much.

SB Growth Partners

People. Talent. Growth.

Why Did an EdTech Startup Need a Replacement Before Probation?

 

I was working with an EdTech startup in Gurugram when the founder asked for a replacement for a candidate who had completed only 2.5 months.

My first thought was not, “Who should we hire next?”

It was:

“Why didn't this hire work?”

Because if we don't understand that, we may make the same mistake again.

Before your next hire, ask yourself:

1. Is the role clear? Does the person know what they are expected to deliver?

2. Is the manager clear? Do both agree on what good performance looks like?

3. Is the first 90 days clear? Are the expectations defined from the start?

4. Are performance issues discussed early? Or only when replacement becomes the answer?

5. If this person leaves, what will you change? The hiring criteria, role, onboarding or management?

Score yourself

5/5 — Good foundation 3–4 — Look at the gaps 0–2 — Fix the basics before hiring again

But the score isn't the most important part.

Ask yourself:

If I had to replace this person tomorrow, would I hire differentlyor just hire again?

A replacement fills the vacancy.

It doesn't tell you why the vacancy happened.

If you're dealing with a similar hiring or people challenge, happy to compare notes.

Why Did an EdTech Startup Need a Replacement Before Probation?

SOMETIMES, PROMOTING YOUR BEST PERFORMER CAN TRIGGER MORE ATTRITION THAN YOU EXPECT.

 

SOMETIMES, PROMOTING YOUR BEST PERFORMER CAN TRIGGER MORE ATTRITION THAN YOU EXPECT. 

A very good individual contributor was promoted to Manager in less than a year in one of the Engineering Company

She was technically strong and consistently delivered.

A few months later, she wanted to resign.

And she wanted her team to leave with her.

That was the real problem.

Don't assume that your best individual contributor is automatically ready to manage people.

Managing people was a different job altogether.

She now had to delegate, manage former peers, handle conflicts, give feedback and take responsibility for the team's performance.

And don't stop paying attention once the promotion is made.

The first few months matter.

Talk to the manager. Talk to the team. Look for friction. Give the new manager support.

Because by the time people start resigning, the problem may have been there for months.

Before promoting your next star performer, ask:

Are we promoting them because they are good at their current job, or because they are ready for the next one?

Have you ever promoted a high performer into management and seen unexpected changes in the team?

What happened? I’d love to hear your experience

The Founder’s Growth Playbook | Edition #8

SB Growth Partners

People. Talent. Growth.

 

“We’re Only 50 Employees. Why Do We Need POSH?”

 

I came across this situation at a CA firm.

Around 50 employees. Nearly 10 years in business.

POSH compliance was still being considered an unnecessary cost.

Then a woman employee raised a concern about a senior team member who had offered her a lift on a rainy day.

Offering a lift, by itself, does not establish sexual harassment.

But the firm had another problem:

There was no formal process to deal with the complaint.

No properly constituted Internal Committee. No clear channel. No defined process.

The matter escalated. The employee started saying she would approach the police.

This is where the cost-cutting decision became a bigger problem.

A complaint doesn't automatically mean harassment.

But when someone raises a sensitive concern, the organisation needs a process to hear it, examine the facts and respond appropriately.

For workplaces with 10 or more employees, the POSH Act requires an Internal Committee.

So the argument:

“We have only 50 employees. We're too small for POSH.”

doesn't hold.

50 employees may be a small organisation. It isn't below the legal threshold.

And more importantly, you don't create the process after a complaint arrives.

Have the process ready before you need it.People & Organisation Advisory

Details have been anonymised to protect confidentiality. This is a general HR perspective, not legal advice.

“We’re Only 50 Employees. Why Do We Need POSH?”

Your next senior hire will fail in 6 months unless you fix these 4 things before day 1.

 

Your next senior hire will fail in 6 months unless you fix these 4 things before day 1. 

If you run a 30 to 200 person company, you've probably done this: hired a senior leader to "take this off my plate." Four to six months later, they left, or you let them go.

Most founders blame the hire. In my experience, the problem is usually what they walked into.

This matters more now. Poaching and lateral hiring are expected to continue for leadership and niche talent. Replacing a leader is slower and costlier than keeping one.

1. Decision rights Make three columns: what they decide alone, what they decide and inform you about, and what needs your approval. Put ₹ limits on each.

2. A scorecard, not a JD A JD lists tasks. A scorecard lists 3 to 5 outcomes for the first 12 months, with numbers. "Reduce sales cycle from [60] to [45] days" is a scorecard line.

3. Team handover Tell the team, in your words, that they report to the new leader now. Then stop answering their questions about decisions the leader owns. Redirect every time.

4. A 90-day plan Day 30: understand and listen. Day 60: first changes. Day 90: first results. Hold a weekly 30-minute 1:1 with you, with the agenda set by them.

Questions founders ask me

"What if I don't trust them yet?" Start with a ₹ limit and raise it every 30 days as they deliver.

"Should I hire from a big company?" Only if they've built something at your size. Big-company leaders often expect systems you don't have yet.

"How do I know early that it's failing?" Three signals by day 45: the team still comes to you, the leader asks permission for things they own, and their key metric hasn't moved.

"I've already been hired and it's going wrong. Replace them?" Not yet. Run these 4 checks first. Usually one is missing.

Next step: If you're about to hire or replace a senior leader, book a 30-minute Leadership Systems Diagnostic Call. We'll map which of these 4 are missing in your company. Calendly

 

My Automation Emailed
 The Wrong Address.

 

You turned on something that sends email for you. It says sent, and you believe it, because there is a tick next to the word.

Mine said sent last week. The message went out from an address the client had never written to, so it landed outside the thread we were already in.

The client saw a stranger. My system saw silence. Then it chased them again.


WHAT WORKS

Find the blanks nobody filled in.

Every automation you switch on has a list of questions it has to answer before it can act. Some of them you answered during setup. The rest it answers for you, quietly, out of your defaults, and it never mentions which ones those were.

Mine had two email accounts connected. Nothing ever asked me which one a reply should leave from, so it used the one I use most. The client had written to the other one.

Here is the part worth understanding. That is not a glitch. A glitch is occasional. A default applied to the wrong record is wrong every single time that record comes up, and it is confidently wrong, and it looks exactly like working.

Sent is a claim about your outbox. It is not a claim about the conversation.

The blanks are always the same handful. For anything that sends on your behalf:

- Which address it sends from, when you have more than one.

- Which name and signature ride on it.

- What time "9am" means when the recipient is in another country.

- Who it replies to when three people are on the thread.

- What it does when it is unsure. Skip, guess, or come and ask you.

For each of those, ask one question: does it read the answer off the thing it is acting on, or off your settings?

Off the thing it is acting on is correct. That client, that conversation, that invoice. Off your settings is a coin flip that lands the same way forever, and the day your work stops being uniform is the day it starts being wrong without telling you.

Then do the arithmetic, because it is worse than it sounds. Two connected accounts and one default is not a small error rate. Every conversation living on the second account is handled wrong, permanently, and none of it shows up as a failure. It shows up as clients who went quiet.


Below is the receipt test I run now. Four things to look at in the recipient's mailbox, and a fifth check that catches what those four miss. (Go visit the link below to see)

Read the rest of this issue on our website: https://ankushchauhan.com/what-works/automation-emailed-wrong-address

The automation in this story is mine. It is called Alacrio, it runs my client follow-ups, and since this happened it shows me the account, the thread and the decision before anything leaves.

I Failed My Own
 Demo Test

 

You sat through a demo recently and the tool did everything the person said it would. It was always going to. I know, because I build them too. A demo is the one path that works, rehearsed until it looks like the product.

Yesterday morning I sat in the buyer's chair for an hour with my own product open, and found three things it got wrong before a prospect could. Not one of them would have come up in the version I usually show.


WHAT WORKS

Bring your worst example and make them run it live.

Nobody builds a demo dishonestly. You build it out of the first case you got right, then you show it two hundred times, and somewhere in there you stop being able to see the shape of what you left out. The demo is true. It is also the narrowest possible sample of the product, chosen by the person selling it.

So stop evaluating the demo. Interrupt it.

Before the call, find one real item from your own business that is ugly. The client with two email addresses. The project that changed scope twice. The invoice that came in two parts, late, against a different reference number. Have it open in another window.

Then ask for four things, in this order.

  1. Run mine. Not the sample. The item you brought, in the call, while you watch. Whether they can do it now or need a week to set it up is already an answer.
  2. Show me a real time it got this wrong. One actual case, what it did, and what happened afterwards. A hypothetical does not count.
  3. Tell me what it is bad at. Anyone who has run this in production for a year has a list and will say it out loud without flinching.
  4. Tell me what leaving costs. Where the history sits, who exports it, and what stops working the day you cancel.

The order matters. The first two are expensive to fake in real time. The last two are cheap to answer honestly and get vague fast when there is nothing behind them.

One reply ends the call for me. It is when "what is it bad at" comes back as a benefit. It keeps learning. It handles that automatically. Said once, in passing, that is a founder being proud of their work. Said in place of the list, it means nobody there has met the failure yet, and you will be the one who does.


Below is what happened when I ran this on my own product yesterday morning. Three things it got wrong, and the pattern all three shared, which is the thing I would go looking for in anything you are about to buy.

Read the rest of this issue on our website: https://ankushchauhan.com/what-works/demos-dont-trust-mine

The product I was rehearsing is mine. It is called Alacrio, it runs my client follow-ups, and two of the three gaps are already closed, because an hour in the buyer's chair is cheaper than hearing about it from a client.

Your Quietest Client Is The Expensive One

 

A client who decides not to renew in March usually stops engaging by January.

There won't be a clear complaint or a difficult phone call. Instead, the conversation simply fades—replies get shorter, the pace slows down, and eventually, you are the only one reaching out.

While the actual renewal discussion happens at the end of the contract, the real decision is made much earlier. The warning signs are already sitting in your communication history right now.


When a client decides not to renew, the warning signs usually appear months in advance. The conversation doesn't end abruptly; it simply fades.

To spot this early, look at the data rather than relying on your memory. Count the messages you sent and received from each retainer client over the last three months. You are looking for a specific pattern: a drop in communication by half that doesn't recover.

A few practical tips:

  • Count threads, not individual messages: This prevents highly active clients from skewing the data.

  • Use the right medium: If you mostly talk on WhatsApp or via calls, count those instead.

  • Focus on their activity: A drop in their messages is an interest problem; a drop in yours is just a scheduling issue.

  • Watch the ratio: A month where you send nine messages and only get two back is a major red flag.

If a client's communication drops by more than half for two consecutive months, it’s time to reach out. Schedule a call with a clear, necessary decision on the agenda—don't just check in.


Below is the ledger filled in, four clients across three months, and the one shape on it that tells you which renewal you are about to lose. It is not the client with the lowest numbers.

Read the rest of this issue on our website: https://ankushchauhan.com/what-works/quietest-client-is-the-expensive-one

Counting a quarter of threads by hand takes twenty minutes, and nobody does it twelve times a year. That is the job I built Alacrio for. It watches the client threads I am not thinking about and tells me which one has gone quiet

You Don't Have A Lead Problem.

 

When asked about their biggest challenge, nearly 60% of independent consultants point to finding new clients, while only 6% say it's retaining them. These insights come from the Frak Conference State of Fractional report, which surveyed 250 professionals across 29 states.

I believe both figures are accurate, but I also suspect the latter is the root cause of the former.

A dry spell in new business is obvious, but a departing client often slips away unnoticed.

There is rarely a formal cancellation or final meeting—just a final email followed by a silence that is easily mistaken for a busy period.


WHAT WORKS

To understand your real growth, you have to look at where your revenue actually came from last year.

Start by reviewing every invoice from the past twelve months, grouped by client. Separate them into two categories: clients who were already with you in September of last year (Group A), and those who were not (Group B). Total the revenue for each.

Next, identify the silent departures. List every engagement that ended during this period without a clear reason—excluding those that ended due to budget cuts, in-house hires, or completed scopes. For each of these, note what they billed in the year before they left.

Subtract this lost revenue from your new client total (Group B).

What remains is your true growth. Everything else is just replacement revenue—which is the most expensive kind, because it is business you already had.

Here is why that math works against you. Landing a new $2,000 client takes an intro call, a proposal, two follow-ups, and a scoping call. That is easily eight hours of unpaid work before you ever send an invoice.

Keeping an existing client, however, usually just takes one honest thirty-minute conversation about their upcoming needs. Every time a client quietly slips away, it costs you about eight unpaid hours just to get back to where you started.

Last year, I had a retainer that lasted for eleven months and then simply stopped. There was no final complaint. Their replies just slowed down—from once a day to once a week, and eventually to a file I had to ask for twice. I chalked it up to their busy season. It finally showed up on my books as a gap I had to fill in June with someone new. After about nine hours of calls and proposals, I remember thinking of that June as a successful month. :) Lol

The client you win in March to cover the one who went quiet in January is not a new client. That is the same revenue, bought twice.        

Which is why retention comes last on the survey and first on the bank statement. Finding clients hurts in a way you feel on a Tuesday. Losing one hurts in a way that only ever shows up in a column.


Here is a complete year, with 96,000 billed, alongside the deduction that reveals much of that column is simply money you already earned. The actual growth was only half of what the invoices suggest...

Read the rest of this issue on our website: https://ankushchauhan.com/what-works/you-dont-have-a-lead-problem

The two clients who stopped without saying why were visible months earlier, in threads that got shorter. That is the job I built Alacrio for. It watches the client conversations I am not currently thinking about and tells me which ones have gone still.

Your Next Client Is A Price Increase.

 

In the survey behind our newsletter issue 31, 36.4% of consultants said pricing was one of their biggest problems. Only finding clients ranked higher. So this week I put the two side by side.

I used the same made-up year from issue 31: $96,000 billed. Raise your price 10% on that same work and you earn $9,600 more. Same clients, same hours. To earn that $9,600 by selling more, you need a new client, a pipeline, and weeks of follow-up.

One takes a conversation. The other takes three months.

If you want to earn more next year, charging a bit more to the same clients is far less work than finding more clients.


WHAT WORKS

Put your numbers in two columns.

Column one: what you would earn if you raised your price and did the same amount of work.

Column two: how much more work you would need to earn the same at today's price.

Most consultants never do this sum. They judge their price by feel. Nobody has complained lately, invoices get paid, so the price must be fine.

The sum tells a different story.

At +10%, $96,000 becomes $105,600. Your week does not change. No extra calls, no extra proposals, no extra invoices to chase.

To reach $105,600 at today's price, you have to do 10% more work. More scoping, more revisions, more onboarding, more admin. And one more client who might go quiet in month four, like I wrote about in issue 30. The money is the same. The work is not.

Raising your price changes one number. Selling more changes every week of your year.

At +20% the gap gets bigger. A higher price gets you to $115,200 with one line on one proposal. Getting there at today's price means giving away a fifth of your year.

This will not tell you how much to raise. It shows you what avoiding that conversation costs, in money, so you stop guessing from a feeling.


That is the easy half. The rest is the four-step AI prompt that turns your invoice export into both columns, plus the two mistakes that make silence look like your clients are happy with your price.

Read the rest of this issue on our website: https://ankushchauhan.com/what-works/raise-the-rate-not-the-count

The quotes that never became invoices are the ones this method cannot see. Alacrio watches the proposal threads in your inbox and tells you which ones went quiet before they turned into a yes, a no, or a discount.

Your Next Client Is A Price Increase.

 

Your Next Client Is A Price Increase. 

In the survey behind our newsletter issue 31, 36.4% of consultants said pricing was one of their biggest problems. Only finding clients ranked higher. So this week I put the two side by side.

I used the same made-up year from issue 31: $96,000 billed. Raise your price 10% on that same work and you earn $9,600 more. Same clients, same hours. To earn that $9,600 by selling more, you need a new client, a pipeline, and weeks of follow-up.

One takes a conversation. The other takes three months.

If you want to earn more next year, charging a bit more to the same clients is far less work than finding more clients.


WHAT WORKS

Put your numbers in two columns.

Column one: what you would earn if you raised your price and did the same amount of work.

Column two: how much more work you would need to earn the same at today's price.

Most consultants never do this sum. They judge their price by feel. Nobody has complained lately, invoices get paid, so the price must be fine.

The sum tells a different story.

At +10%, $96,000 becomes $105,600. Your week does not change. No extra calls, no extra proposals, no extra invoices to chase.

To reach $105,600 at today's price, you have to do 10% more work. More scoping, more revisions, more onboarding, more admin. And one more client who might go quiet in month four, like I wrote about in issue 30. The money is the same. The work is not.

Raising your price changes one number. Selling more changes every week of your year.

At +20% the gap gets bigger. A higher price gets you to $115,200 with one line on one proposal. Getting there at today's price means giving away a fifth of your year.

This will not tell you how much to raise. It shows you what avoiding that conversation costs, in money, so you stop guessing from a feeling.


That is the easy half. The rest is the four-step AI prompt that turns your invoice export into both columns, plus the two mistakes that make silence look like your clients are happy with your price.

Read the rest of this issue on our website: https://ankushchauhan.com/what-works/raise-the-rate-not-the-count

The quotes that never became invoices are the ones this method cannot see. Alacrio watches the proposal threads in your inbox and tells you which ones went quiet before they turned into a yes, a no, or a discount.

 

Your next senior hire will fail in 6 months unless you fix these 4 things before day 1.

 

If you run a 30 to 200 person company, you've probably done this: hired a senior leader to "take this off my plate." Four to six months later, they left, or you let them go.

Most founders blame the hire. In my experience, the problem is usually what they walked into.

This matters more now. Poaching and lateral hiring are expected to continue for leadership and niche talent. Replacing a leader is slower and costlier than keeping one.

1. Decision rights Make three columns: what they decide alone, what they decide and inform you about, and what needs your approval. Put ₹ limits on each.

2. A scorecard, not a JD A JD lists tasks. A scorecard lists 3 to 5 outcomes for the first 12 months, with numbers. "Reduce sales cycle from [60] to [45] days" is a scorecard line.

3. Team handover Tell the team, in your words, that they report to the new leader now. Then stop answering their questions about decisions the leader owns. Redirect every time.

4. A 90-day plan Day 30: understand and listen. Day 60: first changes. Day 90: first results. Hold a weekly 30-minute 1:1 with you, with the agenda set by them.

Questions founders ask me

"What if I don't trust them yet?" Start with a ₹ limit and raise it every 30 days as they deliver.

"Should I hire from a big company?" Only if they've built something at your size. Big-company leaders often expect systems you don't have yet.

"How do I know early that it's failing?" Three signals by day 45: the team still comes to you, the leader asks permission for things they own, and their key metric hasn't moved.

"I've already been hired and it's going wrong. Replace them?" Not yet. Run these 4 checks first. Usually one is missing.

Next step: If you're about to hire or replace a senior leader, book a 30-minute Leadership Systems Diagnostic Call. We'll map which of these 4 are missing in your company. Calendly

Your next senior hire will fail in 6 months unless you fix these 4 things before day 1.

How Vivek Ramaswamy's Well-Timed Ohio Move Likely Saved Him $12 Million In Taxes

 

Good evening,

Billionaire gubernatorial candidate Vivek Ramaswamy thinks his plan to have Ohio stop taxing capital gains would make founders flock to the state. In fact, his own move from New York to the state of Ohio in late 2019 tactically came just before one of the largest windfalls of his career, likely saving him millions of dollars in New York state and municipal taxes. Here's how.

Thanks for reading!

Kris Kornbluth Assistant Editor, Platforms & Curation


More Recommended Reads

Article content
MattGush/iStock via Getty Images

The 25 Best Places To Retire If You Love Arts, Fine Dining And The Outdoors

We screened nearly 1,000 U.S. locales to uncover the best places for lovers of the arts, fine dining and the outdoors to retire. View the list here.

Article content
Getty Images

Argentine Citizenship Will Be New ‘Status Symbol’ For Wealthy Americans, Say Experts

Announced Friday and set to launch before the end of 2026, the country’s citizenship-by-investment program is the first in South America, the first for a G20 country and the first to recognize same-sex married couples.

Do We Grow Software or Do We Design It?

 

Vibe-coding is growing software. Start with the germ of the idea. Iterate on it. Let’s try this. Poke the petri dish with a bit of glucose ; oh, that didn’t work. Maybe some thymol blue to see if the colony is alive? Time to start again.

The most sophisticated vibe-coders test with 4-5 different petri dishes in parallel & pick the one whose bacteria have evolved optimally.

Designed software in the AI era is state machine design : flow charts that work. First, the email comes in. Three options : archive, add to the CRM, or escalate to a person. If adding to the CRM, determine the company’s stage.

When co-designing a state machine with AI, ask for the flowchart. The AI willingly shares schematics. Lay out every fork in a table with the right outcome. The holes jump out immediately. Plus, formal verification proves the software will work as intended.

Boris explains why.1

Article content

Growing software is organic. We can just program! State-machines are mechanical, industrial, & rigid : great for core systems that must work.

Software engineering has many philosophies : test-driven development,2 pair programming,3 move fast & break things.4 In this new era, we add two more.


  1. Boris Cherny on formally verifying the Claude Agent SDK with Lean & TLA+. ↩︎
  2. Test-Driven Development (TDD), popularized by Kent Beck in ‘Test-Driven Development: By Example’ (2002), dictates writing automated test cases before writing the minimal production code necessary to pass them. ↩︎
  3. Pair programming, a core practice of Extreme Programming (XP), pairs two developers at one workstation : one ‘driver’ typing code while the other ’navigator’ reviews and plans strategic direction in real time. ↩︎
  4. ‘Move fast and break things’ was Facebook’s early internal motto, celebrated by Mark Zuckerberg as a mandate to accept collateral bugs as the acceptable cost of developer velocity, later replaced in 2014 by ‘Move fast with stable infra.’ ↩︎

Sunday, 4 October 2026

The awards criterion is not a trophy count. It is a proof problem.

 

Your awards are worth less than you think.

Every EB1A applicant likes the awards criterion. It sounds like a concrete win: check a box. And every year, thousands of petitions lose on that same criterion, because the awards look impressive on the résumé and unimpressive on the record.

USCIS is not counting trophies. It is evaluating whether the recognition is nationally or internationally credible — and most awards do not clear that bar.

The Awards Criterion: What Actually Qualifies

What the regulation actually asks

The criterion calls for “lesser nationally or internationally recognized prizes or awards for excellence in the field.” Every word does work. National or international scope. Recognition meaning credibility, not just existence. Excellence, meaning selection on merit. Field, meaning your defined subfield, not a general audience.

An award that fails any of these tests is decorative, not evidentiary.

What actually qualifies

Strong award evidence typically shares several traits:

  • The awarding body is credible in your field, established, independently governed, and known to the industry.
  • The selection was competitive and merit-based, with a documented process.
  • The recognition extends beyond a single company or employer's ecosystem.
  • There is public, independent coverage, not just a press release from the awarding organization.

Awards that quietly hurt you

Some categories create the appearance of achievement without the substance. Internal company awards. Pay-to-enter “top 40 under 40” lists. Awards from organizations you cannot verify. Recent proliferation of “global excellence” award mills has trained adjudicators to spot them at a glance. When they see one, credibility drops for the entire award section.

How to strengthen the evidence

Document what the award actually means. Include the awarding body's charter, selection process, prior recipients, and the pool size. Add third-party coverage of your specific award year. If the award is niche, argue why the niche matters a small, respected field award can outperform a global generic one. And prioritize independent recognition: awards you were nominated for by others, not awards you applied for yourself.

Bottom line: The awards criterion is not about how many you have. It is about how much your field respects the ones you have.

FIVE MOVES FOR STRONGER AWARD EVIDENCE

  • Audit each award for scope, credibility, selectivity, and field relevance. If any of the four is weak, so is the evidence.
  • Remove internal company awards from the petition; they weaken the credibility of stronger items.
  • Document each awarding body: charter, process, prior recipients, pool size.
  • Prefer independent nominations over self-applications wherever possible.
  • One credible field-recognized award outperforms five vague global ones.

FROM THE BLOG

▸ Complete EB1A Checklist: Documents, Evidence and Winning Strategy

How awards fit into the full evidence picture.

▸ EB1A Visa: 7 Critical Mistakes That Lead to Rejection

Weak award evidence is a repeat offender.

YOUR NEXT STEP

Not sure whether your awards will hold up? Book a free 30-minute review, and we will audit each one honestly.

→ Book your free 30-minute consultation

EB1A — Your Path to a U.S. Green Card

Contact Us  · contact@eb1a.io

LinkedIn · Instagram · Facebook · Visit the blog

Disclaimer: The information in this newsletter is for educational and informational purposes only. It is not legal advice and does not create an attorney–client relationship. Immigration outcomes depend on the details of individual cases. Consult a qualified immigration attorney for guidance specific to your situation.

You are receiving The EB1A Edge because you subscribed at eb1a.io. To stop receiving these emails, click Unsubscribe.

Alert debt:the liability that never shows up on the balance sheet

  Ask a bank CEO what an analyst costs and you'll get a number in seconds. Ask how many alerts are open right now, and how old th...