Dental Equipment Maintenance Log: Service Dates and AI Reminders

Keep one spreadsheet with a row for each item: serial number, supplier, purchase date, warranty end, service interval, last service and next due. Formulas flag overdue items and calendar events remind the right person. AI earns its place by turning invoices and service reports into rows and writing a weekly summary of what is due.

The reminders themselves should not depend on a chat tool. A formula and a calendar event fire every time. AI is the clerk who does the dull typing and the proofreader who spots the odd date, and in a practice with forty or so items that is where the hours go.

Follow me on Instagram@sagnikteaches

What belongs on the register

Start with a walk round the building and list everything that has a service interval, a warranty or a legal or insurer requirement attached. For a typical practice that includes:

Connect on LinkedInSagnik Bhattacharya

Some of these checks are required by law or by your regulator, others by the manufacturer or the warranty, and the strictest source decides your interval. This tutorial does not give intervals, because they vary by device and by rule. Copy them from the manual and your current guidance, and write the source in a notes column.

Subscribe on YouTube@sagnikteaches

The sheet: columns that do the work

Use one tab for the register and one for a log of service visits. Register columns:

1. Asset ID (your own: "STER-01")
2. Item and model
3. Serial number
4. Location (surgery 2, decontamination room)
5. Supplier or maker, and service company
6. Purchase or install date
7. Warranty end date, plus a note of the conditions
8. Service interval in months, plus its source
9. Last service date
10. Next due (formula)
11. Status (formula)
12. Link to the latest service report
13. Owner (a role, such as Practice Manager, not a person)

Three formulas make it self-checking. If the last service is in column I, the interval in months in column H, and the warranty end in column G:

Next due:   =EDATE(I2,H2)
Service:    =IF(J2<TODAY(),"OVERDUE",IF(J2-TODAY()<=60,"DUE SOON","OK"))
Warranty:   =IF(G2="","",IF(G2<TODAY(),"EXPIRED",IF(G2-TODAY()<=90,"EXPIRES SOON","IN WARRANTY")))

Add conditional formatting: red for OVERDUE and EXPIRED, amber for DUE SOON and EXPIRES SOON. Sort or filter by status on Monday morning. If formulas are unfamiliar, the Google Sheets AI prompts tutorial shows how to ask an assistant to write and explain one, which you then test on a row you can check by hand.

Calendar reminders that reach a person

Colours in a sheet need someone to open it. A calendar event reaches people who never will. For each item, create reminders at the lead times you need, such as 60, 30 and 7 days before the next due date, addressed to a role mailbox or shared calendar rather than an individual who might leave. Google Calendar's help page says only two CSV columns, Subject and Start Date, are required, with the headers in English, and that repeating events imported from a CSV may arrive as a series of one-time events, so do not rely on a recurrence column. Its example date is written month first (05/30/2020). Test with two rows before importing the lot, and check that each lands on the right day.

When a service is done, update "last service", and replace the next set of reminders. This is the step most registers miss: the date moves, the old reminders do not. A tidy way is to keep calendar events only for the next 12 months, and rebuild the import file each January from the register.

Chat assistants with scheduled tasks can also send you a weekly digest, but plans cap them. ChatGPT's help centre, as of November 2026, lists 3 active tasks on Free and Go, 5 on Plus, 10 on Business and 15 on Pro, and says Free tasks run at most once a day in a flexible window such as morning rather than at an exact time. Caps change, so treat a digest like that as a supplement. A formula and a calendar event are plain, free and hard to break.

Turning an invoice into a log row

This is the dull job where AI is genuinely good. Suppose a service company emails a PDF after the annual compressor service. Open it, copy the text or attach the file, and use this prompt with a business account (training off):

Extract a register row from this service invoice or report.
Return a table with: asset, model, serial number, service date,
what was done, parts replaced, engineer's recommendations,
next service recommended by the engineer (as written),
and total cost. Use ISO dates (YYYY-MM-DD). If a field is not in
the document write "not stated". Do not infer anything.
Document: [paste text]

An illustrative output for a made-up invoice reads: asset "Compressor, two-surgery oil-free unit", serial from the plate, service date 2026-10-14, work "filter replaced, drain cleared, pressure test", parts "intake filter", recommendation "replace dryer cartridge within 6 months", next service "not stated", cost $410. What you check and fix:

• Dates. "03/04/26" is 3 April in some places and 4 March in others. The invoice's own layout and the supplier's habits settle it; ask the tool to quote the original text beside the converted date for anything ambiguous.
• Serial numbers. Letters and digits get swapped (O and 0). Compare against the plate on the machine at least once.
• Invented intervals. If the tool writes "next service 2027-10-14" where the document says nothing, that is a guess. Your interval comes from the manual and the register, not the invoice.
• Totals. It sometimes picks up the subtotal. Compare with the amount you paid.

Paste the row into the log tab, update "last service" in the register, file the PDF under a consistent name such as 2026-10-14_COMP-01_service_[supplier].pdf and paste the link into the register. The next engineer, or an inspector, finds the report in one click.

