Ask what was observed before a repair was proposed

At Burj Khalifa, two FCUs were connected but only one was recorded operating. The second actuator lacked power from the existing controls. That finding supports checking the control interface; it does not support treating every connected unit as a completed repair.

Ask whether the fault is inside the AC scope

SpaceHUB had three phases absent at its panel because a connection from the main panel was broken. The wire was connected and insulated before the team reported completion and top-up. Ask a prospective contractor to identify the failed interface, rather than infer an AC component fault from a stopped system.

Ask precisely what the completion statement covers

Port de la Mer has checked Nest controls: controllers were connected, the app configured and rooms labelled. A separate water-leak investigation and an extra controller request were not closed by that confirmation. A useful work record names the completed item and its exclusions.

Compare the explanation, not an unsupported promise

Ask for an observed finding, the proposed action, the evidence needed to verify it and the scope boundary. These examples do not establish prices, certifications, response times or guarantees for another job.