Your team member in Lagos is one hour ahead of the one in Accra, two hours behind the one in Nairobi, and shares a clock with the one in Algiers. Build your schedule around the three zones that matter for business, WAT, CAT, and EAT, and treat the islands as edge cases.

Africa spans six offsets from UTC-1 (Cabo Verde) to UTC+4 (Mauritius), but over 95% of the continent's business activity runs on just three: WAT, CAT, and EAT. For a US or European manager, the practical question is never "What time is it in Africa?" but "Which Africa?" Lagos runs an hour behind Cairo, which runs an hour behind Nairobi. Get the zone right and arranging calls becomes straightforward. Get it wrong and you will be calling Kenya at midnight.

Which time zones actually matter for remote work on the continent?

Four standard designations cover nearly all business activity:

  • WAT (West Africa Time): UTC+1. Nigeria, Algeria, Tunisia, Niger, Chad, Benin, and parts of DRC.
  • CAT (Central Africa Time): UTC+2. South Africa, Egypt, Zimbabwe, Zambia, Mozambique, Botswana, Rwanda, Burundi, Malawi, and the rest of DRC.
  • EAT (East Africa Time): UTC+3. Kenya, Ethiopia, Tanzania, Uganda, Somalia, Comoros, Madagascar, Mayotte.
  • SAST (South African Standard Time): UTC+2. Identical offset to CAT but used only in South Africa, Lesotho, and Eswatini.

Ghana sits on GMT (UTC+0), not WAT. Morocco runs on UTC+0 with DST to UTC+1, suspended during Ramadan. The remaining offsets matter less for remote work: Cabo Verde at UTC-1, and Mauritius, Seychelles, and Reunion at UTC+4. The island nations are the exception that proves the rule. The continent's economic engines all sit within the UTC+1 to UTC+3 band.

How do I find working hours that overlap with US teams?

Morning US Eastern (08:00-10:00) matches afternoon Africa: 13:00-15:00 WAT, 14:00-16:00 CAT, 15:00-17:00 EAT.

West Coast teams get almost nothing. A 09:00 Los Angeles start is 17:00 in Lagos, 18:00 in Johannesburg, and 19:00 in Nairobi. By the time California wakes up, your colleagues have left the office.

East Coast and Central US managers fare better:

US Time WAT (Lagos) CAT (Johannesburg) EAT (Nairobi)
08:00 ET 14:00 15:00 16:00
09:00 ET 15:00 16:00 17:00
10:00 ET 16:00 17:00 18:00

Block 08:00-10:00 US Eastern. That gives a solid two-hour shared window with West Africa and a narrow but workable one with East Africa. For West Coast teams, accept that you will work early mornings or your colleagues will work evenings. There is no third option.

How do I find working hours that overlap with European teams?

Europe-to-Africa is the easiest relationship on the calendar. The difference runs 0-3 hours. Most of the working day coincides naturally.

  • London to Lagos: 1 hour (London behind)
  • Paris to Lagos: same hour
  • London to Nairobi: 3 hours
  • Paris to Nairobi: 2 hours

Book a 10:00 London meeting. That is 11:00 in Lagos and 13:00 in Nairobi. Everyone is awake. Everyone is productive. The morning Europe to late morning Africa window is the best shared period for the continent's most important trade corridor.

The trap: when Europe shifts to daylight saving in late March, the difference narrows or disappears for WAT countries. When Morocco suspends DST for Ramadan, the usual rules flip.

How do I find working hours that overlap with Asian teams?

Asia is the hardest direction. China Standard Time (UTC+8) runs 5-7 hours ahead of the main zones. Your Chinese colleagues are leaving work just as your Nairobi team starts.

The realistic window: 08:00 in Beijing is 03:00 EAT. That does not work. Your practical options:

  • Early morning Asia, late evening Africa: 15:00 China time is 10:00 EAT, 09:00 CAT, 08:00 WAT. Workable for East Africa.
  • Late evening Asia, early morning Africa: 20:00 China time is 15:00 EAT. Works if your team shifts later.

India (UTC+5:30) sits between Africa and East Asia: 14:00 IST is 11:00 EAT, 10:00 CAT, 09:00 WAT. Morning India to afternoon East Africa is your most reliable Asia-Africa bridge.

What tools stop me messing up time zone math?

