Separate visible problems from unknowns
Describe damage, wear, and systems that are not functioning as expected. Say when you first noticed each issue and whether anyone has assessed it. Avoid presenting a guess as a confirmed diagnosis. A clear summary lets a property discussion focus on what is known and what needs review.
Use information you already have
Previous inspections, estimates, and repair records can help explain the property. Mention those documents if they exist; you do not need to order new reports to submit an inquiry. If further review is proposed, confirm which information is required and the appropriate way to provide it.
Compare taking on the work with changing ownership
A repair plan can involve more than the contractor’s price: access, scheduling, and further discoveries may matter too. A sale has its own costs and conditions. Compare specific proposals and realistic responsibilities, rather than deciding from a general claim about saving money or avoiding all effort.
Make site conditions clear before a visit
Tell us about restricted areas, unsafe conditions, or utilities that are not available. Any property review should be arranged with those conditions in mind. The inquiry process is not an engineering assessment or a recommendation about how to repair the building.
Leave the conversation with a clear next step
Ask whether the property fits current coverage, what additional information is needed, and who would be involved in a possible transaction. If a proposal is discussed, request the purchaser’s identity and the complete written terms, including any assignment provisions.
An inquiry is not a valuation or a promise to purchase. Before accepting an offer, consider its price, conditions, costs, and timing alongside other routes available to you. Bring in your own qualified adviser for questions specific to legal authority, taxes, or the agreement.
A quick way to prepare
Keep a short summary of the address, condition, occupancy, and your priorities beside you when you call. Details you do not know can be flagged for a later discussion.
Use the first-call checklist