The memo that turns a declined trip into a plan

A one-page note, sent by the person who said no, on the day they said it. It is the difference between a travel budget and a travel discipline.

Every travel policy fails the same way. A trip gets proposed, someone senior decides it is not worth the money, and the answer comes back as one word. The rep hears a budget cut. The account keeps whatever problem the trip was supposed to solve. And because nothing was written down, the next weak trip in that territory gets booked without anyone asking the question again — which is how a company ends up with a travel budget and no travel discipline.

The No-Trip Memo is the fix, and it is deliberately small: one page, sent by the person who said no, on the day they said it.

What a No-Trip Memo contains

Four parts. Fewer and it is a rejection with extra steps; more and nobody writes it.

1. What the trip was supposed to change. Stated as the account outcome, not the activity — get the security review unblocked, not meet the CISO. Half of all weak trips die honestly right here, because the answer turns out to be "build the relationship" with nothing under it.
2. Why presence will not change it yet. The specific reason: no confirmed buyer-side attendance, no decision on the calendar, no economic buyer identified, a blocker that is contractual rather than relational.
3. The remote sequence that replaces it. What happens instead, with owners and dates. This is the part that makes the memo a plan rather than a refusal, and it is the part most often skipped.
4. The trigger that puts the trip back on the calendar. A named, observable condition — the moment procurement schedules the review, we go. The trip is not killed. It is made conditional, and the condition is written down where both people can see it.

When to send one

When a proposed trip does not clear the scorecard, or when it clears on points but trips an override — no confirmed buyer-side attendance, no decision event on the calendar, no economic buyer named. The override matters more than the score: a trip can look fundable on paper and still be un-takeable because the one person it depends on is not going to be in the building.

Score the trip first. Use the Revenue Travel Trip Scorecard if you are the rep deciding whether to go, or the Trip ROI Scorecard if you are the approver deciding whether to fund it. The memo is what the second one produces when the answer is no.

Why a memo works where a "no" does not

Three reasons, and none of them are about the travel budget.

It survives the quarter. A verbal no is gone in a week. A memo with a trigger in it is a document someone re-reads when the trigger fires — which means the trip that was worth taking actually gets taken, on the date it became worth taking.

It protects the person who asked. A rep who proposes a trip and gets one word back learns not to propose trips. A rep who gets a memo learns what a fundable trip looks like, which is the only durable way a travel policy ever improves.

It makes the refusal auditable. When a deal is lost and someone asks whether the team should have been on site, the memo is the record of what was decided and why — written before the outcome was known, which is the only time that record is worth anything.

Who writes it

The approver, not the rep. A memo written by the person whose trip was declined is a justification; a memo written by the person who declined it is a decision. In practice it takes about ten minutes, and it is the cheapest instrument in the standard — the only one that needs no data, no vendor, and no tool.

What it is not

It is not a cost-control device. A No-Trip Memo that always concludes "do it remotely" is a budget freeze wearing a template, and the reps will read it that way inside a month. The instrument only works if the trigger is real and the trips that hit their trigger actually get funded — which is why it belongs to the same standard as the scorecards rather than to the expense policy.