28 Other Ways to Say “Please Be On Time” (With Examples)

The best other ways to say please be on time are “please arrive promptly” for invitations, “let’s start on time” for a team meeting, and — better than any request — stating the time itself: “we’ll start at 10:00 sharp”.

There is a reason this phrase so rarely works. It asks for a behaviour without defining it, and the reader fills the gap with their own idea of what “on time” means. Below are 28 alternatives, sorted by how blunt each one is and who you can safely send it to.

What Does “Please Be On Time” Mean?

It asks someone to arrive at or before the stated time. Punctuality is defined as “the characteristic of completing a required task or fulfilling an obligation before or at a previously designated time” — which sounds precise until you notice that the designated time is exactly what the phrase leaves out.

⚡ The Short Version

Do not ask for punctuality. State the time and the reason: “we start at 10:00 sharp because the client joins at 10:05.” Nobody can misread that, and nobody can resent it.

When to Use “Please Be On Time”

• 🕐 Inviting people to a meeting with a hard start
• 🕐 A written invitation to an event or ceremony
• 🕐 Briefing a group before a trip or a site visit
• 🕐 Reminding a team before something with an external audience
• 🕐 Setting expectations with a new starter or a student group

Pros and Cons of “Please Be On Time”

Pros	Cons
Short and universally understood	Never says what time you mean
Polite on the surface	Implies the reader would otherwise be late
Works for groups and individuals	Gives no reason, so feels arbitrary
Safe in most written contexts	Reads as a reprimand after a late start
Fits any invitation	Rarely changes anyone’s behaviour

Why We Need Alternatives

Because punctuality is not a matter of willingness, and the phrase treats it as one.

People arrive late because a previous meeting overran, because the car park fills, because nothing in the invitation suggested the start mattered. A request addresses none of those. A time and a reason address all three.

28 Other Ways to Say “Please Be On Time”

Each entry leads with real examples, then explains why it works and who it suits. Read the Bluntness line first — several of these are rebukes wearing the clothes of a request.

1. Kindly arrive on time

Softened with “kindly”.

Examples:

• “Kindly arrive on time, as the room is booked until eleven.”
• “Kindly arrive on time — we have a lot to get through.”
• “Kindly arrive on time for the site induction.”

Why it works: “Kindly” softens the instruction, though to many British and American ears it also sounds slightly formal or officious.

Tone: Formal, polite  |  Formality: Formal  |  Bluntness: Gentle
Safe for: Anyone  |  Avoid with: Casual team chat

2. Please don’t be late

Negative framing of the same request.

Examples:

• “Please don’t be late — the assessor will not wait.”
• “Please don’t be late; the doors are locked at nine.”
• “Please don’t be late for your own interview.”

Why it works: Naming the failure rather than the behaviour makes it land as a warning. It works when lateness has already happened.

Tone: Direct, firm  |  Formality: Neutral  |  Bluntness: Firm
Safe for: Team members and students  |  Avoid with: Clients and guests

3. Be prompt

Short, formal, impersonal.

Examples:

• “Be prompt — registration closes at 08:45.”
• “Please be prompt for the Monday briefing.”
• “Be prompt; the coach leaves without stragglers.”

Why it works: Two words with no softening at all, which suits notices and signage where brevity is the point rather than warmth.

Tone: Formal, brisk  |  Formality: Formal  |  Bluntness: Neutral
Safe for: Notices and instructions  |  Avoid with: Personal invitations

4. Make sure you’re on time

Puts responsibility on them.

Examples:

• “Make sure you’re on time — the test starts exactly at two.”
• “Make sure you’re on time for the handover.”
• “Make sure you’re on time; there is no late entry.”

Why it works: “Make sure” assigns the duty explicitly, which reads as supportive from a teacher and patronising from a peer.

Tone: Direct, firm  |  Formality: Neutral  |  Bluntness: Firm
Safe for: Students, trainees, direct reports  |  Avoid with: Colleagues and seniors

5. Please be punctual

