News

From Paper Files to Digital Records: 7 Steps for Bhutanese Offices

Many Bhutanese offices, schools and businesses still run important work on paper: leave forms, stock registers, applications, receipts and client files kept in folders and cupboards. Paper works until someone needs a record quickly, a file goes missing, or two branches need the same information on the same day. Moving to digital records does not have to mean replacing everything at once. A careful, step-by-step approach keeps daily work running while the new system takes shape.

1. Start with one process, not the whole office

Pick a single process that causes the most delay or repeated effort, such as leave requests, purchase approvals or customer enquiries. Map how it works today: who fills in the form, who checks it, who signs it and where it is filed. A short, honest map shows where time is lost and what the digital version really needs to do.

2. Decide what information you actually need

Old forms often carry fields nobody uses any more. Before building anything, agree on the information that must be captured, which fields are required, and who is allowed to see or change each record. This keeps the new system simple for staff and avoids collecting personal details you do not need.

3. Choose between scanning, re-entering, or starting fresh

Not every old file needs the same treatment. Some records only need to be scanned and stored so they can be found later. Others, such as active client or stock records, are more useful when their details are entered into a proper database so they can be searched and reported on. For very old archives, it may be enough to start fresh from a set date and keep the paper files for reference.

4. Plan who can access what

Digital records are easier to share, which also means they are easier to share with the wrong person. Set up user accounts with roles, so each person sees only what their job requires. Keep a record of who created or changed important entries. This is more control than most paper cupboards ever offered.

5. Back up from the first day

Once records live on a computer or server, a failed disk or a mistaken deletion can undo months of work. Arrange automatic backups before staff start relying on the system, keep at least one copy away from the main office, and test that you can actually restore a file.

6. Run paper and digital side by side for a short time

For the first few weeks, let the new system and the old paper process run together. Staff can compare results, report confusing screens and suggest small changes. Set a clear date when the paper version stops, so the transition does not drag on indefinitely.

7. Train people and keep listening

A system is only as good as the people using it every day. Give short, practical training to each group of users, write a one-page guide for common tasks, and name someone staff can ask for help. Small improvements made in the first months often decide whether a digital system is welcomed or worked around.

Where eDruk can help

eDruk Private Limited has worked in Bhutan’s software sector since 2004. We help organisations plan their move from paper, build web and mobile systems that fit the way they work, and set up the networks, backups and support that keep those systems running.

If your team is ready to turn a paper process into a digital one, talk to us. Email edruk@edruk.com.bt, call +975 2 332277, or visit www.edruk.com.bt.

News

Knowing When the Network Goes Down: A Practical Watch for Bhutanese Offices

Many offices in Bhutan only discover a network problem when someone cannot open email, print a form or join a meeting. By then, work has already stopped. You do not need a large operations centre to do better. A small, regular watch of the internet link, the office LAN and the Wi-Fi people actually use tells you something is wrong while you can still act.

When “the internet is down” is not one problem

Staff often describe every fault the same way. In practice, several different things can fail. The internet link from your provider can drop while computers in the office can still share files and print. A switch, patch cable or wall point in one room can fail while the rest of the building is fine. One Wi-Fi access point can stop, so a meeting room goes quiet while wired desks keep working. A power cut at the cabinet can take the modem, router and switches down together.

Knowing which layer failed saves time. Calling the internet provider when the switch in the cabinet has simply lost power does not help. Planning new coverage or laying new cable is a different job; this is about noticing that what you already have has stopped working.

Start with a simple picture of what you have

You cannot watch what you have not named. On one page, write down who provides the internet, where the modem, router and main switch sit, which rooms share which access points, and which services matter first — email, shared files, a records system or payment terminals. Note whether more than one building or floor depends on the same cabinet. That short picture is also what a technician will ask for when you need help.

Watch more than one place

A useful check is small and repeatable. Try the same task from more than one device and more than one room, so you can tell a single laptop problem from a wider fault. Look at the lights on the modem, router and main switch — many faults show there before anyone opens a browser. Once or twice a day, confirm that a page or service outside the office still loads. A silent failure is easy to miss if nobody happens to be online at that moment. If you have more than one site, check whether only one location is affected.

If something fails, try a wired connection as well as Wi-Fi. If the cable works and the wireless does not, look at the access point or its power supply first.

Write down what failed, and when

