Kavitha Raman and her two colleagues run a small travel desk out of a rented office near Anna Salai, arranging weekend breaks and short Chennai itineraries for visiting families. For their first three years, they described their working life as a series of emergencies. Then one December they changed a single habit, and the emergencies stopped. This is the story of how a Chennai travel calendar, built from public dates and early reminders, replaced improvisation with routine.
The December that broke the pattern
The desk had promised a family from out of town a week in the city during the winter music season. Sabhas hold concerts and lecture-demonstrations through the cooler months, and Chennai fills with rasikas, visiting performers and tourists alike. Kavitha had known this in a general way. What she had not done was check how early the popular stays and tickets tighten. By the time the booking began, the neighbourhood hotels the family preferred were full, and two venues had limited seats left. The week still happened, but it cost a lot of extra effort and a good part of the desk’s goodwill.
At the review meeting afterwards, the team’s coordinator, Arun, asked a pointed question: which part of this was a surprise? The honest answer was none of it. The music season returns every year. So do the Pongal holidays, the book fair that many families like to visit, and the northeast monsoon that shapes the city’s autumn. All of it was on a calendar somewhere. It simply was not on theirs.
What they built
The team spent one afternoon assembling a shared calendar with five colour-coded categories.
- Festivals and cultural seasons: Pongal in January, the Tamil New Year in April, the winter music and dance season, and the temple festivals around Mylapore and elsewhere, each marked as “confirm exact dates”.
- Weather bands: the hotter months before the rains, the southwest monsoon breeze period, and the northeast monsoon stretch in the later part of the year, when heavy rain can disrupt plans.
- Holiday windows: school vacations and long weekends, when demand from domestic travellers peaks.
- Venue and attraction timings: opening days and hours for museums, temples and beaches that clients ask about most.
- Business dates: client payments, supplier invoices, licence renewals and tax filing for the desk itself.
Every entry carried two reminders. The first fired at the point where the slowest task, usually securing rooms and tickets, needed to begin. The second fired a week before travel to reconfirm everything.
Checking the dates, not trusting them
Arun made one rule that kept the calendar honest. No date entered the “confirmed” colour without a source: a venue notice, an official tourism page or a trusted local announcement. Dates tied to lunar calendars were marked “expected” until verified. This single rule prevented the mistake the desk had feared most, which was copying a date from the previous year and being wrong by a week.
When they needed material for clients who were new to the city, they leaned on resources like a primer on preparing a first visit to Chennai, and linked relevant entries from the calendar to the checklist items inside it.
The first winter with the calendar
By October the reminders were doing their work. An early alert prompted Kavitha to open bookings for the music-season group while rooms were still plentiful. A second alert reminded the desk to ask clients about their must-see concerts well before listings filled. The monsoon band on the calendar flagged that outdoor seafront time should be planned for flexible slots, with museum and gallery visits kept in reserve for rainy afternoons.
The team also used the calendar to size stays properly. Clients often asked how long they needed in the city, and the answer depended on what the dates allowed. A helpful reference for that conversation was a plain look at how many days Chennai deserves, which the desk shared whenever a client was unsure.
A rainy test of the system
In November, the northeast monsoon delivered a few days of heavy rain, and a group of six was due to arrive. Under the old way of working, the desk would have learned about the weather on the morning of arrival. Now the calendar had already marked the season, and the itinerary built in October carried a quiet alternative: indoor attractions pencilled in for the likeliest wet days, a flexible beach morning and a note to confirm road conditions before each outing. When the rain came, the team moved two items by a day, called the hotel to arrange a late check-in, and told the family the plan had been adjusted in advance. The clients saw a calm response; the team saw the calendar paying for itself.
A wider habit
Kavitha noticed something about her own personal finances at the same time. Her tax and renewal dates were scattered across emails. She came across the learning site Stocks Mantra, whose resources include a page of important dates for investors, and it struck her that every field with recurring deadlines eventually publishes a list. She did not take advice from it; she took the idea, and moved her own personal deadlines into the same calendar as the desk’s work dates, each with a lead reminder.
What changed in the numbers that matter to a small desk
The team did not measure it scientifically, and we would not claim a precise figure. But the observable changes were clear. Peak-season bookings were made earlier and with more choice. Last-minute rebooking calls dropped. Clients received itineraries with fixed dates, alternative options for rainy days and a short note on timings that were worth reconfirming. Staff stayed late far less often during festival weeks, and the Monday review meeting became shorter because nothing was on fire.
How the desk keeps the calendar alive
Arun owns the calendar, and Kavitha is his deputy, so the document never depends on a single person’s attendance. Each Monday the team opens it together and runs through the next six weeks. Any entry marked “expected” gets a quick verification attempt, and any new date that a client mentions, from a family function to a school break, is added on the spot. Once a quarter they look at the next twelve months and ask whether any stretch is overloaded with dates. When one is, they bring forward some of the preparation so that the busy weeks are not also the weeks of last-minute booking.
Lessons the team wrote on the office wall
- If it recurs, it belongs on the calendar.
- No source, no confirmed status.
- Remind at the start of the slowest task, not at the deadline.
- Review the calendar every Monday for ten minutes.
- After every trip, add whatever caught us out.
The ending Kavitha prefers
The following December, a similar family arrived for the same winter week. This time the rooms had been held since autumn, the concert seats were booked in the order the family preferred, and a spare morning had been set aside in case the weather turned. Kavitha spent the week answering questions about filter coffee and the best time to see the beach, rather than apologising. Visitors who want a flavour of what the desk recommends can browse a roundup of enjoyable things to do around Chennai.
The calendar did not make the city quieter or the rain lighter. It simply meant that the predictable parts of the job stopped masquerading as emergencies, which is the whole point of keeping one.