The formal standard.

Examples:

• “Please be punctual, as the ceremony begins at noon.”
• “Please be punctual for tomorrow’s inspection.”
• “Guests are asked to be punctual.”

Why it works: “Punctual” is the dictionary word for the behaviour, which gives it a slightly official register suited to invitations and notices.

Tone: Formal, neutral  |  Formality: Formal  |  Bluntness: Neutral
Safe for: Invitations and formal notices  |  Avoid with: Informal messages

6. Don’t keep us waiting

Blunt to the point of rude.

Examples:

• “Don’t keep us waiting — we start at nine either way.”
• “Please don’t keep us waiting again.”
• “Don’t keep us waiting; there are twelve of us.”

Why it works: It makes the group the injured party, which is effective as a reprimand and unusable as a request. Send it only where a rebuke is intended.

Tone: Blunt, impatient  |  Formality: Casual  |  Bluntness: Blunt
Safe for: Nobody, in writing  |  Avoid with: Clients, guests, anyone senior

7. Try to be on time

Weakened by “try”.

Examples:

• “Try to be on time — we’d rather not start twice.”
• “Try to be on time for the rehearsal.”
• “Try to be on time if you can.”

Why it works: “Try” concedes in advance that they might not. If the time genuinely matters, this is the wrong phrasing; if it does not, why ask.

Tone: Gentle, weak  |  Formality: Casual  |  Bluntness: Gentle
Safe for: Low-stakes gatherings  |  Avoid with: Anything with a hard start

8. Be there right on time

Emphatic and informal.

Examples:

• “Be there right on time — the photographer only has an hour.”
• “Be there right on time, not five past.”
• “Be there right on time and we’ll be finished by four.”

Why it works: “Right on time” closes the usual grace period, which is the point. It also sounds spoken rather than written.

Tone: Direct, informal  |  Formality: Casual  |  Bluntness: Firm
Safe for: Friends and close colleagues  |  Avoid with: Formal invitations

9. Show up on time

Very casual, faintly sharp.

Examples:

• “Show up on time and we’ll get out early.”
• “Just show up on time — that’s all I’m asking.”
• “Show up on time for once.”

Why it works: “Show up” treats attendance as the minimum expectation, which carries an edge whether or not you intend one.

Tone: Casual, sharp  |  Formality: Casual  |  Bluntness: Blunt
Safe for: Close colleagues only  |  Avoid with: Clients, students, invitations

10. Don’t be behind schedule

Project language, oddly applied to people.

Examples:

• “Don’t be behind schedule on the Thursday deliverable.”
• “Please don’t be behind schedule for the inspection window.”
• “Don’t be behind schedule — the crane is booked by the hour.”

Why it works: “Behind schedule” belongs to workstreams rather than arrivals, which makes it right for deadlines and awkward for meetings.

Tone: Formal, technical  |  Formality: Formal  |  Bluntness: Firm
Safe for: Project and site teams  |  Avoid with: Social invitations

11. Arrive promptly

Clean and formal.

Examples:

• “Please arrive promptly at 09:30.”
• “Arrive promptly; late arrivals cannot be admitted.”
• “Delegates should arrive promptly for registration.”

Why it works: “Promptly” pairs naturally with a stated time, which is why it appears on so many formal invitations and event notices.

Tone: Formal, neutral  |  Formality: Formal  |  Bluntness: Neutral
Safe for: Invitations, events, notices  |  Avoid with: Casual messages

12. Be on schedule

Broader than arrival time.

Examples:

• “Be on schedule for the whole morning, not just the start.”
• “Please be on schedule — each slot is fifteen minutes.”
• “Be on schedule and we will finish on time.”

Why it works: It covers keeping to timings throughout rather than merely arriving, which makes it right for agendas and running orders.

Tone: Neutral, professional  |  Formality: Formal  |  Bluntness: Neutral
Safe for: Agendas and multi-part events  |  Avoid with: Single meetings

13. Join us on time

