The property condition report
PCA Reliance Letter Request Template & Example
Last updated 2026-10-10
A lender asks to rely on the buyer's property condition report two days before its credit meeting. Before anyone changes an addressee, assemble the exact report, the proposed relying party's legal name, the intended transaction and the requested terms. Those are the inputs this packet collects for the consultant and contracting client.
E2018 describes use tied to identified objectives and contracting parties; its public discussion at 4.2.3–4.2.4 contemplates agreement to extend reliance. NEEDDA's Document Center separately lists reliance and information-only letters. These sources support distinguishing a request to receive a report from a request to rely on it. They do not supply a universal grant of reliance.
The template is a request and decision record, with any resulting letter identified as a separate attachment. Complete the reliance terms through the parties handling the engagement. The property condition report remains the underlying deliverable; sending its executive summary alone leaves the scope and limitations out of the packet. The Bellwether example ends with terms still unresolved.
Jurisdiction
Written primarily against US practice: the ASTM E2018 baseline, agency scopes such as Fannie Mae Form 4099, and — where a page says so explicitly — California statute. Client scope governs any individual engagement and may expand or reduce what is described here. State and local inspection obligations differ, and licensure requirements for the work described vary by state. Outside the US, treat the structure as transferable and the standards and statutes as not.
PCA Reliance Letter Request template
Free Word download, no email required. Or open it in Professional Drafter — it lands in your template library, ready to draft against.
When to use this document
- A lender or another named entity asks to use a PCR commissioned by a different party.
- A request names affiliates, participants or future purchasers beyond the entity identified in the engagement.
- A report is available in a transaction folder but the file contains no documented answer to the proposed party's reliance request.
Worked example
Fictional. A reliance request following the Bellwether Commons PCR issued on 27 March 2026 for Northbank Capital. The property, parties, correspondence and dates are invented and illustrative. This example records a request; it grants no reliance and leaves the proposed lender's terms open.
Report and Engagement Identification
The request concerns Bellwether Commons, 4400 Ridgeline Drive, Columbus, Ohio, under Northbank Capital engagement NC-2026-0217. The packet identifies the PCR issued on 27 March 2026 following M. Reyes's visit on 4 March. It includes the report narrative, Immediate Repairs Table, Replacement Reserves Table and report appendices as one issue set. Northbank's transaction coordinator has also retained the 18 March draft summary in the transaction folder; that draft is identified in this request as superseded and is excluded from the proposed reliance packet. The issue date is recorded separately from the visit date so the request does not suggest another visit occurred in late March.
Proposed Relying Party and Use
On 30 March, the proposed acquisition lender, Cedar Reach Bank, asks for a letter naming it as a relying party for its lending decision on Bellwether Commons. Cedar Reach Bank is an invented institution used only in this example. Its request also refers to future loan participants without naming them. The log records the bank's name as supplied and flags the additional parties for clarification. The bank's transaction contact is the correspondence recipient, not an extra relying entity. The existing PCR already identifies Northbank Capital and its lender as intended users; the packet asks how the newly supplied name and broader request fit the actual engagement terms.
Existing Terms and Requested Changes
Northbank asks the consultant to consider the bank's proposed wording and to identify any consent or amended terms needed under the engagement. The request attaches the bank's wording alongside the engagement reference rather than replacing the PCR's purpose paragraph. The bank's request for unnamed future participants has no recorded agreement. No fee, liability allocation or assignment provision is invented to fill that gap. The coordinator leaves those fields pending and asks the contracting parties to provide their settled wording. No signed letter is included in the packet at this stage, and the coordinator's covering email is labelled as a request for a decision.
Scope, Dates and Outstanding Questions
The packet directs the bank to the issued limitations concerning the unaccessed clubhouse roof, snow-covered northern paving and unidentified electrical panels. It asks the consultant whether the proposed lending use calls for any additional work. It does not report that any of these questions has been resolved. The request concerns the existing acquisition assessment and supplies no new client form or revised observation scope. Agency financing was contemplated, but this request does not convert the existing work into an agency assignment. Any request to describe present conditions will receive its own scope and date discussion before the report is changed.
Decision and Distribution Record
As of the coordinator's 31 March entry, the consultant has acknowledged receipt and asked for clarification of the proposed additional parties. The status remains pending. The log records the complete issue set supplied for consideration, the requesting bank contact, Northbank's transaction contact and the consultant's engagement contact. The letter-issued field remains empty with the note 'not issued', rather than carrying the date of the acknowledgement email. The next action belongs to Northbank's transaction coordinator: obtain the clarified request and return it to the contracting parties. The file contains no representation that the bank has accepted the report or that the open property questions have changed.
Section-by-section guide
What each section is for, what a good one contains, and where they typically go wrong.
1.Report and Engagement Identification
Identify the complete report by property, engagement reference, issue date and revision. Record the observation date separately. Include the schedules and appendices in the file description so the request cannot drift onto a detached summary or an earlier draft.
2.Proposed Relying Party and Use
Name the legal entity and describe the decision it wants to make. Keep an email recipient, an institution's trading name and a proposed relying party in separate fields. List any additional entities explicitly; a request for a bank and its future loan purchasers needs an answer to both parts.
3.Existing Terms and Requested Changes
Attach the engagement's existing reliance language and mark what the request would change. Refer questions about assignment, liability allocation, fees and signatures to the people settling those terms. The request log records their answer; it should not silently supply one.
4.Scope, Dates and Outstanding Questions
Ask the consultant to compare the proposed use with the work actually performed. Carry unresolved findings by report reference, including the effect described in the limitations statement. Record a request for current observations as additional work for consideration, with its own status.
5.Decision and Distribution Record
Use an explicit status such as pending, declined, or letter issued. Record who answered and which document contains the operative terms. A sent email establishes that the request travelled; it does not establish the answer. Keep the distribution list tied to the exact files supplied.
Common mistakes
The failure modes that show up most often when this document is reviewed later.
Changing the addressee before identifying the requested use.
The party may be seeking a different transaction or a broader group of users. Record that request before treating it as a clerical correction.
Attaching the latest summary and an older schedule.
The proposed relying party receives conflicting versions. Identify a complete issue set and list exactly which files accompanied the request.
Recording 'approved' when the consultant only acknowledged the email.
An acknowledgement leaves the substantive request unanswered. Record the response as received and keep the decision pending until the parties supply it.
Treating a new letter date as a new observation date.
Keep both dates visible. If additional observations are requested, identify them as work to be considered and document their outcome separately.
Questions
- Is this a reliance letter I can sign?
- It is a request packet and decision record. The resulting letter, if agreed, is a separate document. NEEDDA's public directory links model reliance resources, but this template does not reproduce their terms or determine what the parties should sign.
- What if the report already says it is intended for the buyer and its lender?
- Include that language in the packet and ask how it applies to the named entity and requested use. Do not assume it settles additional affiliates, future participants or changed purposes. The Bellwether example follows precisely that situation.
- What should accompany the request?
- The exact report issue, both cost schedules and appendices, the proposed party's name and use, its requested wording, and the existing engagement provisions available to the parties. Flag missing material so the recipient can distinguish an incomplete packet from an unanswered request.
The blank template
Exactly what is in the Word download, so you can see the structure before deciding whether you want it.
Report and Engagement Identification
Proposed Relying Party and Use
Existing Terms and Requested Changes
Scope, Dates and Outstanding Questions
Decision and Distribution Record
Download this template
Free Word download, no email required. Or open it in Professional Drafter — it lands in your template library, ready to draft against.
Sources
Related templates
ASTM E2018-24 Property Condition Report Template
An ASTM E2018-24 property condition report template with a filled-in example — plus what changed in the 2024 edition and who the guide binds. Free Word download.
PCA Executive Summary Template & Example
An executive summary template for a property condition report, with a filled-in example: what belongs in it, what does not, and the totals it must reconcile.
Limitations & Field Conditions Statement Template & Example
A limitations statement template for a property condition report, with a filled-in example showing how to record snow cover, inaccessible roofs and unavailable units. Free Word download.
This page is a documentation aid — not engineering advice, not legal advice, and not a substitute for the standard or client scope your engagement runs under. A template cannot tell you what your assessment requires. The worked example describes a fictional property, and its costs, quantities and service lives are illustrative only.