The update goes out on the first Monday, as it has for eleven months. Twelve recipients, the numbers in the same order as last time, no replies — which stopped surprising you around month four.
Six weeks later, on another call, one of them mentions she knows two people running operations at regional carriers. That is the introduction you asked for, in paragraph nine, phrased as always happy to meet anyone in logistics.
She read the update. She did not read a request, because there was not one anywhere a request goes.
An update gets filed. A request gets answered.
An update is a broadcast. It arrives on a schedule, addresses nobody in particular, and the correct response is to read it and carry on. Filing it is not rudeness; it is compliance with the format.
A request is directed at one person and has two endings: they do it, or they decline. Until one happens, it sits as an open loop.
Put the second object inside the first and it inherits the first one's handling. Your reader reaches the ask already in report mode, and report mode has no slot for an action item. Eleven previous updates ended with nothing required, so you have personally trained this reader that skimming is safe.
Bolding will not fix that; bolding is what skimming filters out. Either the ask leaves the update as its own message to one named person, or it sits at the very top, addressed by name, above the reporting — read before report mode engages.
Make the ask grantable
Three-part test. Could this person complete it in one sitting? Without asking you a question first? Would they know when they were done?
"Any intros appreciated" fails all three. It asks the reader to search their own network against a filter you never supplied, produce candidates, and guess whether any count. That is homework with no marking scheme, and the rational response is to do nothing and feel mildly guilty.
Three shapes that pass:
- A named introduction. Not "anyone in logistics" but "you're connected to Priya at Northwind — would you forward the paragraph below?" You did the searching, selecting and drafting. Their cost is one forward.
- A decision only they can make, options closed. How to ask for a decision covers the mechanics.
- A specific judgement. "You've watched three companies hire a first salesperson — is two quarters before a first closed deal normal, or a signal?"
An introduction and an opinion are not interchangeable. One spends the reader's time; the other spends their credibility with a third party, and deserves its own message rather than a clause in a paragraph about pipeline — a distinction worked through in asking an advisor or board member.
Put the bad news near the top, in plain words
Each update is read against the ones before it. Over a year, what is being evaluated is not any single month but whether your reporting is a reliable instrument. That is the only thing in an update that compounds.
Two habits break it. Euphemism is the first: "growth was more measured than planned" exists only to be technically compatible with a bad number, and anyone who has read a few recognises the register on sight. The plain version costs less — what happened, the number, what caused it, what you are doing.
The second is the metric that appears once and never returns. A number you stopped reporting reads as a number you stopped liking, and the reader substitutes the worst plausible value.
Bad news near the top can also carry a request. Buried on the second page, by the time anyone notices, the only available response is judgement.
Keep the series comparable
An update's value lives in the differences between this one and the last. Same metrics, same definitions, same order, same period boundaries. If a definition has to change, report both for one period and say which changed and why — otherwise you have not improved the reporting, you have reset the series to month one.
A report and an ask are different fields
The RelayLink briefing format makes that split mechanical rather than stylistic. Every package carries a response shape, one of exactly five values: opinion, decision, review, info, fyi. Four of them leave the thread sitting on the other person. The fifth does not — a thread whose latest package is an fyi drops to idle once it has been seen, instead of remaining an open obligation.
So the report goes as fyi, and the ask goes as a decision, an opinion or a review, with an urgency beside it drawn from none, when convenient, this week, or today. Your own thread view then stops lying to you: report threads sit under idle, ask threads under awaiting others, marked seen or not seen yet.
"Seen" is narrower than it sounds — their assistant pulled the package, or somebody opened the link. Notification emails are plain text with no tracking pixel, so an opened email and an unopened one look identical from your side.
Two limits before you try it
No attachments. There is no file field in the format at all, so a deck or a spreadsheet has to live somewhere the reader can reach, and any number you want compared across months has to be in the text.
No CC either. One package goes to one recipient, on its own thread. For the ask that is correct — a request addressed to twelve people is addressed to nobody. For the report it means twelve recipients is twelve sends, each drafted and approved separately.
What you are obliged to disclose to people holding shares in your company is a legal question with different answers in different places. That one is for your counsel; this is a page about writing.
Try the split on the last one you sent
Open your most recent update and find the request in it. If that takes more than five seconds, your readers did not find it either. Pull it out, address it to one person, make it completable in a sitting, and send it on its own. The TL;DR discipline applies to both halves.
If you would rather report-versus-request were a field than a judgement call you make at 11pm, connect your assistant.