Warm and inclusive.

Examples:

• “Join us on time — we’re starting with the client update.”
• “Do join us on time tomorrow.”
• “Join us on time and we’ll have coffee before we begin.”

Why it works: “Join us” frames attendance as welcome rather than required, which makes it the friendliest phrasing here.

Tone: Warm, inviting  |  Formality: Neutral  |  Bluntness: Gentle
Safe for: Anyone, including clients  |  Avoid with: Disciplinary conversations

14. Please be timely

Formal and slightly stiff.

Examples:

• “Please be timely with both attendance and submissions.”
• “Please be timely — the panel keeps to the minute.”
• “Candidates are asked to be timely.”

Why it works: “Timely” is more common about documents than people, which gives this an administrative flavour.

Tone: Formal, administrative  |  Formality: Formal  |  Bluntness: Neutral
Safe for: Official communications  |  Avoid with: Conversational messages

15. Don’t be delayed

Focuses on obstacles rather than choice.

Examples:

• “Don’t be delayed — there are roadworks on the A38.”
• “Please don’t be delayed getting through security.”
• “Try not to be delayed by the car park; it fills by half eight.”

Why it works: It treats lateness as something that happens to them rather than something they choose, which is tactful when travel is genuinely difficult.

Tone: Neutral, practical  |  Formality: Formal  |  Bluntness: Firm
Safe for: Travel and logistics  |  Avoid with: Habitual lateness

16. Make it on time

Casual and encouraging.

Examples:

• “Make it on time and you’ll catch the opening remarks.”
• “See if you can make it on time tomorrow.”
• “Make it on time — it’s worth being there from the start.”

Why it works: “Make it” acknowledges effort, which suits people with a genuine difficulty getting somewhere.

Tone: Casual, warm  |  Formality: Casual  |  Bluntness: Gentle
Safe for: Friends and colleagues  |  Avoid with: Formal notices

17. Stick to the time

About holding to a plan.

Examples:

• “Stick to the time — we have the room for one hour only.”
• “Please stick to the time on your slot.”
• “Stick to the time and everyone gets their turn.”

Why it works: It works best when the request is about the whole schedule rather than the start, such as speaking slots or interviews.

Tone: Neutral, firm  |  Formality: Neutral  |  Bluntness: Firm
Safe for: Panels, slots and interviews  |  Avoid with: Simple arrival requests

18. Keep to the schedule

Formal and collective.

Examples:

• “Please keep to the schedule circulated yesterday.”
• “Keep to the schedule and we will finish by five.”
• “Everyone should keep to the schedule from ten onwards.”

Why it works: Addressing the schedule rather than the person depersonalises the request, which is useful with a whole group.

Tone: Formal, neutral  |  Formality: Formal  |  Bluntness: Neutral
Safe for: Group and event communications  |  Avoid with: One-to-one conversations

19. Respect the time

Implies they currently do not.

Examples:

• “Please respect the time — people have travelled for this.”
• “Respect the time; we all have other commitments.”
• “Respect the time set aside for this session.”

Why it works: “Respect” turns punctuality into a moral question, which makes it a rebuke rather than a request. Readers hear the accusation.

Tone: Firm, moralising  |  Formality: Formal  |  Bluntness: Blunt
Safe for: Rarely appropriate in writing  |  Avoid with: Clients, guests, first requests

20. Please be ready on time

About readiness, not arrival.

Examples:

• “Please be ready on time — the taxi arrives at seven.”
• “Be ready on time with your documents.”
• “Please be ready on time; we cannot wait for the ferry.”

Why it works: “Ready” asks for more than presence, which is right when arriving is not enough — papers, kit, or a prepared contribution.

Tone: Neutral, practical  |  Formality: Neutral  |  Bluntness: Neutral
Safe for: Travel, filming, group departures  |  Avoid with: Ordinary meetings

21. Let’s start on time

Collective and blame-free.

Examples:

