One source for all documents, and every decision about it.
The milestone went out as three zips across three emails. The site pulled a drawing off a shared drive that was already superseded. A dimension query left in an inbox that the next crew never saw.
And the sign-off that made it all contractual is somewhere in a sent-mail folder. Every document was there, none of it pointed back to a single source.
A document becomes a record through its history — where it went, what changed, who approved it.Easy access to the latest version of all available information is the most important advantage. That prevents errors and simplifies the records we need for quality assurance.
Document control is a chain-of-custody problem more than a filing one. Catenda Hub treats it that way: every document sits in a governed CDE, versioned and carried through review, discussion, and approval on the file itself.
Explore how document control, review and delivery work on a live CDE.
Get started10×.
Document control looks like admin, until the moment someone needs proof. Then the question is always the same: who got this, who changed it, who signed it, and can you show it. On most projects the answer is a search through shared drives, zip files and sent mail, reconstructed under contractual pressure months after the fact.
In Hub it's a byproduct of doing the work: every delivery, comment, markup and sign-off is recorded against the document and the revision it concerned, aligned to ISO 19650. Handover, an audit or a dispute becomes a lookup, not an investigation. Two of the moments where that shows up:
A milestone that went out as three zips in three inboxes becomes one collection, one link, and a record of who received what. When the client asks three months later whether a spec was in Friday's issue, it's a check, not a search through sent mail.
No shared-drive hunt, no stale local copy. Open the Published folder and the revision on screen is the one approved to build from, version state visible, so no crew pours concrete off a superseded drawing.
Everyone can find the information they need whenever they want, instead of searching for the latest versions of files in the attachments of numerous emails.
Document control lives in the Hub. Catenda AI sits on top of it to read the register for you so you find the right revision and see what changed without digging through folders.
The ISO 19650 CDE where every document lives. Control revisions, run transmittals and approvals, and keep one source of truth with the audit trail to prove who did what, and when.
The layer that reads the register for you, surfacing the document you need, summarising what changed between revisions, and flagging the approvals still waiting on someone.
Yes. Catenda Hub gives you the mechanisms ISO 19650 requires from a CDE - controlled information states, revisions, role-based access, formal approval workflows with full audit trail, federated coordination, and archiving. The standard governs process; Catenda provides the toolset to run it.
Approval workflows are configurable, serial, parallel or hybrid, with role-based reviewers and mandatory sign-off before anything publishes. Every transmittal is its own record: who sent what to whom, what was acknowledged, what was rejected and why. The audit log is tamper-evident and exportable.
Yes. External recipients join a transmittal or review through a magic link, no paid seat, no separate account to manage. Pricing is by project, so inviting everyone who touches the information costs nothing extra.
IFC, DWG, DGN, PDF and ZIP, with OCR-indexed full-text search. It connects to Revit, ArchiCAD, Tekla, Solibri, Bluebeam and more, plus a REST API and webhooks on every state change.
Every state change, approval and transmittal is time-stamped and immutable. When a project is contested, the timeline is already there, exportable to PDF, CSV or JSON, with acknowledgement receipts showing what each party saw and when.
Built by the people who shaped ISO 19650.
Bring your messiest register. That's it.