Use tools that handle zones natively. Never rely on memory or manual conversion.

  • World Time Buddy: free converter for visualising shared hours across multiple zones.
  • Every Time Zone: simple visual grid showing who is awake where.
  • Calendly: lets each party see availability in their own local time.
  • Google Calendar world clock: shows multiple zones side by side.
  • Slack timezone feature: shows each member's local time next to their name.

Practices that prevent disaster:

  1. State the time in UTC and local time in every invitation: "10:00 UTC (12:00 WAT, 13:00 CAT, 14:00 EAT)."
  2. Rotate meeting times if you have members in both West and East Africa. One side will always be inconvenienced.
  3. Record every meeting, standup, and client call. Absent members catch up asynchronously.
  4. Use async-first communication for non-urgent matters. Shared docs, Loom videos, and project trackers beat real-time meetings for anything that does not require immediate discussion.

Does Ramadan change when my team is available?

Yes. Morocco does something unique with its clocks: it suspends daylight saving during Ramadan and reverts to UTC+0 for the holy month. The suspension follows the lunar calendar, shifting roughly 11 days earlier each Gregorian year. Check the exact dates annually. The change affects the entire country's business hours.

In other Muslim-majority countries (Egypt, Algeria, Tunisia, Senegal, northern Nigeria), work hours shorten during Ramadan but clocks stay put. Expect businesses to open later and close earlier. The workday typically runs 09:00-15:00 or 10:00-16:00 instead of the standard 08:00-17:00. Productivity drops in the afternoon.

Other holidays that affect arranging calls:

  • Eid al-Fitr and Eid al-Adha: moveable dates, 1-3 days each, widely observed across North and West Africa.
  • Christmas: 25 December is a public holiday in all 54 countries. Christian-majority nations also observe 26 December as Boxing Day.
  • Good Friday and Easter Monday: public holidays in most sub-Saharan countries.
  • Independence days: every country has one, usually a single day but sometimes a week.

Check the specific country's holiday calendar before you book anything. A meeting request that lands on Eid or Independence Day will be ignored. Or worse, resented.

What happens when the power cuts out mid-call?

Time zone coordination means nothing if your team cannot connect. Infrastructure has improved dramatically but remains uneven.

South Africa, Kenya, Nigeria, and Egypt all have robust fibre backbones and multiple undersea cable connections. Major cities, Nairobi, Lagos, Johannesburg, Cairo, Accra, have reliable 4G and increasingly common 5G coverage. Video calls work well in these hubs.

Power outages remain common in many countries. Internet speeds drop when the grid fails and businesses switch to generators.

What to do:

  • Assume your team members have a backup plan. Most experienced remote workers keep multiple ISPs and mobile data plans.
  • Build in flexibility for outages. Allow asynchronous catch-up when connections fail.
  • Test video quality before critical calls. Confirm your developer in Kenya can join the client presentation well before the start time.
  • East Africa (Nairobi, Kampala) generally has better infrastructure than West Africa (Lagos, Accra). Schedule your most critical meetings accordingly.

Where are the continent's tech hubs and what zones are they in?

Lagos, Nigeria (WAT, UTC+1). The startup capital. Y Combinator-backed companies, fintech giants like Flutterwave and Paystack, a large developer community. Lagos is one hour behind London, six hours ahead of New York.

Nairobi, Kenya (EAT, UTC+3). The "Silicon Savannah." Home to M-Pesa and a growing number of remote-friendly employers. Three hours ahead of London, eight hours ahead of New York.

Cape Town and Johannesburg, South Africa (CAT/SAST, UTC+2). The continent's most developed economy. Johannesburg's financial district and Cape Town's tech scene host banking and AI startups. Two hours ahead of London, seven hours ahead of New York.

Cairo, Egypt (CAT, UTC+2). The Middle East's gateway to the continent. Egypt's startup scene is growing fast. Its zone aligns with South Africa, making calls across northern and southern hubs straightforward.

Accra, Ghana (GMT, UTC+0). Accra runs on GMT, making it the easiest hub to coordinate with London (same time) and a convenient bridge to US East Coast mornings.

When arranging calls across hubs, remember: a 15:00 Lagos call is 14:00 in Accra, 16:00 in Johannesburg, and 17:00 in Nairobi. Pick one anchor city and convert from there.