Managing Projects in Nepal: WhatsApp Groups, Festivals, Clients

Project management books are written for teams with stable internet, a Monday to Friday week and clients in the same time zone. Nepali teams work differently, and pretending otherwise leads to missed dates. Here are the local realities that most affect delivery and how to handle them, whether you run a development agency in Lalitpur, a construction firm in Pokhara or an NGO programme across several districts.

WhatsApp groups: useful, but not a system

WhatsApp and Viber groups are how Nepali teams talk, and they are not going away. The problem arises when tasks are assigned inside them. A task given at 4 pm between a meme and a lunch photo is lost by 6 pm. A practical split that works in many teams:

• Chat group: quick questions, urgent alerts, coordination on the day.
• Task board: assignments, deadlines, files, decisions and status.

The rule is simple: if work is assigned in chat, the person assigning it creates or updates the task right away, and the chat message links to it. After a few weeks, people check the board because that is where the truth is. A system such as project management software can send reminders by email so the board becomes part of the routine without replacing conversation.

Plan around the Nepali calendar

Dashain and Tihar can remove two or more weeks of effective work, as many staff travel home and shops, banks and government offices close for days. Other regular interruptions include public holidays, local festivals such as Indra Jatra or Chhath in particular regions, Saturday weekly off, elections, bandhs and strikes, and the monsoon for site work. Good habits:

1. Mark known holidays on the project calendar at kick-off.
2. Tell clients early that delivery dates skip these periods.
3. Avoid scheduling client reviews or launches immediately after long breaks.
4. Keep a small buffer before festival weeks because people leave early.

Display due dates in Bikram Sambat if your team thinks in BS, and keep the English date for overseas clients. Having both avoids the classic misunderstanding of "end of Kartik".

Working with overseas clients

Many Nepali agencies and freelancers serve clients in Australia, the UK, the US or the Gulf. Typical frictions are time zones, unclear scope and trust. A shared board helps with all three:

Friction	What helps
Time zone gap	Written updates on the task so the client reads progress at their morning, not on a late call
Scope creep	Every new request becomes a task with an estimate and an agreed date
Trust in hours billed	Time logs against specific tasks, shared in a client report
Approvals	A review stage where the client comments on the exact deliverable

If your invoices and payment collection involve foreign currency, handle that with your bank, accountant and the relevant rules; the project tool only provides the records that support your billing.

Power cuts and unstable internet

Load-shedding is much better than before in many cities, but connection drops still happen, and in district sites they are common. Choose tools that work on a mobile phone browser, keep important files accessible outside a single computer, and agree what happens when someone is offline: they update the task when back online and mention the delay. For site teams, a short end-of-day photo and note on each task is often more valuable than a long report. Mobile data is usually the backup.

Handling people and hierarchy

In many Nepali workplaces, juniors hesitate to say a deadline is unrealistic or that they are stuck. A task board makes silence visible: a card stuck in progress for five days prompts a gentle question. Managers can create a safe habit by saying that moving a task to "Waiting" with a reason is good practice, not failure. Praise early warnings. A team that reports problems on day two saves a crisis on day twenty.

Documenting decisions

Verbal agreements with clients, landlords, contractors and officials are common, and memories differ later. Record decisions as comments on the task, and confirm key ones in writing. When a team member leaves, the record of what was decided and why stays with the project. This also makes it easier to connect to other systems, for example when a project needs staff time from attendance records or a client history from your CRM.

Field teams and district projects

NGO programmes, construction sites and survey work often run across several districts with limited supervision. The manager cannot visit every site every week, so reporting discipline matters more. Agree a small, fixed daily or weekly update: a short note, a photo and a percentage or checklist for the activity. Keep forms short enough to complete on a phone with patchy signal. A manager who receives structured updates can spot a delayed site in the capital without waiting for a phone call from the field.

Language and clarity

Teams mix Nepali, English and Roman Nepali in messages. That is natural, but task titles and acceptance notes should be written clearly enough for a new colleague to understand. Use short, specific titles such as "Prepare quotation for Pokhara branch" rather than "Quotation work". Where clients are overseas, write the client-facing parts in plain English and keep internal notes in whichever language the team uses best.

Your next step

Hold a thirty-minute session with your team to agree what lives in chat and what lives on the board, and mark the next three months of holidays on your project calendar. For a tool to do this with reminders, client reports and BS dates, message WebsNP on WhatsApp at +977 9846280400.

Get a demo and quote for Project Management Software

Tell us about your business and we will reply the same working day with a demo and a clear quote. No obligation.

Chat on WhatsApp

Or call / WhatsApp +977 9846280400

Your name Phone / WhatsApp Email (optional) Business / organisation What do you need?

Request demo

More guides on Project Management Software