Senior living

Senior living vendor accountability

By the LockProof Team · Last updated August 6, 2026

Senior living vendor accountability is easiest to think about backwards — not from the vendor, but from the person who will one day ask about the vendor. A surveyor arrives, picks a system, asks for its history, and whatever you hand over is the whole case. Which part of that file is carrying it? On a normal work order, none of it: the name, the date, the result and the signature all come from one person, so a stranger has to take the file’s word for itself. The fix is narrow — put one element in there that the filer did not author.

Start at the end: the morning of the survey

Long-term care facilities are surveyed on a recurring cycle, and the process runs on the facility’s own documentation — CMS sets the framework and state agencies carry out the inspections. Assisted living is licensed by states rather than by CMS, so the specifics differ. The shape does not: somebody external asks, and the file answers.

So picture the ask. A surveyor names a system — the fire alarm panel, the sprinkler riser, the generator — and asks for its service history. You produce the work orders. At that point the conversation is no longer about whether the work happened. It is entirely about whether the paperwork is convincing.

A residential community building with lawns and mature planting
Photo: Barion McQueen / Pexels

Read your own file the way they will

Take one completed work order and ask a blunt question of each element: who made this, and could they have made it later?

The technician’s name is theirs. The date field is theirs. The pass or fail result is their assessment. The signature is theirs. If there is a photo, their phone took it and their phone dated it. Every element is true, and every element has one author.

That is not an accusation and it is not unusual — it is how field documentation works nearly everywhere. It matters in one situation, which happens to be the one a survey creates: somebody outside the building is evaluating a file produced entirely inside it.

The “Filed by the technician” entries are fine for most of a service history. The “Sealed on submission” ones are what a surveyor can weigh without taking anyone’s word for it.
On one work orderSealed on submissionFiled by the technician
Whose clock the time came fromThe server, on submissionThe person filling in the form
Where the image came fromThe live camera onlyAny file on the phone
A later editStops the fingerprint agreeingLeaves nothing behind

Year three is the real test

The gap between the work and the question is what makes this hard. Retention runs for years and varies by state and by accrediting organization, so a record routinely outlives the technician who filed it, the manager who accepted it, and any memory that might have filled a gap.

A line reading “quarterly inspections completed” is fine in month one, while somebody can still explain it. In year three it is a sentence with nothing behind it. Specificity is what survives the wait: this panel, this date, this reading.

Add one element the filer did not author

Nothing about the vendor relationship has to change. What changes is where one line of the file originates.

Run the surveyor’s four questions against a LockProof capture and see where each one lands. Was this taken here?The technician opens a texted link that goes straight to the camera, with no route to the photo roll, so last quarter’s panel shot has no way in.Was it taken then?The clock belongs to our server, stamped as the submission lands — the handset never gets a vote. Was it altered afterwards? Picture and stamp go into a single SHA-256 fingerprint, joined by coordinates whenever the technician shares location; disturb any piece later and the fingerprint stops agreeing with what it describes.

And can I look at it myself?Yes — you hand over a URL and it opens in whatever browser they already have, sign-in free. Treat that URL as a day pass rather than an archive: it lapses after a week, and issuing another takes a moment. Your vault holds the evidence permanently; only the door you opened onto it closes.

A residential building exterior surrounded by greenery
Photo: Paparazzi Ratzfatzzi / Pexels

Why one category beats a policy

Take the systems on a required schedule and stop there. Those are the records most likely to be pulled, and the ones where a gap is hardest to explain to somebody holding a clipboard. The NFPA 101 Life Safety Code and the standards it references are the usual source of those schedules — adopted federally for certified facilities and through state codes elsewhere. The intervals themselves live in the referenced standards rather than in 101.

A rule covering every vendor visit in the building is a rule that gets skipped in week two, and a skipped rule is worse than no rule — it reads as coverage in an audit and is not. One category, followed consistently, beats a policy everybody nods at.

What it does not settle

Be clear about the size of the claim, because overselling it here is how you lose a surveyor you had convinced. Two things get established: the image was captured live rather than selected afterwards, and the file has sat untouched ever since. Everything a surveyor genuinely cares about beyond that — whether the test was run properly, whether the equipment in frame is the equipment on the schedule, whether the reading means what the technician says it means — is still decided by people who know the work. This is a better exhibit, not a shortcut past the expertise.

It changes one thing, on the morning it matters. The answer to “how do you know this was done” stops being the word of the person who did it.

Common questions

What does a surveyor ask for on vendor work?

Usually the documentation for one system on one date: the fire alarm test, the sprinkler inspection, the generator run. Surveys work from your own records, so the file you produce is the evidence. Ask your state agency what it expects, because requirements differ by state and by accrediting organization.

How long do senior living communities keep vendor records?

Long enough that memory is useless by the time anyone looks, and set by your state and accrediting body rather than one national rule. The practical consequence matters more than the number: a record has to make sense to a stranger years later, with nobody around to explain it.

What makes a maintenance record hard to question?

Specificity and independence. Specific means this equipment, this date, this result, not a monthly summary. Independent means at least one element the filer did not produce, so the file does not rest entirely on the word of the party being asked about.

Does attaching a photo to the work order close the gap?

It narrows it. A picture of the panel is far better evidence than a tick in a box. But a surveyor holding it still has to decide when it was taken, and that judgement lands back on the same file: the shot arrived with the paperwork, from the same person, on the same afternoon.

Where should a community start without a big rollout?

One category rather than everything. Take the life-safety systems on a required schedule, because those are the records most likely to be pulled and the ones where a gap is hardest to explain. Prove the habit holds there before extending it to routine maintenance.

Pick the system they always ask about

Name the one whose file you would least like handed to a surveyor cold. We will pull up what its next service visit looks like when the timestamp is not the technician’s to set.