The problem isn't your documents. It's how the software thinks about them.
Every major document control tool in AEC was built the same way: fixed objects, fixed forms, fixed modules. A Submittal is a Submittal. An RFI is an RFI. A Drawing is a Drawing. Each lives in its own silo. You can't relate them cleanly. You can't extend them without the vendor building something new — and charging for it.
That model made sense twenty years ago. It doesn't make sense now.
Documents are Records — not files.
Tracta is built around a different idea: every meaningful object in a project is a Record.
A Document is a Record. A Transmittal is a Record. A Package, a Contact, a Company — all Records. Each Record Type has its own Fields, its own lifecycle, and native connections to every other Record in the project.
When you upload a drawing, Tracta doesn't just store a file. It creates a Document Record — with System Fields extracted automatically (document number, revision, discipline, date, status) and Custom Fields your team defines. Every Revision is tracked within that Document's history. Every Transmittal that carries it is a linked Record in its own right.
Nothing lives in a silo. Everything is connected.
The audit trail isn't a feature. It's built in.
In traditional AEC software, the audit trail is an afterthought — a log table, a PDF export, a compliance module you pay extra for.
In Tracta, traceability is native to every Record. Every status change is logged. Every Transmittal is a permanent record of what was sent, to whom, when, and what action was required. Every Workflow step has a timestamp and an owner. The Register for any Record Type is always current — no manual reconciliation.
When a project goes wrong — and they do — the question isn't whether you have records. It's whether you can find them, trust them, and present them clearly. Tracta is built to answer that question on every project, without anyone having to think about it.
Why AI makes this possible now.
Flexible data models aren't new. The reason they failed in the past is simple: someone had to fill them in. If every Document Record has fifteen Fields, manual data entry is painful enough that people skip it, corrupt it, or abandon the system.
Tracta uses AI to extract and populate System Fields automatically — from the documents themselves. Upload a PDF and Tracta reads it: document number, Revision, title, discipline, date, status. The Schema gets built as a byproduct of the work, not as extra overhead on top of it.
That's a genuinely new unlock. And it's why a flexible, practitioner-grade system is possible now when it wasn't five years ago.
Built for practitioners. Not for enterprise procurement.
Procore, Aconex, Newforma — they're built for large organisations with dedicated document controllers, IT teams, and implementation budgets. Their flexibility ends at the module list the vendor decided to build.
Tracta is built for the engineers, project managers, and document controllers who actually live with the problem. Flexible enough to match how your project is structured — your Record Types, your Fields, your Schema. Opinionated enough to not require a consultant to configure it. And priced for firms that don't have a six-figure software budget.
One pattern. Every object. Always.
Every object in Tracta — Documents, Packages, Transmittals, Contacts, Companies — follows the same Record model. As the product grows, every new Record Type (RFIs, inspections, tasks, whatever comes next) will follow the same pattern.
One consistent way to understand, relate, and trace everything in a project. That's the bet.