• “Let’s start on time today — there’s a lot on the agenda.”
• “Let’s start on time so we can finish early.”
• “Let’s start on time; I’ll be in the room from five to.”

Why it works: “Let’s” includes you in the obligation, which removes the accusation entirely. It is the best option for a recurring team meeting.

Tone: Warm, collective  |  Formality: Neutral  |  Bluntness: Gentle
Safe for: Teams and recurring meetings  |  Avoid with: Formal external invitations

22. Join promptly

Short, and suited to video calls.

Examples:

• “Join promptly — the recording starts at ten.”
• “Please join promptly; the webinar closes entry at 14:05.”
• “Join promptly so we can start with everyone present.”

Why it works: “Join” has become the standard verb for video calls, which makes this the natural online equivalent of “arrive promptly”.

Tone: Formal, brisk  |  Formality: Formal  |  Bluntness: Neutral
Safe for: Video calls and webinars  |  Avoid with: In-person social events

23. Be there without delay

Urgent and rather dramatic.

Examples:

• “Be there without delay — the surgeon is waiting.”
• “Please be there without delay once you are called.”
• “Be there without delay; the window is fifteen minutes.”

Why it works: “Without delay” signals genuine urgency, so it overstates an ordinary meeting and fits an emergency or a hard cut-off.

Tone: Urgent, formal  |  Formality: Formal  |  Bluntness: Firm
Safe for: Genuine urgency  |  Avoid with: Routine appointments

24. Arrive without delay

Formal twin of the above.

Examples:

• “Please arrive without delay after the second bell.”
• “Arrive without delay to be seated before the performance.”
• “Arrive without delay; latecomers wait for the interval.”

Why it works: Common in theatre, court and medical settings where late entry is genuinely impossible rather than merely inconvenient.

Tone: Formal, official  |  Formality: Formal  |  Bluntness: Firm
Safe for: Venues with hard cut-offs  |  Avoid with: Casual gatherings

25. Be right on schedule

Emphatic and slightly odd.

Examples:

• “Be right on schedule — the broadcast is live.”
• “Please be right on schedule for your slot.”
• “Be right on schedule and nobody has to rush.”

Why it works: “Right on” adds emphasis that “on schedule” does not need, which makes it sound spoken rather than written.

Tone: Neutral, emphatic  |  Formality: Neutral  |  Bluntness: Firm
Safe for: Live and timed events  |  Avoid with: Formal written invitations

26. We’ll start at 10:00 sharp

Replaces the request with a fact.

Examples:

• “We’ll start at 10:00 sharp, with or without a full room.”
• “The session starts at 14:00 sharp; I’ll open the call at 13:55.”
• “We start at nine sharp on Mondays.”

Why it works: “Sharp” closes the grace period, and stating your own intention is not a request at all — so there is nothing to resent and nothing to negotiate.

Tone: Direct, neutral  |  Formality: Any  |  Bluntness: Neutral
Safe for: Anyone, including clients  |  Avoid with: Nothing — it is the safest option here

27. Doors open at 6:30 for a 7:00 start

The invitation convention.

Examples:

• “Doors open at 6:30 for a 7:00 start.”
• “Arrivals and drinks from 2:30; the ceremony begins at 3:00.”
• “Registration from 08:45; the first session starts at 09:15.”

Why it works: Two times remove the guesswork completely: one to arrive, one when things begin. Weddings and events use it precisely because it asks nobody to be punctual and yet everybody is.

Tone: Formal, neutral  |  Formality: Formal  |  Bluntness: Gentle
Safe for: Invitations, weddings, events  |  Avoid with: Internal meetings

28. The client joins at 10:05, so we need to be underway

Gives the reason the time matters.

Examples:

• “The client joins at 10:05, so we need to be underway by then.”
• “The room is booked until eleven, so a late start costs us the last item.”
• “The surgeon has a list at nine, so 08:30 is genuinely 08:30.”

Why it works: People are late to meetings whose timing appears arbitrary. A reason converts a rule into a consequence, and consequences change behaviour where requests do not.

