Construction RFI Photos: What to Include Before Asking for Clarification

A close-up can show a wall opening clearly and still leave the recipient asking: Which wall? What drawing did you check? What do you need clarified?

A construction request for information, or RFI, asks for clarification through the project's established process. Before submitting one, prepare the photos and context so someone away from the site can understand the specific question. The aim is not to send every available image. It is to make the location, visible condition, relevant reference and remaining uncertainty understandable together.

Start With One Understandable Question

Write the question before choosing the attachments. If it takes several unrelated questions to describe the issue, first check whether you are combining different conditions into one request.

"See photos. Please advise" leaves the recipient to work out both the problem and the response you need. A focused question identifies the condition and asks for the missing information.

Throughout this guide, consider one illustrative, fictional example: a rectangular opening in the east wall of Room 214 on Level 2. The team has checked drawing A-204, detail 3, revision C, but has not identified the opening's intended treatment. These identifiers describe an example, not a real project or customer record.

The working question is: Which drawing or detail governs the intended treatment of this opening? That is different from assuming the opening is wrong or asking someone to approve a repair you have already chosen.

This emphasis on a concise request and relevant references is consistent with AIA's G716 RFI instructions. Use your project's required form and process; the photo package supports the question rather than replacing it.

Identify the Exact Location, Date and Reference

Give the recipient a location they can use

Use the location convention already recognized by the project team: building, level, room, grid, elevation or another established identifier. Add the wall or viewing direction when it matters.

For the example, "Level 2, Room 214, east wall" is more useful than "opening upstairs." The context photo should help the recipient relate that description to the visible area. A GPS location alone does not identify a particular indoor room or wall.

Include the capture date, not just the date you are sending the request. If the photos come from different dates, identify which view shows which observation. If a date is uncertain, say so rather than presenting it as confirmed.

These identifiers also belong with the retained record, not only in a message that may become separated from the photo. The broader method for keeping searchable construction project records helps when the team needs to retrieve the evidence later.

Use Context and Detail Photos Together

Give each photo a distinct job

Select views that answer different questions:

• Context view: Where is the condition within the identified area? For the example, show enough of the east wall and surrounding room to orient the recipient.
• Detail view: What exactly prompted the question? Show the opening and the relevant surrounding surface clearly.
• Additional view, when needed: What ambiguity remains? A different angle may reveal a relationship hidden in the first views. Do not add it simply to increase the attachment count.

Number the views consistently and refer to those numbers in the written request. "Photo 1: Room 214 east wall, context" and "Photo 2: opening, detail" let the reader connect the question to the right view.

Check the files at the size the recipient will actually see. The condition should be visible without searching through a cluttered frame or trying to read a tiny label. If the view does not show enough, obtain a clearer view where site access and safety procedures allow; do not substitute an assumption.

Procore's construction RFI guide similarly identifies relevant visual attachments as useful supporting context. The important choice is which evidence explains this question, not how many files you can attach.

Keep annotations simple and retain the original

An arrow or short identifier can direct attention to the opening. Keep it away from the edges or details the recipient needs to inspect, and retain the unmarked source image.

Use the same identifier in the photo label, reference excerpt and written question. Do not use an annotation such as "incorrect opening" when the evidence only establishes that an opening is present. Nor should an unscaled photo be treated as a reliable measurement or proof of compliance.

Separate What the Photo Shows From What Is Still Unknown

An observation describes what the record visibly supports. A clarification request identifies information the record does not establish. Keeping those apart prevents a confident label from doing more work than the evidence can support.

For the illustrative opening:

Keep the wording equally precise: "The opening is visible in Photos 1 and 2; its intended treatment remains unclear from the reference checked." That gives the recipient an observation and a question without embedding an engineering conclusion.

A missing photo is a coverage gap, not proof that an installation is missing. If the requested clarification depends on something outside the frame, identify the additional view or information needed.

The same distinction matters when reviewing documented changes over time. Here, apply it to one request: what is shown, what remains unknown and what the recipient is being asked to clarify.

Run a remote-reader check

Before sending, read the package as someone who has not visited the location:

• Can I identify the exact area and tell when it was photographed?
• Can I match the context view, detail view and cited reference?
• Is the written observation supported by what the photos show?
• Is the remaining uncertainty explicit, and does the request ask one understandable question?

If one answer is no, fix that specific gap. You may need a wider view, a legible reference excerpt or clearer wording rather than more attachments. When evidence cannot be obtained, make the limitation visible instead of implying the package is complete.

Then submit through the project's established RFI process. Evidence preparation helps explain the request; it does not replace the project's review or authorization requirements.

How Filio Can Support the Evidence Preparation

Filio can support the record-organization work that comes before a clarification request. It organizes field records by project and supports contextual photos and media, metadata, tags and retrieval. Available location, map and plan context can help the team identify relevant records. Selected evidence can also be organized into a report.

The team still chooses the views, checks dates and references, writes the observation and decides what needs clarification. A report is an optional way to organize those inputs, not a prerequisite for every request.

Filio supports preparing and organizing the evidence. Formal RFI routing, assignment, approvals, status tracking and responses remain part of the project’s established RFI process.

Frequently Asked Questions

How many photos should you include with a construction RFI?

There is no universal fixed number. Use enough evidence to establish context and show the specific condition. Often that means a wider context view plus one or more detail views, depending on the question. Follow any project-specific attachment requirements, and remove redundant photos that add no useful information.

Can an older photo support a current clarification request?

Yes, when its date and relevance are clear. An older photo may provide background or show a condition before it became concealed, but it does not establish today's condition. Label it as an earlier view, explain why it is included, and obtain current evidence where the question depends on what is present now.

To organize selected field records into a report, see how to create a report in Filio.