How We Run Renovation Oversight Without Setting Foot on the Property

Every milestone completion requires a photo set before the next payment is released. We define exactly which photos we need: framing before drywall goes up, rough plumbing before walls close, tile work before grout, final fixtures in place. We send the contractor a shot list. They send us the photos. We review and either approve the milestone payment or flag what is missing.

This is not a trust issue — it is a documentation issue. When photos exist at every stage, there is no ambiguity about what was completed and when. It also creates a visual record that is worth its weight in gold if a dispute ever arises.

At major milestones, we schedule a 15-minute video walk-through with the contractor. They carry the phone. We direct what to show. We ask them to open the cabinet, run the water, flip the switch, walk the perimeter. We see the same things a site visitor would see — we just see them through a camera.

Most contractors have never done this before and find it completely reasonable once they try it. The ones who resist video walk-throughs are usually the ones with something they would rather you not see. That resistance itself is useful information.

No texts to the contractor's personal number. No calls that go undocumented. Every communication about the project runs through our system — whether that is email, a project thread, or a platform we set up for the job. This is not bureaucracy. It is protection. When every conversation is documented and timestamped, there is no "I never said that" and no "I thought you approved that."

The documentation discipline also makes handoffs seamless. If something changes — on our side or theirs — the next person who picks up the project has the full picture. Nothing lives in someone's text message thread.

When a project reaches substantial completion, we build a remote punch list from the photo and video record. Every item that is incomplete or deficient goes on the list with a photo reference. The contractor receives the list and confirms each item in writing as it is resolved. Final payment is held until the list is closed.

We have managed projects where the punch list had 40 items. We have managed projects where it had 2. The number does not matter. What matters is that nothing gets released until everything is right — and that the whole process is documented.