You have known since Tuesday that the launch list will not all ship. Friday you still owe your manager a message. The draft you keep rewriting opens with sorry, then a week of tickets, then a soft "we may need to talk about scope."
That version gets a calendar invite. It does not get a cut.
Lead with the cut, not the apology
Put the drop and what it protects in the first two sentences. Before the history, before the feeling that you should have seen this earlier.
"I want to drop the export polish from this release so the billing path stays on the 12th. Three options below."
That is not bluntness. It is the shape of a message that respects the reader's time. Two lines in, they know what this is about and what saying yes buys. A paragraph of context first trains them to skim, and the decision is what they miss.
An apology can sit later, in one sentence, if something was actually yours. A vague sorry at the top invites a conversation about blame. You came for a cut.
Split the record from the choice
Two things are in your head and they must not share a paragraph. The first is the record: what was agreed, what is done, what moved. Factual, short. The second is the decision: what drops, what slips, what you will hold.
Merging them produces a status dump. A dump is comfortable to write and expensive to answer, because the reader has to reconstruct the choice you already made in private.
Give a closed list you would live with:
- Drop the polish. Billing ships on the 12th. Export moves to the next train.
- Hold both and move the date. Name the new date.
- Keep the polish and cut a different piece. Name the piece.
Asking for a decision has a general shape. This is that shape aimed upward. Only include options you would accept. A decoy you hope they refuse reads as one.
Label the estimate that got you here
Most scope fights start as "you said it would fit." Usually you did say it, it was an estimate, and nothing marked it as one.
- "Fourteen points closed as of Thursday" — checkable.
- "The remaining two flows look like another week, assuming the vendor sandbox matches production" — a projection, with the thing it rests on.
The assumption is the useful part. A manager who knows the sandbox is a toy can tell you now. State it as a line someone can answer no to, not as a clause inside the plan.
What the assistant can assemble, and what only you can send
If you worked the cut through with an assistant, the options and the rejected ones are already in the session. They do not travel unless you put them in a briefing and approve the exact package. A paste of the chat is your working notes, in the order you happened to have them, with nothing marking guess from fact.
RelayLink carries this as text fields. There are no attachments, so point at the ticket or the doc rather than stuffing a spreadsheet into the message. If your manager already has an account, you need an accepted contact before a new thread will go. If they do not, the send travels as email and a page; they need nothing installed to read it or reply.
Write the choice tonight. Send the version you still mean in the morning. If you want the first draft pulled from the session where you already argued with yourself, connect your assistant.