CASE STUDIES › INFRASTRUCTURE
How Dynamic Engineering Connects Field Photos to Locations, Findings, and Repairs
Using Filio, Dynamic Engineering keeps high-volume field documentation connected to locations, observations, timing, and repair context – so the team can retrieve the right evidence and build reports that move from overview to action.
A field photo can be technically sharp and still be weak documentation. A close-up of corrosion, concrete spalling, or a roof anomaly may show the condition clearly, but if the reader cannot tell which unit, wall, column, or roof area it belongs to, the image has lost the context needed to act on it. Dynamic Engineering Design & Inspection uses Filio to preserve that missing context. By connecting field media with tags, geolocation, timestamps, observations, and report references, the team can manage hundreds of images without forcing engineers, contractors, or clients to reconstruct the story later.
Documentation-Heavy Engineering Work
Dynamic Engineering focuses on preserving and enhancing existing building envelopes through structural engineering, roof consulting, inspections, assessments, and related project services. Its Filio workflow is especially important in quality assurance, roof and structural assessments, field testing, claim support, and client reporting. For this case study, Junior Project Manager Anthony Gosner shared how the team uses Filio across documentation-heavy field work.
The volume can grow quickly. Anthony described more than 400 photos for a single report. Another project accumulated approximately 700 media files in about six weeks. By his estimate, he personally added more than 3,000 photos to Filio from the beginning of 2026 through the August interview. Each image may need to answer several questions later: What does it show? Where was it captured? When was it taken? Which observation does it support? What should happen next?
A Close-Up Can Lose Its Location
Anthony joined Dynamic Engineering shortly after the company began using Filio. Based on earlier reports he reviewed, the previous workflow relied on JPEG files inserted into documents, with important photos potentially spread across individual devices and Drive folders. That approach becomes fragile when the image is a tight detail. A photo may show a concrete spall or corroded railing while offering no dependable frame of reference for the repair location. After repeated site visits, the person reviewing the record may remember the condition but not the file name, date, folder, or device where the image was stored. Dynamic Engineering needed the location and meaning of each image to remain attached from the moment it was captured.
Capture Context While the Work Is Happening
Projects are typically prepared before the team reaches the site. Anthony begins with overview photos that establish the general area, then moves from broad conditions to increasingly detailed observations. Tags add structure to that sequence. For predictable work such as water testing, the team can prepare tags for known locations and procedures in advance. For roof or structural assessments, Anthony creates tags as conditions emerge. Establishing shared tags early also keeps team members from describing the same condition in different ways.
Timestamps document the start, required duration, and sequence of water tests. Geolocation preserves spatial context at the same time, reducing reliance on memory after a high-volume day in the field.
Reports That Move from Overview to Action
“It’s like you’re building a story with your photos,” Anthony explained.
Dynamic Engineering’s reports often begin with an overview, narrow to a specific location, and then show the detailed condition that supports the observation. Observation tables reference individual media numbers. If a row identifies corrosion on a railing, for example, the reader can locate the exact supporting photo in the Filio report.
Linked media lets the reader open a photo and zoom into a small detail while the report preserves the tag, location, and sequence that explain where it belongs. The same logic supports moisture surveys. A contractor can move from a roof overview to the location of an anomaly, review the detailed evidence, and use the accompanying exhibit to investigate the issue. Report formats can match the assignment: routine work may use two- or four-photo layouts, while detailed claim-support documentation may use a map, a plan view when available, and one image per page.
Redacted sample showing media references and the overview-to-detail reporting flow.
Unit-Level Tagging Connects Balcony Findings to Repairs
A condition assessment involving 186 balconies shows how this structure supports both complete documentation and selective communication. The team retains unit-specific photos without placing every image into one oversized client report. Representative conditions can appear in the main report, while the supporting record remains available when a specific unit needs review.
In the Balcony Condition Assessment workflow, Anthony creates tags for each unit and relates those tags to the repairs needed for that unit. The result is more than an archive of construction photos. It is a practical path from a building-wide assessment to the exact media and repair context associated with an individual unit.
High-Volume Records That Stay Searchable
Filio helps Dynamic Engineering preserve the complete record without turning the final deliverable into a photo dump. The team selects the images needed to explain a finding while keeping the remaining media available for later questions. Anthony described finding media by a remembered keyword even when he could not recall the observation title. He can also narrow records by date and return to project documentation from 2024. The larger the visual record becomes, the more valuable its structure is. Hundreds or thousands of images are useful only when the team can retrieve the right evidence and understand its context.
Less Manual Assembly, More Usable Information
Anthony estimated that manually inserting and organizing photos for a large report could take approximately one to two hours before observations were developed. With Filio, the media is already organized around the sequence and context of the inspection, reducing the manual assembly required during report preparation. Contractors have responded positively to the reporting pages because they can see what was observed, where the condition exists, and which image supports the finding. On occasional projects, contractors have also been given access so Dynamic Engineering can document the problem and the contractor can document the response. Anthony summarized the relationship simply: “Filio has been a really beneficial partner to us.”
More Project Context in One Environment
Dynamic Engineering also works with 360-degree captures and drone imagery, while LiDAR scanning and 3D mapping currently involve separate software. Anthony is interested in reducing the number of disconnected platforms required to understand a project. The customer need is clear: field teams benefit when more of the visual and spatial record can remain connected.
Conclusion
Dynamic Engineering’s experience shows that the challenge is not taking hundreds of field photos. It is preserving enough context around those photos that people can find, interpret, report, and act on them later. When location, tags, timing, observations, and report references remain connected, field photos become a searchable project record rather than a folder of disconnected files.
