The admin behind your clinic, out of spreadsheets and into one system
If your practice tracks equipment checks on paper, staff certifications in a spreadsheet and purchase requests by email, I build one system for that admin. Checks are done on a phone, incidents get an owner, and you get a reminder before a certification expires. Patient records stay in your clinical system.
Built on the Microsoft 365 you already pay for.
Does this sound like your practice?
- Equipment checks are ticked on a paper sheet on the wall, and nobody looks at last month's.
- Staff certifications and training dates live in one person's spreadsheet, and an expiry gets noticed after the fact.
- Incidents and near misses are reported by email, then nobody's sure who followed up.
- Purchase and leave requests wait in an inbox while the person asking chases.
- Each branch does all of this its own way, so the owner can't see across them.
What changes once it's in place?
Equipment checks on a phone
Staff run the daily or weekly check on a phone and submit it, with a photo where it helps. Missed checks show up, so they don't stay missed.
Reminders before certifications expire
Who is certified for what, and until when, is kept in one place, with a reminder ahead of the expiry date. I built the same reminder pattern for an industrial safety team.
Incidents with an owner
An incident or near miss is reported once, goes to the person responsible, and escalates if nobody picks it up.
Approvals that don't stall
Purchase and leave requests go to the right approver, who gets a reminder if it sits too long. The person asking can see where it is.
How does a project run?
01
A 30-minute call
You tell me how this admin runs in your practice today. You get a straight answer on whether this is worth building, including when it isn't.
02
A fixed scope and price, in writing
What gets built, in what order, and what I need from your side. You see the total before any work starts.
03
One process first
Your team uses a working version early, usually one check or one request type at one branch, and tells me what gets in the way. I fix that before it goes wider.
04
Rollout and handover
The rest of your processes and branches come on board. Whoever looks after it day to day gets handover notes and a walkthrough.
What does it cost?
Approvals are the easiest place to start. Sign-off for one request type, such as purchase or leave requests, is a fixed price from $1,800 and goes live in two to three weeks.
Checks, incident reporting and certification tracking depend on how many forms and branches they cover, so I quote them after the first call. The price is agreed in writing before work starts.
Related work
I've built apps for clinics, but those projects aren't written up publicly. The closest published work is the incident reporting and certification reminders I built for an industrial operator in the Gulf, plus the approval pattern I use everywhere.
Illustrative UI concept - not an actual client screenshot.
Common questions
Does this touch patient records?
No. This is for the admin around your clinic: equipment, incidents, staff and approvals. Patient records stay in your clinical system. If a process ever needs patient details, we decide together on the first call whether it belongs in this system at all.
Where is our data kept?
In your own Microsoft 365 environment, alongside your email and files, with access set by role. It's built there and stays there.
Do I need an IT team to run it?
No. I build and set it up, then hand over notes and a walkthrough. Where it makes sense, your practice manager can add a checklist question or a new branch without calling me.
How long does it take?
An approval process goes live in two to three weeks. Checks and incident reporting take longer, depending on the number of forms and branches, and you get the timeline with the fixed price.
Will we need to buy new software?
Usually not much. If your company already pays for Microsoft 365, that's the base it sits on. Some features need an extra Microsoft licence for the people who use them, and I tell you which, and why, before you commit to anything.
Do you work with clinics in the UK and the Gulf?
Yes. I'm based in Amman, which is on UTC+3 all year, so my working day covers the UK working day and the Gulf's. Projects are delivered remotely, with short written updates as the work goes.
Last updated
Tell me which admin is eating your week
30 minutes, no cost, no pitch. If an app isn't the answer, I'll say so on the call.
Or reach me directly at asem@asemalabtah.com