When the network misbehaves, a short note is more useful than a vague memory later in the day. Record the time it started, which rooms or services were affected, whether wired desks and Wi-Fi failed together, whether the power was out, and whether the service came back on its own. That record helps you see patterns — the same access point every afternoon, or a drop each time the power flickers — and it is the information a support visit needs.

Decide who should hear about it

The person who sits nearest the router is not automatically the right person to watch the network. Name someone who will do the regular check, who they tell, and what they should try before calling for outside help: confirm power at the cabinet, look at the device lights, test a wired point, and restart equipment in a sensible order if that is your agreed practice. When that person is on leave, someone else should know the same steps and where the cabinet key is kept.

Talk to us

An office can lose a shared folder, a payment terminal or a connection between two buildings without anyone shouting right away. A simple watch will not prevent every outage, but it means you find out from your own checks instead of from frustrated staff or customers.

If you would like help mapping what you already have, setting up a simple watch, or planning the network itself, eDruk can help. We have been building software, websites, mobile applications and network infrastructure in Bhutan since 2004.

Get in touch at edruk@edruk.com.bt, call +975 2 332277, or visit https://www.edruk.com.bt.

News

Custom Software or Ready-Made Tools? 7 Questions for Bhutanese Organisations

When an office in Bhutan needs a better way to track requests, manage records or serve customers online, the first choice is often “buy a ready-made tool” or “build custom software.” Both paths can work. The wrong path usually shows up later as unused licences, awkward workarounds, or a system nobody can change when a process changes.

eDruk Private Limited has been building software, websites and mobile apps in Bhutan since 2004, alongside networking and fibre work for organisations across the country. Before you commit budget or a tender, these seven questions help you decide what fits your people and processes.

1. What exact work must the system support?

Write down the daily tasks: who enters data, who approves it, who needs a report, and what happens when something is rejected or delayed. Ready-made tools are strong when your process is close to a common pattern such as invoicing, basic CRM or simple ticketing. Custom software is stronger when your rules are specific to your organisation or a workflow that must match forms and approvals you already use.

2. How much can you adapt your process?

Off-the-shelf products usually expect you to follow their way of working. If your team can adjust a few steps and still meet policy, a standard tool can be faster to launch. If the process is fixed by regulation, audit or long-standing practice, forcing staff into a mismatched product creates shadow spreadsheets and chat workarounds. Be honest about what you can change before you buy.

3. Who will use it, and on which devices?

Desk staff, field teams on phones, and occasional public users need different interfaces. Check whether a ready-made product supports the languages, forms and mobile use you need. If people must work offline, upload photos, or follow a multi-step approval that no standard product covers well, a tailored web or mobile application may be clearer.

4. What must connect to systems you already have?

List email, accounting, SMS, identity logins, payment channels or other portals the new system should talk to. Some ready-made tools offer connectors; others stop at export spreadsheets. Custom development can build the integrations you need, but only if those other systems have clear interfaces and owners. Map the connections early so the choice is not based on a demo alone.

5. Who owns the data, logins and configuration?

Keep domain names, hosting accounts, admin users and export rights in your organisation’s name. For a ready-made SaaS product, confirm how you export data and what happens if you stop the subscription. For custom software, agree where the source code and documentation live, and how another developer could maintain it later. Ownership problems are harder to fix after go-live than during procurement.

6. How will it be supported after the first month?

Ask who resets passwords, fixes bugs, applies updates and trains new staff. Vendor support hours, local partners and in-house skills all matter in Bhutan, especially when a problem appears outside Thimphu. A cheaper licence with no practical support can cost more than a clearer support plan. For custom systems, plan maintenance the same way you would for a network: updates, backups and a named contact.

7. Can you start small and grow?

Many successful projects begin with one process — applications, inventory or service requests — then expand. A ready-made tool that covers that first process well can be enough. A small custom module that matches your real workflow can also be enough. Avoid a large all-in-one build or purchase until the first version is used daily and you know what to improve.

Making the decision

There is no single right answer for every organisation. Ready-made tools suit common needs when you can adapt a little and the vendor can support you. Custom software suits distinctive processes, local integrations and long-term control — when you also plan ownership and maintenance. A short requirements note and a few demos usually make the choice clear.

If you are weighing a ready-made product against a custom web or mobile system, tell us what staff need to do each week. We can help you compare options and plan a practical first version.

Contact eDruk:
Email: edruk@edruk.com.bt
Phone: +975 2 332277
Web: https://www.edruk.com.bt