The Straight Answer
Colombia runs on Colombia Time, which is UTC-5 all year round. No daylight saving adjustments. No exceptions. That means when it's 12:00 PM in Bogotá, it's also 12:00 PM in New York during standard time, but New York has already shifted to EDT (UTC-4) while Colombia hasn't moved at all. That mismatch is where most scheduling errors happen. The confusion isn't really about what Colombia does. It's about what everyone else does around it. Colombia sits at the same offset as Eastern Standard Time, Eastern European Time, and Central European Time depending on the season. When you're coordinating a call between Bogotá, Berlin, and New York, all three cities can appear on the same clock hour at different times of year, and then suddenly they don't. That's the trap. I've been the person who scheduled a vendor sync for 3 PM Bogotá time and had the Berlin team show up at 2 PM because I didn't account for Europe entering DST while Colombia stayed flat. Wasted an hour of everyone's morning. Now I check three things before sending any calendar invite: the host city's current offset, whether any participant region is in or out of DST, and whether the platform I'm using auto-converts correctly. Most platforms get it right, but not all of them, and not consistently.
The practical workaround I settled on is simple. I only schedule meetings during the overlap window between Bogotá and the complicating region. That means for European coordination, the sweet spot is roughly 9 AM to 1 PM Bogotá time, which maps to 2 PM to 6 PM Central European Summer Time. For US coordination, it's wider because Eastern time and Colombia share the same base offset, but again only when the US is on standard time. In summer, you lose that two-hour window on the late side. A 4 PM Bogotá meeting is 5 PM in New York in July, not 3 PM like people assume. There are a few lesser-known details that matter more than the basic offset. Colombia's timezone has been UTC-5 since 1993. Before that, parts of the country experimented with regional time differences, but those were abolished. The government has discussed adopting DST several times, usually tied to energy conservation arguments, but nothing has ever passed. So you can safely assume UTC-5 indefinitely. Don't build automation around the possibility of a change without a fallback. Another thing people miss: Colombia shares its timezone with Ecuador and Panama, but not Venezuela, which is UTC-4, or most of Brazil, which spans three offsets. If you're running a LATAM-wide operation, treating "South American time" as one thing will cost you. A team in Manaus operates on UTC-4, which is the same as Bogotá in summer but half an hour behind in winter relative to US Eastern time. That half hour compounds when you're juggling five countries on one call.
For tools, I use time.is/colombia for a quick visual check before any important scheduling, and my calendar system auto-populates timezone offsets when I add a location. The risk there is that some location entries default to the wrong timezone database entry if you pick a smaller city. Bogotá is always correct. Medellín is correct. Pick a major city every time to avoid database edge cases. If you need to coordinate internationally on a regular basis, the most reliable method is to pick one reference timezone for all your internal scheduling and display everything else as secondary. I use UTC as my anchor and show the local equivalent in parentheses on every invite. That way the math never depends on whether someone remembered that Colombia doesn't change clocks. It just shows the correct conversion every single time regardless of season. The downside of that approach is that it adds cognitive load for participants who prefer seeing their own clock time front and center. Some teams push back on it. The alternative is accepting that miscommunication will happen during transition weeks in March and October when the US and Europe shift and Colombia doesn't. Those two weeks per year are when I double-check everything and avoid scheduling anything time-sensitive if I can help it.
Get the Full Details
