Managing a renovation from a distance after the contractor signs is the long tail of the project, and where most owner-contractor relationships either solidify or unravel. The pattern that works: a 30-minute kickoff that explicitly sets expectations on communication and updates; daily photo updates from active work areas (5–10 photos); a 15-minute weekly status call covering progress, blockers, and the next week's plan; a written decision log for every choice that affects scope or cost; written change orders with cost and timeline impact before any disputed work proceeds; and a structured substantial-completion sign-off with a punch list before final retainage gets paid. Tools that consolidate the photos, conversations, and decisions in one place reduce the back-and-forth dramatically.
The kickoff meeting
Schedule a 30-minute video call within a week of contract signing, before any meaningful work has started. The goal isn't to re-litigate the contract — it's to set the operating rhythm explicitly so neither party drifts. Cover six things: communication cadence (daily photos, weekly call, how urgent messages flow), key contacts (who you reach for what, who replaces them when on vacation), decision authority (what the contractor can change without asking, what requires sign-off), change-order process (written, signed, before work, including cost and timeline), payment process (pay app format, lien waivers, payment turnaround), and substantial completion criteria (how you'll declare the project functionally done and trigger punch list).
Document the kickoff outcomes in writing and send to the contractor as a summary email. That becomes the operating-norms reference for the rest of the project. "Per our kickoff conversation" is a useful phrase later when reminding the contractor of an agreement.
Daily photo updates
Photos are the bridge between you and the work. Ask for 5–10 photos at the end of each active workday, taken by the foreman or lead contractor. They should cover the active work areas (what got done today), any decisions or surprises that came up (a finding behind drywall, a material that didn't fit, a layout question), and any safety or condition flags (water damage discovered, electrical surprises, anything unexpected).
Set the expectation explicitly that photos are part of the job, not an extra. Establish a single channel for them — Perch's photo timeline, a dedicated email folder, a shared cloud folder, whatever works. The single channel matters because you'll want to scroll back six weeks later when something goes wrong. Scattered photos across text, email, and WhatsApp threads are unsearchable.
On days when there's no progress (subs didn't show, weather, materials delay), the photo should be replaced by a brief explanation. Not silence. Silence is the failure mode that destroys trust over time.
Weekly status call
Fifteen minutes, same time every week. The call has four parts: progress against schedule (where are we vs. plan), this week's planned work, blockers and pending decisions, and any open change-order discussions. Keep it tight — the daily photos and decision log carry most of the information already, so the call is mostly the resolution of things photos can't convey: judgment calls, scheduling logic, what the contractor needs from you.
Send a one-paragraph summary email after each call confirming any decisions made and any actions assigned (with deadlines). The email becomes the record. "Per our Tuesday call" is the second-most-useful phrase after "Per our kickoff."
Decision log discipline
Every renovation involves dozens of small decisions that shift scope, cost, or finish quality — the kind of choices that get made over text and then forgotten until the punch list. Switching tile grout color. Changing outlet locations. Deciding whether to keep a damaged door or replace it. Picking the paint sheen. None of these are change orders (they don't usually move price), but each is a decision that one or both parties might mis-remember later.
Maintain a running decision log: date, decision summary, who made it, the photo or reference that prompted it. Tools like Perch are built around exactly this pattern — every photo can spawn a decision, every decision links to its evidence, the log exports as a PDF for handoff. Manual versions work too (a shared Google Doc or Notion page) as long as the discipline holds.
Change-order process
Change orders are different from decisions — they move price or timeline. The rule is simple and load-bearing: no change-order work proceeds without a signed change-order document specifying the new scope, the cost adjustment (positive or negative), and the timeline impact (days added or removed). Verbal change orders are how renovations end up 30% over budget with no clear paper trail of why.
Standard change-order template: brief description, reason for change, cost impact, timeline impact, signature lines for both parties. Some contractors keep their own template; ask for it during the kickoff. AIA G701 is the industry-standard form if you need a reference. Most residential contractors use a simplified version.
When the contractor says "we can sort that out at the end" Don't. End-of-project reconciliations of accumulated verbal changes are where most contract disputes happen. The accumulated cost is always larger than expected, the memory of who agreed to what is always different on each side, and the leverage at that point has shifted to the contractor — they're holding final invoices and your retainage hasn't been released yet. Make every change a formal change order before the work proceeds.
Pay applications and lien waivers
Before each milestone payment, the contractor submits a pay application: a one-page document listing the work claimed complete, the corresponding contract value, and the requested payment amount. Photos document the completed work. You verify against the milestone schedule and the photos.
Pay the contractor and require a conditional lien waiver from the GC and from each sub paid through this draw. After the payment clears, the conditional waivers become unconditional. Without lien waivers, a sub paid by the GC can still file a mechanics lien against your property if the GC doesn't actually pay them. The waiver dance is the only defense.
Substantial completion and the punch list
Substantial completion is the moment the work is functionally usable and the warranty clock starts ticking. It triggers the punch list — a written list of remaining minor items the contractor must address before final retainage release. Set the expectation during kickoff that substantial completion will be declared jointly with a documented walk.
Do the substantial-completion walk in person if you can. If not, do it via a thorough video walkthrough with the contractor and your trusted local pair of eyes (a handyman, a property manager, a friend). Walk every room methodically. Document every defect, every missed item, every finish blemish with photo and location. The punch list becomes a written deliverable list with target completion dates.
Release final retainage only when every punch list item is complete and signed off, and you have unconditional lien waivers from the GC and all subs. This is the single biggest piece of leverage you have over quality in the entire project. Don't release it for any reason short of full punch-list closure.
Frequently asked questions
Frequently asked
What do I do if the contractor stops sending daily photos?
Address it on the next weekly call directly: "the daily photos are part of how we work together; the cadence has slipped — what do you need to get it back on track?" If it slips again after, send a written email referencing the kickoff agreement. Persistent failure to communicate is one of the strongest early warning signs of a project going off track; treat it as such.
How do I handle the situation when the contractor wants to start work that exceeds the scope without a change order?
Politely refuse, in writing. "This sounds like a change to the scope; please send a change order with cost and timeline impact and I'll sign it before the work starts." Most experienced contractors respect this and produce the document; ones who resist are signaling something. Don't let the work proceed under "we'll figure it out later."
Can I require my contractor to use a specific tool or app for updates?
You can ask, but be reasonable. Contractors run multiple projects and have their own systems. Most will accommodate a tool that's frictionless for them (upload photos via mobile, text-based updates), but will balk at tools that require learning a new system. Perch is designed to be near-zero learning curve for contractors — they get a link from the owner, take photos like normal, and the photos land in the right place. Whatever tool you pick, optimize for the contractor's side of the friction, not yours.
How do I deal with my contractor's subs directly?
Generally, don't. The GC is responsible for managing their subs; going around them undermines the relationship and creates ambiguity about whose responsibility a problem is. If you have a concern about a sub's work, raise it with the GC and let them handle it. Exception: if you observe a safety issue, address it directly with the sub on site (or the GC immediately) — safety overrides chain-of-command.
What's the right cadence to visit the property during a renovation?
Twice for most residential renovations: once at the start of demolition or rough-in (to confirm scope and catch any major surprises early), and once at substantial completion (to walk the punch list). For longer or higher-value projects, add a mid-project visit around the drywall stage. Travel is expensive and rarely produces information that good photos and a video walk can't deliver.