Run every nurse, every day, on one system

Either. It deploys to a dedicated cloud tenancy, to a server in your own office, or to cloud infrastructure you own and control. Because it is built on an open framework rather than a closed product, the database is yours in every case — you can take a full backup at any time and move it elsewhere.

You do, and you can prove it. The system runs on an open-source core with a standard MariaDB database. There is no proprietary format holding your records hostage and no export request to raise with us. If you decide to leave, you leave with everything.

A great deal. Fields, forms, workflows, print layouts, approval steps and reports are configuration rather than code. Where you need genuine new logic — a rate rule nobody else has, an integration with a system specific to you — that is development work on the same platform, not a plugin fighting the product.

The platform supports Arabic including right-to-left layout, and print formats such as contracts, invoices and payslips can be produced bilingually. We set the document set up during implementation rather than shipping a fixed template.

It is a server-based system, so a branch with no connection cannot record transactions at that moment. To be straight about it: there is no offline mode that queues work locally and syncs later. Attendance and allocations are normally corrected the same day, and the automatic marking from confirmed allocations means the default state is already right — but if you operate somewhere with genuinely unreliable connectivity, raise it with us early so we scope it properly.

Spreadsheets are the normal starting point and they migrate reasonably well, because the data you need is usually already there: nurses, customers, services, rates and the current roster. We take masters and open commitments across, start with one branch as a pilot, and run the first month closely. Historic detail beyond opening positions is rarely worth migrating — most operators keep the old workbooks for reference and start clean.

Not from the software. There is no per-user licence fee, so putting every supervisor, coordinator and accountant on the system does not change what it costs. Practical limits come from server sizing, which we scale to your headcount and transaction volume.

No — it installs onto it. CareOps is built as an application on the same Frappe and ERPNext foundation, so your existing customers, items, accounts and employees stay where they are and the nursing operation is added on top. You keep one database, one login and one set of books.

That is the honest trade-off to discuss early. The value here comes from the roster, the invoice and the payroll being the same records, so running the accounts elsewhere reintroduces the reconciliation this is meant to remove. Some operators move accounting across as part of the project; others integrate and accept the seam. We will tell you which we think fits rather than pretend both are equal.

That is the risk worth taking seriously, and it is why the daily board and the booking console exist as purpose-built screens rather than generic forms. Supervisors work on one board rather than hunting through menus. Staff get a phone app for attendance, leave and payslips, which removes most of the reasons they would otherwise call the office.

Role by role, on your own configured system rather than a generic demo — coordinators on booking and allocation, supervisors on the daily board and dispatch, HR and finance on payroll, compliance and invoicing. Staff get the mobile app, which needs almost no training because it does five things.

An annual maintenance arrangement covering support, version upgrades, refresher training as your team changes and performance tuning as your data grows — the same arrangement as the rest of our ERPNext work. The people who configured your system are the ones who answer.