On-call rota
Each doula sees who is on call and when, and changes reach the whole team at once.
A staff operations app for doula practices puts on-call rotas, backup coverage, client handover notes and birth kit checklists on each doula's phone, so a backup can step in without starting from zero. SIZ Group designs the iOS and Android builds around how small practices really cover births, with privacy controls on every client file.
Doula practices are small, and their work is unpredictable by nature. A doula can be at one birth when a second family goes into labor, and a backup may have only a few hours' notice. The client's trust depends on the backup knowing the birth plan, the partner's name and the visit history, which often sit in one doula's head or in a folder only she can open.
Generic business tools do not solve that. A shared calendar shows who is busy but not what a backup needs to know. The staff app has to carry the handover, so that when a backup is called, the first thing she sees is the client's essentials and what has already been agreed, rather than a long call to the primary doula at an hour when she should be resting.
Families choosing a doula compare the team as well as the person: whether there is a backup, what happens if their doula is at another birth and how notes are kept. Those answers matter as much as the package price. Some families ask specifically about a team approach, while others rely on a midwife or hospital contact to point them to a doula with a dependable backup.
For the operations manager, the staff app becomes part of that answer. It can show that a backup is named for every due date, that handover notes exist and that the rota is clear. The practice should promise only what the rota and the notes can actually deliver.
Most doula practices run on a calendar, a contract tool and a shared drive for client paperwork. Common choices include Google Workspace or Microsoft 365 for calendars and documents, Dubsado or HoneyBook for contracts and invoices, and Stripe for card payments. The staff app should link to those tools rather than keep its own copy of a contract or payment history.
Client health and birth details belong in a secure, access-controlled system, not in a shared document. If the practice wants the app to read its rota from a calendar, a read-only connection is usually enough for the first release. Writing into client files is scoped separately, once the team has settled its record rules.
Each doula sees who is on call and when, and changes reach the whole team at once.
Birth plan essentials, partner details and visit history are ready for the backup before she is called.
Every family's due window appears on one screen, with the primary doula and backup named beneath.
Kit items are checked and restocked against set levels, with a note of who restocked them and when.
Travel to births and visits is logged with the route, so mileage claims match the work actually done.
Doulas record arrival and departure times at each client visit, and those times feed the timesheet.
Doula practices handle sensitive information about pregnancy, birth and newborns, and families expect it to be treated with care. HIPAA applies to covered entities and their business associates, so whether it governs your practice depends on who pays for the work and which hospitals or insurers you work with. Some states have their own rules for doula services, and the compliance advisor should confirm what applies before the build starts.
The app should also protect the team. A doula's phone may hold the only copy of a client's number, so the app should lock quickly, clear data at sign-out and keep a client's name off the lock screen. Backup access should end when a rota ends, and a doula who leaves the practice should lose access the same day.
Births follow their own calendar, so a doula practice can see several due dates bunch together in one month and then go quiet. Holidays, summer heat and early winter all shift timing, and some births arrive early or late enough to clash with a planned vacation. A fixed rota gets stretched during the busy weeks and sits idle in the quiet ones.
The app should let the operations manager plan for those swings. A due-date view can show every family's window at once, with the named backup beneath each one. The manager can spot a conflict early, such as a planned vacation falling inside a due-date window, and adjust the rota before the weeks get crowded.
The practice needs to supply its list of doulas and backups with availability, the due-date window for each client and the rota rules it works to, such as how far ahead a backup must be named. It also needs the birth kit checklist, the supply levels for each item and the mileage rules for travel to births and visits.
Access needs clear edges. Each doula should see the clients she is assigned to and the handover notes for her backups, and nobody should see clients they do not cover. The operations manager sees the rota and supplies, and the owner sees billing. Any note that includes health information should be reviewed with the compliance advisor before the team starts using it.
Yes, if the handover is current. The backup sees the essentials, the birth plan summary and the last visit notes before she is called. The app will not replace a conversation between the two doulas, but it removes the scramble for basic facts.
The app is never the emergency channel. Calls and texts to the on-call number remain the route for urgent needs. The rota shows who is next, and the app can alert that person once the primary doula has been unavailable for a set period.
Client files are visible only to the doula assigned to the client and to backups during the periods they are on the rota. Access ends automatically when the rota changes, and the owner can review the access log at any time.
Most practices can move supplies into the app. Each item has a reorder level, and anything that falls below it is flagged. If a supplier needs a spreadsheet, the app can export one each week, so purchasing does not have to change overnight.
Mobile apps start at $4,500. Cost follows the rota features, the number of team members and the systems the app connects to. The written scope sets out each part before any build, so the practice can choose its first release.
Book a free scoping call and get the rota and handover scope in writing.