Keep a Vendor Arrival Proof Log for Rental Work Orders

A vendor arrival log settles a narrow question: did the scheduled visit occur, and what happened at the door? It should not double as an invoice approval or a claim that the repair is complete. Keeping those decisions separate prevents a check-in message from becoming unsupported proof of finished work.

Use the vendor scope approval record before dispatch and the reopen evidence check when the issue returns.

Quick Overview

Capture the property identifier, work-order reference, promised window, actual arrival time, access result, and the person who recorded the event. Link an approved photo or system event when one exists. If nobody can verify arrival, mark the event unknown instead of filling the gap from a later invoice.

Common Mistakes

A vendor may arrive and still be unable to enter, find the reported problem, obtain a part, or finish safely. Give the access outcome and the work outcome their own fields. That distinction helps the next coordinator decide whether to reschedule, request evidence, or route a scope question to the authorized manager.

Common Questions Answered

The daily review should focus on missed windows, denied access, repeat visits, and records with no outcome. Assign one owner and a due time to each exception. Avoid copying resident contact details into a broad operations sheet; use the controlled work-order system for sensitive information.

Ready to close the loop

Before closing the arrival record, confirm that the next action has a named owner. A completed visit may proceed to workmanship review or invoice matching. An incomplete visit needs a reason that came from the actual record, not a guess. The log is useful because it preserves what happened without granting approval that belongs elsewhere.

Published September 15, 2026.

See NIST digital evidence preservation guidance for general evidence context.