Curated directory of Field & Mobile software for AEC teams. 82 published tools.
Field and mobile tools exist because the authoritative model rarely lives where the work happens. Superintendents, inspectors, and trade partners need fast capture, offline tolerance, and simple publishing back to the office. Good products reduce duplicate entry, attach media to the right location or asset, and respect permissions so subcontractors only see their scope. When you compare options, test battery use, camera workflows, and how well the app syncs after a dead zone. Ask whether templates match your daily report format, whether you can lock signoffs, and how exports land in your project management or Common Data Environment. If you run lean IT on site, favor vendors with clear device support and MDM guidance. This category groups mobile experiences across quality, safety, logistics, and simple model viewers. Use it to shortlist products that fit your site culture, then validate training time with a crew lead before you scale licenses.
Offline should queue forms, photos, and markups with clear sync status once connectivity returns. Ask how conflicts resolve if two people edit the same item. Confirm whether attachments compress automatically and whether GPS metadata is optional for privacy sensitive sites. Pilot on a live slab pour or envelope inspection where signal is weak so you learn real limits before rollout.
Connections vary from lightweight PDF exports to deep APIs into Procore, Autodesk Construction Cloud, or custom data warehouses. Map the golden thread for your pilot: who publishes locations, who consumes issues, and what closes a loop in the schedule of values. If integration is email based, expect drift. Prefer systems that write back IDs your coordination team can trace in the model or in the PM log.
Photos can leak signage, badges, or neighbor properties. Set policies on face blurring, retention windows, and gallery access by role. Confirm whether media stays in your tenant and whether share links expire. For government work, verify FedRAMP or equivalent attestations if required. Train crews on what never belongs in a jobsite stream.
All in one suites reduce vendor count but can be heavier on small projects. Focused apps win when they solve one workflow extremely well, such as trench inspections or facade punch. Decide based on portfolio scale, internal integration capacity, and whether you need a single support throat to call. Hybrid stacks are normal if APIs are solid.
Track time from observation to recorded corrective action, percentage of issues with photos, and reopen rates after verification. Pair quantitative metrics with superintendent interviews so you catch usability friction early.
Use listings to compare categories and pricing signals, then run your standard vendor security and onboarding steps. The hub speeds discovery; your governance still owns final selection.
