How ANS Geo’s Filio workflow shows a better way to handle geotechnical photo documentation
Geotechnical teams do not usually lose time because they fail to capture photos. They lose time because those photos are hard to organize, hard to standardize, and hard to turn into report-ready documentation.
That is the most useful takeaway from Filio’s ANS Geo case study: the real bottleneck was not field capture itself, but the manual work that followed it.
ANS Geo is a geotechnical, civil, and structural engineering firm that works across multiple offices. According to the case study, the team was dealing with a large volume of field photos from activities like soil borings, test pits, and field logging. Before Filio, those images lived on individual phones, which made the documentation process fragmented and difficult to manage.
For engineering teams, that pattern is common:
- photos are captured in the field
- files land in personal camera rolls
- someone later has to sort, resize, rotate, annotate, and format them
- report production becomes a separate manual task
In ANS Geo’s workflow, one photo could take 20 to 30 minutes of manual preparation, and sometimes longer. The case study describes that as a poor use of highly trained engineering time, which is exactly the point many documentation systems miss.
The workflow lesson: reduce the number of steps between capture and report
ANS Geo chose Filio because the platform fit the way its team already worked. The company needed a system that could organize visual assets, keep project records consistent, and make report preparation faster without forcing people to rebuild their entire process.
What stands out here is not just speed. It is structure.
Filio was used to streamline photo logging and create more consistent photo logs across a growing, multi-office engineering organization. The case study also notes that implementation was straightforward: ANS Geo introduced the platform in a one-hour team call, then used Filio support to resolve early setup issues quickly.
That kind of onboarding matters because documentation tools fail when teams cannot adopt them quickly enough. A platform may be technically capable, but if it is cumbersome to roll out, field teams often fall back to the same old habits.
Why this matters for geotechnical documentation
Geotechnical work often depends on detailed visual records that need to stay tied to the project context. When the photos are scattered, report production slows down and consistency suffers.
ANS Geo’s case study suggests a more practical approach:
- Capture field photos in a workflow designed for project documentation.
- Keep them organized instead of storing them only on individual devices.
- Standardize photo logs so teams across offices use the same format.
- Reduce repetitive formatting work so engineers can spend more time on technical review.
The result described in the case study is a major reduction in time spent on photo logging, along with faster report delivery and more consistent documentation.
A useful pattern for other engineering teams
If your team handles large volumes of field imagery, the ANS Geo case study is worth reading as a workflow example. It shows how documentation improves when the system is built around the actual path from field capture to client-ready reporting.
That is especially relevant for teams that need to coordinate across offices, keep records uniform, and avoid turning engineering staff into photo editors.
Read the full case study here: ANS Geo Case Study: How Filio Streamlined Geotechnical Photo Documentation
Canonical: https://www.filio.io/case-studies/filio-case-study-ans-geo-inc-engineering-project
Related Filio resources:
Top comments (0)