Running Late Message for Work: 10 Polite Texts to Copy
Running a few minutes behind happens to everyone. The tricky part isn't the lateness itself — it's finding the right words to say so, quickly, without over-explaining or sounding stressed. A short, well-worded heads-up goes a long way toward keeping things professional.
Why a short message works best
Your manager or team doesn't need a full explanation in the moment — they need two things: that you're aware you're late, and a rough sense of when you'll arrive. Save the details for later if anyone asks.
10 ready-to-use examples
- Running a few minutes behind — see you shortly! Good for informal team chats.
- Stuck in traffic, but on my way. Should be there by [time]. Gives a concrete ETA when you have one.
- Sorry for the late notice — I'll be about 15 minutes behind schedule. Acknowledges the short notice without over-apologising.
- Quick heads up, I'm running late this morning. I'll update you on my ETA. Useful when you don't yet know exactly when you'll arrive.
- Apologies for the delay — I'm on my way and should arrive shortly. A safe, formal option for a manager or client.
- I'm running behind due to a transport delay — I'll keep you posted. Adds a brief, non-detailed reason.
- Sorry, running a bit late! I'll be there as soon as I can. Casual and warm — good for a close team.
- Heads up — I'm delayed this morning, expect me around [time]. Direct and easy to scan.
- My apologies, I'm running late. I'll join as soon as I'm able. Works well for a meeting you're about to miss the start of.
- Running late — I'll fill you in on the details when I arrive. Keeps things brief while signalling more context is available if needed.
A few quick tips
- Send it as soon as you know. A message before your start time is always better than one after.
- Give an ETA if you can. Even a rough one ("about 20 minutes") is more useful than "running late" alone.
- Match the tone to the audience. A client or manager usually warrants a more formal message than a team chat.
- You don't owe a detailed explanation. "Running behind" is a complete sentence — you can share more later if it's relevant.
Which message fits which situation
The ten examples above all do the same job, but they suit different moments. A few rules of thumb:
- You know your arrival time: use an example with a time in it (numbers 2, 3 and 8). A time lets the other person plan, which is the real reason to send the message.
- You don't know yet: use number 4 and then follow up. "I'll update you" is only a good line if you actually do.
- You're late to a meeting, not to work: keep it to one line and send it to the organiser or the chat, not to every attendee (number 9 works well).
- You're writing to a client: go for the formal wording (numbers 3 and 5) and give a time. Clients notice vague messages more than they notice a few minutes of delay.
Send an update if your ETA changes
The part people skip is the second message. If you said "about 15 minutes" and the delay stretches to 40, tell them before the 15 are up. A short follow-up such as "Update: the train is still held, now expecting to arrive around 9:45" keeps people's trust far better than silence followed by an arrival nobody was ready for. One honest revision is fine. Three vague ones start to look like you aren't in control of the situation.
What to leave out of a running-late message
- A long explanation. The more detail you give, the more it reads like an excuse, and the more questions it invites.
- A time you can't keep. "Five minutes" that turns into twenty does more damage than saying "about 20" to begin with. Add a small buffer.
- Repeating the same reason. If the cause is the same as last week, the message itself isn't the problem; see the section below.
- Blame. "The bus was late again" is fine as a fact. A complaint about someone else's mistake is not what your manager needs at 8:55.
When running late keeps happening
A single late arrival needs a good message. A pattern needs a conversation. If you're regularly a few minutes behind because of a commute, a school run or a shift that starts too early for your transport, it is usually better to raise it yourself than to keep sending apologies. Ask whether a later start, a different arrival window or a day or two working from home is possible, and propose the arrangement you'd like. Managers tend to respond far better to "here is what would fix it" than to a fourth apology.
Common questions
Should I text or call? Follow whatever your workplace has set out. If there is no rule, a text is normal for being a few minutes late. If you will miss a meeting that can't start without you, or you'll be more than an hour behind, a call is more considerate because it lets the other person ask questions straight away.
Do I need to give a reason? Not usually. "Running behind" is a complete message. Give a reason when it helps the other person (a transport disruption they may also be affected by, for example) or when you know they'll ask.
How early should I send it? As soon as you know you'll be late, and ideally before your start time. A message at 8:50 for a 9:00 start is far better than one at 9:10.
Is it rude to apologise too much? One apology is enough. Repeating it across several messages draws more attention to the lateness than the lateness deserves.
For more wording, see our 20 late to work text message examples, or read how to apologise for being late to a meeting if you've already walked in late.
Want a message written for your exact situation? Our free Late to Work Excuse Generator builds a polite, ready-to-send message in seconds — just pick a tone, reason, and length.
Try the Late to Work Generator →