A client report may show a small selection from an inspection that produced hundreds of construction photos. Weeks later, someone asks for a wider view, a clearer detail or evidence from another area. The useful question is whether the team can explain the selection and find the relevant source record.
That becomes harder when “not in the report” is treated as a single condition. A photograph might exist elsewhere in the project, remain unverified, be missing from an expected record, or be inaccessible to the recipient. Each situation needs a different response.
The following approach connects a selected deliverable to its source collection without assuming that either proves complete inspection coverage.
Define what this report is meant to show
Start with the report's purpose, recipient, project and revision. A report summarizing selected conditions has a different purpose from a complete photographic appendix. Make that scope clear enough that a later reviewer can understand why particular photographs appear.
Keep a usable source reference beside each important report image. It may be an existing media identifier, a meaningful filename or a reference supported by the team's established system. Pair it with enough location and subject context to distinguish similar-looking photographs.
The National Park Service's project-photograph procedure provides one concrete example: its photo log records project identifiers, date, photographer and subject. That is an agency procedure; the principle applied here is keeping an image identifiable when it moves into a report.
Also identify the source collection being checked. “The project photos” is too broad if the reviewer has opened only one folder, filtered date range or export. State what was reviewed and leave anything outside that scope unresolved.
Separate selection from missing evidence
Use precise language when a requested view does not appear in the deliverable.
Selected means the photograph is included in the identified report revision. It does not establish that the recipient can open its linked detail or that the report contains every relevant view.
Available but not selected means the team has found the source photograph and confirmed that it is outside that report. Its absence may reflect a deliberate editorial choice, but the reason still needs to come from the preparer or existing record.
Unverified means the review has not established whether the requested photograph exists. A search with no result is insufficient to conclude that nobody captured it.
Missing should describe a record known to have existed that cannot be located through its recorded source route. If the responsible inspector confirms that an expected view was never captured, record that specific fact instead.
Access is a separate question across these states. A selected photograph can exist in the source library while its recipient cannot reach it. Resolve the sharing or delivery issue without changing the factual description of the photograph's availability.
Follow one fictional report back to its source
Fictional editorial example: a team prepares inspection report IR-07, revision 2. The example below concerns three references only. It is not an ACM project, a Filio interface or a complete project inventory.
| Reference | What the reviewer has established | Relationship to IR-07, revision 2 | Next question |
|---|---|---|---|
| P-084 | A detail photograph of the west stair wall is identifiable in the source collection. | Selected as report item 4. | Can the recipient open the intended detail and read its context? |
| P-085 | A wider view of the same wall has been located and its subject confirmed. | Available in the source collection; not selected in this revision. | Would this wider view help explain item 4? |
| Request Q-12 | A reviewer has asked for an east stair landing overview. No matching source photograph has yet been verified in the collection checked. | No corresponding photograph has been identified in the report. | Was it captured elsewhere, outside the visit scope, or not captured? |
On a small screen, scroll the table horizontally to read every column.
P-085 is an available photograph omitted from this deliverable. Q-12 is an unanswered request. Calling both “missing photos” would hide the difference between a selection decision and an unresolved evidence question.
Suppose the client can open the report but cannot open P-084's linked detail. That is an access problem affecting a selected photograph. It does not establish that the source image has disappeared.
The review can now produce a specific next action: ask whether P-085 belongs in a revised report, resolve Q-12 with the responsible inspector, or correct the recipient's access to P-084. Keep those answers in the existing report or project review process. This small example does not certify the rest of the inspection record.
Check the route in both directions
Begin with one report item. Open the exact revision intended for the recipient, identify its source reference and find the corresponding media. Confirm the subject and context rather than relying on a similar thumbnail. A successful check should explain why this image supports this item.
Then begin with one known source photograph. Ask whether it appears in the selected report revision and, if so, where. If the system does not provide that relationship, check the report directly and retain a brief reference in the existing review record. This is a human comparison, not an assumed automatic report-membership function.
In Filio, the report creation procedure includes selecting media and reviewing order or removals before generation. The Pro Search guide explains separate Media and Report search modes. Those procedures support finding the relevant objects; the reviewer still has to establish the relationship being checked.
A change to report wording or presentation also needs attention. Filio's report-specific text, order and presentation edits do not change the underlying Media Record. Compare the actual report and source when their wording matters. The construction reporting feature overview provides the broader capability context.
On narrow screens, scroll this panel sideways if needed.
What ACM's published workflow demonstrates
The American Construction Monitoring and Services case study describes Angel Rodriguez adding photographs, tags and spoken descriptions during inspections. For a separate Texas assignment, he estimated capturing approximately 3,000 photographs during a six-hour field session. That is an attributed scale example, not a reporting-speed benchmark.
The case describes a horizontal four-photo report layout and a client request for one photograph per page. It also describes clients accessing fuller-resolution media from the selected report. It does not establish that recipients can browse the entire project library.
Angel still prepared a cover page in Word and combined files in Adobe. Personalized report templates were an opportunity for him to explore, not a step already eliminated from his process. AI descriptions also required review.
This supports the value of carrying context into report preparation. The fictional comparison above adds a separate editorial teaching method; it is not presented as an inclusion-and-exclusion record used by ACM.
Check the assembled file and the recipient's access
The final deliverable may pass through more than one application. A cover page, report export and additional attachment can become a combined PDF with a different page sequence.
Adobe's file-combination guidance explains that files and pages can be previewed and arranged before a combined PDF is created. The practical implication is to check the assembled version, including any page references that earlier material depends on.
Open the actual file or link intended for delivery. Confirm its project, revision and scope, then inspect a selected image, its description and its source reference. For a report exported from Filio, use the current download procedure and inspect the resulting file; do not assume every interactive behavior carries into every format.
Check access through the recipient's intended route and appropriate permissions. Opening a link successfully as its author does not answer whether the recipient can use it. Confirm what they can reach: the report, included media where supported, and any separately shared material.
The larger source collection can remain available to the authorized team under its existing access and retention arrangements. Sharing a selected deliverable does not establish unrestricted access to that collection.
Keep the next question answerable
Choose one upcoming report and ask a colleague to follow a selected image back to its source. Then test one relevant photograph that was not selected and one unresolved request. Ask them to describe the difference without help from the original preparer.
If the answer depends on memory, improve the reference or context at that point. If the evidence is unavailable, preserve the unresolved question and assign the next check through the team's existing process. Adding more images alone will not explain an unclear selection.
For the broader capture-to-report process, use Filio's construction field documentation workflow. This narrower check helps a report remain understandable after it leaves the person who assembled it.
Discuss your inspection reporting workflow with Filio. Bring a representative report and a permitted source sample so the discussion can focus on selection, retrieval and the recipient's actual experience.
