The red-flag language audit

A single wrong noun is enough. Read your own documents the way HMRC will.

Section II covered what HMRC tests for. This section covers how the test is applied in practice – at the level of the individual sentence. Most refusals do not come from substantive disqualification. They come from a sentence in a pitch deck, a line item on a use-of-funds slide, or a phrase in a covering letter that names something HMRC reads as outside the schemes. The underlying business is usually qualifying. The wording is not.

The schemes are interpreted literally. Royalty income means royalty income, whether or not the founder uses the word colloquially. Acquisition means acquisition, whether or not the deck distinguishes between buying a competitor and a small "acqui-hire" of a team. Recurring revenue reads to an investor as predictable cashflow and to a caseworker, in some contexts, as rental, royalty, or licence income. The same noun does different work in different rooms.

The audit in this section is structured by document, in the order HMRC reads them: covering letter first, application form second, business plan and financial model in support, pitch deck as ambient context. For each document, the audit names the phrases that get applications flagged and the substitutions that do not. Then comes the substitution vocabulary table proper – two pages of avoid this, use this instead, grouped by the test each phrase triggers. The table is the section most worth keeping at hand while you rewrite.

Before the audit begins, fix the five documents in mind. HMRC reads each, and each can independently cause refusal:

The audit's running order – pitch deck first, then covering letter, then cross-document consistency – runs in the opposite direction to how HMRC reads, deliberately. The pitch deck is where most language-driven refusals originate, so it is the first place to clean. The covering letter is where the application is won or lost on first read, so it is the last place to draft. The cross-document audit is the final pass before submission.

Open the document you are about to submit. Read it once for substance – does it say what your business actually does? – then read it a second time against this section, sentence by sentence, looking for any phrase that appears in the audit's avoid column. Each match is either a fix or a deliberate decision to leave it in. None should be there by accident.

A document that has been through this audit will not necessarily be approved. A document that has not been through it will, in our experience, contain at least one phrase that could have been substituted out without changing what the business is, and which materially raises the risk of refusal.

Document one of five · highest risk.

The pitch deck is the document HMRC reads least carefully and refuses applications on most often. It is not part of the formal application. Caseworkers read it as ambient context. They are not looking for the investor narrative. They are looking for the disqualifying noun.

Five slides in a typical deck cause the great majority of language-driven refusals. Run each through the audit before submission.

Avoid this. Use this instead.

The phrases on the left have specific meanings in HMRC's interpretation that founders often do not intend. The phrases on the right describe the same underlying activity in language the schemes read as qualifying. Each pair is grouped under the test it triggers.

Document two of five · first read.

HMRC reads the covering letter before anything else. A letter that sets the reading frame cleanly carries the rest of the application; a letter that does not, forces the caseworker to reconstruct the case from documents that often disagree with each other.

In one or two pages, it should state plainly: the trade the company carries on; the scheme being applied for; the amount being raised and the use of those proceeds; the share class being issued and its key terms; the company's position on independence and control; and a short risk-to-capital statement grounded in the company's specifics. Each of those six items maps to a test in Section II. A caseworker should be able to identify which paragraph addresses which test on a single pass.

"We are excited to share our journey…" reads as a pitch deck opening. The covering letter is not a pitch. "Our innovative solution disrupts…" tells HMRC nothing about the qualifying trade. "We believe we qualify under SEIS because we are a small UK company…" wastes the most-read paragraph in the application on a statement HMRC will verify on the form. The strongest first paragraphs name the trade in plain English, identify the qualifying activity, and move on.

A first paragraph that reads "The Company develops and licenses a proprietary software platform used by independent fitness studios in the United Kingdom for class scheduling and membership billing. The Company seeks advance assurance under SEIS for a proposed issue of £150,000 of ordinary shares, the proceeds of which will fund engineering, sales, and market expansion as set out in Section 3 below" – sets the entire reading frame in two sentences. Trade, scheme, amount, use of proceeds, share class, all named.

A covering letter that contradicts the business plan on the trade description, or the application form on the share class, or the pitch deck on the use of proceeds – even by a single noun – is read by HMRC as the company having three different positions and being unsure which one is correct. The fix is mechanical: read the covering letter, the form, the plan, and the deck side by side, and reconcile every reference to trade, share class, use of proceeds, and ownership before submission.

Documents three to five · consistency.

HMRC reads the application form, the business plan, the financial model, the articles of association, and the pitch deck as a single document. Where they disagree, HMRC treats the most damaging version as the most honest. The audit below is five consistency questions, each of which catches a specific category of avoidable refusal.

A practical habit while drafting: keep a small datapoint log alongside the application – incorporation date, first invoice date, first recurring invoice date, latest accounts date, latest cap-table date – and reference it consistently in every document. Five minutes of pre-drafting saves five paragraphs of post-submission explanation.