What a surveyor actually asks for when they look at your equipment records

Facilities rarely fail an equipment review because the work was not done. They fail because the record cannot prove it was.

That distinction is worth sitting with. A technician can service a pump correctly, and if the work order says "PM completed, device passed," the facility has almost nothing. There is no evidence of what was checked, against what specification, using what test equipment, or how far the device had drifted before it was adjusted.

Here is what gets asked for, and what a record needs to contain to survive it.

The first request is always the inventory

Before anyone looks at a single work order, they want the list of devices.

This is where most facilities lose the thread immediately. The list is out of date, or it lives in three places that disagree, or it was built once and never maintained. Pumps get borrowed between suites and never returned on paper. A loaner arrives during a repair and quietly stays. Something bought eighteen months ago went straight into service and onto nobody's list.

Every device that is not on the list is a device with no maintenance history, and it will be found. Reviewers walk the building. They open cabinets.

A usable inventory carries, for each device: make, model, serial number, current location, ownership status (owned, leased, loaned), risk classification, and the assigned maintenance interval. If your list has make and model but no serials, you cannot tie a work order to a specific device, which means you cannot prove anything about any individual asset.

Then they want to see the interval justified

Not "we do it annually." Why annually.

The defensible answer traces back to the manufacturer's recommendation, adjusted for how the device is used and what happens if it fails. That reasoning should be written down somewhere, once, per model or per device class. It does not need to be long. It needs to exist.

The weak answer, and the common one, is that the interval was inherited. Somebody set it years ago, nobody recorded why, and it has propagated across every model in the building regardless of how any of them are actually used.

If you have deviated from the manufacturer's recommended interval, that is allowed, and it is also the thing most likely to be questioned. Have the rationale ready.

Then the work orders

Pick a device, pull its records. This is the core of the review.

A complete work order carries:

• The device identifier, matching the inventory. Serial number, not just "infusion pump, Room 4."
• Date of service, and who performed it.
• What was done, in enough detail to know which procedure was followed.
• The test equipment referenced, ideally with its own calibration status.
• As-found values. What the device measured before anyone touched it.
• As-left values. What it measured when the technician finished.
• Parts replaced, with an indication of whether they were OEM, tested pre-owned, or third-party equivalent.
• The disposition. In service, out of service, removed from the fleet.

As-found is the field that separates a real program from a paperwork exercise, and it is the one most often blank. As-left proves the device is correct today. As-found proves the device was checked at all, shows how far it had drifted, and is the only data that lets you argue your interval is right. Without it, "passed" is an assertion.

The gaps that come up most

A few patterns recur.

Records assembled retroactively. Fifteen work orders all created within the same week, covering twelve months of supposed activity, formatted identically. It reads exactly like what it is.

Completion with no measurements. Every line says "passed." No numbers anywhere. This invites the follow-up question you least want, which is whether the work happened.

Overdue with no documented decision. A device is past its interval. That happens; facilities are busy. What is damning is no record acknowledging it and no risk decision about continuing to use it. An overdue device with a written, dated deferral rationale is a managed program. An overdue device with silence is not.

Test equipment with no calibration status. If you verified a pump with an analyzer, the analyzer's own calibration is fair game. Untraceable test equipment undermines every measurement taken with it.

Contractor work that never reached your files. An outside technician serviced the device, kept the record in their system, and nobody imported it. From the facility's side, the service does not exist. Ask for records in a format you can actually file, and check that they arrive.

Where an outside service provider fits

If you use an independent organization or an OEM for some or all of this, the records are still yours to hold. The provider's job is to hand you documentation you can drop straight into your own system without retyping it.

Reasonable things to require of anyone servicing your equipment:

1. A consistent work-order format, every visit, no exceptions.
2. As-found and as-left values recorded as a matter of course, not on request.
3. Explicit disclosure when a part is not OEM, before it is ordered.
4. A written statement of scope. Servicing that returns a device to its original specification is a different regulatory posture than modifying it, and your records should be unambiguous about which happened.
5. Delivery in whatever format your CMMS ingests. If a provider cannot tell you what their output looks like, assume you will be retyping it.

The uncomfortable but useful summary

If you want to know how your program would hold up, do this: pick three devices at random, walk to them, read the serials off the labels, and find every record for each one from the last two years.

If that takes ten minutes, you are fine. If it takes an afternoon, or if one of the three is not on the list at all, you have your answer, and you have it on your own timetable rather than someone else's.