Practical guide · Sri Lanka
Working With a Sri Lankan Development Team
This is the practical detail a buyer needs after deciding to work with a team in Sri Lanka: how the clock lines up with yours, what the working week and the holiday calendar look like, how written communication usually runs, and which contracting, payment and data questions to settle in the first week. Code Sage Labs is based in Colombo, so this is written from the inside; the arrangements described are ordinary for the market, not specific to us.
By Anjula Paulus, Founder and software engineer · Published · 9 min read
Key takeaways
- Sri Lanka is UTC+5:30 year-round and does not observe daylight saving.
- A Colombo day overlaps Europe and the Gulf well, Australia partly, and the Americas not at all.
- The holiday calendar includes a Poya day each month and the dates move each year.
- English is the normal working language of the local software industry.
- Settle currency, payment route, data terms and the governing law in week one.
01
Terms used in this guide
A few of these are local and the rest are cross-border contracting vocabulary.
- UTC+5:30 — Sri Lanka Standard Time, fixed all year, with no daylight saving adjustment.
- Overlap window — the hours in which both your working day and the team's are open.
- Poya day — the monthly full-moon public holiday in Sri Lanka; the date moves with the lunar calendar.
- Asynchronous handover — a written end-of-day summary that lets the next time zone continue without a meeting.
- SWIFT transfer — the usual international bank route for paying a Sri Lankan supplier.
- Standard contractual clauses — the data-transfer terms a European or British client typically attaches when a processor is outside their jurisdiction.
- Governing law and forum — the law the contract is read under and where a dispute would be heard; both are chosen, not inherited from the supplier's location.
02
The time zone, concretely
Sri Lanka sits at UTC+5:30 and stays there. Your own clock is the one that moves, so the gap changes twice a year if you observe daylight saving and never otherwise. The lines below take an ordinary Colombo working day of 09:00 to 18:00 and give the approximate shared hours with a 09:00 to 17:00 or 18:00 day elsewhere.
- London — about three and a half shared hours in winter, about four and a half during British Summer Time.
- Berlin, Paris, Amsterdam — about four and a half shared hours in winter, five and a half in summer.
- Dubai and the Gulf — around seven shared hours; effectively a normal working relationship.
- Singapore and Hong Kong — around six and a half shared hours, weighted to the Colombo afternoon.
- Sydney and Melbourne — about three and a half shared hours, falling to two and a half under daylight saving, in the Colombo afternoon.
- New York and Toronto — no shared hours within normal working days; collaboration is asynchronous or scheduled outside one side's day.
- San Francisco — no shared hours; the practical pattern is a written handover each way.
03
What the overlap means in practice
Three to five shared hours is enough for a normal working relationship if the day is arranged around it. Put the standing call, reviews and anything needing a decision inside the window, and leave deep work outside it. The common mistake is to spread meetings across the window until it is full, which removes the only hours in which questions can be answered quickly.
For the Americas, do not try to fix the clock by asking a Colombo team to work nights permanently. It holds for a few weeks and then the good engineers leave. The arrangement that lasts is a genuine asynchronous one: written end-of-day handovers, acceptance conditions clear enough to unblock without a call, and one scheduled overlap meeting a week at a time that is inconvenient for both sides equally.
04
The working week and the holiday calendar
The software industry works Monday to Friday. The public holiday calendar is longer than in most Western countries and includes a Poya day every month, when the full moon falls, plus religious and national holidays across several traditions. The dates of many of them move each year, and some are confirmed only a few months ahead.
None of this is a problem if it is planned, and it is a recurring irritation if it is not. Ask for the supplier's holiday calendar at kickoff, put it in the shared project calendar, and plan releases and milestones around it rather than discovering a holiday on the morning of a deadline.
- Request the year's holiday calendar in the first week
- Agree cover arrangements for any holiday that lands on a release date
- Check how April's festival period is handled, as it is a longer break than most
- Agree in advance what counts as an emergency and who responds
- Note that your holidays are equally invisible to them; share both calendars
05
Language and written communication
English is the working language of the Sri Lankan software industry: documentation, code, tickets and client meetings are normally in English, and Sinhala and Tamil are the languages spoken at home and between colleagues. For a client this means written communication is rarely the obstacle, though accents and speaking pace take a short adjustment on both sides, as they do in any cross-border team.
Judge this per team rather than per country, as with any destination. The useful test is not a sales call, which is rehearsed, but a written one: ask for a short written analysis of an ambiguous requirement from the engineer who would do the work, and read how they handle the ambiguity as well as the language.
06
Contracting, payment and data
Cross-border agreements with Sri Lankan suppliers are commonly written under the client's own law or a neutral forum, with arbitration named for disputes. That is a choice you make, not a consequence of where the supplier sits, and it is worth making deliberately rather than accepting a default template.
Suppliers normally invoice in a major currency and receive payment by international bank transfer into a Sri Lankan account. Agree which currency, which route, who absorbs the transfer fees and what the payment terms are before the first invoice. On data, Sri Lanka has a Personal Data Protection Act; confirm its current status and, more importantly, keep your own obligations under British or European law satisfied through the contract, since those are the rules that will be enforced against you.
- Governing law, forum and arbitration named explicitly
- Currency, payment route, fee responsibility and payment terms
- Intellectual property assigned to the client on payment, in writing
- A data processing agreement with transfer terms attached where required
- Confidentiality covering client data, commercial terms and unpublished work
- Named-account access with an offboarding checklist
07
What to arrange in the first week
The arrangements below take an hour each and prevent most of the friction that remote engagements accumulate over months.
- The overlap window, written down, with the standing call inside it
- One accountable lead on each side and an escalation route
- A shared calendar carrying both countries' holidays
- An end-of-day written handover, if the overlap is under three hours
- Repository, cloud and secret ownership in your accounts
- An answer to what happens if power or connectivity fails, which is a question worth asking any remote team anywhere
08
A decision rule
Apply these in order and stop at the first that matches.
- Rule 1: if your working day is British, European, African or Gulf, a Sri Lankan team fits your clock without anyone working unusual hours.
- Rule 2: if your working day is Australian or Singaporean, the overlap is real but sits in the Colombo afternoon; schedule accordingly.
- Rule 3: if your working day is North American and you need live daytime collaboration, choose a nearer time zone instead of asking anyone to invert their day.
- Rule 4: if your working day is North American and the work can be asynchronous, insist on written handovers and acceptance conditions before you start, not after the first misunderstanding.
- Rule 5: if your project has hard release dates, map them against the Sri Lankan holiday calendar before you commit to them publicly.
- Rule 6: whatever your time zone, judge the individual team on a written response to an ambiguous requirement rather than on any country-level claim, including the ones in this guide.
Questions
Common questions about working with a sri lankan team
What time zone is Sri Lanka in?
UTC+5:30, all year. Sri Lanka does not observe daylight saving, so the difference to your own clock changes only when yours does. It is the same offset as India.
How many hours does a Sri Lankan team overlap with the United Kingdom?
A Colombo working day of 09:00 to 18:00 shares roughly three and a half hours with a London working day in winter and about four and a half during British Summer Time. That is enough for a daily call and same-day answers if meetings are kept inside the window.
Is English used in Sri Lankan software teams?
Yes. English is the normal working language of the industry for documentation, code, tickets and client meetings, alongside Sinhala and Tamil in daily life. Verify it with the engineers on your own project rather than relying on a country-level statement.
What public holidays affect a Sri Lankan development team?
The calendar includes a Poya day each month on the full moon, plus national and religious holidays across several traditions, and many dates move year to year. Ask for the supplier's calendar at kickoff and plan releases around it.
Can a Sri Lankan team work with United States clients?
Yes, asynchronously. There is no overlap with a United States working day, so it depends on written handovers, clear acceptance conditions and autonomy rather than on live collaboration. Permanently inverting the team's day is not a stable arrangement.