The last open-wall walk in a Greenwich house is when the AV contract stops being a sales document and starts becoming a construction document. The electrician wants final keypad counts. The millworker wants exact speaker back-box depths. Someone asks whether the rack can give back 14 inches to the linen closet. If the agreement is vague, the next month is change orders.
That matters more now than it did a few years ago. Lutron's Luxury Residential 2026 Trend Report, released on December 9, 2025, found that 94% of designers and architects say clients consider lighting highly important, while 56% already include automated shades in final designs [2]. In a luxury estate, the contract is not just buying TVs and speakers. It is buying part of the house.
Start With System Ownership
Ask which platform owns lighting, shades, AV, and the network
A proposal that says smart home package is not specific enough. The contract should name the actual systems and the job each one owns.
In Cave Group's residential stack, that usually means Lutron HomeWorks QSX for lighting and shades, with Palladiom keypads, Palladiom or Sivoia QS shades, and Ketra where tunable light is part of the design. Control typically lives on Crestron Home OS with a CP4-R, DIN-AP4-R, or MC4-R depending on scale, with interfaces such as a TSW-1070 where a touchpanel actually earns its place. Networking lives on UniFi, sized as infrastructure, not as a few access points added at the end.
The reason to ask this up front is simple: blurred ownership creates service problems. If Lutron scenes are supposed to drive the daily lighting experience, say that. If Crestron is calling whole-house scenes, intercom, gate control, climate actions, and AV macros, say that too. If UniFi Protect cameras are included, say whether the contract also covers door access, alarm sensors, or neither. The systems can work together just fine. The confusion starts when nobody wrote down where one ends and the next begins.
Lutron's December 2025 research is useful here because it confirms what good residential jobs already show on site: lighting, shades, and controls are now treated as core design elements, not as trim-stage extras [2]. If the proposal still treats them like accessories, the contract is already behind the house.
Ask what is being delivered now and what is only being prepared for later
A clean contract separates day-one deliverables from future-proofing. Those are not the same line item.
If the theater is phase two, the contract should say whether phase one includes conduit, dedicated circuits, speaker paths, ventilation, rack allowance, blocking for a projector lift or screen, and cable pulls for future fiber or HDMI transport. That is very different from delivering a Barco projector, Screen Innovations screen, Kaleidescape, Trinnov calibration, or a StormAudio processor on closeout.
The same goes for guest house coverage, gate intercom, pool audio, and landscape lighting. A house can be prewired for future Coastal Source or Sonance outdoor audio without actually delivering that system today. The trap is letting future-ready language sound like present-day scope.
Ask the integrator to mark every major subsystem as one of three things: included now, rough-in only, or excluded. That one habit prevents an astonishing amount of argument later.
Ask For A Design Package, Not Just A Price
Ask for drawings that are tied to the contract
The best contracts are almost boring. Room by room. Device by device. Drawing by drawing.
Ask for a reflected ceiling plan showing speakers, displays, touchpanels, access points, cameras, sensor locations, and shade pockets. Ask for elevations where TVs, soundbars, recessed boxes, and millwork speakers need exact placement. Ask for a rack elevation. Ask for a keypad schedule with engraving. Ask for a shade schedule by opening. Ask for a network one-line that shows core switching, UPS placement, WAN handoff, and any outbuilding connectivity.
Ubiquiti's April 2, 2026 rebuild of UniFi Design Center put floor plans, LiDAR capture, device relationships, and automatically generated installer-ready documentation at the center of deployment [3]. That is a good cue for residential clients: current platforms assume documentation is part of the job. Your integrator should too.
This is where details save money. Sonance Visual Experience speakers need known depths. James Loudspeaker millwork or in-wall subwoofer locations need structure and finish coordination. A TSW-1070 at the service entry needs a back box that does not fight cabinetry. Lutron keypad spacing needs to be coordinated with trim, stone, and mirror lines, not guessed after paint.
If the answer is we will sort that out in the field, you are not looking at a finished contract. You are looking at a placeholder.
Ask how lighting scenes and keypad engravings will be approved
The easiest way to spot a weak lighting package is by the keypad language. If the contract talks about elegant control but does not say how scenes are named, tested, and approved, the project is not ready.
In a luxury residence, the lighting experience lives in a handful of repeat moments: morning, dinner, entertaining, movie, away, goodnight. The engravings matter because they turn a system into a habit. The same is true for shade groups. South-facing glass, a primary bath, a study, and a two-story great room do not all want the same behavior.
Ask these questions before you sign:
- Who is writing the first scene list?
- Who approves final keypad engravings?
- Are Ketra and shade scenes part of the base programming scope?
- How many revision rounds are included?
- What happens if decorative fixtures change late and loads have to be regrouped?
That conversation sounds fussy until drywall is closed and the family is living with six buttons labeled Scene 1 through Scene 6.
Ask Hard Questions About The Network
Ask what happens when the internet dies at 6:40 p.m.
Most residential AV problems that get called user problems are really network design problems.
The contract should say whether the system remains functional when the ISP goes down. Local lighting control should still work. Local AV control should still work. Cameras should still record locally if that is in scope. Remote access, cloud notifications, and some streaming services may drop, but the house itself should not feel broken.
That means asking about more than Wi-Fi coverage. Ask about the gateway, switching, UPS runtime, rack cooling, and failover. Ask whether the network is being built around a primary circuit only, a second WAN, or a cellular fallback. Ask how remote service is handled if the home sits behind carrier-grade NAT or an ISP with awkward IPv6 behavior.
UniFi Network 10.4, released on May 19, 2026, added WireGuard over IPv6, 5G telemetry, blueprint synchronization, and configurable UPS battery thresholds [4]. Two days later, Ubiquiti introduced UniFi 5G Backup, a PoE-connected add-on with SIM and eSIM support that can work with any UniFi gateway [5]. Those releases are a useful reminder that a current residential network is not just radios and passwords. It is routing policy, power behavior, visibility, and a plan for the first outage.
If the proposal says network included, ask the follow-up question: included at what resilience level?
Ask how outdoor coverage and outbuildings are being handled
The rear terrace is usually where optimistic Wi-Fi plans go to die.
Pool houses, detached garages, gatehouses, court areas, and deep rear yards change the job. A good contract says whether those areas are getting hardwired connectivity, fiber, point-to-point links, or only best-effort coverage from the main house. It should say whether weather-rated access points such as a UniFi U7 Pro Outdoor are in scope, where they mount, and how they are powered.
Do not accept broad language like full property Wi-Fi without a drawing and a definition. Full property could mean patio coverage near the facade. It could also mean stable roaming to a guest house and reliable bandwidth at the gate. Those are not the same result and they are not the same budget.
If cameras or intercoms live outdoors, ask for the same level of clarity. A G6 Pro Bullet at a driveway is different from a G6 PTZ watching a larger approach. One is a fixed view. One introduces presets, tracking, and different expectations for storage, aiming, and user training.
Ask What Happens After Drywall
Ask what triggers a change order
A good integrator will not pretend change orders disappear on custom residential work. The honest question is what causes them.
Typical triggers are predictable:
- A TV wall shifts after millwork revisions.
- Speaker counts change after ceiling details are finalized.
- Window treatment pockets or hembar details change.
- The equipment rack moves to another room.
- Decorative lighting changes the load schedule.
- Camera positions move because landscaping or exterior lighting changed.
- The client adds a generator interface, gate control, or a golf simulator after rough-in.
Put the trigger language in the contract. Also put the pricing method in the contract. Fixed fee for minor revisions, time and material for design changes, or a written proposal per change are all workable. The bad version is finding out the method only after the first redraw.
Ask what documentation you receive at turnover
Closeout should hand you a house that can be serviced, not a mystery that can only be decoded by the original programmer.
Ask for a turnover package that includes:
- As-built floor plans
- Rack elevations
- A network one-line and IP scheme
- A lighting and keypad scene list
- A shade schedule by opening
- A camera map and retention plan
- A device inventory with model numbers, serial numbers, and MAC addresses where relevant
- Service contacts, warranty dates, and escalation paths
If the system is using Crestron Home OS, ask whether backups are stored and how recovery is handled if a processor fails. If the lighting system is HomeWorks QSX, ask how databases and engraving records are archived. If the house has UniFi routing, switching, and Protect, ask who holds administrator access and whether the homeowner gets view-only, full admin, or an escrow path if service ever changes hands.
The point is not to become your own integrator. The point is to avoid owning a black box.
Ask how software updates and service windows are handled
Software changes now shape the lived experience of the house. That is good when it is planned and bad when it is casual.
Crestron Home OS 4.10, released on March 31, 2026, added support for the 80 Series touch screens and three new partner keypad brands [1]. That is exactly why the contract should define the software policy. Ask what version ships at handover. Ask whether auto-updates are enabled or disabled. Ask who tests updates before they are applied to the live residence. Ask whether after-hours service windows are included. Ask what happens if a touchpanel, Apple TV driver, or network device behaves differently after an update.
The same discipline applies to Lutron and UniFi. Firmware is part of the job now. Put it in writing.
Ask What Monitoring Actually Means
Ask whether security means cameras, alarm, or both
One of the fastest ways to misunderstand a residential proposal is the word security.
UniFi Protect cameras are one scope. Door access is another. Alarm sensors and central-station dispatch are another. Live human video intervention is another again.
At Cave Group, Cave Guard 24/7 is the sensor and alarm layer. It covers intrusion, fire and smoke, CO, water leak, freeze, and power-loss monitoring through a UL-listed Five Diamond central station. Deep Sentinel is the live video layer. That is not the same thing as camera recording, and it is not a substitute for alarm monitoring.
Ask the contract to separate those scopes plainly:
- What devices are being installed?
- What is locally recorded?
- What is remotely monitored?
- Who receives alerts first?
- What response path exists for intrusion, leak, or smoke?
- Is video review human, automated, or just homeowner notification?
If those answers are vague before signature, they will stay vague when the first alarm happens.
Ask who answers after move-in
The handover meeting is not the finish line. It is the start of living with the house.
Ask who answers the call on a Saturday night when the primary bath keypad stops responding. Ask whether remote diagnostics are included. Ask whether annual maintenance visits are part of the service plan. Ask whether lighting scene revisions after furniture and art install are included or billable. Ask how quickly a failed shade motor, touchpanel, access point, or UPS can actually be swapped.
This is also where brand choice matters in a practical way. A Crestron CP4-R, Lutron HomeWorks QSX processor, and a UniFi network are supportable systems when the integrator documents them well and keeps replacement paths clear. The hardware matters, but the service model matters just as much.
The Contract You Actually Want
The right residential AV contract is specific enough to survive a real build. It names the systems, the processor, the lighting platform, the access points, the cameras, the drawings, the exclusions, the change-order rules, the commissioning steps, and the service terms. It tells you what is live on day one and what is only being prepared for later.
That is how Cave Group prefers residential work to read: Crestron for control, Lutron for lighting and shades, and UniFi treated like infrastructure rather than an afterthought. Before you sign, ask the questions that force that level of clarity. The right integrator will already have the answers.