Main worked example: building the register in an afternoon

An illustrative four-surgery practice has 38 items worth registering. The practice manager opens the surgeries one at a time with a tablet, photographs each serial plate (equipment plates, with no patients or records in view), and types asset ID, location and serial. That takes about 90 minutes. She then gathers the last two years of supplier invoices and service reports, nine documents in all, and has an assistant extract the rows. Twenty-five minutes later the register has dates and costs for 29 of the 38 items. The nine without paperwork go on a "chase" list.

The formulas now show something she could not see before:

• Three items are OVERDUE, including the second steriliser, last serviced 15 months ago against a 12-month interval from its manual.
• Two items are DUE SOON within 60 days.
• One warranty, on the main compressor, ends in 6 weeks, and the notes say it covers parts and labour if serviced by the maker's approved engineer.

The compressor has been making a new noise. With the warranty flag showing, she books the approved engineer now. Suppose a fault is found and the repair would have cost $1,400 out of warranty; a claim made before the end date costs nothing. That figure is an illustration, but the shape is the point: warranty dates are worth money only while they are known. The overdue steriliser service is booked for the same week, and the three overdue items become the first agenda point at the next huddle, which the daily brief tutorial shows how to automate.

Reading a warranty document properly

Warranty dates alone are not enough. The conditions decide whether a claim works. Attach each warranty PDF and ask the assistant for five fields: start date and what triggers it (purchase or installation), end date, what is covered (parts, labour, call-out), conditions (who must service it, how often, whether a log is needed), and how to claim. Treat the answer as a draft and read the document for the conditions, because a misread condition can cost more than the typing saved.

A common trap is the start date. A warranty that starts at installation and was installed three months after purchase ends later than the purchase date suggests, and the other way round. Put both dates in the register and note which one the warranty uses.

Another trap is the link between servicing and cover. If the warranty needs a service by an approved engineer every 12 months, a missed service can end the cover early. So the register row carries both flags, and when the status says DUE SOON for service, it is also a warranty reminder.

A weekly digest for the practice manager

Each Monday, filter the register to rows that are OVERDUE, DUE SOON or EXPIRES SOON, copy the visible rows (no patient data is involved) and use:

Write a short weekly message to the practice manager from this table.
Group by urgency: overdue, due within 60 days, warranties ending
within 90 days. For each item give asset ID, what is due, the date,
and the service company. Keep it under 150 words. Do not add items
that are not in the table.
[paste rows]

The result is a tidy list that goes into the huddle or email. It might save ten minutes a week, which is not much, but it also gets read, because it is short and specific. For the wider question of which admin jobs a dental practice can safely hand to AI, see admin jobs that need no patient data.

Three more rows, three different traps

The emergency kit, where the dates are many and small

A defibrillator is one asset with several expiry dates: battery, pads, sometimes the unit's own service. An oxygen cylinder has a content check and a test date. The emergency drug box has a dozen items with different expiries. Do not squeeze these into one cell. Give the kit its own small tab, one row per expiring item, with the same status formula, and add a monthly "checked by, date" column. An illustration:

Two rows are amber and the practice manager has the replacement ordered before they turn red. That is the whole benefit of the tab, and an assistant can build the first version quickly if you paste the kit list your guidance requires.

A support contract nobody remembered

Digital kit has renewal dates that behave like warranties. The scanner's support contract, the practice server's licence and the cloud backup subscription lapse without a bang, and then something stops working on a busy Tuesday. Add them to the register with the renewal date in the warranty column and the vendor's support number in the notes. The annual cost of one unnoticed lapse is easy to imagine; the cost of a row in a sheet is nothing.

The invoice that is really an email chain

Not every service record is a tidy PDF. Sometimes it is a forwarded email: "Hi, we serviced the unit in surgery 2 on the 14th, replaced the filter, we'll be back in the spring, invoice to follow." Before: unstructured, no serial, "the 14th" with no month, "spring" for the next visit. Give it to the assistant with the register tab open and ask which asset it most likely refers to, listing what is missing. The sensible reply is a row with service date "14th (month not stated; email dated 2026-10-15, so likely October)" and next visit "spring (not a date)". You then confirm with the engineer. The AI cannot know the missing parts, but it spots them and writes the clarifying question for you.

Who does what, so the log survives holidays

A register works when roles are clear and boring. A sensible split for a small practice:

• Practice manager: owns the register, runs the Monday filter, books engineers, files reports.
• Lead nurse or decontamination lead: owns the decontamination and emergency-kit rows, and signs the monthly check.
• Principal dentist or owner: approves replacement spending and any change of service company.
• Deputy (named): covers the manager's holidays. The Monday digest goes to both.

Put these roles in the owner column and the calendar invites, and write a one-paragraph procedure in the policy manual. When an inspector or insurer asks to see the service history of the steriliser, you filter the register by asset ID, open the linked reports and answer in a minute, which is a very different afternoon from hunting through emails.

