Property management
Vendor work verification for multifamily
Start with what the sign-off actually rests on
A unit gets turned. The vendor marks the work order complete, sometimes in the portal, more often by replying to a text. A site manager who was not in the unit accepts it, because the unit is now occupied or because the vendor has been reliable for three years. The invoice posts. That is the whole evidentiary chain, and every link in it was authored by one of the two parties with a reason to want the job marked done.
Nothing about that is unusual or dishonest. It is how most portfolios run, and it works almost all of the time. It is worth looking at closely anyway, because the places where it fails are the places that cost the most.
Credentialing answers a different question
Search for vendor verification in this industry and the results are about credentialing. The two most thorough guides on the first page — one from VendorAccess, one from NetVendor — run to a few thousand words each, walking through insurance limits, licence expiry, risk tiers and continuous monitoring. Both are genuinely useful. Neither contains a section on confirming that work was completed, because that is not what the category is for.
The distinction is easy to state and easy to lose. Credentialing is a gate at the property line: it decides who is allowed in. Work verification is about what happened after they went through the gate. A vendor can hold current insurance, a valid licence, a clean background check and a five-year relationship with your firm, and still invoice for a job that did not happen. The credential file will not show it, and it was never supposed to.
| If it is questioned | Work verification | Vendor credentialing |
|---|---|---|
| What it answers | What happened at the unit | Who may enter the property |
| When it is checked | After the job is called done | Before the vendor arrives |
| Who produces the record | The camera, on site | The vendor, at onboarding |
| What it covers | A specific job on a specific date | Insurance, licence, screening |
Where the paperwork is the whole scheme
In April 2026, a former property manager who handled the finances of several Florida homeowner associations turned herself in to the Martin County Sheriff’s Office. She faces 124 felony charges, among them grand theft, uttering false instruments, and embezzlement tied to forged financial instruments and false entries in business records. These are charges: she is accused, not convicted, and as reported in April 2026 the case was open and untried.
What investigators allege is worth reading closely, because the method they describe is entirely documentary. On their account it ran on four kinds of paper: cheques made out to herself, invoices for work that had no vendor behind it, ledger lines edited to agree with them, and signatures added to close the loop. Reported by KATV.
Set the alleged theft aside and look at the machinery. An invoice, a ledger entry, and a signature: three documents that corroborate each other, all of them produced by the same hand. A board reviewing that file sees three independent-looking records agreeing. They are not independent. They never were. That is a general property of self-authored paperwork, and it is true of an honest vendor’s work order too — the sign-off agrees with the invoice because the same party wrote both, not because the work happened.
Change one input
You do not need to redesign vendor management to close this. You need one artifact in the file that the vendor could not have written at their desk.
A live photo is that artifact, but only under two conditions, and both matter more than they sound. It has to be taken through the camera rather than selected from a photo roll, because a gallery is a place old pictures live. And the time on it has to be written by something other than the phone that took it, because a device clock belongs to whoever holds the device.
With LockProof, the vendor gets a text link and taps it. The link opens the camera directly and the gallery is blocked, so there is no path to attach a photo from a previous job. When they submit, the server writes the time on arrival, and the image, that server-set time and the coordinates — when the vendor shares location — are sealed together under one SHA-256 fingerprint. Change any of those afterwards and the fingerprint stops matching, which is what makes a later edit detectable rather than silent.
Two details matter specifically for multifamily. You can require a location reading before a submission is accepted at all, which is useful on scattered-site and suburban portfolios — though it requires that a reading exist, not that it match the property, so treat it as a completeness control rather than as a fence. And the finished record lives at a link you can forward: an owner, a board member or an adjuster opens it in a browser with no account and no login. That link is deliberately short-lived — it expires after seven days, and you mint a fresh one when someone asks. The record itself keeps; the link is the part that is temporary.
Four steps, in the order they survive contact
The failure mode of every documentation policy is that it applies to everything, so it is followed for nothing. Narrow it first.
- Pick the jobs where a dispute is expensive. Turns and make-readies, roof and mechanical work, anything a board reviews line by line, anything over a threshold you set. For most portfolios that is a small fraction of work orders and a large fraction of the money.
- Say what the photo has to show, in writing, before the vendor starts. The completed work, wide enough to place it in the unit, plus one detail shot. A vendor who knows the requirement will meet it; a vendor asked afterwards will send whatever they have.
- Put the requirement in the vendor agreement, not in the reminder text. It is a term of doing business with the portfolio, the same as the insurance certificate. That framing removes the argument about whether it applies this time.
- File it against the unit and the date, not the invoice.Disputes arrive as “what happened in 4B in March”, never as “show me invoice 8812”. A record you cannot find on the axis the question arrives on is a record you do not have.
What this does not do
A sealed photo shows a live capture and shows that the record has not changed since it was sealed. It does not certify that the work was any good, that the right unit was photographed, or that a scene is what it appears to be. Inspection and judgment are still yours to apply, and a vendor determined to defraud you can still photograph the wrong thing correctly.
What changes is narrower, and worth having anyway. The dispute stops being your word against the vendor’s and starts from an artifact that neither of you authored alone. Most vendor disagreements in multifamily are not fraud at all — they are two people remembering a January turn differently in July. Those end quickly when there is something to look at.
Common questions
What is vendor work verification in multifamily?
It is confirming a specific job was actually done, at that unit, on that date — separate from vendor credentialing, which confirms the vendor carries insurance and licences. Credentialing screens who may enter the property. Work verification concerns what happened once they were inside, which is where the money is.
Is vendor credentialing the same as verifying the work?
No, and conflating them is the common gap. Credentialing is checked before the vendor arrives and covers insurance, licences and background screening. It says nothing about whether a turn was completed. A fully compliant vendor can invoice for work nobody performed.
How do you prove a vendor completed a job at an apartment?
Ask for a record the vendor cannot author alone: a photo taken live through the camera rather than chosen from a roll, carrying a time written by a server on submission rather than by the phone. That is checkable in a way a signed line on a work order is not.
Is a photo texted from the vendor good enough?
It is better than nothing and it settles most ordinary questions. What it does not answer is when the image was made, because the file carries a date its sender can edit, and any picture can be sent later than it was taken. For routine work that is fine. For a disputed invoice it is thin.
What should a portfolio require on high-value work orders?
Pick the jobs where a dispute is expensive — turns, make-readies, roof and mechanical work, anything a board or owner reviews — and require a live photo with a server-set time on those. Requiring it everywhere is how the habit collapses. Requiring it where money moves is how it holds.