Case 1: Tourist ETA before a last-minute flight
| Profile | Risk found | Route decision | Next page |
|---|---|---|---|
| EU passport, hotel stay, flight in four days | Return plan and accommodation dates did not match the stated short-stay timing | Tourist ETA stayed the right route, but the document story needed cleanup before submission | Tourist ETA |
The file looked simple because the trip was short. The risk was not the passport; it was inconsistent timing. We aligned the hotel dates, onward logic and travel purpose so the short-stay explanation read as one file instead of three disconnected facts.
Case 2: Business vs transit correction
| Profile | Risk found | Route decision | Next page |
|---|---|---|---|
| UK passport, one-night Colombo stop, supplier meeting on arrival | The draft looked like transit, but the actual activity inside Sri Lanka was commercial | Moved from transit logic to Business ETA review before the wrong category was used | Business ETA |
This is the type of case where number of hours can mislead the applicant. A short stop can still be a business visit if the traveler has meetings, supplier contact or commercial activity.
Case 3: Extension planning after a trial month
| Profile | Risk found | Route decision | Next page |
|---|---|---|---|
| Remote professional, mixed housing budget, likely extension | Vacation-style budget notes did not match a realistic long-stay intention | Separated immediate entry from later extension timing and living-cost assumptions | Visa Extension |
The strongest move was not pretending the whole plan was a simple holiday. We kept the first step clean, then mapped current status, address, budget, insurance and timing.
Case 4: Residence discovery for a company-backed profile
| Profile | Risk found | Route decision | Next page |
|---|---|---|---|
| Founder with a local commercial idea and source-of-funds questions | A short-stay explanation could not carry the real intention | Moved the conversation into company, residence and investor-route discovery | Residence / Company Setup |
Rather than forcing the profile into a tourist or business ETA frame, we treated it as an early residence discovery case.
Case 5: Refusal recovery before reapplying
| Profile | Risk found | Route decision | Next page |
|---|---|---|---|
| Previous refusal, unclear travel purpose, new itinerary | The new file repeated the same weak explanation with different dates | Paused the reapplication and rebuilt the purpose, evidence and timeline first | Refusal recovery guide |
After a refusal or delay, speed is tempting. The safer sequence is to identify what changed, what evidence is stronger and whether the new category answers the old concern.
Case 6: Indian passport with business and family overlap
| Profile | Risk found | Route decision | Next page |
|---|---|---|---|
| Indian applicant combining a family visit with a supplier meeting | Tourist wording hid a commercial activity that needed explanation | Kept family context visible while reviewing Business ETA fit for the meeting portion | Indian citizens guide |
Mixed-purpose files need careful wording. The goal was not to exaggerate the business purpose, but to avoid hiding it inside a pure tourism story.
Case 7: GCC resident with passport-country confusion
| Profile | Risk found | Route decision | Next page |
|---|---|---|---|
| GCC resident traveling on a non-GCC passport | Residence country and passport country were being treated as the same thing | Separated passport nationality, residence base and Sri Lanka travel purpose before route choice | GCC residents guide |
For GCC residents, the file story often has two identity layers: passport country and residence base. Keeping them separate makes the rest of the route easier to read.
Case 8: Digital nomad income consistency check
| Profile | Risk found | Route decision | Next page |
|---|---|---|---|
| Remote worker with foreign clients and changing monthly income | Income proof looked real but irregular, with no explanation of work model | Built a clearer remote-work narrative before digital nomad or extension planning | Digital Nomad |
The issue was not whether the applicant worked online; it was whether documents could explain income, client relationship, insurance and stay length coherently.
Case 9: Retirement city-fit review
| Profile | Risk found | Route decision | Next page |
|---|---|---|---|
| 55+ applicant comparing Galle, Colombo and Kandy for long stay | Housing and healthcare assumptions were based on holiday experience | Recommended a trial stay and retirement-route evidence review before deeper commitment | Retirement / My Dream Home |
Long-stay comfort depends on more than visa days. Healthcare, transport, housing, monthly rhythm and support network all affect whether the route is realistic.
Case 10: Medical Ayurveda travel timing
| Profile | Risk found | Route decision | Next page |
|---|---|---|---|
| Traveler with planned Ayurveda program and companion | Treatment dates, companion purpose and accommodation were not aligned | Rebuilt the health-travel timeline and separated companion logic from the main treatment file | Medical / Ayurveda Visa |
Health-travel files need privacy-aware clarity. Appointment timing, companion role and accommodation should support the same treatment plan.
Case 11: Investor route pre-screen
| Profile | Risk found | Route decision | Next page |
|---|---|---|---|
| Capital owner considering company setup after a market visit | Investor language appeared before source-of-funds and role questions were ready | Started with business visit clarity, then mapped investor and residence discovery questions | Investor / Golden Visa |
Investor planning becomes stronger when the first conversation separates market visit, company role, funds evidence, banking and residence timeline.
Case 12: US traveler with transit and tourism overlap
| Profile | Risk found | Route decision | Next page |
|---|---|---|---|
| US passport holder leaving the airport during a long stopover | The stopover included sightseeing, which made pure transit logic weak | Reviewed whether Tourist ETA was cleaner than forcing the plan into transit | US citizens guide |
Transit is not only about flight hours. If the traveler turns the stop into a real Sri Lanka visit, the category should reflect that reality.
What these examples have in common
- Purpose first, not form first
- Dates, documents and route must tell one story
- Short-stay logic should not hide long-stay intent
- Transit, tourist and business labels should not be used interchangeably
- Official decisions remain with Sri Lankan authorities
Send your plan for a 24-hour pre-check if you want us to identify the cleanest route before you apply.