Latista → Oracle Prime Field

A few problems came up consistently across sites.

The primary add-issue action was hard to find. Foremen had to hunt for it in the interface. The issue-creation form itself was too long to use during a walk. The file library kept every project drawing in one flat directory, so an electrical foreman had to scroll past four hundred plumbing and structural sheets to reach their own trade. The app had no concept of drawings organized by discipline.

Task distribution was worse, and it wasn't in the app at all. Every morning the general contractor printed the day's tasks on paper. Subcontractor foremen walked to the GC's trailer, picked up their sheet, and walked back out. The GC then walked the field again to track progress, took photos, and reconciled everything across three or four systems: Latista for issues, Primavera for the master schedule, another application for daily tasks, another for drawings. Files were spread across AWS, SharePoint, and email attachments. Most of the subcontractor foremen were native Spanish speakers. Most of them used Android phones. Most of them were not iPad users. They were being asked to reconcile all of that in their heads.

The final walk was its own problem. The general contractor, subcontractor, and owner walk the site together at the end of a phase. The owner calls out issues every few seconds and the subcontractor's rep takes notes on paper. Latista took about two minutes to log a single issue in that flow. A walk with sixty items meant either falling behind and dropping some, or logging them properly and losing the owner's attention.

Each of these became its own project. The four chapters below are the ones that shipped.