Tone: Practical, collegial  |  Formality: Neutral  |  Bluntness: Neutral
Safe for: Anyone  |  Avoid with: When no real reason exists

Detailed Comparison Table

All 28 alternatives, with formality, tone, how blunt each is, who it is safe to send to, and who to avoid sending it to.

Phrase	Formality	Tone	Bluntness	Safe for	Avoid with
Kindly arrive on time	Formal	Formal, polite	Gentle	Anyone	Casual team chat
Please don’t be late	Neutral	Direct, firm	Firm	Team members and students	Clients and guests
Be prompt	Formal	Formal, brisk	Neutral	Notices and instructions	Personal invitations
Make sure you’re on time	Neutral	Direct, firm	Firm	Students, trainees, direct reports	Colleagues and seniors
Please be punctual	Formal	Formal, neutral	Neutral	Invitations and formal notices	Informal messages
Don’t keep us waiting	Casual	Blunt, impatient	Blunt	Nobody, in writing	Clients, guests, anyone senior
Try to be on time	Casual	Gentle, weak	Gentle	Low-stakes gatherings	Anything with a hard start
Be there right on time	Casual	Direct, informal	Firm	Friends and close colleagues	Formal invitations
Show up on time	Casual	Casual, sharp	Blunt	Close colleagues only	Clients, students, invitations
Don’t be behind schedule	Formal	Formal, technical	Firm	Project and site teams	Social invitations
Arrive promptly	Formal	Formal, neutral	Neutral	Invitations, events, notices	Casual messages
Be on schedule	Formal	Neutral, professional	Neutral	Agendas and multi-part events	Single meetings
Join us on time	Neutral	Warm, inviting	Gentle	Anyone, including clients	Disciplinary conversations
Please be timely	Formal	Formal, administrative	Neutral	Official communications	Conversational messages
Don’t be delayed	Formal	Neutral, practical	Firm	Travel and logistics	Habitual lateness
Make it on time	Casual	Casual, warm	Gentle	Friends and colleagues	Formal notices
Stick to the time	Neutral	Neutral, firm	Firm	Panels, slots and interviews	Simple arrival requests
Keep to the schedule	Formal	Formal, neutral	Neutral	Group and event communications	One-to-one conversations
Respect the time	Formal	Firm, moralising	Blunt	Rarely appropriate in writing	Clients, guests, first requests
Please be ready on time	Neutral	Neutral, practical	Neutral	Travel, filming, group departures	Ordinary meetings
Let’s start on time	Neutral	Warm, collective	Gentle	Teams and recurring meetings	Formal external invitations
Join promptly	Formal	Formal, brisk	Neutral	Video calls and webinars	In-person social events
Be there without delay	Formal	Urgent, formal	Firm	Genuine urgency	Routine appointments
Arrive without delay	Formal	Formal, official	Firm	Venues with hard cut-offs	Casual gatherings
Be right on schedule	Neutral	Neutral, emphatic	Firm	Live and timed events	Formal written invitations
We’ll start at 10:00 sharp	Any	Direct, neutral	Neutral	Anyone, including clients	Nothing — it is the safest option here
Doors open at 6:30 for a 7:00 start	Formal	Formal, neutral	Gentle	Invitations, weddings, events	Internal meetings
The client joins at 10:05, so we need to be underway	Neutral	Practical, collegial	Neutral	Anyone	When no real reason exists

Two findings in that table. 3 of the 28 are blunt enough to read as a rebuke — “don’t keep us waiting”, “show up on time” and “respect the time” all accuse the reader of something before they have done it. And only 3 of the 28 contain an actual time, which is the one piece of information that would settle the question.

Asking Guests on an Invitation

Formal invitations solved this problem long ago, and the solution is to give two times instead of a request.

“Doors open at 6:30 for a 7:00 start” tells a guest when to arrive and when things begin. Nobody is asked to be punctual, and nobody arrives at 7:05 wondering whether they have missed anything.

