When the Draft Cites a Recent Announcement

You ask an assistant for help with a letter. It hands back four tidy paragraphs, and the second one opens like this:

Your recent announcement about expanding the platform into healthcare caught my attention, as it maps closely to the compliance work I’ve been doing.

Read that as a writer and it’s a good sentence. Read it as a fact and it is, most of the time, unsourced. Nobody looked anything up. The model produced the shape of a researched sentence, complete with the word “recent,” because that is what the second paragraph of a strong cover letter tends to contain.

This is the most common way a letter becomes confidently wrong, and it deserves its own post, because the usual advice — delete anything you didn’t supply — doesn’t catch it.

Why this one gets past you

The standing rule about AI drafts is to mark every fact and cut anything you didn’t provide. That rule works well for claims about you. If a draft says you cut processing time by forty percent, you know instantly that you never said that, because it’s your own history and the number isn’t in it.

Claims about the employer break the rule, and the reason is uncomfortable: you have no memory to check them against.

When you read “your recent expansion into healthcare,” there’s no internal contradiction to trip over. It doesn’t feel invented. It feels like something you read during the twenty minutes you spent poking around their site earlier, and you can’t quite remember which page it was on — which is exactly what genuinely remembering a real fact also feels like.

So the sentence survives the proofread. It survives it because it’s about a subject you have no independent record of. The whole safeguard depends on you being the authority on the claim, and here you aren’t.

The other reason it survives: it flatters you. It is the sentence you were hoping to be able to write. Drafts that tell us we did more homework than we did get read generously.

Retrieval and generation are different operations

Worth being precise about the mechanism, because it determines what question you should ask.

An assistant with no access to the live web produces text that is consistent with how the world tends to be described. Companies do announce expansions; the sentence is well-formed and plausible. Plausibility is the output, not accuracy — there’s no step in which anything was checked, because there is nothing to check against.

An assistant that has been given a search tool is doing something categorically different: it issues an actual request to a search or news endpoint and reads back what comes in. That machinery is mundane and publicly documented — Serply’s published endpoint reference covers a set of plain GET endpoints, one per result type, that return results as structured records rather than prose.

The difference that matters to you is not sophistication. It’s that in the second case a record exists. There is a publisher, a URL, and a date sitting behind the sentence, and you can ask to see them. In the first case there is nothing behind the sentence at all, and asking for the source produces a description of a source — which reads exactly like a source and is not one.

The question that catches it

For every sentence in the draft that makes a claim about the employer, ask one thing:

What is the URL, who published it, and what is the date?

Then open the URL yourself.

That last clause is not optional and it is where people stop. A returned link is a claim like any other. Open it, confirm it says what the draft says it says, and look at the date on it — the dating habit applies with more force here, not less, because a fact you didn’t find yourself is a fact you have no feel for.

Three outcomes:

No URL comes back. Delete the sentence. Not soften it, not hedge it with “I believe” — delete it. A claim about someone else’s business with no source is the one kind of error in a letter you cannot talk your way out of.

A URL comes back and it doesn’t say that. Also delete, and be a little more suspicious of the rest of the draft. This happens: a real page, a real company, and a claim assembled from the general vicinity of both.

A URL comes back and it checks out. Now read the date, and rewrite the sentence in your own words with the source visible in it — your engineering blog’s post from March about… rather than your recent announcement about…. You’ve just converted a liability into the best sentence in the letter.

Prevention is cheaper than detection

The version of this that actually works is to never ask for the employer-side fact in the first place.

Do your own reading, in the four-field form: publisher, date, one-line summary, subject. Then hand that to the assistant as source material, along with an explicit prohibition — use only the facts I have supplied about this company; do not add any others, and do not describe anything as recent. That instruction is worth adding to the standard set of inputs you supply before drafting, because it closes the one hole the other inputs leave open.

You lose nothing by doing it this way. The research was twenty minutes; the drafting help is still available for everything downstream of it.

What it costs when it goes through

Play the sentence forward. It works — the letter reads as researched, you get a conversation, and forty minutes in someone says: you mentioned the healthcare expansion, what interested you about it?

There is no recovery from that. Not because the interviewer is offended by an error, but because there are only two available explanations, and both are bad: you invented a fact about their company, or you sent a letter you hadn’t read closely enough to notice a fact you didn’t recognise. The first is dishonest and the second is careless, and you don’t get to pick which one they assume.

Compare the cost of the alternative. A letter with no company-specific detail at all is a perfectly good letter — write about the work, which you know, and let the specificity come from your side of the table. That’s the argument in what a cover letter is actually for, and it holds here: the reader wants evidence that you understand the job, not proof that you skimmed their news page.

The rule, short

Facts about you: check them against your memory. Facts about them: check them against a page you opened, with a date on it.

Anything else in the letter is a sentence you’re going to have to defend, written by something that doesn’t have to.