A quick sum: what the register costs and saves

The build is roughly three to four hours for a practice of this size, as in the example above, and about 15 minutes a week afterwards: filter, read the digest, book what is due, update rows after visits. At an illustrative $30 an hour of the manager's time, the first month costs about $150 in time and each month after about $30. Against that, put one avoided out-of-warranty repair, one avoided week of a surgery out of action because a service was booked in advance, and the hours saved when someone asks for service history. You do not need exact figures to see which side is heavier, but if you want to be careful, tally the avoided costs in the log tab as they happen so the next review has real numbers instead of impressions.

How registers go stale, and the fixes

• New kit never enters the register. Add a step to your purchase process: nothing is paid until it has a register row. Consumables and small stock are a different system; see the consumables stock ordering tutorial.
• Moved or sold equipment. If a unit moves from surgery 1 to surgery 3, update the location, or the service engineer arrives and cannot find it.
• Reminders addressed to a person. When that person leaves, the reminders go nowhere. Use a role mailbox.
• Interval copied from the wrong source. Two manuals, one older. Record the source and the date you checked it.
• Edited by many hands. Give edit rights to two people and view rights to the rest, and keep the version history on.

Using the log to decide when to replace

Once you have repair costs in the log tab, the register can show a running total per asset. Add a column for cumulative repair spend and one for age in years. A rule such as "review for replacement when yearly repair spend passes half the replacement price" is only an example; your accountant or supplier may suggest a different test. The point is that you set the rule in advance and the sheet raises the flag, instead of arguing about a failing machine on the day it fails. Your policies and procedures manual is a good home for the rule once you have set it.

Checking the system works

Ten minutes a month: sort by status, confirm nothing is OVERDUE without an explanation, check that the last three service reports are filed and linked, and spot-check one row against the machine's plate. Once a year, walk the building again with the register and add anything missing. A practice that does this rarely discovers a lapsed warranty by accident.

If you would like the register, calendar import and Monday digest set up for your own equipment, that is the sort of job an AI implementation consultation covers.

Intervals, repairs and approvals stay human

Choosing intervals from the right documents, deciding whether a failing item is repaired or replaced, and making sure the engineer who attends is approved. AI types and summarises, and the sheet reminds. The decisions about patient safety and cost are the practice's.

Equipment log questions from practice managers

Can AI actually send the service reminders?

It can help, but the dependable reminders come from the sheet's formulas and calendar events, which fire whether or not anyone opens a chat. Use AI to turn invoices into rows and to write a weekly summary of what is due. Chat tools with scheduled tasks can send that summary, though plans cap how many tasks run.

Is it safe to give AI an equipment invoice?

Usually, because invoices carry supplier, item, serial number, date and price, not patient data. Still check the document first: remove bank details, and never include a patient record, a referral or a treatment note in the same file. Use a business account with training switched off.

How often should each item be serviced?

The manufacturer's manual and your regulator's or insurer's requirements decide, and they differ by item and model. Copy the interval from those documents into the sheet, note the source, and ask the supplier if it is unclear. Do not take an interval from an AI tool's memory.

What if the warranty needs servicing by an approved engineer?

Record that condition next to the warranty dates. Some warranties lapse if servicing is missed or done by someone not approved, so the service reminder and the warranty flag should sit in the same row and be treated as linked.

Further reads

• How to Use AI in a Dental Clinic: A Four-Week Starting Plan — A wider plan for adding AI to a dental clinic step by step.
• Dental Complaints Procedure: A Template and AI-Drafted Replies — Another log-based routine that protects the practice.
• Dental Practice Valuation Explained: Prepare Your Figures With AI — A tidy asset register helps when the practice is valued.
• Which Dental Front Desk Tasks Can AI Take Over? — Which front desk tasks AI can take, including reminders.
• Dental Lab Case Tracking Template and AI Status Updates — Another tracking sheet with AI status updates, for lab cases.
• GDPR in a Dental Practice: Which AI Tools Staff May Use — Rules for which AI tools staff may use and what they can paste.
• Can AI Build a Gym Equipment Maintenance Checklist From Manuals? — How to turn gym equipment manuals into a checked maintenance checklist, a service calendar and a fault log with AI, and which jobs stay with qualified people.
• Dental Lab Quality Control Checklist and Remake Log With AI — Stage checklists for crowns, dentures and implant work, a remake log with cause codes, and a monthly AI prompt that finds repeat causes.
• Dental Practice Policies and Procedures: Section List and AI Prompts — A section list for a dental policies and procedures manual, prompts that draft from your own routines, and the review steps that keep it safe.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Google Sheets (EDATE, TODAY, conditional formatting) and Google Calendar CSV import help pages; OpenAI help-centre article on tasks in ChatGPT (active-task limits, checked November 2026); the manufacturer manuals, warranty documents and your own regulator's and insurer's guidance for service intervals, which should be checked per item.