TBC meaning: TBC stands for “to be confirmed.” At work, it marks a detail, such as a date, time, venue or speaker, that has a likely answer but is not final yet. It is close to TBD (to be determined), which means no decision has been made, and TBA (to be announced), which means the decision will be shared later.
What does TBC mean at work?
TBC is a placeholder that says “we think it’s this, but don’t lock it in yet.” You’ll see it in meeting agendas, event invites, travel plans, project timelines and job postings.
For example, “Workshop: Tuesday 2 p.m. (TBC)” suggests Tuesday at 2 is the plan, but someone still needs to confirm the room or the speaker’s availability.
TBC is common in British and international business English. In the US, many people use TBD for the same purpose, even though the meanings are slightly different.
Examples of TBC in emails and messages
Agenda: “10:00 Welcome – Priya. 10:15 Product update – speaker TBC.”
Email: “Offsite is planned for March 12 (venue TBC). I’ll confirm by Friday.”
Slack: “Launch date TBC, waiting on legal sign-off.”
Calendar title: “Client dinner – time TBC”
Project plan: “Phase 2 budget: $25K (TBC after vendor quotes).”
TBC vs TBD vs TBA
| Term | Stands for | What it signals | Example |
|---|---|---|---|
| TBC | To be confirmed | A tentative answer exists, awaiting confirmation | “Friday 3 p.m. (TBC)” |
| TBD | To be determined (or decided) | No decision yet | “Location: TBD” |
| TBA | To be announced | Decided or will be decided, shared later | “Keynote speaker: TBA” |
Simple rule: if you have a best guess, use TBC. If you have no idea yet, use TBD. If the information exists but isn’t public, use TBA.
How to use TBC correctly
- Put it next to the uncertain detail only. “Thursday, 4 p.m. TBC” is clearer than marking the whole invite TBC.
- Say when it will be confirmed. “TBC by Wednesday” helps people plan.
- Follow up. Send a quick confirmation and update the calendar so old TBCs don’t linger.
- Use brackets or a dash. “(TBC)” or “– TBC” keeps it visually separate.
- Write it out for unfamiliar audiences. US clients may know TBD better than TBC. “To be confirmed” is always safe.
How do you follow up on a TBC item?
TBC is a promise that an answer is coming. If nobody owns that promise, the detail can stay unconfirmed until the last minute. These steps keep it moving:
- Name an owner. “Venue TBC (Jamie confirming)” tells everyone who to ask.
- Add a confirm-by date. “Speaker TBC, confirmed by Friday” sets an expectation.
- Update everyone in one place. Change the original invite, agenda or document rather than sending a separate note people may miss.
- Mark it confirmed clearly. Replace “TBC” with the final detail, and add “Confirmed” if the change is important.
TBC in invitations, agendas and schedules
TBC is most common where several details come together and some are settled before others. Here’s how it looks in practice:
Event invite: “Team offsite, Thursday, May 14. Location TBC, we’ll confirm by May 1.”
Meeting agenda: “10:30 – Product update (presenter TBC)”
Project plan: “Phase 2 start date: TBC, depends on client sign-off.”
Travel note: “Flights booked. Hotel TBC once the conference block opens.”
Follow-up email: “Update: the venue is now confirmed as the Riverside Conference Center.”
What can you write instead of TBC?
TBC is common in British and international business writing. In the US, many readers know it, but TBD is more familiar. If you aren’t sure your audience will understand it, write it out:
- “Not confirmed yet, we’ll update you by Friday.”
- “Pending confirmation from the venue.”
- “Expected to be 2 p.m., to be confirmed.”
- “Final details coming next week.”
Spelling it out is also a good idea for customers, job candidates and anyone outside your company, since a short form can look like a typo to someone who hasn’t seen it before.
Why does TBC matter in planning?
Marking a detail TBC is more honest than guessing. If you write a date as final and it later moves, people may book travel, invite clients or plan work around the wrong information. TBC tells them to hold off on anything that depends on that detail.
It also helps teams spot risk. A plan with one TBC item is normal. A plan where the date, venue, budget and owner are all TBC a week before launch is a warning sign, and a good prompt to ask what’s blocking those decisions. Project managers often review open TBC items in status meetings for exactly this reason.
Should you use TBC in contracts or offer letters?
It’s best to avoid it. Formal documents should state final terms. If a start date or detail truly isn’t settled, say how it will be decided, for example “Start date to be agreed in writing by both parties,” so there is no confusion later about what was promised.
Related terms
Browse more short forms in our Workplace Acronyms hub.
FAQ
What does TBC stand for?
TBC stands for to be confirmed. It marks a detail that is planned but not final.
Is TBC the same as TBD?
They are similar but not the same. TBC means a likely answer exists and needs confirming. TBD means the detail has not been decided yet.
Is TBC used in American English?
Yes, but it is more common in British and international English. Many US offices use TBD in the same places.
Is TBC professional in email?
Yes. TBC is widely used in agendas, invites and project plans. Adding when the detail will be confirmed makes it even more useful.
