A fall vendor review is not a contest to find the most confident sentence on a website. A property manager needs to know what a vendor agreed to inspect, what equipment is included, which records support the work, how access will be handled, how an estimate is approved, and what happens when the first visit does not settle the issue.
The Bay Area Home Service Pros informational blog is the informational resource, and the home service contact page is the live route for site questions. This guide does not rank vendors, verify a particular company’s current claims, give legal advice, or promise a heating result.
The author publishes this site as part of the Adrium family.
Start with the equipment scope
List each building, unit, zone, thermostat, outdoor unit, furnace, heat pump, air handler, and shared system that the engagement may include. Record the asset label, location, model if safely visible, access owner, and known relationship to other equipment. Keep tenant comfort complaints separate from the asset list until the pattern is documented.
Ask the vendor to state what is included and what is excluded. “HVAC maintenance” can mean different work in different contracts. A property team should be able to compare the written scope with the work order and later invoice without guessing what a line item means.
Do not infer that a vendor covers every system in a building because one system appears on a public page. Confirm the actual address, equipment type, service boundary, and approval path in the engagement documents.
Review the record quality
A useful file contains the date, asset, observed symptom, control state, visible condition, work performed, measured findings when supplied, parts or materials identified, open questions, and next owner. It should distinguish a tenant report from a technician finding and a recommendation from approved work.
Look for repeated entries that preserve the original symptom. A later normal cycle should not erase an earlier alarm, leak, noise, or no-heat event. If a record says “checked” without describing the scope or result, mark that as a question rather than filling in the missing detail.
Public reviews can describe a person’s experience, but they are not a substitute for an equipment record. Keep reviews in a separate reference section and do not convert a general rating into a claim about a particular system.
Confirm access and communication
Write down keys, lockboxes, tenant notice, roof or mechanical-room access, parking, escorts, pets, restricted areas, quiet hours, and the person who can authorize entry. State who receives the arrival note, finding, estimate, invoice, and follow-up question.
An access plan is part of the scope. A vendor cannot inspect an inaccessible unit, and a property manager cannot evaluate a missed step if the record does not say that access was unavailable. Keep tenant privacy and security information in the approved channel. Do not place codes or keys in a public review file.
Ask how a vendor documents a no-access visit, a tenant cancellation, a safety stop, and a return visit. These are process questions, not predictions about timing.
Read the estimate path
Separate inspection or diagnosis from proposed repair work. The estimate should identify the asset, observed issue, recommended scope, exclusions, assumptions, approval contact, and the condition that would require a change. If a line is unclear, ask for plain language before approval.
Do not compare generic prices from a website with a site-specific estimate as though they cover the same work. Do not treat an estimate as a promise that a particular part will solve the complaint. A written document is useful because it shows what was proposed at that point in the process.
Keep approved work, declined work, deferred work, and monitoring in separate statuses. A deferred item is not a completed repair. An invoice is not proof that every related symptom was resolved.
Check public and contract facts separately
For a public claim, record the URL, date viewed, exact wording, and what the claim appears to cover. For a contract fact, record the document name, version or date, asset, and responsible party. Do not repeat a current-sounding statement without checking whether it applies to the property and equipment.
Review license, insurance, manufacturer authorization, warranty language, and maintenance scope only from the sources the property team is permitted to use. Do not publish a credential or claim that has not been checked. If a vendor says it covers an area or equipment type, ask for the service boundary in the engagement record.
Define escalation without a promise
An escalation map should say who receives a recurring alarm, a safety concern, a tenant complaint, a failed visit, an access problem, an unavailable part, or a disputed scope. Include the building contact, vendor contact, approval owner, and communication channel. State what evidence should travel with the escalation.
Do not write a fixed restoration claim, “always available,” or a fixed response promise unless a current contract explicitly supports that wording and the property team has permission to publish it. A plan can describe decisions and owners without predicting what a technician or piece of equipment will do.
Run the review as a handoff
At the end, the property manager should have a current asset list, written scope, record sample, access plan, estimate workflow, public-claim notes, contract facts, open items, and escalation contacts. Mark every unknown. Assign the next question to a person rather than silently assuming the answer.
Review the file again after the first fall visit or after a scope change. Preserve the prior version so the team can see what changed. The purpose is a cleaner decision path for the property, not a score that promises a particular heating performance.