GoldnThread is not a maintenance tool with compliance bolted on. It is a record built around the four moments where building information usually breaks, and it is designed so that nothing crosses those moments without being captured.
The problem. Practical completion hands over a hard drive. Models nobody opens, warranties nobody indexes, an asset register that does not match the compliance schedule the council issued. Six months later the operations team is rebuilding the building's history from memory and invoices.
What GoldnThread does. Ingests IFC and JSON directly from the model. Maps assets to physical location, not just a floor number. Reconciles against the compliance schedule so you can see which specified systems have no record attached. Shows a completeness score you can hand back to the contractor before you sign off, while you still have leverage.
The outcome. The operations team inherits a building, not a folder.
The problem. A flat asset register is a list of nouns. It cannot tell you which of four identical air handling units failed, which riser serves it, or what the technician who attended in March actually found.
What GoldnThread does. Spatial capture using iPhone LiDAR: walk a plant room, capture it, tag assets in place, no survey crew. Full service history against the asset. Contractor coordination in one place. Offline first mobile for basements and plant rooms with no signal. IoT thresholds over LoRaWAN where sensors exist, attached to the same asset record.
The outcome. When something fails at 2am, the person who picks up the phone already knows what it is, where it is and what was last done to it.
The problem. A Building Warrant of Fitness falls due on the anniversary of the compliance schedule issue date, so every building in a portfolio runs on a different date. Each Form 12 requires a Form 12A from every IQP covering every specified system, and the council checks each IQP's registration. In Australia the artefact changes name, signatory, deadline and recipient at every state border.
What GoldnThread does. Tracks each specified system against the procedure written in that building's compliance schedule. Counts down to each building's own anniversary and escalates before it. Gives IQPs a direct portal to file Form 12As with the evidence attached. Holds the NSW AFSS, Victorian AESMR, Queensland Occupier's Statement and South Australian Form 3 in the same view.
The outcome. Certification stops being an annual scramble and becomes a status you can read.
The problem. The question always arrives at the worst moment. After an incident. During due diligence. When an insurer is deciding what to pay. And the answer usually lives in four inboxes, two shared drives and one person's memory.
What GoldnThread does. Every action is timestamped and attributed. Entries are appended, not overwritten. Export a full evidence pack for a system, a building or a portfolio in a form a lawyer or an auditor can read. Retention built for the requirement: NSW now sets a seven year minimum, and the record is held for the life of the building.
The outcome. An officer relying on the record can say they verified. That is the word the Act uses, and it is the word that matters.
We load one building. Its compliance schedule, its specified systems, its current certificate position, its asset register in whatever state it is in. You see the gaps immediately, which is uncomfortable and useful.
We bring in the rest of the portfolio, connect your contractors, and set the escalation rules so the right person hears about the right thing at the right time.
Spatial capture as buildings come up in the maintenance cycle. IQP portal access as certificates fall due. Nothing has to happen all at once, because the thread starts from wherever the building currently is.
Book thirty minutes. Bring one real building, with its real compliance schedule and its real mess.