The flight is already paid for. That is the whole basis of the negotiation, and it is stronger than most people think.
A company that has bought you a return to Lisbon on Wednesday has bought the expensive part. Moving the return to Sunday usually costs nothing, occasionally costs less, and once in a while costs sixty pounds in a fare difference you should simply offer to pay. What you are actually asking for is not money. You are asking to be trusted with an unsupervised weekend on the company's dime-adjacent itinerary, and the person deciding is the same person who will later decide who gets the four-day week, the compressed hours, the conference in March.
So the ask is small and the file note is permanent. Treat it accordingly.
What you are actually asking
There are three different requests and people muddle them, which is why they get refused.
- A changed flight date, with you covering any fare difference and all accommodation from the last work night onwards. Cheapest, cleanest, most often granted.
- Annual leave adjacent to a work trip. This is a leave request, not a travel request, and it goes through the normal channel.
- Working remotely for two or three days from wherever the trip put you. This is the expensive one politically, because it involves your manager vouching for output nobody can see.
Bundle all three into one message and you have created a project. Ask for the first, take the second as leave, and only raise the third if remote work is already normal where you are.
The paper trail
Put in writing: the dates, who is paying for what, and the confirmation that you are on leave rather than on duty from a named hour on a named day. That last line is not bureaucracy. It is the sentence that decides, if you fall down a staircase on Saturday, whether this was a business trip or your holiday, and which insurer is looking at it. Companies care about that more than they care about your itinerary. Say it plainly and you look like someone who has read a travel policy.</br>
Do not put in writing: what you intend to do with the days. No hotel names, no plans, no charming detail about the market you want to see. Enthusiasm reads as leverage to anyone looking for a reason to say no, and it converts a scheduling question into a favour. Favours get remembered as favours.
Also keep off the record anything that implies the work portion is the pretext. "Since I'll be out there anyway" is fine. "I've wanted to go for years" is not a sentence for email.
Expenses, line by line
The single fastest way to lose the next request is a receipt that arrives in someone's inbox with a Saturday date on it. Split everything at the boundary and split it visibly.
Check out of the company hotel and check into your own, even if it is the same building and the desk offers to run it as one booking. Two invoices, two cards, no reconciliation problem for whoever processes it. If the hotel will only issue one folio, ask for it itemised by night and pay your nights separately at the desk. Take the taxi to the airport out of your own pocket if the return leg is yours. Do not put a client dinner on Friday through as work if you stayed on to eat it. And be careful with the small stuff, because small stuff is what gets noticed: nobody audits a flight change, everybody notices an eleven-pound airport sandwich on a day you were supposedly not working.
Where the fare difference is genuinely in the company's favour — a Sunday return that comes in cheaper than the Wednesday one — say so once, in one line, and then never mention it again. It is a good fact. It is not an argument you want to be seen enjoying.
Timing the ask
Ask when the trip is approved and before the flights are booked. That is a narrow window and it is the only one where the answer costs nobody anything. After booking, you are asking for an amendment fee and an admin task. Before approval, you are attaching a personal want to a business case that has not yet been made, and you are inviting someone to weigh them against each other.
If you missed the window, wait for the next trip rather than reopening this one. The request survives. The reputation for fiddling with settled arrangements does too.
How it reads upward
Flexibility is allocated, not granted. Somewhere above you is a person with a rough and mostly unexamined sense of who can be let off the leash, and the evidence they use is small: whether your handover was written, whether anyone had to chase you, whether you came back with the trip's actual work done.
So the extra days are not the thing being assessed. The Wednesday is. Land the meetings, file the note by the time you said you would, and the weekend becomes invisible — which is the goal. A trip extension that goes well is one nobody remembers approving.
One more thing about the leash. If you are the first person on your team to ask, you are also setting the precedent, and you will be cited by everyone who asks after you. That is worth doing deliberately: ask in a way you would be happy to see repeated back at you by a colleague you do not much rate.
The hard cases
Some trips cannot be extended and it is better to know which before you ask. Anything on a client's budget rather than your employer's, where the client is signing off travel line by line. Anything with visa terms tied to the purpose of entry — a business visa is not a tourist visa, and the dates on it are the dates. Anything where you are travelling with kit, samples, cash or someone else's documents, because insurance on all of that usually stops when the work does. And anything where you are the only person going, and going means a chain of people are waiting on you at the other end.
Regulated industries have their own rules about who pays for what and when it becomes a declarable benefit, and those rules do not care how reasonable you are being. Find out before the email, not after.
Do this
Once the trip is approved and before anything is booked, send five lines: the new return date, the offer to cover the fare difference, the hour at which you go on leave, confirmation that accommodation from that point is yours, and the leave request logged separately in the usual system. No reasons. No plans.
Then do the Wednesday well.


