At the start of my 2017 conversation with Jordan Williams, I named long-lead concerns from recent projects: fire-rated doors, sinks coming from China, and tile coming from Italy. Ordering early had not removed the need for calls, emails, and follow-up about arrival and condition.
The practical question was not whether the project could store more data. It was what the owner could verify as a material moved from an order to a shipment, a receipt, a location, and eventually a payment.
Shipped is not the same as received
Jordan Williams described a familiar gap. A vendor may say an item shipped because the purchase order shows that it was supposed to ship. A transaction history can tell a different and more useful story by recording when the item moved, when it arrived, when the receipt was processed, and whether it had been issued for use.
That distinction changes the next conversation. The team can work from recorded events instead of treating a planned date as proof that the material completed the hand-off.
A useful location has to work in the map and in the yard
Jordan Williams explained that SightSense kept two descriptions of location. The system could capture latitude and longitude, and it could also use the language a crew would recognize, such as a warehouse, section, bin, laydown area, or bunk number.
Both descriptions matter for different reasons. Coordinates support the map. A familiar site location helps the person retrieving the material know where to walk and what to look for.
Jordan described the two-location design simply: “we keep the best of both worlds.”
A photograph can make the receipt usable later
Jordan also described photographs becoming part of the receipt record. A picture could show the truck, the box, the item inside, or the material itself. Those images helped later users identify what they were trying to find without relying only on markings.
The field event comes before the shared record
In Jordan Williams's example, the mobile workflow could scan an identifier, compare quantities, note visible damage, capture location, and record who completed the activity. A second person could review the receipt before it was posted when the project used that control.
The transaction layer then connected purchase order, shipment, receipt, acceptance, and payment events in sequence. The two layers have different jobs. Sensors and mobile tools capture what happened in the field. The transaction history preserves how those events connect.
A shared ledger cannot repair a missing receipt, an unreadable tag, or a condition nobody recorded. Trust in the sequence begins with a field event the project can recognize and review.
Procurement decides whether the hand-off can be read
Jordan Williams gave a specific warning about RFID tags. A supplier could meet a broad requirement to add a tag and still use a type that the project's readers could not recognize. The tag would be present, but it would not help the tracking workflow.
His response was to define the details during procurement. The bid documents could identify the tag or barcode type, placement, quantity, electronic file format, and transfer method. Vendors could then include the requirement in their bids and prepare to use the same hand-off rules as the project team.
Before the next bid for one material package, define the identifier the supplier will attach, the proof the field team will capture at shipment, receipt, and acceptance, and the format used to transfer that information. Make the receipt review and final payment posting visible in the same workflow. Jordan's examples kept a person at both points: an administrator could review the receipt before it was posted, and someone could make the final payment posting. If the current process is on paper, the first step can be a standardized electronic handover rather than a full blockchain implementation.
Material tracking becomes more useful when the supplier, field team, and owner can recognize the same hand-off. Standardization strengthens that connection because the evidence arrives in a form people and systems can read, while receipt review and final payment posting remain visible human checks.