Event	The convention
Wedding	“Arrivals from 2:30; the ceremony begins at 3:00” — guests seated well before the bridal party
Theatre or concert	“Doors 7:00, curtain 7:30”, often with “latecomers admitted at the interval”
Conference	“Registration from 08:45; first session 09:15”
Dinner at home	“Come from seven, we’ll eat at eight” — which is why nobody minds a 7:20 arrival

Guest: Invitation says three o’clock — does that mean be there at three?

Bride’s mother: Be there at half two. The cars arrive at five to.

Guest: Then why does it say three?

Bride’s mother: Because I wrote it badly. Everyone else is asking too.

The pattern is the same every time: an arrival window, then a fixed moment. If you only have one time to give, add what happens at it — “we sit down at eight” does more than “please be punctual” ever will.

When Someone Is Repeatedly Late

If a person is late every week, the phrasing of your reminder is not the problem.

Searching for a politer way to say it is usually a way of avoiding a conversation. A group email asking everyone to be punctual, aimed at one person, is the least effective option available: the person it targets rarely recognises themselves, and everyone else feels accused.

• ✅ Speak to them directly and privately. One sentence: “you’ve been ten minutes late to the last four stand-ups — is something clashing?”
• ✅ Ask before instructing. Often there is a school run, a previous meeting that overruns, or a bus that arrives at 09:02.
• ✅ Fix the cause if you can. Moving a meeting by ten minutes solves more lateness than any request.
• ❌ Do not send a group reminder about one person. It damages the group and misses the target.

This is also the point at which an announcement stops being information and becomes a request — and those need to be addressed to somebody, not circulated to everyone as background.

“On Time” Does Not Mean the Same Thing Everywhere

This is the part that quietly ruins international meetings.

Wikipedia’s account of punctuality is explicit: “each culture tends to have its own understanding about what is considered an acceptable degree of punctuality”, and in most Western cultures “a small amount of lateness is acceptable — this is commonly about five to ten minutes”, though even that is context-dependent.

So “please be on time” is read through the reader’s own norm. To one person it means 09:00. To another it means 09:05 and no harm done. In cultures that place a high value on punctuality, the article notes, “being late is seen as disrespectful of others’ time and may be considered insulting” — which is why the same ten minutes can be unremarkable to one colleague and offensive to another.

The fix is not cultural training. It is a number and a consequence:

• ✅ “We start at 09:00 and the recording begins then.”
• ✅ “I’ll open the call at 13:55; we begin at 14:00.”
• ✅ “The first ten minutes are the client’s, so please be in the room by 09:55.”
• ❌ “Please be on time”, which every reader translates differently.

Say the Time, Not “On Time”

Almost every problem on this page disappears when you stop asking and start informing.

Team lead: Reminder: please be on time for stand-up.

Dev: We never actually start until ten past, so I stopped rushing.

Team lead: Fair. From Monday I’m starting at 09:30 exactly, whoever is in the room.

Dev: That I can work with.

Three elements make a reminder work, and none of them is politeness:

• ✅ An exact time — “09:30”, not “the morning meeting”.
• ✅ A consequence — what happens at that moment whether or not everyone is present.
• ✅ A reason — the client, the room booking, the recording, the ferry.

Then do the thing you said. A team that has been told “09:30 sharp” twice and started at 09:40 both times has learned that 09:30 means 09:40, and no amount of rephrasing will teach them otherwise. If the time then changes, say so in the same thread rather than sending a fresh message that contradicts the first, and confirm the new one plainly, much as you would acknowledge a time someone else has fixed.

The Bottom Line

Searching for other ways to say please be on time is a sign you have asked already and it did not work. It did not work because the phrase carries no information: no time, no reason, and a faint accusation.

Use please arrive promptly on an invitation, let’s start on time with a team, and give two times whenever guests are involved. Best of all, replace the request entirely — we’ll start at 10:00 sharp because the client joins at 10:05 — and then start at 10:00. The sentence does the work once; the following through is what makes it true.