Skip to content

Clinic Equipment Checks and Maintenance on Microsoft 365, Without the Spreadsheet

Equipment checks on a clipboard and service dates in a spreadsheet work until an inspector asks for last month's records. Here is how a clinic runs them on the Microsoft 365 it already pays for.

| 5 min read

A patient monitor on a wheeled stand, a phone showing a completed checklist, and a calendar with a ringing bell

A clinic can run its equipment checks and maintenance on Microsoft 365 with three parts: a register of every device, a Power Apps checklist staff complete on a phone, and Power Automate flows that report faults to the right person and send a reminder before a service or calibration date passes. Patient records stay in the clinical system. This covers the admin around them.

The usual setup is a printed checklist on a clipboard, a spreadsheet of service dates kept by the practice manager, and faults reported by whoever happens to be nearby. It works on a quiet week. It falls apart when a device fails a check on a Friday evening, or when someone asks to see six months of records.

What does a clinic need from an equipment system?

Four things. A list of every device with its location and service dates, a quick daily or weekly check that staff can finish in a minute, a way to report a fault so it reaches an owner, and a record you can show an inspector without rebuilding it from paper. If a feature does not serve one of those, leave it for later.

Need What it looks like in practice
Register Every device, its room, serial number, supplier and next service date
Routine checks A short checklist on a phone, stamped with who did it and when
Fault reporting A failed check opens a fault with one owner, not an email to everyone
Records Every check and fault kept against the device, searchable by date

How should the equipment register be structured?

Three lists, kept separate. A Devices list with one row per item, a Checks list with one row each time someone completes a check, and a Faults list for anything that fails. Separating them is what lets you pull up the full history of one autoclave or one defibrillator in seconds instead of searching a spreadsheet.

For most single-site and small multi-site clinics, SharePoint lists are enough and come with Microsoft 365. If you have many sites, or contractors who should see only their own jobs, Dataverse handles that better. The trade-offs are in Dataverse vs SharePoint Lists.

Keep the checklist questions as data too. When a new device type needs a different check, that should be a new row, not a change to the app.

What does the daily check look like for staff?

Open the app, pick the room or scan the label on the device, answer a few yes or no questions, and submit. A photo is optional for a pass and required for a fail. The whole thing should take less time than finding the clipboard.

Staff do not type device names. They pick from the register, because "Steriliser 2", "steriliser two" and "the big autoclave" are three different devices to any report you run later.

If a room has poor signal, the app can be built to work offline in the Power Apps mobile app, with some conditions that are set out in How to Build an Inspection App in Power Apps.

What happens when a check fails?

A flow opens a fault, assigns it to the person responsible for that device type, and tells them by email or Teams. If nobody picks it up within the time you agree, it goes to the practice manager. The device can be marked out of service in the register at the same moment, so the next person who opens the app sees it.

This is the part clinics usually get most value from. A failed check stops being a note on a clipboard that someone may or may not read.

How do service and calibration reminders work?

A scheduled flow runs every morning, finds devices whose next service date is coming up, and emails the owner or the supplier contact. How far ahead it warns you is your choice: two weeks is common for routine servicing, longer if the supplier needs notice. When the service is done, someone updates the date and the reminder moves forward on its own.

The same flow can produce a weekly summary for the practice manager: what was checked, what failed, and what is overdue.

What licences does this need?

On SharePoint lists with standard connectors such as Outlook, Teams and Approvals, the app is classed by Microsoft as a Standard app, which staff can run under most Microsoft 365 business plans. Moving the data to Dataverse makes it Premium, and each user then needs a Power Apps licence. Microsoft explains the difference on its page about app license designation (checked November 2026).

Frequently asked questions

Does this replace our clinical or patient management system? No. Patient records stay where they are. This handles the admin around the clinic: equipment, faults, servicing, and the records you show an inspector.

Can staff use their own phones? Yes, through the Power Apps mobile app and their Microsoft 365 sign-in. Nothing is stored on the phone once a check is submitted, and access ends when the account is disabled.

Can we see the history of one device? Yes. Because checks and faults are linked to the device, its full record is one screen in the app or one filtered view in the list.

How long does it take to set up? A first version with the register, one checklist and fault reporting is usually a matter of weeks, not months. The time goes into agreeing the checklist and who owns which device, not into the build.

Getting it set up for your clinic

I've built apps like this for clinics, and the clinics and healthcare practices page shows the wider picture: equipment, incidents, certifications and approvals in one place. If you want to talk through how your checks run today, book a 30-minute call.

Last updated

Working through this on a real project?

30 minutes, no cost, no pitch. Describe what you are building and I’ll tell you what I would do.